From mailnull@www1.ietf.org  Wed Jan  1 01:50:56 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 BAA06755
	for <sigtran-archive@odin.ietf.org>; Wed, 1 Jan 2003 01:50:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h016wah03668
	for sigtran-archive@odin.ietf.org; Wed, 1 Jan 2003 01:58:36 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h016w2J03653;
	Wed, 1 Jan 2003 01:58:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h016t6J03596
	for <sigtran@optimus.ietf.org>; Wed, 1 Jan 2003 01:55:06 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06690
	for <sigtran@ietf.org>; Wed, 1 Jan 2003 01:46:55 -0500 (EST)
Received: from axsppc44 (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with SMTP id h016o2aN001391;
	Wed, 1 Jan 2003 00:50:03 -0600 (CST)
Message-ID: <0bab01c2b162$b6c6abe0$5e01ff0a@axsppc44>
From: "S Magesh" <magesh.shanmugam@alcatel.com>
To: <bidulock@openss7.org>
Cc: <sigtran@ietf.org>
References: <OE45nzNwRC6HixqDCZx00000a10@hotmail.com> <070401c2afcb$d6788640$5e01ff0a@axsppc44> <OE43UnIzJFucppbSvAK0000378c@hotmail.com> <071801c2afcd$e9218600$5e01ff0a@axsppc44> <OE649tMTF4ia5wAz8AW00006661@hotmail.com> <OE59brr0jI8fL9cNZxS0000da7b@hotm <20021230012914.A7172@openss7.org> <007601c2b006$44d07640$7501ff0a@axsppc67> <20021230132301.B20504@openss7.org> <00b101c2b087$58743700$7501ff0a@axsppc67> <20021230223226.A32746@openss7.org>
Date: Wed, 1 Jan 2003 12:25:02 +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.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] Contradiction between M2PA RFC Draft Version 6 and M2PA RFC Test Specification Draft Version 02
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

Brian,

In M2PA RFC Draft Version 6, Section 4.1.3 Para 4, Sentence "If M2PA has not
already received the Link Status Alignment message from its peer, then M2PA
starts timer T1" and Para 5, Sentence "M2PA stops timer T1 when it has
received the Link Status Alignment message from its peer".

Above two sentences CONFLICTS with Section 3.1.3 and Section 3.1.4 of M2PA
Test Specification Draft Version 02, which talks about Timers T3 (ALIGNED)
and T1 (ALIGNED READY).

Thanks

S Magesh





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



From mailnull@www1.ietf.org  Wed Jan  1 03:50: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 DAA01484
	for <sigtran-archive@odin.ietf.org>; Wed, 1 Jan 2003 03:50:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h018vrG19851
	for sigtran-archive@odin.ietf.org; Wed, 1 Jan 2003 03:57:53 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h018vVJ19838;
	Wed, 1 Jan 2003 03:57:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h018uRJ19821
	for <sigtran@optimus.ietf.org>; Wed, 1 Jan 2003 03:56:27 -0500
Received: from gw.openss7.com (IDENT:QP7UCh3edoU2az8BfhwBhq7OM6OxQseh@gw.openss7.com [142.179.199.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01430
	for <sigtran@ietf.org>; Wed, 1 Jan 2003 03:48:09 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:3yBrSjJBNQStBIMnn4e85yGLaKDqs2uB@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h018mil09720;
	Wed, 1 Jan 2003 01:48:44 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h018miS02374;
	Wed, 1 Jan 2003 01:48:44 -0700
Date: Wed, 1 Jan 2003 01:48:44 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: S Magesh <magesh.shanmugam@alcatel.com>
Cc: sigtran@ietf.org
Message-ID: <20030101014844.A2362@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: S Magesh <magesh.shanmugam@alcatel.com>, sigtran@ietf.org
References: <OE43UnIzJFucppbSvAK0000378c@hotmail.com> <071801c2afcd$e9218600$5e01ff0a@axsppc44> <OE649tMTF4ia5wAz8AW00006661@hotmail.com> <OE59brr0jI8fL9cNZxS0000da7b@hotm <20021230012914.A7172@openss7.org> <007601c2b006$44d07640$7501ff0a@axsppc67> <20021230132301.B20504@openss7.org> <00b101c2b087$58743700$7501ff0a@axsppc67> <20021230223226.A32746@openss7.org> <0bab01c2b162$b6c6abe0$5e01ff0a@axsppc44>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <0bab01c2b162$b6c6abe0$5e01ff0a@axsppc44>; from magesh.shanmugam@alcatel.com on Wed, Jan 01, 2003 at 12:25:02PM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: Contradiction between M2PA RFC Draft Version 6 and M2PA RFC Test Specification Draft Version 02
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>

S,

Timer names will be corrected in M2PA Draft 7.

--brian

S Magesh wrote:                                 (Wed, 01 Jan 2003 12:25:02)
> Brian,
> 
> In M2PA RFC Draft Version 6, Section 4.1.3 Para 4, Sentence "If M2PA has not
> already received the Link Status Alignment message from its peer, then M2PA
> starts timer T1" and Para 5, Sentence "M2PA stops timer T1 when it has
> received the Link Status Alignment message from its peer".
> 
> Above two sentences CONFLICTS with Section 3.1.3 and Section 3.1.4 of M2PA
> Test Specification Draft Version 02, which talks about Timers T3 (ALIGNED)
> and T1 (ALIGNED READY).
> 
> Thanks
> 
> S Magesh
> 
> 
> 
> 

-- 
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 Jan  1 07:48: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 HAA03511
	for <sigtran-archive@odin.ietf.org>; Wed, 1 Jan 2003 07:48:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h01Cu0j29686
	for sigtran-archive@odin.ietf.org; Wed, 1 Jan 2003 07:56:00 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h01CtbJ29670;
	Wed, 1 Jan 2003 07:55:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h01CssJ29642
	for <sigtran@optimus.ietf.org>; Wed, 1 Jan 2003 07:54:54 -0500
Received: from web12807.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA03495
	for <sigtran@ietf.org>; Wed, 1 Jan 2003 07:46:35 -0500 (EST)
Message-ID: <20030101124945.50896.qmail@web12807.mail.yahoo.com>
Received: from [62.29.77.120] by web12807.mail.yahoo.com via HTTP; Wed, 01 Jan 2003 04:49:45 PST
Date: Wed, 1 Jan 2003 04:49:45 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Routing Key
To: sigtran@ietf.org
In-Reply-To: <20021231150113.A23158@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,
> > > Chak,
> > > 
> > > I said that M3UA does not *_register_* SCCP
> users.  M3UA makes no
> > > restrictions on what is used as a static routing
> key.  SSN and TID were
> > > removed from the M3UA Routing Key parameter
> because M3UA does not support
> > > SCCP or TCAP users.  To support SCCP properly
> would require doing most of
> > > the things that SUA already does.
> > > 
> > > CIC is included in the M3UA Routing Key, and
> yet, M3UA has little to no
> > > support for ISUP as anything but an MTP-User. 
> The only reason for leaving
> > > CIC was the lack of an ISUP-UA.
> > > 
> > > There is a long thread from July/Aug 2001, which
> was M3UA Issue 6 at Last
> > > Call entitled:
> > > 
> > > 	"M3UAv8: SSN in Routing Key and TCAP TID in
> example."
> > > 
> > > Concensus was to remove SSN and TID from routing
> (both examples and
> > > Routing Key parameter).  It looks like it was
> never properly removed from
> > > the examples.
> > > 
> > > I would propose that the M3UA IG say that
> > > 
> > >    "Although it is provided in several examples,
> routing keys based on SSN
> > >    is not supported by M3UA."
> > [TOLGA]Although I agree that M3UA is not very
> suitable for SSN based RKs,
> > still such a sentence would contradict with the
> statement that there is no
> > limit/restriction for RKs. If somebody can/want
> support SSN based RKs(or
> > something else) IMO they should be free to do so.
> 
> They are also free to invent their own private
> protocol, and that's what
> they'll be doing.
> 
> Unlimited routing keys and interoperability are at
> cross purposes.   It was
> agreed that M3UA routing keys should stick to MTP3
> information with the
> possible exception of CIC for ISUP/TUP (which in
> some cases overlaps with SLS
> anyway).
> 
> More embellishments of routing key will only result
> in proprietary
> implementations that don't interoperate.  The IETF
> doesn't waste its time on
> such stuff.
[TOLGA] If a node supports this just by itself -with
no additional requirement to the on the wire
protocol/procedures-, IMO this should be allowed, and
there is no need to add anything to the existing M3UA
documents. 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Wed Jan  1 09:30: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 JAA05523
	for <sigtran-archive@odin.ietf.org>; Wed, 1 Jan 2003 09:30:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h01Ecgb17674
	for sigtran-archive@odin.ietf.org; Wed, 1 Jan 2003 09:38:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h01EcKJ17551;
	Wed, 1 Jan 2003 09:38:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h01EbxJ17035
	for <sigtran@optimus.ietf.org>; Wed, 1 Jan 2003 09:37:59 -0500
Received: from gw.openss7.com (IDENT:grNieU0qKrY3a2wjQ5j96fiWtx3NxbVH@gw.openss7.com [142.179.199.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05435
	for <sigtran@ietf.org>; Wed, 1 Jan 2003 09:29:38 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:+5DfhVPVkuDyIHTMbvvnG78fiPHBCQTK@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h01D0Fl17628;
	Wed, 1 Jan 2003 06:00:15 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h01D0E705967;
	Wed, 1 Jan 2003 06:00:14 -0700
Date: Wed, 1 Jan 2003 06:00:14 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Routing Key
Message-ID: <20030101060014.B5900@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20021231150113.A23158@openss7.org> <20030101124945.50896.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: <20030101124945.50896.qmail@web12807.mail.yahoo.com>; from tolga_asveren@yahoo.com on Wed, Jan 01, 2003 at 04:49:45AM -0800
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, 01 Jan 2003 04:49:45)
> > 
> > They are also free to invent their own private protocol, and that's what
> > they'll be doing.
> > 
> > Unlimited routing keys and interoperability are at cross purposes.   It
> > was agreed that M3UA routing keys should stick to MTP3 information with
> > the possible exception of CIC for ISUP/TUP (which in some cases overlaps
> > with SLS anyway).
> > 
> > More embellishments of routing key will only result in proprietary
> > implementations that don't interoperate.  The IETF doesn't waste its time
> > on such stuff.
> [TOLGA] If a node supports this just by itself -with no additional
> requirement to the on the wire protocol/procedures-, IMO this should be
> allowed, and there is no need to add anything to the existing M3UA
> documents. 

But that is not the case with SSN in Routing Keys.  It is also not the
case for CIC for that matter.

--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  Wed Jan  1 16:17: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 QAA13819
	for <sigtran-archive@odin.ietf.org>; Wed, 1 Jan 2003 16:17:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h01LP0h25164
	for sigtran-archive@odin.ietf.org; Wed, 1 Jan 2003 16:25:00 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h01LNxJ25124;
	Wed, 1 Jan 2003 16:24:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h01LMvJ25103
	for <sigtran@optimus.ietf.org>; Wed, 1 Jan 2003 16:22:57 -0500
Received: from web12803.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA13792
	for <sigtran@ietf.org>; Wed, 1 Jan 2003 16:14:29 -0500 (EST)
Message-ID: <20030101211739.22367.qmail@web12803.mail.yahoo.com>
Received: from [62.29.65.150] by web12803.mail.yahoo.com via HTTP; Wed, 01 Jan 2003 13:17:39 PST
Date: Wed, 1 Jan 2003 13:17:39 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Routing Key
To: sigtran@ietf.org
In-Reply-To: <20030101060014.B5900@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,
> > > They are also free to invent their own private
> protocol, and that's what
> > > they'll be doing.
> > > 
> > > Unlimited routing keys and interoperability are
> at cross purposes.   It
> > > was agreed that M3UA routing keys should stick
> to MTP3 information with
> > > the possible exception of CIC for ISUP/TUP
> (which in some cases overlaps
> > > with SLS anyway).
> > > 
> > > More embellishments of routing key will only
> result in proprietary
> > > implementations that don't interoperate.  The
> IETF doesn't waste its time
> > > on such stuff.
> > [TOLGA] If a node supports this just by itself
> -with no additional
> > requirement to the on the wire
> protocol/procedures-, IMO this should be
> > allowed, and there is no need to add anything to
> the existing M3UA
> > documents. 
> 
> But that is not the case with SSN in Routing Keys. 
> It is also not the
> case for CIC for that matter.
[TOLGA] Why? I would expect that necessary changes on
a SG to support SSN based routing is, to
filter/regenerate/imitate some SCCP management
messages. Those changes, I would consider as changes
to NIF not to the on the wire M3UA protocol. 

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Wed Jan  1 17:27: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 RAA14483
	for <sigtran-archive@odin.ietf.org>; Wed, 1 Jan 2003 17:27:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h01MZFm28428
	for sigtran-archive@odin.ietf.org; Wed, 1 Jan 2003 17:35:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h01MYqJ28412;
	Wed, 1 Jan 2003 17:34:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h01MXTJ28371
	for <sigtran@optimus.ietf.org>; Wed, 1 Jan 2003 17:33:29 -0500
Received: from gw.openss7.com (IDENT:lV76mTzaTDohM55Yy/uRG5F3fUHvpKoD@gw.openss7.com [142.179.199.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14212
	for <sigtran@ietf.org>; Wed, 1 Jan 2003 16:59:35 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:rMOMKhc9ZwEfvewyzbEJ64TiIVzS4uyc@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h01M0cl24668;
	Wed, 1 Jan 2003 15:00:38 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h01M0ar14562;
	Wed, 1 Jan 2003 15:00:36 -0700
Date: Wed, 1 Jan 2003 15:00:35 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Routing Key
Message-ID: <20030101150035.A14470@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030101060014.B5900@openss7.org> <20030101211739.22367.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: <20030101211739.22367.qmail@web12803.mail.yahoo.com>; from tolga_asveren@yahoo.com on Wed, Jan 01, 2003 at 01:17:39PM -0800
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, 01 Jan 2003 13:17:39)
> [TOLGA] Why? I would expect that necessary changes on a SG to support SSN
> based routing is, to filter/regenerate/imitate some SCCP management
> messages. Those changes, I would consider as changes to NIF not to the on
> the wire M3UA protocol. 

Read the thread.

--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  Thu Jan  2 06:09:52 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 GAA02743
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 06:09:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02BI6J13795
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 06:18:06 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02BGlJ13725;
	Thu, 2 Jan 2003 06:16:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02BEfJ13625
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 06:14:41 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02706
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 06:05:56 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h02B96aN001994;
	Thu, 2 Jan 2003 05:09:06 -0600 (CST)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h02B8fM18025;
	Thu, 2 Jan 2003 05:08:41 -0600 (CST)
Date: Thu, 2 Jan 2003 05:08:41 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
In-Reply-To: <20021223063159.A8878@openss7.org>
Message-ID: <Pine.SOL.4.10.10301020445160.23295-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sigtran] [M3UA]1 AS and 1 ASP
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,

 Suppose an AS has single ASP and wants to connect to SGP1
and SGP2 for the same RK1.

  
+---------+                                 +-----+
|+------+ |          RK1      SCTP1         | ASP |
|| SGP1 |-|---------------------------------+-----+
|+------+ |                                    |
|         |                                    |
|+------+ |          RK1      SCTP2            |
|| SGP2 |-|------------------------------------+
|+------+ |
+---------+ 

Does REG procedures at SGP allow this kind of scenario?

This kind of scenario may be required in case SGP1 goes down 
still ASP can deliver messages via SGP2.

--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 mailnull@www1.ietf.org  Thu Jan  2 06:49: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 GAA03074
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 06:49:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02BvgV16139
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 06:57:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02BvEJ16100;
	Thu, 2 Jan 2003 06:57:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02BuFJ16065
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 06:56:15 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03044
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 06:47:28 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:A+XJ9Lwv4viaB/CiBYPPdww3vA9txLEV@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02BODl12620;
	Thu, 2 Jan 2003 04:24:13 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02BOCB01173;
	Thu, 2 Jan 2003 04:24:12 -0700
Date: Thu, 2 Jan 2003 04:24:12 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Message-ID: <20030102042412.A1077@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20021223063159.A8878@openss7.org> <Pine.SOL.4.10.10301020445160.23295-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.10301020445160.23295-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Thu, Jan 02, 2003 at 05:08:41AM -0600
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: [M3UA]1 AS and 1 ASP
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,

Yes, all the SS7 UAs support this.  The ASP registers once each with SGP1
and SGP2.

--brian

Samuel Dur D. Jeyaseelan wrote:                  (Thu, 02 Jan 2003 05:08:41)
> 
> Hi,
> 
>  Suppose an AS has single ASP and wants to connect to SGP1
> and SGP2 for the same RK1.
> 
>   
> +---------+                                 +-----+
> |+------+ |          RK1      SCTP1         | ASP |
> || SGP1 |-|---------------------------------+-----+
> |+------+ |                                    |
> |         |                                    |
> |+------+ |          RK1      SCTP2            |
> || SGP2 |-|------------------------------------+
> |+------+ |
> +---------+ 
> 
> Does REG procedures at SGP allow this kind of scenario?
> 
> This kind of scenario may be required in case SGP1 goes down 
> still ASP can deliver messages via SGP2.
> 
> --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. *******
> 

-- 
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 Jan  2 06:50:23 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 GAA03099
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 06:50:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02Bwcc16208
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 06:58:38 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02Bw3J16175;
	Thu, 2 Jan 2003 06:58:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02BvnJ16155
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 06:57:49 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03070
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 06:49:02 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h02BqDaN004165;
	Thu, 2 Jan 2003 05:52:13 -0600 (CST)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h02BpTM01124;
	Thu, 2 Jan 2003 05:51:29 -0600 (CST)
Date: Thu, 2 Jan 2003 05:51:29 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
In-Reply-To: <20030102042412.A1077@openss7.org>
Message-ID: <Pine.SOL.4.10.10301020550010.23295-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sigtran] Re: [M3UA]1 AS and 1 ASP
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,

For RK1 ,Will SGP1 and SGP2 return same RC?

-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, 2 Jan 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> Yes, all the SS7 UAs support this.  The ASP registers once each with SGP1
> and SGP2.
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                  (Thu, 02 Jan 2003 05:08:41)
> > 
> > Hi,
> > 
> >  Suppose an AS has single ASP and wants to connect to SGP1
> > and SGP2 for the same RK1.
> > 
> >   
> > +---------+                                 +-----+
> > |+------+ |          RK1      SCTP1         | ASP |
> > || SGP1 |-|---------------------------------+-----+
> > |+------+ |                                    |
> > |         |                                    |
> > |+------+ |          RK1      SCTP2            |
> > || SGP2 |-|------------------------------------+
> > |+------+ |
> > +---------+ 
> > 
> > Does REG procedures at SGP allow this kind of scenario?
> > 
> > This kind of scenario may be required in case SGP1 goes down 
> > still ASP can deliver messages via SGP2.
> > 
> > --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. *******
> > 
> 
> -- 
> 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 Jan  2 06:51: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 GAA03122
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 06:51:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02BxI616259
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 06:59:18 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02Bx5J16247;
	Thu, 2 Jan 2003 06:59:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02BwSJ16200
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 06:58:28 -0500
Received: from hermes.fm.intel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03091
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 06:49:42 -0500 (EST)
Received: from petasus.fm.intel.com (petasus.fm.intel.com [10.1.192.37])
	by hermes.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id h02BoRT00287
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 11:50:27 GMT
Received: from fmsmsxvs041.fm.intel.com (fmsmsxvs041.fm.intel.com [132.233.42.126])
	by petasus.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.27 2002/10/16 23:46:59 dmccart Exp $) with SMTP id h02Bm8a24376
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 11:48:08 GMT
Received: from FMSMSX017.fm.intel.com ([132.233.42.196])
 by fmsmsxvs041.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2003010203505906945
 ; Thu, 02 Jan 2003 03:50:59 -0800
Received: by fmsmsx017.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <V97F3X5F>; Thu, 2 Jan 2003 03:52:52 -0800
Message-ID: <12B638FEE763F74696D8544752E7204802C478DF@bgsmsx101.iind.intel.com>
From: "Nagar, Ashish" <ashish.nagar@intel.com>
To: "'Tolga Asveren'" <tolga_asveren@yahoo.com>,
        "'Brian F. G. Bidulock'"
	 <bidulock@openss7.org>
Cc: sigtran@ietf.org
Subject:  [Sigtran] M3UA - ASP UP and ASP DN in Double Exchange
Date: Thu, 2 Jan 2003 03:47:32 -0800 
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/Tolga

    From section 5.5.2 (Double Exchange) of M3UA RFC 
    "only one single exchange of ASP Up 
    message can be considered as enough since the response by the other 
    peer can be considered as a notice that it is in ASP_UP state"

    My point is because it is a double ended mode this message should come 
    from both the side. There is no point in keeping ASP UP and ASP DN 
    from another end as optional. This I am asking just for the sake of 
    similarity with ASP AC and ASP IA message and also its behavior will be
same as 
    the name implies (Double Exchange).

    So my suggestion is to change ASP UP and ASP DN as mandatory.

    I know that ASP AC / ASPIA contains RC.

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



From mailnull@www1.ietf.org  Thu Jan  2 07:15: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 HAA03459
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 07:15:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02CO1f18080
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 07:24:01 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02CNRJ18058;
	Thu, 2 Jan 2003 07:23:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02CM1J18003
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 07:22:01 -0500
Received: from gw.openss7.com (IDENT:U2752yaPCxXRcr8BFBlIiK9fbbGxdf+r@gw.openss7.com [142.179.199.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03447
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 07:12:57 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:noAw0y6AhtWLcdOBlLPBNbS2HrqlFBxu@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02BwPl13612;
	Thu, 2 Jan 2003 04:58:25 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02BwP102517;
	Thu, 2 Jan 2003 04:58:25 -0700
Date: Thu, 2 Jan 2003 04:58:25 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Nagar, Ashish" <ashish.nagar@intel.com>
Cc: "'Tolga Asveren'" <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA - ASP UP and ASP DN in Double Exchange
Message-ID: <20030102045825.B2482@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Nagar, Ashish" <ashish.nagar@intel.com>,
	'Tolga Asveren' <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <12B638FEE763F74696D8544752E7204802C478DF@bgsmsx101.iind.intel.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: <12B638FEE763F74696D8544752E7204802C478DF@bgsmsx101.iind.intel.com>; from ashish.nagar@intel.com on Thu, Jan 02, 2003 at 03:47:32AM -0800
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>

Ashish,

Sorry, the concensus was to leave ASPUP/DN (ACK) single ended.

Certainly the IPSP which sends ASPUP ACK has an available local M3UA layer.
Also, whether an IPSP sends ASPDN ACK or ASPDN, the entire relation is down.

There is no need to change it just to make it like ASPAC/IA (ACK).

--brian

Nagar, Ashish wrote:                                 (Thu, 02 Jan 2003 03:47:32)
> Hi Brian/Tolga
> 
>     From section 5.5.2 (Double Exchange) of M3UA RFC 
>     "only one single exchange of ASP Up 
>     message can be considered as enough since the response by the other 
>     peer can be considered as a notice that it is in ASP_UP state"
> 
>     My point is because it is a double ended mode this message should come 
>     from both the side. There is no point in keeping ASP UP and ASP DN 
>     from another end as optional. This I am asking just for the sake of 
>     similarity with ASP AC and ASP IA message and also its behavior will be
> same as 
>     the name implies (Double Exchange).
> 
>     So my suggestion is to change ASP UP and ASP DN as mandatory.
> 
>     I know that ASP AC / ASPIA contains RC.
> 
> Regards
> Ashish
>      

-- 
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 Jan  2 07:54:25 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 HAA03843
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 07:54:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02D2gi20144
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 08:02:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02D2DJ20120;
	Thu, 2 Jan 2003 08:02:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02D20J20089
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 08:02:00 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03833
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 07:52:15 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:/Ju5HqkHtiDvzQ3q9FVH3ny9MmWJyl7S@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02CtBl15334;
	Thu, 2 Jan 2003 05:55:11 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02BtAo02503;
	Thu, 2 Jan 2003 04:55:10 -0700
Date: Thu, 2 Jan 2003 04:55:10 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Message-ID: <20030102045510.A2482@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030102042412.A1077@openss7.org> <Pine.SOL.4.10.10301020550010.23295-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.10301020550010.23295-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Thu, Jan 02, 2003 at 05:51:29AM -0600
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: [M3UA]1 AS and 1 ASP
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,

Not necessarily.  They SHOULD return the same RC value.

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 02 Jan 2003 05:51:29)
> 
> Brian,
> 
> For RK1 ,Will SGP1 and SGP2 return same RC?
> 
> -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, 2 Jan 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > Yes, all the SS7 UAs support this.  The ASP registers once each with SGP1
> > and SGP2.
> > 
> > --brian
> > 
> > Samuel Dur D. Jeyaseelan wrote:                  (Thu, 02 Jan 2003 05:08:41)
> > > 
> > > Hi,
> > > 
> > >  Suppose an AS has single ASP and wants to connect to SGP1
> > > and SGP2 for the same RK1.
> > > 
> > >   
> > > +---------+                                 +-----+
> > > |+------+ |          RK1      SCTP1         | ASP |
> > > || SGP1 |-|---------------------------------+-----+
> > > |+------+ |                                    |
> > > |         |                                    |
> > > |+------+ |          RK1      SCTP2            |
> > > || SGP2 |-|------------------------------------+
> > > |+------+ |
> > > +---------+ 
> > > 
> > > Does REG procedures at SGP allow this kind of scenario?
> > > 
> > > This kind of scenario may be required in case SGP1 goes down 
> > > still ASP can deliver messages via SGP2.
> > > 
> > > --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. *******
> > > 
> > 
> > -- 
> > 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 mailnull@www1.ietf.org  Thu Jan  2 08: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 IAA03971
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 08:03:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02DBto21180
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 08:11:55 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02DB7J21136;
	Thu, 2 Jan 2003 08:11:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02DA8J21077
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 08:10:08 -0500
Received: from web12807.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA03939
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 08:01:20 -0500 (EST)
Message-ID: <20030102130431.10919.qmail@web12807.mail.yahoo.com>
Received: from [62.29.66.77] by web12807.mail.yahoo.com via HTTP; Thu, 02 Jan 2003 05:04:31 PST
Date: Thu, 2 Jan 2003 05:04:31 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
To: sigtran@ietf.org
In-Reply-To: <20030102045510.A2482@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Sigtran] Re: [M3UA]1 AS and 1 ASP
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,
> Samuel,
> 
> Not necessarily.  They SHOULD return the same RC
> value.
[TOLGA] Why "SHOULD"? If SGPs are part of the same SG,
this would be probably the case, but why has it to be
a "SHOULD" from protocol point of view?
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                     
>                                (Thu, 02 Jan 2003
> 05:51:29)
> > 
> > Brian,
> > 
> > For RK1 ,Will SGP1 and SGP2 return same RC?
> > 
> > -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, 2 Jan 2003, Brian F. G. Bidulock wrote:
> > 
> > > Samuel,
> > > 
> > > Yes, all the SS7 UAs support this.  The ASP
> registers once each with SGP1
> > > and SGP2.
> > > 
> > > --brian
> > > 
> > > Samuel Dur D. Jeyaseelan wrote:                 
> (Thu, 02 Jan 2003 05:08:41)
> > > > 
> > > > Hi,
> > > > 
> > > >  Suppose an AS has single ASP and wants to
> connect to SGP1
> > > > and SGP2 for the same RK1.
> > > > 
> > > >   
> > > > +---------+                                
> +-----+
> > > > |+------+ |          RK1      SCTP1         |
> ASP |
> > > > || SGP1
> |-|---------------------------------+-----+
> > > > |+------+ |                                   
> |
> > > > |         |                                   
> |
> > > > |+------+ |          RK1      SCTP2           
> |
> > > > || SGP2
> |-|------------------------------------+
> > > > |+------+ |
> > > > +---------+ 
> > > > 
> > > > Does REG procedures at SGP allow this kind of
> scenario?
> > > > 
> > > > This kind of scenario may be required in case
> SGP1 goes down 
> > > > still ASP can deliver messages via SGP2.
> > > > 
> > > > --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. *******
> > > > 
> > > 
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > > 
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jan  2 08:07:15 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 IAA04020
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 08:07:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02DFW621327
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 08:15:32 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02DC7J21204;
	Thu, 2 Jan 2003 08:12:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02DBKJ21144
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 08:11:20 -0500
Received: from web12806.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA03956
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 08:02:32 -0500 (EST)
Message-ID: <20030102130543.69251.qmail@web12806.mail.yahoo.com>
Received: from [62.29.66.77] by web12806.mail.yahoo.com via HTTP; Thu, 02 Jan 2003 05:05:43 PST
Date: Thu, 2 Jan 2003 05:05:43 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Routing Key
To: sigtran@ietf.org
In-Reply-To: <20030101150035.A14470@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:                                
>   (Wed, 01 Jan 2003 13:17:39)
> > [TOLGA] Why? I would expect that necessary changes
> on a SG to support SSN
> > based routing is, to filter/regenerate/imitate
> some SCCP management
> > messages. Those changes, I would consider as
> changes to NIF not to the on
> > the wire M3UA protocol. 
> 
> Read the thread.
[TOLGA] Which one/time?
> 
> --brian
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jan  2 08:14:15 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 IAA04120
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 08:14:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02DMWp21638
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 08:22:32 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02DM7J21607;
	Thu, 2 Jan 2003 08:22:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02DLPJ21561
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 08:21:25 -0500
Received: from gw.openss7.com (IDENT:zBMXDPKdxm2XOHlHxDcT1WmMgJrvz5Lm@gw.openss7.com [142.179.199.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03967
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 08:03:28 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:a8CxnW2kj7pFjrHiKi2+nT0aCJcBWO8m@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02BtBl13406;
	Thu, 2 Jan 2003 04:55:11 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02BtAo02503;
	Thu, 2 Jan 2003 04:55:10 -0700
Date: Thu, 2 Jan 2003 04:55:10 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Message-ID: <20030102045510.A2482@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030102042412.A1077@openss7.org> <Pine.SOL.4.10.10301020550010.23295-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.10301020550010.23295-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Thu, Jan 02, 2003 at 05:51:29AM -0600
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: [M3UA]1 AS and 1 ASP
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,

Not necessarily.  They SHOULD return the same RC value.

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 02 Jan 2003 05:51:29)
> 
> Brian,
> 
> For RK1 ,Will SGP1 and SGP2 return same RC?
> 
> -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, 2 Jan 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > Yes, all the SS7 UAs support this.  The ASP registers once each with SGP1
> > and SGP2.
> > 
> > --brian
> > 
> > Samuel Dur D. Jeyaseelan wrote:                  (Thu, 02 Jan 2003 05:08:41)
> > > 
> > > Hi,
> > > 
> > >  Suppose an AS has single ASP and wants to connect to SGP1
> > > and SGP2 for the same RK1.
> > > 
> > >   
> > > +---------+                                 +-----+
> > > |+------+ |          RK1      SCTP1         | ASP |
> > > || SGP1 |-|---------------------------------+-----+
> > > |+------+ |                                    |
> > > |         |                                    |
> > > |+------+ |          RK1      SCTP2            |
> > > || SGP2 |-|------------------------------------+
> > > |+------+ |
> > > +---------+ 
> > > 
> > > Does REG procedures at SGP allow this kind of scenario?
> > > 
> > > This kind of scenario may be required in case SGP1 goes down 
> > > still ASP can deliver messages via SGP2.
> > > 
> > > --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. *******
> > > 
> > 
> > -- 
> > 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 mailnull@www1.ietf.org  Thu Jan  2 08:19: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 IAA04173
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 08:19:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02DS0K21925
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 08:28:00 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02DRTJ21892;
	Thu, 2 Jan 2003 08:27:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02DQRJ21850
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 08:26:27 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04153
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 08:17:36 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:sEiByEjQ3xn6E0Zm12tQnxRlaO5i6tY9@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02DKlD01648
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 06:20:47 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02DKkb07584
	for sigtran@ietf.org; Thu, 2 Jan 2003 06:20:46 -0700
Date: Thu, 2 Jan 2003 06:20:46 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: sigtran@ietf.org
Subject: Re: [Sigtran] Routing Key
Message-ID: <20030102062046.A7412@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: sigtran@ietf.org
References: <20030101150035.A14470@openss7.org> <20030102130543.69251.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: <20030102130543.69251.qmail@web12806.mail.yahoo.com>; from tolga_asveren@yahoo.com on Thu, Jan 02, 2003 at 05:05:43AM -0800
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, 02 Jan 2003 05:05:43)
> > 
> > Read the thread.
> [TOLGA] Which one/time?

See my third note on *this* thread.

--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  Thu Jan  2 08:22: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 IAA04233
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 08:22:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02DURe22063
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 08:30:27 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02DU5J22038;
	Thu, 2 Jan 2003 08:30:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02DT7J21997
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 08:29:07 -0500
Received: from shardagate.mahindrabt.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04192
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 08:20:17 -0500 (EST)
Received: from thisdomain (mailscan.sharda.mahindrabt.com [10.5.0.97])
	by shardagate.mahindrabt.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id SAA28399
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 18:53:23 +0530
Received: from intranet.sharda.mahindrabt.com by mahindrabt.com ; Thu, 02 Jan 2003 18:42:55 +0530
Date: Thu, 02 Jan 2003 18:42:55 +0530
X-Originating-IP: 10.5.0.15
X-Auth-User: jaya.panem@mahindrabt.com
Received: from dscp00950 ([10.5.14.17])
	by intranet.sharda.mahindrabt.com (8.9.3/8.9.3) with SMTP id SAA21230;
	Thu, 2 Jan 2003 18:53:15 +0530
From: "Sanjeev P.J" <jaya.panem@mahindrabt.com>
To: <bidulock@openss7.org>, "Tolga Asveren" <tolga_asveren@yahoo.com>
Cc: <sigtran@ietf.org>
Subject: RE: [Sigtran] Routing Key
Date: Thu, 2 Jan 2003 18:56:12 +0530
Message-ID: <NEBBJFMCBDDCAGAJKJCDIEABCMAA.jaya.panem@mahindrabt.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.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <20030101150035.A14470@openss7.org>
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

Couldn't the Network Appearance be used for this?

-Sanjeev.

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
Brian F. G. Bidulock
Sent: Thursday, January 02, 2003 4:53 AM
To: Tolga Asveren
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Routing Key

Tolga,

Tolga Asveren wrote:                                   (Wed, 01 Jan 2003
13:17:39)
> [TOLGA] Why? I would expect that necessary changes on a SG to support SSN
> based routing is, to filter/regenerate/imitate some SCCP management
> messages. Those changes, I would consider as changes to NIF not to the on
> the wire M3UA protocol.

Read the thread.

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

*********************************************************
Disclaimer

This message (including any attachments) contains 
confidential information intended for a specific 
individual and purpose, and is protected by law. 
If you are not the intended recipient, you should 
delete this message and are hereby notified that 
any disclosure, copying, or distribution of this
message, or the taking of any action based on it, 
is strictly prohibited.

*********************************************************
Visit us at http://www.mahindrabt.com



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



From mailnull@www1.ietf.org  Thu Jan  2 08:31: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 IAA04335
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 08:31:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02DdmJ23106
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 08:39:48 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02Dd8J23066;
	Thu, 2 Jan 2003 08:39:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02DcCJ23027
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 08:38:12 -0500
Received: from gw.openss7.com (IDENT:Dse+CtZg6VqL0lWfc6W+w7D44Zj4Ur/b@gw.openss7.com [142.179.199.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04309
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 08:29:16 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:FNOiXv3MTu6j49z17FXrWuNdpbtoBeB1@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02DTtD01743;
	Thu, 2 Jan 2003 06:29:55 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02DTsG08189;
	Thu, 2 Jan 2003 06:29:54 -0700
Date: Thu, 2 Jan 2003 06:29:54 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] [M3UA]1 AS and 1 ASP
Message-ID: <20030102062954.B7412@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <01f801c2b262$5cc79cc0$7501ff0a@axsppc67>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <01f801c2b262$5cc79cc0$7501ff0a@axsppc67>; from chak@axes-mach01.usa.alcatel.com on Thu, Jan 02, 2003 at 06:54:43PM +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>

PSK,

PSK Chakravarthi wrote:                                                                (Thu, 02 Jan 2003 18:54:43)
> Brian,
> 
> In that case what is Routing Context from each SGP? Will it be same?
> It has to be same because it is for the same AS and the scope of routing
> context is per SG and not per SGP.

No.  The scope of RC is SGP not SG.

> In that case SGP2 should return error for REG REQ of RK1 as RK1 for ASP is
> already registered.

Wrong.

Read Section 3.6.1, 3.6.3, 3.7.1, and particularly 4.4.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



From mailnull@www1.ietf.org  Thu Jan  2 08:33:02 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 IAA04375
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 08:33:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02DfJZ23232
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 08:41:19 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02Df4J23202;
	Thu, 2 Jan 2003 08:41:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02DeMJ23166
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 08:40:22 -0500
Received: from web12801.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA04349
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 08:31:33 -0500 (EST)
Message-ID: <20030102133445.53693.qmail@web12801.mail.yahoo.com>
Received: from [62.29.66.77] by web12801.mail.yahoo.com via HTTP; Thu, 02 Jan 2003 05:34:45 PST
Date: Thu, 2 Jan 2003 05:34:45 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA - ASP UP and ASP DN in Double Exchange
To: sigtran@ietf.org
In-Reply-To: <12B638FEE763F74696D8544752E7204802C478DF@bgsmsx101.iind.intel.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>

Ashish,
--- "Nagar, Ashish" <ashish.nagar@intel.com> wrote:
> Hi Brian/Tolga
> 
>     From section 5.5.2 (Double Exchange) of M3UA RFC
> 
>     "only one single exchange of ASP Up 
>     message can be considered as enough since the
> response by the other 
>     peer can be considered as a notice that it is in
> ASP_UP state"
> 
>     My point is because it is a double ended mode
> this message should come 
>     from both the side. There is no point in keeping
> ASP UP and ASP DN 
>     from another end as optional. This I am asking
> just for the sake of 
>     similarity with ASP AC and ASP IA message and
> also its behavior will be
> same as 
>     the name implies (Double Exchange).
> 
>     So my suggestion is to change ASP UP and ASP DN
> as mandatory.
> 
>     I know that ASP AC / ASPIA contains RC.
[TOLGA]Personally I don't consider DE as a robust
peer-to-peer communication model (even SE is
questionable IMO, but better than DE). But for your
question, I would think  that the name has "double"
inside does not necessarily mean that everything
should be double. Important is how AS related messages
are exchanged, i.e. with DE each IPSP tells the other
one, which traffic range it can serve (this is also
the reason, why it is still a client/server
relationship, not a peer-to-peer relationship IMO).
ASPUP/ASPDN is not for a specific AS but for the whole
IPSP (so basically relad with all AS). So, I think, it
is the double ASPAC/ASPAC-ACK, which makes this model
to be called DE.
But having double ASPUP/ASPDN might have the
advantage, that one can use ASP/SGP state machines
unmodified (the reason why so many people were
attracted by DE model initially, including me)
> 
> Regards
> Ashish
>      
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jan  2 08:37: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 IAA04460
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 08:37:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02DjxV23474
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 08:45:59 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02Di5J23377;
	Thu, 2 Jan 2003 08:44:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02DhOJ23340
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 08:43:24 -0500
Received: from gw.openss7.com (IDENT:FROk5/fG7GdRbcuP6fu8JdDTqyhwrTm6@gw.openss7.com [142.179.199.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04367
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 08:32:16 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:bwi/gPvElhkTEeYrDOCqzTr+OAD7h7Y+@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02DX2D01875;
	Thu, 2 Jan 2003 06:33:02 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02DX1e08427;
	Thu, 2 Jan 2003 06:33:01 -0700
Date: Thu, 2 Jan 2003 06:33:01 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Sanjeev P.J" <jaya.panem@mahindrabt.com>
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Routing Key
Message-ID: <20030102063301.D7412@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Sanjeev P.J" <jaya.panem@mahindrabt.com>,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030101150035.A14470@openss7.org> <NEBBJFMCBDDCAGAJKJCDIEABCMAA.jaya.panem@mahindrabt.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: <NEBBJFMCBDDCAGAJKJCDIEABCMAA.jaya.panem@mahindrabt.com>; from jaya.panem@mahindrabt.com on Thu, Jan 02, 2003 at 06:56:12PM +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>

Sanjeev,

Sanjeev P.J wrote:                                 (Thu, 02 Jan 2003 18:56:12)
> Couldn't the Network Appearance be used for this?
> 

No.

--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  Thu Jan  2 08:38: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 IAA04496
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 08:38:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02DlHi23545
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 08:47:17 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02Dl4J23525;
	Thu, 2 Jan 2003 08:47:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02Dk3J23492
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 08:46:03 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04439
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 08:36:32 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:VleAzqMQOrYpHB5B32RDCFXu6kqc/2b+@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02DdJD01947;
	Thu, 2 Jan 2003 06:39:19 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02DdI508851;
	Thu, 2 Jan 2003 06:39:18 -0700
Date: Thu, 2 Jan 2003 06:39:18 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA - ASP UP and ASP DN in Double Exchange
Message-ID: <20030102063918.E7412@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <12B638FEE763F74696D8544752E7204802C478DF@bgsmsx101.iind.intel.com> <20030102133445.53693.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: <20030102133445.53693.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Thu, Jan 02, 2003 at 05:34:45AM -0800
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, 02 Jan 2003 05:34:45)

-X- snip -X-
> But having double ASPUP/ASPDN might have the
> advantage, that one can use ASP/SGP state machines
> unmodified (the reason why so many people were
> attracted by DE model initially, including me)

Dream.  You cannot reuse the ASP/SGP state machines for DE, only
for SE.  This is because DE only handles half traffic flows,
whereas the normal ASP/SGP state machines handle traffic flow in
both directions, just as does SE.

--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  Thu Jan  2 09:02: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 JAA04832
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 09:02:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02EAkS25241
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 09:10:46 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02EA8J25192;
	Thu, 2 Jan 2003 09:10:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02E9qJ25151
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 09:09:52 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04778
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 09:00:58 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:pJEMpgahZEVXnYSEbMevjPJiEhGtNUfq@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02DVcD01856
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 06:31:38 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02DVcf08342
	for sigtran@ietf.org; Thu, 2 Jan 2003 06:31:38 -0700
Date: Thu, 2 Jan 2003 06:31:37 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
Message-ID: <20030102063137.C7412@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: sigtran@ietf.org
References: <20030102045510.A2482@openss7.org> <20030102130431.10919.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: <20030102130431.10919.qmail@web12807.mail.yahoo.com>; from tolga_asveren@yahoo.com on Thu, Jan 02, 2003 at 05:04:31AM -0800
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, 02 Jan 2003 05:04:31)
> Brian,
> > Samuel,
> > 
> > Not necessarily.  They SHOULD return the same RC
> > value.
> [TOLGA] Why "SHOULD"? If SGPs are part of the same SG,
> this would be probably the case, but why has it to be
> a "SHOULD" from protocol point of view?

Because that was the consensus.

--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  Thu Jan  2 09:03: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 JAA04863
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 09:03:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02EBJ425278
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 09:11:19 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02EB5J25269;
	Thu, 2 Jan 2003 09:11:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02EAJJ25207
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 09:10:19 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04803
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 09:01:29 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h02E2eBE022135;
	Thu, 2 Jan 2003 08:02:41 -0600 (CST)
Received: from axsppc67 by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id SAA26791; Thu, 2 Jan 2003 18:31:42 -0500 (GMT)
Message-ID: <023001c2b269$2d1423c0$7501ff0a@axsppc67>
From: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
To: <bidulock@openss7.org>
Cc: <sigtran@ietf.org>
References: <01f801c2b262$5cc79cc0$7501ff0a@axsppc67> <20030102062954.B7412@openss7.org>
Subject: Re: [Sigtran] [M3UA]1 AS and 1 ASP
Date: Thu, 2 Jan 2003 19:43:35 +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.50.4133.2400
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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

Brian,

As per RFC 3332 Section 1.4.2.1
"The Routing Context therefore can be viewed as an index into a sending
node's Message Distribution Table containing the Routing Key entries"

Here what is the 'sending node'?  Is it not SG.

thanks
Chak
----- Original Message -----
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
Cc: <sigtran@ietf.org>
Sent: Thursday, January 02, 2003 6:59 PM
Subject: Re: [Sigtran] [M3UA]1 AS and 1 ASP


> PSK,
>
> PSK Chakravarthi wrote:
(Thu, 02 Jan 2003 18:54:43)
> > Brian,
> >
> > In that case what is Routing Context from each SGP? Will it be same?
> > It has to be same because it is for the same AS and the scope of routing
> > context is per SG and not per SGP.
>
> No.  The scope of RC is SGP not SG.
>
> > In that case SGP2 should return error for REG REQ of RK1 as RK1 for ASP
is
> > already registered.
>
> Wrong.
>
> Read Section 3.6.1, 3.6.3, 3.7.1, and particularly 4.4.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



From mailnull@www1.ietf.org  Thu Jan  2 09:04: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 JAA04892
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 09:04:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02ECIU25358
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 09:12:18 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02EC3J25337;
	Thu, 2 Jan 2003 09:12:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02EBVJ25312
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 09:11:31 -0500
Received: from rtp-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04853
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 09:02:42 -0500 (EST)
Received: from cia.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h02E6LSk009745;
	Thu, 2 Jan 2003 09:06:22 -0500 (EST)
Received: from kmorneau-w2k.cisco.com (rtp-vpn1-444.cisco.com [10.82.225.188])
	by cia.cisco.com (Mirapoint)
	with ESMTP id ABL76247;
	Thu, 2 Jan 2003 08:55:37 -0500 (EST)
Message-Id: <4.3.2.7.2.20030102090451.01a9ff40@cia.cisco.com>
X-Sender: kmorneau@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 02 Jan 2003 09:05:39 -0500
To: bidulock@openss7.org
From: Ken Morneault <kmorneau@cisco.com>
Subject: Re: [Sigtran] I-D
  ACTION:draft-ietf-sigtran-m3ua-implementors-guide-02.txt
Cc: sigtran@ietf.org
In-Reply-To: <20021231182143.A28785@openss7.org>
References: <4.3.2.7.2.20021220110935.09ca8da0@cia.cisco.com>
 <4.3.2.7.2.20021219142717.0a086bf0@cia.cisco.com>
 <200211081236.HAA16065@ietf.org>
 <200211081236.HAA16065@ietf.org>
 <20021218034323.C19607@openss7.org>
 <4.3.2.7.2.20021219142717.0a086bf0@cia.cisco.com>
 <20021219145109.D10658@openss7.org>
 <4.3.2.7.2.20021220110935.09ca8da0@cia.cisco.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,

Please address your concerns to the entire group as your proposed
change is something for all to discuss.

Regards,

Ken

At 06:21 PM 12/31/2002 -0700, Brian F. G. Bidulock wrote:
>Ken,
>
>Section 3.2.
>
>What does it matter if the SGP sends "Unsupported Message Type" or
>"Unsupported Message Class"?  Acutally, if we ever add a message to the class,
>"Unsupport Message Class" might no longer be correct, whereas "Unsupported
>Message Type" survives the addition of new message types to the class.
>
>Also, as the only necessary piece of information given in the Error message
>is the Message Class and Type, why force an implementation to include the
>first 40 bytes of the message?  That's ridiculous.  All that needs to be
>included a couple bytes of the message header.
>
>Also, there is no more need to correlate this error than others.  The
>ASP is obviously misconfigured (it figures it can register with an SGP
>that does not even supoprt registration), so it really doesn't matter
>what happens to it: there are many ways to misconfigure an ASP so that
>it will not be caught by the protocol.
>
>Please strike section 3.2.
>
>Also note that M2UA and SUA also use the same text.  It makes no sense to
>have M3UA act differently in this regard than M2UA and SUA.
>
>--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 mailnull@www1.ietf.org  Thu Jan  2 09:43: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 JAA05458
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 09:43:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02EpPJ27976
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 09:51:25 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02EohJ27933;
	Thu, 2 Jan 2003 09:50:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02En3J27876
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 09:49:03 -0500
Received: from revere.sonusnet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05427
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 09:40:11 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3.sonusnet.com [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h02EdNS23614;
	Thu, 2 Jan 2003 09:39:23 -0500 (EST)
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19)
	id <Y68HRGPX>; Thu, 2 Jan 2003 09:39:52 -0500
Message-ID: <4CF48720B6E9D4118D040060CF2074E9072F6B8D@sonusdc3.sonusnet.com>
From: "Wung, Joseph" <JWung@sonusnet.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
Date: Thu, 2 Jan 2003 09:39:43 -0500 
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,

It is not up to the ASP or AS.  The SS7 side can choose
to opearate on any circuit group as they want.

For example, 
ASP-a serves AS-1(CIC=5000~5071) and 
		 AS-2(CIC=5072~5143),
 
ASP-b serves AS-3(CIC=5144~5215) and
		 AS-4(CIC=5216~5287)

Neither the ASPs nor the ASes are splitting anything here.
The SS7 side can send a group related ISUP message, e.g.,
CGB, using any 24 circuit range across 5000~5287.  I
guess this is legal for them to do so.

But this would cause the SG send the message to ASP-a if 
the CIC range in the CGB crosses the ASP boundary, or cause
one ASP to send it to AS-1 or AS-3 if crossing the AS 
boundary.

Joe 

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: Friday, December 27, 2002 5:08 PM
To: Wung, Joseph
Cc: 'sigtran@ietf.org'
Subject: Re: [Sigtran] M3UA distributing ISUP group messages


Joseph,

That would be up to the ASP.  If you want to make things easier
for the ASP, don't split circuit groups across AS either.

--brian

Wung, Joseph wrote:
(Fri, 27 Dec 2002 16:30:23)
> Brian,
> 
> "don't split up your circuit groups across ASPs" would
> solve the problem of distributing group messages for the
> SG.  What if an ASP serves multiple ASes, which cover
> a spectrum of contiguous CICs.  For example, an ASP
> serves AS1(CIC=5000~5071), AS2(CIC=5072~5143).  Now
> the ASP receives a message about CICs(5060~5083).
> How would the ASP distribute the received message to
> the ASes it serves?
> 
> Thanks,
> Joe
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Friday, December 27, 2002 3:59 PM
> To: Wung, Joseph
> Cc: 'sigtran@ietf.org'
> Subject: Re: [Sigtran] M3UA distributing ISUP group messages
> 
> 
> Joseph,
> 
> Section A.2.1 says:
> 
>   "For example, where Application Servers are defined using ranges of
>    ISUP CIC values, the Operator is implicitly splitting up control of
>    the related circuit groups.  Some CIC value range assignments may
>    interfere with ISUP circuit group management procedures."
> 
> 
> The solution is: don't split up your circuit groups across ASPs: which
> makes sense anyway.
> 
> --brian
> 
> Wung, Joseph wrote:                              (Fri, 27 Dec 2002
15:14:38)
> > Each of the ISUP group related messages, i.e., CGB, CGU, GRS, GRA, etc.,
> has
> > a range field in addition to the CIC parameter that together specify a
> range
> > of circuits to operate on.  I would assume that the SGP that receives
> those
> > message would distribute them toward an ASP based on the CIC parameter
in
> > the messages without looking at the range field.  This may be ok if the
> > entire range fall into the same AS as the CIC.  What if the range
crosses
> > the boundary of the AS?  This may seem like an implementation dependent
> > issue, but it does impact how ISUP messages are distributed based on the
> > routing key.  Any solution?
> > 
> > Joe
> > _______________________________________________
> > 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 mailnull@www1.ietf.org  Thu Jan  2 10:12: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 KAA06021
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 10:12:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02FKmU29950
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 10:20:48 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02FKBJ29894;
	Thu, 2 Jan 2003 10:20:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02FJgJ29752
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 10:19:42 -0500
Received: from shardagate.mahindrabt.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05958
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 10:10:51 -0500 (EST)
Received: from thisdomain (mailscan.sharda.mahindrabt.com [10.5.0.97])
	by shardagate.mahindrabt.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id UAA12977
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 20:43:56 +0530
Received: from intranet.sharda.mahindrabt.com by mahindrabt.com ; Thu, 02 Jan 2003 20:33:27 +0530
Date: Thu, 02 Jan 2003 20:33:27 +0530
X-Originating-IP: 10.5.0.15
X-Auth-User: jaya.panem@mahindrabt.com
Received: from dscp00950 ([10.5.14.17])
	by intranet.sharda.mahindrabt.com (8.9.3/8.9.3) with SMTP id UAA25026;
	Thu, 2 Jan 2003 20:43:48 +0530
From: "Sanjeev P.J" <jaya.panem@mahindrabt.com>
To: "Wung, Joseph" <JWung@sonusnet.com>, <bidulock@openss7.org>
Cc: <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
Date: Thu, 2 Jan 2003 20:46:45 +0530
Message-ID: <NEBBJFMCBDDCAGAJKJCDCEAECMAA.jaya.panem@mahindrabt.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.2910.0)
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <4CF48720B6E9D4118D040060CF2074E9072F6B8D@sonusdc3.sonusnet.com>
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

True. But the response can have "no indication" for the CICs outside the
range defined for the AS allowing the other end to resend the group message
with the modified range.

Can't this be done??

sanjeev.

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
Wung, Joseph
Sent: Thursday, January 02, 2003 8:34 PM
To: 'bidulock@openss7.org'
Cc: 'sigtran@ietf.org'
Subject: RE: [Sigtran] M3UA distributing ISUP group messages

Brian,

It is not up to the ASP or AS.  The SS7 side can choose
to opearate on any circuit group as they want.

For example,
ASP-a serves AS-1(CIC=5000~5071) and
		 AS-2(CIC=5072~5143),

ASP-b serves AS-3(CIC=5144~5215) and
		 AS-4(CIC=5216~5287)

Neither the ASPs nor the ASes are splitting anything here.
The SS7 side can send a group related ISUP message, e.g.,
CGB, using any 24 circuit range across 5000~5287.  I
guess this is legal for them to do so.

But this would cause the SG send the message to ASP-a if
the CIC range in the CGB crosses the ASP boundary, or cause
one ASP to send it to AS-1 or AS-3 if crossing the AS
boundary.

Joe

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: Friday, December 27, 2002 5:08 PM
To: Wung, Joseph
Cc: 'sigtran@ietf.org'
Subject: Re: [Sigtran] M3UA distributing ISUP group messages

Joseph,

That would be up to the ASP.  If you want to make things easier
for the ASP, don't split circuit groups across AS either.

--brian

Wung, Joseph wrote:
(Fri, 27 Dec 2002 16:30:23)
> Brian,
>
> "don't split up your circuit groups across ASPs" would
> solve the problem of distributing group messages for the
> SG.  What if an ASP serves multiple ASes, which cover
> a spectrum of contiguous CICs.  For example, an ASP
> serves AS1(CIC=5000~5071), AS2(CIC=5072~5143).  Now
> the ASP receives a message about CICs(5060~5083).
> How would the ASP distribute the received message to
> the ASes it serves?
>
> Thanks,
> Joe
>
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Friday, December 27, 2002 3:59 PM
> To: Wung, Joseph
> Cc: 'sigtran@ietf.org'
> Subject: Re: [Sigtran] M3UA distributing ISUP group messages
>
>
> Joseph,
>
> Section A.2.1 says:
>
>   "For example, where Application Servers are defined using ranges of
>    ISUP CIC values, the Operator is implicitly splitting up control of
>    the related circuit groups.  Some CIC value range assignments may
>    interfere with ISUP circuit group management procedures."
>
>
> The solution is: don't split up your circuit groups across ASPs: which
> makes sense anyway.
>
> --brian
>
> Wung, Joseph wrote:                              (Fri, 27 Dec 2002
15:14:38)
> > Each of the ISUP group related messages, i.e., CGB, CGU, GRS, GRA, etc.,
> has
> > a range field in addition to the CIC parameter that together specify a
> range
> > of circuits to operate on.  I would assume that the SGP that receives
> those
> > message would distribute them toward an ASP based on the CIC parameter
in
> > the messages without looking at the range field.  This may be ok if the
> > entire range fall into the same AS as the CIC.  What if the range
crosses
> > the boundary of the AS?  This may seem like an implementation dependent
> > issue, but it does impact how ISUP messages are distributed based on the
> > routing key.  Any solution?
> >
> > Joe
> > _______________________________________________
> > 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

*********************************************************
Disclaimer

This message (including any attachments) contains 
confidential information intended for a specific 
individual and purpose, and is protected by law. 
If you are not the intended recipient, you should 
delete this message and are hereby notified that 
any disclosure, copying, or distribution of this
message, or the taking of any action based on it, 
is strictly prohibited.

*********************************************************
Visit us at http://www.mahindrabt.com



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



From mailnull@www1.ietf.org  Thu Jan  2 10:15: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 KAA06176
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 10:15:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02FNjs30174
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 10:23:45 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02FN5J30079;
	Thu, 2 Jan 2003 10:23:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02FMuJ30062
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 10:22:56 -0500
Received: from gw.openss7.com (IDENT:oRbYT5iKtXTRPSKrTd1VnBBzDrdfX+4c@gw.openss7.com [142.179.199.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05338
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 09:34:12 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:cK69KX0FT6oc5PO/NJcEKGjDEbMm0lsb@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02EYoD02647;
	Thu, 2 Jan 2003 07:34:50 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02EYm113570;
	Thu, 2 Jan 2003 07:34:48 -0700
Date: Thu, 2 Jan 2003 07:34:48 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] [M3UA]1 AS and 1 ASP
Message-ID: <20030102073448.B12557@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <01f801c2b262$5cc79cc0$7501ff0a@axsppc67> <20030102062954.B7412@openss7.org> <023001c2b269$2d1423c0$7501ff0a@axsppc67>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <023001c2b269$2d1423c0$7501ff0a@axsppc67>; from chak@axes-mach01.usa.alcatel.com on Thu, Jan 02, 2003 at 07:43:35PM +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>

PSK,

4.4.1 Registration

   ...       The method of Routing Context value assignment at the SGP
   is implementation dependent but must be guaranteed to be unique for
   each Application Server or Routing Key supported by the SGP.

The scope of RC is SGP not SG.

In fact, the RC identifies an AS on an SCTP association, so its scope
is the SGP-ASP relation (SCTP association) only.

--brian

PSK Chakravarthi wrote:                                 (Thu, 02 Jan 2003 19:43:35)
> Brian,
> 
> As per RFC 3332 Section 1.4.2.1
> "The Routing Context therefore can be viewed as an index into a sending
> node's Message Distribution Table containing the Routing Key entries"
> 
> Here what is the 'sending node'?  Is it not SG.
> 
> thanks
> Chak
> ----- Original Message -----
> From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> To: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
> Cc: <sigtran@ietf.org>
> Sent: Thursday, January 02, 2003 6:59 PM
> Subject: Re: [Sigtran] [M3UA]1 AS and 1 ASP
> 
> 
> > PSK,
> >
> > PSK Chakravarthi wrote:
> (Thu, 02 Jan 2003 18:54:43)
> > > Brian,
> > >
> > > In that case what is Routing Context from each SGP? Will it be same?
> > > It has to be same because it is for the same AS and the scope of routing
> > > context is per SG and not per SGP.
> >
> > No.  The scope of RC is SGP not SG.
> >
> > > In that case SGP2 should return error for REG REQ of RK1 as RK1 for ASP
> is
> > > already registered.
> >
> > Wrong.
> >
> > Read Section 3.6.1, 3.6.3, 3.7.1, and particularly 4.4.1.
> >
> > --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 mailnull@www1.ietf.org  Thu Jan  2 10:50:08 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 KAA06848
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 10:50:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02FwRW32529
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 10:58:27 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02FvgJ32492;
	Thu, 2 Jan 2003 10:57:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02FuWJ32444
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 10:56:32 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06818
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 10:47:35 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:g/04RRJixwdHqXwevL/vCPHqvNnxQh70@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02FoVD03730;
	Thu, 2 Jan 2003 08:50:31 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02FoVP15915;
	Thu, 2 Jan 2003 08:50:31 -0700
Date: Thu, 2 Jan 2003 08:50:31 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Sanjeev P.J" <jaya.panem@mahindrabt.com>
Cc: "Wung, Joseph" <JWung@sonusnet.com>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030102085031.B14969@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Sanjeev P.J" <jaya.panem@mahindrabt.com>,
	"Wung, Joseph" <JWung@sonusnet.com>, sigtran@ietf.org
References: <4CF48720B6E9D4118D040060CF2074E9072F6B8D@sonusdc3.sonusnet.com> <NEBBJFMCBDDCAGAJKJCDCEAECMAA.jaya.panem@mahindrabt.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: <NEBBJFMCBDDCAGAJKJCDCEAECMAA.jaya.panem@mahindrabt.com>; from jaya.panem@mahindrabt.com on Thu, Jan 02, 2003 at 08:46:45PM +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>

Sanjeev,

Sanjeev P.J wrote:                                                                 (Thu, 02 Jan 2003 20:46:45)
> True. But the response can have "no indication" for the CICs outside the
> range defined for the AS allowing the other end to resend the group message
> with the modified range.
> 
> Can't this be done??
> 

Yes it could, but maintenance would probably be informed, generating log
records and possibly alarms.  It would not be a good way to go about things
in the normal course of events.

--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  Thu Jan  2 11:02:19 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 LAA07155
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 11:02:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02GAcI01403
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 11:10:38 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02GA8J01347;
	Thu, 2 Jan 2003 11:10:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02G9nJ01312
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 11:09:49 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07087
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 11:00:57 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:S85VtF5C4/0c4mcaMrKISZDgdpGbp776@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02EUiD02606;
	Thu, 2 Jan 2003 07:30:44 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02EUh313121;
	Thu, 2 Jan 2003 07:30:43 -0700
Date: Thu, 2 Jan 2003 07:30:43 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Ken Morneault <kmorneau@cisco.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] I-D ACTION:draft-ietf-sigtran-m3ua-implementors-guide-02.txt
Message-ID: <20030102073043.A12557@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Ken Morneault <kmorneau@cisco.com>, sigtran@ietf.org
References: <4.3.2.7.2.20021220110935.09ca8da0@cia.cisco.com> <4.3.2.7.2.20021219142717.0a086bf0@cia.cisco.com> <200211081236.HAA16065@ietf.org> <200211081236.HAA16065@ietf.org> <20021218034323.C19607@openss7.org> <4.3.2.7.2.20021219142717.0a086bf0@cia.cisco.com> <20021219145109.D10658@openss7.org> <4.3.2.7.2.20021220110935.09ca8da0@cia.cisco.com> <20021231182143.A28785@openss7.org> <4.3.2.7.2.20030102090451.01a9ff40@cia.cisco.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: <4.3.2.7.2.20030102090451.01a9ff40@cia.cisco.com>; from kmorneau@cisco.com on Thu, Jan 02, 2003 at 09:05:39AM -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>

Ken Morneault wrote:                             (Thu, 02 Jan 2003 09:05:39)
> 
> 
> Brian,
> 
> Please address your concerns to the entire group as your proposed
> change is something for all to discuss.
> 
> Regards,
> 
> Ken


SIGTRAN,

Section 3.2.

What does it matter if the SGP sends "Unsupported Message Type" or
"Unsupported Message Class"?  Acutally, if we ever add a message to the class,
"Unsupport Message Class" might no longer be correct, whereas "Unsupported
Message Type" survives the addition of new message types to the class.

Also, as the only necessary piece of information given in the Error message
is the Message Class and Type, why force an implementation to include the
first 40 bytes of the message?  That's ridiculous.  All that needs to be
included a couple bytes of the message header.

Also, there is no more need to correlate this error than others.  The
ASP is obviously misconfigured (it figures it can register with an SGP
that does not even supoprt registration), so it really doesn't matter
what happens to it: there are many ways to misconfigure an ASP so that
it will not be caught by the protocol.

Please strike section 3.2.

Also note that M2UA and SUA also use the same text.  It makes no sense to
have M3UA act differently in this regard than M2UA and SUA.

--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  Thu Jan  2 11:18: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 LAA07596
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 11:18:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02GQsn02304
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 11:26:54 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02GQ8J02252;
	Thu, 2 Jan 2003 11:26:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02GPgJ02228
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 11:25:42 -0500
Received: from revere.sonusnet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07574
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 11:16:50 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3.sonusnet.com [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h02GH0S02355;
	Thu, 2 Jan 2003 11:17:00 -0500 (EST)
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19)
	id <Y68HRHA6>; Thu, 2 Jan 2003 11:17:29 -0500
Message-ID: <4CF48720B6E9D4118D040060CF2074E9072F6B8E@sonusdc3.sonusnet.com>
From: "Wung, Joseph" <JWung@sonusnet.com>
To: "'Sanjeev P.J'" <jaya.panem@mahindrabt.com>,
        "Wung, Joseph"
	 <JWung@sonusnet.com>, bidulock@openss7.org
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
Date: Thu, 2 Jan 2003 11:17:23 -0500 
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>

Sanjeev,

No.

ANSIT1.113-4 Section 2.8.2.3

"When an exchange upon receipt of a CGB Message in not
able to give an appropriate blocking acknowledgement 
indication for each CIC ..., then no blocking 
acknowledgement indication" relating
to that/those CICs shall be given in the Status field
of the corrsponding CGBA Message which shall be sent
in response."  

"If a CGBA message in response to a CGB Message is
received containing in the status field the indications
no blocking acknowledgement for some or all of the 
circuits which are to be blocked due to the previously
sent CGB Message, then the maintenance personnel should
be notified for the circuits concerned"

How is the CGBA receiving side at the SS7 network to 
know a modifed CGB message would work.  I don't see 
M3UA has a solution here.

Joe

-----Original Message-----
From: Sanjeev P.J [mailto:jaya.panem@mahindrabt.com]
Sent: Thursday, January 02, 2003 10:17 AM
To: Wung, Joseph; bidulock@openss7.org
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA distributing ISUP group messages


True. But the response can have "no indication" for the CICs outside the
range defined for the AS allowing the other end to resend the group message
with the modified range.

Can't this be done??

sanjeev.

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
Wung, Joseph
Sent: Thursday, January 02, 2003 8:34 PM
To: 'bidulock@openss7.org'
Cc: 'sigtran@ietf.org'
Subject: RE: [Sigtran] M3UA distributing ISUP group messages

Brian,

It is not up to the ASP or AS.  The SS7 side can choose
to opearate on any circuit group as they want.

For example,
ASP-a serves AS-1(CIC=5000~5071) and
		 AS-2(CIC=5072~5143),

ASP-b serves AS-3(CIC=5144~5215) and
		 AS-4(CIC=5216~5287)

Neither the ASPs nor the ASes are splitting anything here.
The SS7 side can send a group related ISUP message, e.g.,
CGB, using any 24 circuit range across 5000~5287.  I
guess this is legal for them to do so.

But this would cause the SG send the message to ASP-a if
the CIC range in the CGB crosses the ASP boundary, or cause
one ASP to send it to AS-1 or AS-3 if crossing the AS
boundary.

Joe

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: Friday, December 27, 2002 5:08 PM
To: Wung, Joseph
Cc: 'sigtran@ietf.org'
Subject: Re: [Sigtran] M3UA distributing ISUP group messages

Joseph,

That would be up to the ASP.  If you want to make things easier
for the ASP, don't split circuit groups across AS either.

--brian

Wung, Joseph wrote:
(Fri, 27 Dec 2002 16:30:23)
> Brian,
>
> "don't split up your circuit groups across ASPs" would
> solve the problem of distributing group messages for the
> SG.  What if an ASP serves multiple ASes, which cover
> a spectrum of contiguous CICs.  For example, an ASP
> serves AS1(CIC=5000~5071), AS2(CIC=5072~5143).  Now
> the ASP receives a message about CICs(5060~5083).
> How would the ASP distribute the received message to
> the ASes it serves?
>
> Thanks,
> Joe
>
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Friday, December 27, 2002 3:59 PM
> To: Wung, Joseph
> Cc: 'sigtran@ietf.org'
> Subject: Re: [Sigtran] M3UA distributing ISUP group messages
>
>
> Joseph,
>
> Section A.2.1 says:
>
>   "For example, where Application Servers are defined using ranges of
>    ISUP CIC values, the Operator is implicitly splitting up control of
>    the related circuit groups.  Some CIC value range assignments may
>    interfere with ISUP circuit group management procedures."
>
>
> The solution is: don't split up your circuit groups across ASPs: which
> makes sense anyway.
>
> --brian
>
> Wung, Joseph wrote:                              (Fri, 27 Dec 2002
15:14:38)
> > Each of the ISUP group related messages, i.e., CGB, CGU, GRS, GRA, etc.,
> has
> > a range field in addition to the CIC parameter that together specify a
> range
> > of circuits to operate on.  I would assume that the SGP that receives
> those
> > message would distribute them toward an ASP based on the CIC parameter
in
> > the messages without looking at the range field.  This may be ok if the
> > entire range fall into the same AS as the CIC.  What if the range
crosses
> > the boundary of the AS?  This may seem like an implementation dependent
> > issue, but it does impact how ISUP messages are distributed based on the
> > routing key.  Any solution?
> >
> > Joe
> > _______________________________________________
> > 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

*********************************************************
Disclaimer

This message (including any attachments) contains 
confidential information intended for a specific 
individual and purpose, and is protected by law. 
If you are not the intended recipient, you should 
delete this message and are hereby notified that 
any disclosure, copying, or distribution of this
message, or the taking of any action based on it, 
is strictly prohibited.

*********************************************************
Visit us at http://www.mahindrabt.com


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



From mailnull@www1.ietf.org  Thu Jan  2 11:50: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 LAA08163
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 11:50:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02Gwxd04302
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 11:58:59 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02GwbJ04284;
	Thu, 2 Jan 2003 11:58:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02GvAJ04227
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 11:57:10 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08127
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 11:46:13 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:UZ7Wppgsh3hGeGdWmHKxQvcZH/FH3MJc@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02Gn4D04579;
	Thu, 2 Jan 2003 09:49:04 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02Fn3c15850;
	Thu, 2 Jan 2003 08:49:03 -0700
Date: Thu, 2 Jan 2003 08:49:03 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Wung, Joseph" <JWung@sonusnet.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030102084903.A14969@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Wung, Joseph" <JWung@sonusnet.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <4CF48720B6E9D4118D040060CF2074E9072F6B8D@sonusdc3.sonusnet.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: <4CF48720B6E9D4118D040060CF2074E9072F6B8D@sonusdc3.sonusnet.com>; from JWung@sonusnet.com on Thu, Jan 02, 2003 at 09:39:43AM -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>

Joseph,

Several ways around that:

 o always configure your ISUP switches for pre-arranged circuit groups.

 o always configure your ISUP switches for the same circuit groups on
   both ends of the trunk.

Then you won't have this spanning problem.

But, don't expect me to justify CIC routing in M3UA: I don't think it
can work for a number of other reasons.  For example, what happens when
an IAM arrives for CIC=5288?  What AS does it go to?  Who sends back
REL(Unequipped CIC) and runs that whole part of the state machine?

When a remove ISUP is unavailable, where does DUPU get sent?  Which AS
is responsible for testing the availability of the remote ISUP?

When congestion occurs, which AS is responsible for detecting it an
placing ACL parameters into REL messages?

How much of the ISUP state machines must the SG implement before it can
route on CIC?

I think that, although one can loadshare on CIC, that routing on CIC
is a bad idea.  ISUP should be routed on OPC/DPC/SI=5 at maximum
granularity.  Then if one loadshares CIC over ASPs, it makes more sense.

At any rate, there is a lot of description missing from the M3UA spec
that would allow two implementation to interoperate properly as far as CIC
routing is concerned.

--brian

Wung, Joseph wrote:                        (Thu, 02 Jan 2003 09:39:43)
> Brian,
> 
> It is not up to the ASP or AS.  The SS7 side can choose
> to opearate on any circuit group as they want.
> 
> For example, 
> ASP-a serves AS-1(CIC=5000~5071) and 
> 		 AS-2(CIC=5072~5143),
>  
> ASP-b serves AS-3(CIC=5144~5215) and
> 		 AS-4(CIC=5216~5287)
> 
> Neither the ASPs nor the ASes are splitting anything here.
> The SS7 side can send a group related ISUP message, e.g.,
> CGB, using any 24 circuit range across 5000~5287.  I
> guess this is legal for them to do so.
> 
> But this would cause the SG send the message to ASP-a if 
> the CIC range in the CGB crosses the ASP boundary, or cause
> one ASP to send it to AS-1 or AS-3 if crossing the AS 
> boundary.
> 
> Joe 
> 

-- 
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 Jan  2 11:51: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 LAA08182
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 11:51:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02GxPK04345
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 11:59:25 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02Gx9J04333;
	Thu, 2 Jan 2003 11:59:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02GwRJ04268
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 11:58:27 -0500
Received: from gw.openss7.com (IDENT:5p1dzoeyDfbX3Ne1KwnQ1V0uLuJwrBBz@gw.openss7.com [142.179.199.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08144
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 11:49:35 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:/7hKuM29IjKtapUm8Dd3bHq+u5C1Qa0n@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02GoVD04607;
	Thu, 2 Jan 2003 09:50:31 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02FoVP15915;
	Thu, 2 Jan 2003 08:50:31 -0700
Date: Thu, 2 Jan 2003 08:50:31 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Sanjeev P.J" <jaya.panem@mahindrabt.com>
Cc: "Wung, Joseph" <JWung@sonusnet.com>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030102085031.B14969@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Sanjeev P.J" <jaya.panem@mahindrabt.com>,
	"Wung, Joseph" <JWung@sonusnet.com>, sigtran@ietf.org
References: <4CF48720B6E9D4118D040060CF2074E9072F6B8D@sonusdc3.sonusnet.com> <NEBBJFMCBDDCAGAJKJCDCEAECMAA.jaya.panem@mahindrabt.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: <NEBBJFMCBDDCAGAJKJCDCEAECMAA.jaya.panem@mahindrabt.com>; from jaya.panem@mahindrabt.com on Thu, Jan 02, 2003 at 08:46:45PM +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>

Sanjeev,

Sanjeev P.J wrote:                                                                 (Thu, 02 Jan 2003 20:46:45)
> True. But the response can have "no indication" for the CICs outside the
> range defined for the AS allowing the other end to resend the group message
> with the modified range.
> 
> Can't this be done??
> 

Yes it could, but maintenance would probably be informed, generating log
records and possibly alarms.  It would not be a good way to go about things
in the normal course of events.

--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  Thu Jan  2 13:27: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 NAA10799
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 13:27:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02IaHY11097
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 13:36:17 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02IZSJ11053;
	Thu, 2 Jan 2003 13:35:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02IXxJ11011
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 13:33:59 -0500
Received: from gw.openss7.com (IDENT:JfoPqY5jXyrLO9gZn2l+mUVGEVQ7v+cf@gw.openss7.com [142.179.199.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10535
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 13:18:31 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:SQi1Kl9735OYNDNK/ewqOpYfzk/QyRjm@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02Fn3D03708;
	Thu, 2 Jan 2003 08:49:03 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02Fn3c15850;
	Thu, 2 Jan 2003 08:49:03 -0700
Date: Thu, 2 Jan 2003 08:49:03 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Wung, Joseph" <JWung@sonusnet.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030102084903.A14969@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Wung, Joseph" <JWung@sonusnet.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <4CF48720B6E9D4118D040060CF2074E9072F6B8D@sonusdc3.sonusnet.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: <4CF48720B6E9D4118D040060CF2074E9072F6B8D@sonusdc3.sonusnet.com>; from JWung@sonusnet.com on Thu, Jan 02, 2003 at 09:39:43AM -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>

Joseph,

Several ways around that:

 o always configure your ISUP switches for pre-arranged circuit groups.

 o always configure your ISUP switches for the same circuit groups on
   both ends of the trunk.

Then you won't have this spanning problem.

But, don't expect me to justify CIC routing in M3UA: I don't think it
can work for a number of other reasons.  For example, what happens when
an IAM arrives for CIC=5288?  What AS does it go to?  Who sends back
REL(Unequipped CIC) and runs that whole part of the state machine?

When a remove ISUP is unavailable, where does DUPU get sent?  Which AS
is responsible for testing the availability of the remote ISUP?

When congestion occurs, which AS is responsible for detecting it an
placing ACL parameters into REL messages?

How much of the ISUP state machines must the SG implement before it can
route on CIC?

I think that, although one can loadshare on CIC, that routing on CIC
is a bad idea.  ISUP should be routed on OPC/DPC/SI=5 at maximum
granularity.  Then if one loadshares CIC over ASPs, it makes more sense.

At any rate, there is a lot of description missing from the M3UA spec
that would allow two implementation to interoperate properly as far as CIC
routing is concerned.

--brian

Wung, Joseph wrote:                        (Thu, 02 Jan 2003 09:39:43)
> Brian,
> 
> It is not up to the ASP or AS.  The SS7 side can choose
> to opearate on any circuit group as they want.
> 
> For example, 
> ASP-a serves AS-1(CIC=5000~5071) and 
> 		 AS-2(CIC=5072~5143),
>  
> ASP-b serves AS-3(CIC=5144~5215) and
> 		 AS-4(CIC=5216~5287)
> 
> Neither the ASPs nor the ASes are splitting anything here.
> The SS7 side can send a group related ISUP message, e.g.,
> CGB, using any 24 circuit range across 5000~5287.  I
> guess this is legal for them to do so.
> 
> But this would cause the SG send the message to ASP-a if 
> the CIC range in the CGB crosses the ASP boundary, or cause
> one ASP to send it to AS-1 or AS-3 if crossing the AS 
> boundary.
> 
> Joe 
> 

-- 
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 Jan  2 13:28: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 NAA10826
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 13:28:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02IaYg11115
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 13:36:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02Ia4J11089;
	Thu, 2 Jan 2003 13:36:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02IZxJ11074
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 13:35:59 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10772
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 13:26:21 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:liKnJaEmgnhmAL5t62KGYKzezB5FZVfE@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h02IT8D06176;
	Thu, 2 Jan 2003 11:29:08 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h02FoVP15915;
	Thu, 2 Jan 2003 08:50:31 -0700
Date: Thu, 2 Jan 2003 08:50:31 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Sanjeev P.J" <jaya.panem@mahindrabt.com>
Cc: "Wung, Joseph" <JWung@sonusnet.com>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030102085031.B14969@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Sanjeev P.J" <jaya.panem@mahindrabt.com>,
	"Wung, Joseph" <JWung@sonusnet.com>, sigtran@ietf.org
References: <4CF48720B6E9D4118D040060CF2074E9072F6B8D@sonusdc3.sonusnet.com> <NEBBJFMCBDDCAGAJKJCDCEAECMAA.jaya.panem@mahindrabt.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: <NEBBJFMCBDDCAGAJKJCDCEAECMAA.jaya.panem@mahindrabt.com>; from jaya.panem@mahindrabt.com on Thu, Jan 02, 2003 at 08:46:45PM +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>

Sanjeev,

Sanjeev P.J wrote:                                                                 (Thu, 02 Jan 2003 20:46:45)
> True. But the response can have "no indication" for the CICs outside the
> range defined for the AS allowing the other end to resend the group message
> with the modified range.
> 
> Can't this be done??
> 

Yes it could, but maintenance would probably be informed, generating log
records and possibly alarms.  It would not be a good way to go about things
in the normal course of events.

--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  Thu Jan  2 14:21: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 OAA11897
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 14:21:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02JTnF14788
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 14:29:49 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02JT9J14767;
	Thu, 2 Jan 2003 14:29:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02JSpJ14726
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 14:28:51 -0500
Received: from web8206.mail.in.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA11878
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 14:19:55 -0500 (EST)
Message-ID: <20030102192305.751.qmail@web8206.mail.in.yahoo.com>
Received: from [61.1.106.214] by web8206.mail.in.yahoo.com via HTTP; Thu, 02 Jan 2003 19:23:05 GMT
Date: Thu, 2 Jan 2003 19:23:05 +0000 (GMT)
From: =?iso-8859-1?q?amit=20somani?= <amitksomani@yahoo.co.in>
To: sigtran@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Sigtran] Query from a group of students
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

Hello everyone,

We are a group of 3 students, Anup Deshpande, Prasad
Edlabadkar and Amit Somanai, from Pune Institute of
Computer Technology ,Pune , India. We are studying in
the 4th year(i.e. final year) of Electronics &
Telecommunication Engineering. We have a thrust for
cutting edge technology and love working on
challenging projects. We also like working on
innovative ideas. Right now we are working on our
final year project. The basic Project idea was to
transport SS7 signals using TCP. But then we came
across the disadvantages of TCP.
So we have three options with us :
1. Using SCTP instead of TCP at the transport level
2. Using Sigtran stack
3. Using UDP and develop some application level on it 

The problem is we don`t know which one is actually
feasible. We are implementing the project in Linux. Is
there any Linux Kernel that is supporting SCTP. Can
you suggest any small module that is still to
implemented?

amit. 


________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
       visit http://in.tv.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jan  2 14:36: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 OAA12393
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 14:36:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h02JjEa16230
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 14:45:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02JiOJ16168;
	Thu, 2 Jan 2003 14:44:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02JhLJ16117
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 14:43:21 -0500
Received: from revere.sonusnet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12335
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 14:34:24 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3.sonusnet.com [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h02Jb0S20392;
	Thu, 2 Jan 2003 14:37:00 -0500 (EST)
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19)
	id <Y68HR2D6>; Thu, 2 Jan 2003 14:37:29 -0500
Message-ID: <4CF48720B6E9D4118D040060CF2074E9072F6B90@sonusdc3.sonusnet.com>
From: "Wung, Joseph" <JWung@sonusnet.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>,
        "Wung, Joseph"
	 <JWung@sonusnet.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
Date: Thu, 2 Jan 2003 14:37:25 -0500 
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,

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Thursday, January 02, 2003 10:49 AM
> To: Wung, Joseph
> Cc: 'sigtran@ietf.org'
> Subject: Re: [Sigtran] M3UA distributing ISUP group messages
> 
> 
> Joseph,
> 
> Several ways around that:
> 
>  o always configure your ISUP switches for pre-arranged 
> circuit groups.
> 
>  o always configure your ISUP switches for the same circuit groups on
>    both ends of the trunk.
> 
> Then you won't have this spanning problem.

Can you please elaborate using my example below?

> 
> I think that, although one can loadshare on CIC, that routing on CIC
> is a bad idea.  ISUP should be routed on OPC/DPC/SI=5 at maximum
> granularity.  Then if one loadshares CIC over ASPs, it makes 
> more sense.

Can you please elaborate?

> 
> At any rate, there is a lot of description missing from the M3UA spec
> that would allow two implementation to interoperate properly 
> as far as CIC
> routing is concerned.
> 
> --brian
> 
> Wung, Joseph wrote:                        (Thu, 02 Jan 2003 09:39:43)
> > Brian,
> > 
> > It is not up to the ASP or AS.  The SS7 side can choose
> > to opearate on any circuit group as they want.
> > 
> > For example, 
> > ASP-a serves AS-1(CIC=5000~5071) and 
> > 		 AS-2(CIC=5072~5143),
> >  
> > ASP-b serves AS-3(CIC=5144~5215) and
> > 		 AS-4(CIC=5216~5287)
> > 
> > Neither the ASPs nor the ASes are splitting anything here.
> > The SS7 side can send a group related ISUP message, e.g.,
> > CGB, using any 24 circuit range across 5000~5287.  I
> > guess this is legal for them to do so.
> > 
> > But this would cause the SG send the message to ASP-a if 
> > the CIC range in the CGB crosses the ASP boundary, or cause
> > one ASP to send it to AS-1 or AS-3 if crossing the AS 
> > boundary.
> > 
> > Joe 
> > 
> 
> -- 
> 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 Jan  2 19:23: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 TAA17772
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 19:23:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h030WLg02698
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 19:32:21 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h030VdJ02671;
	Thu, 2 Jan 2003 19:31:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h030TQJ02573
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 19:29:26 -0500
Received: from web12805.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA17693
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 19:20:24 -0500 (EST)
Message-ID: <20030103002335.65382.qmail@web12805.mail.yahoo.com>
Received: from [62.29.65.254] by web12805.mail.yahoo.com via HTTP; Thu, 02 Jan 2003 16:23:35 PST
Date: Thu, 2 Jan 2003 16:23:35 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Routing Key
To: sigtran@ietf.org
In-Reply-To: <20030102062046.A7412@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 F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> Tolga Asveren wrote:                        (Thu, 02
> Jan 2003 05:05:43)
> > > 
> > > Read the thread.
> > [TOLGA] Which one/time?
> 
> See my third note on *this* thread.
[TOLGA] I still don't see why any change is necessary
for the on the wire M3UA protocol to support SSN based
routing for class0/class1 SCCP. One migth need to
implement most of SUA/SCCP management functiuonality
in NIF, but this is not a change to M3UA protocol
itself.
> 
> --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! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jan  2 19:29:56 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 TAA17900
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 19:29:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h030cRC03607
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 19:38:27 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h030c8J03575;
	Thu, 2 Jan 2003 19:38:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h030bSJ03445
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 19:37:28 -0500
Received: from web12803.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA17857
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 19:28:26 -0500 (EST)
Message-ID: <20030103003137.33230.qmail@web12803.mail.yahoo.com>
Received: from [62.29.65.254] by web12803.mail.yahoo.com via HTTP; Thu, 02 Jan 2003 16:31:37 PST
Date: Thu, 2 Jan 2003 16:31:37 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA - ASP UP and ASP DN in Double Exchange
To: sigtran@ietf.org
In-Reply-To: <20030102063918.E7412@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,
> 02 Jan 2003 05:34:45)
> 
> -X- snip -X-
> > But having double ASPUP/ASPDN might have the
> > advantage, that one can use ASP/SGP state machines
> > unmodified (the reason why so many people were
> > attracted by DE model initially, including me)
> 
> Dream.  You cannot reuse the ASP/SGP state machines
> for DE, only
> for SE.  This is because DE only handles half
> traffic flows,
> whereas the normal ASP/SGP state machines handle
> traffic flow in
> both directions, just as does SE.
[TOLGA] This all depends how you model it. If one
thinks DE as ASP+SGP(IMO, this is what DE is), then
between two IPSP there are two bidirectional traffic
flows, but for each of them only one direction is
used. That it is not used does not mean, that it is
not opened.
> --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! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jan  2 19:39: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 TAA18142
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 19:39:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h030lnA04027
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 19:47:49 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h030lAJ03990;
	Thu, 2 Jan 2003 19:47:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h030k8J03957
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 19:46:08 -0500
Received: from web12803.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA18114
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 19:37:05 -0500 (EST)
Message-ID: <20030103004017.34113.qmail@web12803.mail.yahoo.com>
Received: from [62.29.65.254] by web12803.mail.yahoo.com via HTTP; Thu, 02 Jan 2003 16:40:17 PST
Date: Thu, 2 Jan 2003 16:40:17 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <4CF48720B6E9D4118D040060CF2074E9072F6B8E@sonusdc3.sonusnet.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>

Joe,
--- "Wung, Joseph" <JWung@sonusnet.com> wrote:
> Sanjeev,
> 
> No.
> 
> ANSIT1.113-4 Section 2.8.2.3
> 
> "When an exchange upon receipt of a CGB Message in
> not
> able to give an appropriate blocking acknowledgement
> 
> indication for each CIC ..., then no blocking 
> acknowledgement indication" relating
> to that/those CICs shall be given in the Status
> field
> of the corrsponding CGBA Message which shall be sent
> in response."  
> 
> "If a CGBA message in response to a CGB Message is
> received containing in the status field the
> indications
> no blocking acknowledgement for some or all of the 
> circuits which are to be blocked due to the
> previously
> sent CGB Message, then the maintenance personnel
> should
> be notified for the circuits concerned"
> 
> How is the CGBA receiving side at the SS7 network to
> 
> know a modifed CGB message would work.  I don't see 
> M3UA has a solution here.
[TOLGA] IMO it is not very correct to say that "M3UA
has no solution" for this or similar situations. If
RKs based on constructs which are not native to MTP3
are used , one has to implement the necessary
mananegement functionality on NIF. This migth be
ugly/bad/difficult/not elegant/not recommended but IMO
is a valid solution.

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jan  2 19:43: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 TAA18224
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 19:43:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h030plV04200
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 19:51:47 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h030p8J04173;
	Thu, 2 Jan 2003 19:51:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h030opJ04150
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 19:50:51 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18209
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 19:41:49 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:RLw5l+6G/g+kJNGzHekWWMUvDcsjDWQ/@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h030j0D14137;
	Thu, 2 Jan 2003 17:45:00 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h030j0e01467;
	Thu, 2 Jan 2003 17:45:00 -0700
Date: Thu, 2 Jan 2003 17:45:00 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Routing Key
Message-ID: <20030102174500.F26898@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030102062046.A7412@openss7.org> <20030103002335.65382.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: <20030103002335.65382.qmail@web12805.mail.yahoo.com>; from tolga_asveren@yahoo.com on Thu, Jan 02, 2003 at 04:23:35PM -0800
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, 02 Jan 2003 16:23:35)
> 
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                        (Thu, 02
> > Jan 2003 05:05:43)
> > > > 
> > > > Read the thread.
> > > [TOLGA] Which one/time?
> > 
> > See my third note on *this* thread.
> [TOLGA] I still don't see why any change is necessary
> for the on the wire M3UA protocol to support SSN based
> routing for class0/class1 SCCP. One migth need to
> implement most of SUA/SCCP management functiuonality
> in NIF, but this is not a change to M3UA protocol
> itself.

The client needs to know what it is a client of.

--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  Thu Jan  2 19:44: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 TAA18259
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 19:44:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h030rHa04297
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 19:53:17 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h030r8J04287;
	Thu, 2 Jan 2003 19:53:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h030qlJ04261
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 19:52:47 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18244
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 19:43:45 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:jDhNFghvUnBRaNnV76D06vI+5lfrIREy@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h030kuD14164;
	Thu, 2 Jan 2003 17:46:56 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h030kuJ01506;
	Thu, 2 Jan 2003 17:46:56 -0700
Date: Thu, 2 Jan 2003 17:46:56 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA - ASP UP and ASP DN in Double Exchange
Message-ID: <20030102174656.G26898@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030102063918.E7412@openss7.org> <20030103003137.33230.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: <20030103003137.33230.qmail@web12803.mail.yahoo.com>; from tolga_asveren@yahoo.com on Thu, Jan 02, 2003 at 04:31:37PM -0800
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, 02 Jan 2003 16:31:37)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                           (Thu,
> > 02 Jan 2003 05:34:45)
> > 
> > -X- snip -X-
> > > But having double ASPUP/ASPDN might have the
> > > advantage, that one can use ASP/SGP state machines
> > > unmodified (the reason why so many people were
> > > attracted by DE model initially, including me)
> > 
> > Dream.  You cannot reuse the ASP/SGP state machines
> > for DE, only
> > for SE.  This is because DE only handles half
> > traffic flows,
> > whereas the normal ASP/SGP state machines handle
> > traffic flow in
> > both directions, just as does SE.
> [TOLGA] This all depends how you model it. If one
> thinks DE as ASP+SGP(IMO, this is what DE is), then
> between two IPSP there are two bidirectional traffic
> flows, but for each of them only one direction is
> used. That it is not used does not mean, that it is
> not opened.

Take a look back on the SE/DE threads.  It was fairly proven
that DE does not reuse the ASP/SGP state machine.  Instead it
uses half of them an places new requirements for coordinating
the other half-flow with the first.  DE is the criss-crossed
model (there is no other way for it to work).

--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  Thu Jan  2 19:46:50 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 TAA18330
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 19:46:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h030tLo04393
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 19:55:21 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h030t5J04380;
	Thu, 2 Jan 2003 19:55:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h030snJ04355
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 19:54:50 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18303
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 19:45:47 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:eqbhgqOyASxaRwjpsNUN5LNiQlnbafzB@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h030mxD14192;
	Thu, 2 Jan 2003 17:48:59 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h030mwQ01577;
	Thu, 2 Jan 2003 17:48:58 -0700
Date: Thu, 2 Jan 2003 17:48:58 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030102174858.H26898@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <4CF48720B6E9D4118D040060CF2074E9072F6B8E@sonusdc3.sonusnet.com> <20030103004017.34113.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: <20030103004017.34113.qmail@web12803.mail.yahoo.com>; from tolga_asveren@yahoo.com on Thu, Jan 02, 2003 at 04:40:17PM -0800
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, 02 Jan 2003 16:40:17)
> Joe,
> --- "Wung, Joseph" <JWung@sonusnet.com> wrote:
> > Sanjeev,
> > 
> > No.
> > 
> > ANSIT1.113-4 Section 2.8.2.3
> > 
> > "When an exchange upon receipt of a CGB Message in
> > not
> > able to give an appropriate blocking acknowledgement
> > 
> > indication for each CIC ..., then no blocking 
> > acknowledgement indication" relating
> > to that/those CICs shall be given in the Status
> > field
> > of the corrsponding CGBA Message which shall be sent
> > in response."  
> > 
> > "If a CGBA message in response to a CGB Message is
> > received containing in the status field the
> > indications
> > no blocking acknowledgement for some or all of the 
> > circuits which are to be blocked due to the
> > previously
> > sent CGB Message, then the maintenance personnel
> > should
> > be notified for the circuits concerned"
> > 
> > How is the CGBA receiving side at the SS7 network to
> > 
> > know a modifed CGB message would work.  I don't see 
> > M3UA has a solution here.
> [TOLGA] IMO it is not very correct to say that "M3UA
> has no solution" for this or similar situations. If
> RKs based on constructs which are not native to MTP3
> are used , one has to implement the necessary
> mananegement functionality on NIF. This migth be
> ugly/bad/difficult/not elegant/not recommended but IMO
> is a valid solution.

Or, in this case, not specified by M3UA and therefore not
supported by M3UA: i.e. M3UA does not have a solution here.

--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  Thu Jan  2 19:54:17 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 TAA18433
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 19:54:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0312mI04699
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 20:02:48 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03128J04677;
	Thu, 2 Jan 2003 20:02:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0311JJ04650
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 20:01:19 -0500
Received: from web12804.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA18406
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 19:52:16 -0500 (EST)
Message-ID: <20030103005526.71643.qmail@web12804.mail.yahoo.com>
Received: from [62.29.65.254] by web12804.mail.yahoo.com via HTTP; Thu, 02 Jan 2003 16:55:26 PST
Date: Thu, 2 Jan 2003 16:55:26 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <20030102174858.H26898@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, 02 Jan 2003
> 16:40:17)
> > Joe,
> > --- "Wung, Joseph" <JWung@sonusnet.com> wrote:
> > > Sanjeev,
> > > 
> > > No.
> > > 
> > > ANSIT1.113-4 Section 2.8.2.3
> > > 
> > > "When an exchange upon receipt of a CGB Message
> in
> > > not
> > > able to give an appropriate blocking
> acknowledgement
> > > 
> > > indication for each CIC ..., then no blocking 
> > > acknowledgement indication" relating
> > > to that/those CICs shall be given in the Status
> > > field
> > > of the corrsponding CGBA Message which shall be
> sent
> > > in response."  
> > > 
> > > "If a CGBA message in response to a CGB Message
> is
> > > received containing in the status field the
> > > indications
> > > no blocking acknowledgement for some or all of
> the 
> > > circuits which are to be blocked due to the
> > > previously
> > > sent CGB Message, then the maintenance personnel
> > > should
> > > be notified for the circuits concerned"
> > > 
> > > How is the CGBA receiving side at the SS7
> network to
> > > 
> > > know a modifed CGB message would work.  I don't
> see 
> > > M3UA has a solution here.
> > [TOLGA] IMO it is not very correct to say that
> "M3UA
> > has no solution" for this or similar situations.
> If
> > RKs based on constructs which are not native to
> MTP3
> > are used , one has to implement the necessary
> > mananegement functionality on NIF. This migth be
> > ugly/bad/difficult/not elegant/not recommended but
> IMO
> > is a valid solution.
> 
> Or, in this case, not specified by M3UA and
> therefore not
> supported by M3UA: i.e. M3UA does not have a
> solution here.
[TOLGA] IMO, if one wants to support RKs based on CIC
ranges, what needs to be done is taking the relevant
ISUP specifications, and implementing necessary
functionality in NIF. I don't think it is a very good
idea to explain in detail for each and every case,
what needs to be done. Is there a message from SS7
with a CIC value not mapping to any AS? Then IMO what
needs to be done is trying to imitate ISUP, where the
procedure is explained in ISUP specification.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jan  2 19:58:15 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 TAA18504
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 19:58:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0316l304874
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 20:06:47 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03167J04853;
	Thu, 2 Jan 2003 20:06:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0315JJ04793
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 20:05:19 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18472
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 19:56:16 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:4TKYY0+CQpSLATAUIKaRIkU9YDf5yztk@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h030xSD14328;
	Thu, 2 Jan 2003 17:59:28 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h030xSB01896;
	Thu, 2 Jan 2003 17:59:28 -0700
Date: Thu, 2 Jan 2003 17:59:28 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Wung, Joseph" <JWung@sonusnet.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030102175928.I26898@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Wung, Joseph" <JWung@sonusnet.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <4CF48720B6E9D4118D040060CF2074E9072F6B90@sonusdc3.sonusnet.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: <4CF48720B6E9D4118D040060CF2074E9072F6B90@sonusdc3.sonusnet.com>; from JWung@sonusnet.com on Thu, Jan 02, 2003 at 02:37:25PM -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>

Wung,,

Wung, Joseph wrote:                                                                  (Thu, 02 Jan 2003 14:37:25)
> Brian,
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Thursday, January 02, 2003 10:49 AM
> > To: Wung, Joseph
> > Cc: 'sigtran@ietf.org'
> > Subject: Re: [Sigtran] M3UA distributing ISUP group messages
> > 
> > 
> > Joseph,
> > 
> > Several ways around that:
> > 
> >  o always configure your ISUP switches for pre-arranged 
> > circuit groups.
> > 
> >  o always configure your ISUP switches for the same circuit groups on
> >    both ends of the trunk.
> > 
> > Then you won't have this spanning problem.
> 
> Can you please elaborate using my example below?

Well, I presume you are talking about ANSI ISUP, because ITU/ETSI
tends to keep its circuit groups within the E1 span and makes little
provisions for DS0 cross-connect between switches.  Under ANSI, it is
still the case that hardware oriented group reset, blocking and
unblocking is span based: it is just that DSO cross-connect between the
spans causes problems (in both it causes difficulties with CIC assignment
anyway).  The maximum number is 24 for a reason: that's the number of
circuits in a T1 span.

If you configure both the remote switch and the MGC so that CIC are
correctly organized into spans and group messages are generated a span
basis (or by pre-arrangement in ANSI), then you will never get a group
message which straddles a T1 span, and you can arrange your CICs into AS
so that a group message will never span an AS.

> 
> > 
> > I think that, although one can loadshare on CIC, that routing on CIC
> > is a bad idea.  ISUP should be routed on OPC/DPC/SI=5 at maximum
> > granularity.  Then if one loadshares CIC over ASPs, it makes 
> > more sense.
> 
> Can you please elaborate?

The AS routing Key would be DPC=PCA, OPC=PCB, SI=ISUP, representing all the
circuits between two switches and the MTP accessibility and User Part
accessibility as well within the same AS.

Make it a load-share AS.  Instead of "routing" to the ASPs within this AS
using the Routing Key, "load-share" over the ASPs in this AS using CIC.
As each AS must be prepared in a Load-share AS to receive any message, there
is no problem with circuit group management, but the load-sharing could use
the above technique to keep from splitting circuit groups across ASPs.
Then SSNM messages (including DUPU) go to the correct place: all the ASPs
in the ASP-ACTIVE state for the AS.

--brian

> 
> > 
> > At any rate, there is a lot of description missing from the M3UA spec
> > that would allow two implementation to interoperate properly 
> > as far as CIC
> > routing is concerned.
> > 
> > --brian
> > 
> > Wung, Joseph wrote:                        (Thu, 02 Jan 2003 09:39:43)
> > > Brian,
> > > 
> > > It is not up to the ASP or AS.  The SS7 side can choose
> > > to opearate on any circuit group as they want.
> > > 
> > > For example, 
> > > ASP-a serves AS-1(CIC=5000~5071) and 
> > > 		 AS-2(CIC=5072~5143),
> > >  
> > > ASP-b serves AS-3(CIC=5144~5215) and
> > > 		 AS-4(CIC=5216~5287)
> > > 
> > > Neither the ASPs nor the ASes are splitting anything here.
> > > The SS7 side can send a group related ISUP message, e.g.,
> > > CGB, using any 24 circuit range across 5000~5287.  I
> > > guess this is legal for them to do so.
> > > 
> > > But this would cause the SG send the message to ASP-a if 
> > > the CIC range in the CGB crosses the ASP boundary, or cause
> > > one ASP to send it to AS-1 or AS-3 if crossing the AS 
> > > boundary.
> > > 
> > > Joe 
> > > 
> > 
> > -- 
> > 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 mailnull@www1.ietf.org  Thu Jan  2 20:05: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 UAA18726
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 20:05:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h031E2105833
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 20:14:02 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h031DNJ05806;
	Thu, 2 Jan 2003 20:13:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h031C3J05744
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 20:12:03 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18662
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 20:03:00 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:1kYPmwd6uKLGe+sDG3mqLoOKB9lnwJXg@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0316CD14442;
	Thu, 2 Jan 2003 18:06:12 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0316BL02219;
	Thu, 2 Jan 2003 18:06:11 -0700
Date: Thu, 2 Jan 2003 18:06:11 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030102180611.J26898@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030102174858.H26898@openss7.org> <20030103005526.71643.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: <20030103005526.71643.qmail@web12804.mail.yahoo.com>; from tolga_asveren@yahoo.com on Thu, Jan 02, 2003 at 04:55:26PM -0800
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, 02 Jan 2003 16:55:26)
> [TOLGA] IMO, if one wants to support RKs based on CIC
> ranges, what needs to be done is taking the relevant
> ISUP specifications, and implementing necessary
> functionality in NIF. I don't think it is a very good
> idea to explain in detail for each and every case,
> what needs to be done. Is there a message from SS7
> with a CIC value not mapping to any AS? Then IMO what
> needs to be done is trying to imitate ISUP, where the
> procedure is explained in ISUP specification.

In this fantastic SG implementation, what user is there at the
AS?  It is obviously not an MTP-User, but something higher-up in
ISUP.  That interface has not been specified in M3UA and
therefore interoperability cannot be acheived.

Where there is no interoperability there is no IETF standard.
Thus, M3UA does not support this.  Your bundle-fly M3UA might,
but then than would be a creature of your own making and not
the IETF standard.

Because there can be no interoperability without at least an
interface specification, it is not too strong to say that:

   M3UA MUST NOT route on SSN.

Besides, it was the concensus of the LC thread to strike them
along with the TIDs.  Greg just got tied up at about that time.

If you want to use them, you need to describe the interface
between your bundle-fly NIF and the AS-User, because it is not
the MTP/MTP-User interface that M3UA claims to transparently
preserve.

--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  Thu Jan  2 20:14: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 UAA18854
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 20:14:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h031Mc506223
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 20:22:38 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h031M5J06200;
	Thu, 2 Jan 2003 20:22:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h031L5J06159
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 20:21:05 -0500
Received: from web12808.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA18828
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 20:12:02 -0500 (EST)
Message-ID: <20030103011514.26796.qmail@web12808.mail.yahoo.com>
Received: from [62.29.65.254] by web12808.mail.yahoo.com via HTTP; Thu, 02 Jan 2003 17:15:14 PST
Date: Thu, 2 Jan 2003 17:15:14 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <20030102180611.J26898@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, 02 Jan 2003
> 16:55:26)
> > [TOLGA] IMO, if one wants to support RKs based on
> CIC
> > ranges, what needs to be done is taking the
> relevant
> > ISUP specifications, and implementing necessary
> > functionality in NIF. I don't think it is a very
> good
> > idea to explain in detail for each and every case,
> > what needs to be done. Is there a message from SS7
> > with a CIC value not mapping to any AS? Then IMO
> what
> > needs to be done is trying to imitate ISUP, where
> the
> > procedure is explained in ISUP specification.
> 
> In this fantastic SG implementation, what user is
> there at the
> AS?  It is obviously not an MTP-User, but something
> higher-up in
> ISUP.  That interface has not been specified in M3UA
> and
> therefore interoperability cannot be acheived.
[TOLGA] No change is necessary on ASP side. 
> 
> Where there is no interoperability there is no IETF
> standard.
> Thus, M3UA does not support this.  Your bundle-fly
> M3UA might,
> but then than would be a creature of your own making
> and not
> the IETF standard.
[TOLGA] One can speak of interoperability, if there is
a procedure, which needs coordinated involvement of
both SGP and ASP. If necessary procedures are
implemented on SGP and no change is required on ASP,
nothing is changed from M3UA point of view. If changes
on SGP mandate any change on ASP, then I would agree
with you.
> 
> Because there can be no interoperability without at
> least an
> interface specification, it is not too strong to say
> that:
> 
>    M3UA MUST NOT route on SSN.
> 
> Besides, it was the concensus of the LC thread to
> strike them
> along with the TIDs.  Greg just got tied up at about
> that time.
[TOLGA] That M3UA is not friendly to support them and
so they shouldn't be given as examples and saying that
they MUST NOT be used are very different things.
> 
> If you want to use them, you need to describe the
> interface
> between your bundle-fly NIF and the AS-User, because
> it is not
> the MTP/MTP-User interface that M3UA claims to
> transparently
> preserve.
[TOLGA] No, the MTP/MTP-User interface will be
preserved. That you go up on the stack when
necessary(in fact you don't, you can put whatever you
like to NIF, i.e. also the necessary management
functionality) does not mean that you can again go
down before leaving the node.
> 
> --brian
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jan  2 20: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 UAA18995
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 20:24:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h031X7b06631
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 20:33:07 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h031WQJ06565;
	Thu, 2 Jan 2003 20:32:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h031VJJ06548
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 20:31:19 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18934
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 20:22:15 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:UlNpG62zeV1/KuCr7guK562ESBZsP+jf@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h031PRD14656;
	Thu, 2 Jan 2003 18:25:27 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h031PRo02746;
	Thu, 2 Jan 2003 18:25:27 -0700
Date: Thu, 2 Jan 2003 18:25:26 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030102182526.K26898@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030102180611.J26898@openss7.org> <20030103011514.26796.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: <20030103011514.26796.qmail@web12808.mail.yahoo.com>; from tolga_asveren@yahoo.com on Thu, Jan 02, 2003 at 05:15:14PM -0800
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, 02 Jan 2003 17:15:14)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Thu, 02 Jan 2003
> > 16:55:26)
> > > [TOLGA] IMO, if one wants to support RKs based on
> > CIC
> > > ranges, what needs to be done is taking the
> > relevant
> > > ISUP specifications, and implementing necessary
> > > functionality in NIF. I don't think it is a very
> > good
> > > idea to explain in detail for each and every case,
> > > what needs to be done. Is there a message from SS7
> > > with a CIC value not mapping to any AS? Then IMO
> > what
> > > needs to be done is trying to imitate ISUP, where
> > the
> > > procedure is explained in ISUP specification.
> > 
> > In this fantastic SG implementation, what user is
> > there at the
> > AS?  It is obviously not an MTP-User, but something
> > higher-up in
> > ISUP.  That interface has not been specified in M3UA
> > and
> > therefore interoperability cannot be acheived.
> [TOLGA] No change is necessary on ASP side. 

An AS that cannot be sure that the CGBA in response
to its CGB will come back to it, needs to be changed.

An AS that cannot be implemented with the lower boundary
primitives (MTP/MTP-User) specified in the ISUP standards
needs a change.

> > 
> > Where there is no interoperability there is no IETF
> > standard.
> > Thus, M3UA does not support this.  Your bundle-fly
> > M3UA might,
> > but then than would be a creature of your own making
> > and not
> > the IETF standard.
> [TOLGA] One can speak of interoperability, if there is
> a procedure, which needs coordinated involvement of
> both SGP and ASP. If necessary procedures are
> implemented on SGP and no change is required on ASP,

First specify an interface (because MTP/MTP-User will not
do) and then worry about procedures.  You don't even have
an interface specification to work to: how are you going
to describe procedures?

> nothing is changed from M3UA point of view. If changes
> on SGP mandate any change on ASP, then I would agree
> with you.

Change is required on the the ASP, so I suppose you agree.

> > 
> > Because there can be no interoperability without at
> > least an
> > interface specification, it is not too strong to say
> > that:
> > 
> >    M3UA MUST NOT route on SSN.
> > 
> > Besides, it was the concensus of the LC thread to
> > strike them
> > along with the TIDs.  Greg just got tied up at about
> > that time.
> [TOLGA] That M3UA is not friendly to support them and
> so they shouldn't be given as examples and saying that
> they MUST NOT be used are very different things.

The concensus on the thread was that M3UA should stick to
MTP information for routing. (Gee, that sounds like what
MTP does...)

> > 
> > If you want to use them, you need to describe the
> > interface
> > between your bundle-fly NIF and the AS-User, because
> > it is not
> > the MTP/MTP-User interface that M3UA claims to
> > transparently
> > preserve.
> [TOLGA] No, the MTP/MTP-User interface will be
> preserved. That you go up on the stack when
> necessary(in fact you don't, you can put whatever you
> like to NIF, i.e. also the necessary management
> functionality) does not mean that you can again go
> down before leaving the node.

It is not preserved.  That's why there is a problem with
circuit group management and unequipped CIC messages and
ACL congestion controls and ITU response to point code
congestion and inaccessibility of user parts and ...

You will have to back that statement up by demonstrating
to us how all these things will be handled for CIC routed
AS using the MTP/MTP-User interface as specified in the
standards.

You will need to describe all that M3UA lacks in support
of CIC routing.  Once you are finished that exercise you
will have ISUA.  (As mentioned on the original thread
from July 2001.)

--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  Thu Jan  2 22:35: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 WAA21663
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 22:35:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h033i1K14147
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 22:44:01 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h033hNJ14117;
	Thu, 2 Jan 2003 22:43:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h033gAJ14083
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 22:42:10 -0500
Received: from web12801.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA21644
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 22:33:02 -0500 (EST)
Message-ID: <20030103033615.98167.qmail@web12801.mail.yahoo.com>
Received: from [62.29.84.14] by web12801.mail.yahoo.com via HTTP; Thu, 02 Jan 2003 19:36:15 PST
Date: Thu, 2 Jan 2003 19:36:15 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <20030102182526.K26898@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, 02 Jan 2003
> 17:15:14)
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Tolga Asveren wrote:                            
>    
> > >                                 (Thu, 02 Jan
> 2003
> > > 16:55:26)
> > > > [TOLGA] IMO, if one wants to support RKs based
> on
> > > CIC
> > > > ranges, what needs to be done is taking the
> > > relevant
> > > > ISUP specifications, and implementing
> necessary
> > > > functionality in NIF. I don't think it is a
> very
> > > good
> > > > idea to explain in detail for each and every
> case,
> > > > what needs to be done. Is there a message from
> SS7
> > > > with a CIC value not mapping to any AS? Then
> IMO
> > > what
> > > > needs to be done is trying to imitate ISUP,
> where
> > > the
> > > > procedure is explained in ISUP specification.
> > > 
> > > In this fantastic SG implementation, what user
> is
> > > there at the
> > > AS?  It is obviously not an MTP-User, but
> something
> > > higher-up in
> > > ISUP.  That interface has not been specified in
> M3UA
> > > and
> > > therefore interoperability cannot be acheived.
> > [TOLGA] No change is necessary on ASP side. 
> 
> An AS that cannot be sure that the CGBA in response
> to its CGB will come back to it, needs to be
> changed.
> 
> An AS that cannot be implemented with the lower
> boundary
> primitives (MTP/MTP-User) specified in the ISUP
> standards
> needs a change.
> 
> > > 
> > > Where there is no interoperability there is no
> IETF
> > > standard.
> > > Thus, M3UA does not support this.  Your
> bundle-fly
> > > M3UA might,
> > > but then than would be a creature of your own
> making
> > > and not
> > > the IETF standard.
> > [TOLGA] One can speak of interoperability, if
> there is
> > a procedure, which needs coordinated involvement
> of
> > both SGP and ASP. If necessary procedures are
> > implemented on SGP and no change is required on
> ASP,
> 
> First specify an interface (because MTP/MTP-User
> will not
> do) and then worry about procedures.  You don't even
> have
> an interface specification to work to: how are you
> going
> to describe procedures?
> 
> > nothing is changed from M3UA point of view. If
> changes
> > on SGP mandate any change on ASP, then I would
> agree
> > with you.
> 
> Change is required on the the ASP, so I suppose you
> agree.
> 
> > > 
> > > Because there can be no interoperability without
> at
> > > least an
> > > interface specification, it is not too strong to
> say
> > > that:
> > > 
> > >    M3UA MUST NOT route on SSN.
> > > 
> > > Besides, it was the concensus of the LC thread
> to
> > > strike them
> > > along with the TIDs.  Greg just got tied up at
> about
> > > that time.
> > [TOLGA] That M3UA is not friendly to support them
> and
> > so they shouldn't be given as examples and saying
> that
> > they MUST NOT be used are very different things.
> 
> The concensus on the thread was that M3UA should
> stick to
> MTP information for routing. (Gee, that sounds like
> what
> MTP does...)
> 
> > > 
> > > If you want to use them, you need to describe
> the
> > > interface
> > > between your bundle-fly NIF and the AS-User,
> because
> > > it is not
> > > the MTP/MTP-User interface that M3UA claims to
> > > transparently
> > > preserve.
> > [TOLGA] No, the MTP/MTP-User interface will be
> > preserved. That you go up on the stack when
> > necessary(in fact you don't, you can put whatever
> you
> > like to NIF, i.e. also the necessary management
> > functionality) does not mean that you can again go
> > down before leaving the node.
> 
> It is not preserved.  That's why there is a problem
> with
> circuit group management and unequipped CIC messages
> and
> ACL congestion controls and ITU response to point
> code
> congestion and inaccessibility of user parts and ...
> 
> You will have to back that statement up by
> demonstrating
> to us how all these things will be handled for CIC
> routed
> AS using the MTP/MTP-User interface as specified in
> the
> standards.
> 
> You will need to describe all that M3UA lacks in
> support
> of CIC routing.  Once you are finished that exercise
> you
> will have ISUA.  (As mentioned on the original
> thread
> from July 2001.)
[TOLGA] For example for the case Joe has presented,
how it should work IMO with a pure M3UA solution is:
CGB arrives. If the range spans multiple RKs, SG
should generate multiple CGBs, pack them properly and
send them to the corresponding ASPs serving the
relevant AS. I agree, this is ugly and even arguably
against the spirit of a layered approach, but if one
wants to support RKs based on CIC ranges with M3UA,
this is the solution. So, what SG is doing is
filter/generate ISUP/SCCP messages for management
purposes to support CIC/SSN based routing. Where is
the change to M3UA protocol and to the interface
between SGP/ASP? 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jan  2 22:53: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 WAA21929
	for <sigtran-archive@odin.ietf.org>; Thu, 2 Jan 2003 22:53:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0341b114755
	for sigtran-archive@odin.ietf.org; Thu, 2 Jan 2003 23:01:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0341AJ14739;
	Thu, 2 Jan 2003 23:01:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0340nJ14706
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 23:00:49 -0500
Received: from web12807.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA21922
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 22:51:43 -0500 (EST)
Message-ID: <20030103035454.54447.qmail@web12807.mail.yahoo.com>
Received: from [62.29.84.14] by web12807.mail.yahoo.com via HTTP; Thu, 02 Jan 2003 19:54:54 PST
Date: Thu, 2 Jan 2003 19:54:54 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
To: sigtran@ietf.org
In-Reply-To: <20030102063137.C7412@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, 02 Jan 2003
> 05:04:31)
> > Brian,
> > > Samuel,
> > > 
> > > Not necessarily.  They SHOULD return the same RC
> > > value.
> > [TOLGA] Why "SHOULD"? If SGPs are part of the same
> SG,
> > this would be probably the case, but why has it to
> be
> > a "SHOULD" from protocol point of view?
> 
> Because that was the consensus.
[TOLGA] Is this stated somewhere in the M3UA
documents?
> 
> --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! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jan  3 00:00: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 AAA22701
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 00:00:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0359G718639
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 00:09:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0358kJ18615;
	Fri, 3 Jan 2003 00:08:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0357oJ18582
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 00:07:50 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22652
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 23:58:43 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:+m9XZGNP2rIJLtarKdb0XroyeUeTMJec@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0351rD17324;
	Thu, 2 Jan 2003 22:01:53 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0351rW06156;
	Thu, 2 Jan 2003 22:01:53 -0700
Date: Thu, 2 Jan 2003 22:01:53 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
Message-ID: <20030102220153.A4832@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030102063137.C7412@openss7.org> <20030103035454.54447.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: <20030103035454.54447.qmail@web12807.mail.yahoo.com>; from tolga_asveren@yahoo.com on Thu, Jan 02, 2003 at 07:54:54PM -0800
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, 02 Jan 2003 19:54:54)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Thu, 02 Jan 2003
> > 05:04:31)
> > > Brian,
> > > > Samuel,
> > > > 
> > > > Not necessarily.  They SHOULD return the same RC
> > > > value.
> > > [TOLGA] Why "SHOULD"? If SGPs are part of the same
> > SG,
> > > this would be probably the case, but why has it to
> > be
> > > a "SHOULD" from protocol point of view?
> > 
> > Because that was the consensus.
> [TOLGA] Is this stated somewhere in the M3UA
> documents?

No.  I asked for it to be removed because it was an operational
consideration.

I can't see a case where any advantage would be gained by not
making RC values consistent across SGP in the same SG.  Can you?
What is the worth of useless flexibility?  It just creates more
work in handling the atypical cases.

--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  Fri Jan  3 00:01: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 AAA22738
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 00:01:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h035AE418703
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 00:10:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h035A4J18690;
	Fri, 3 Jan 2003 00:10:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0359NJ18653
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 00:09:23 -0500
Received: from mgw-x4.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22697
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 00:00:16 -0500 (EST)
From: john.loughney@nokia.com
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h0355Ht16782
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 07:05:18 +0200 (EET)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5f8f416c50ac158f240d4@esvir04nok.ntc.nokia.com>;
 Fri, 3 Jan 2003 07:02:02 +0200
Received: from esebe018.NOE.Nokia.com ([172.21.138.57]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 3 Jan 2003 07:02:02 +0200
Received: from esebe022.NOE.Nokia.com ([172.21.138.113]) by esebe018.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 3 Jan 2003 07:02:01 +0200
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"
Subject: RE: [Sigtran] Query from a group of students
Date: Fri, 3 Jan 2003 07:02:01 +0200
Message-ID: <A16A3EE4D4CA124FADC7987B1AC89FE4050D11@esebe022.ntc.nokia.com>
Thread-Topic: [Sigtran] Query from a group of students
Thread-Index: AcKylfbY3SdsYzT6S/KqVSZ7kjxsLQATnyTA
To: <amitksomani@yahoo.co.in>, <sigtran@ietf.org>
X-OriginalArrivalTime: 03 Jan 2003 05:02:01.0943 (UTC) FILETIME=[4083CE70:01C2B2E5]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0359NJ18654
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 Amit,

> We are a group of 3 students, Anup Deshpande, Prasad
> Edlabadkar and Amit Somanai, from Pune Institute of
> Computer Technology ,Pune , India. We are studying in
> the 4th year(i.e. final year) of Electronics &
> Telecommunication Engineering. We have a thrust for
> cutting edge technology and love working on
> challenging projects. We also like working on
> innovative ideas. Right now we are working on our
> final year project. The basic Project idea was to
> transport SS7 signals using TCP. But then we came
> across the disadvantages of TCP.
> So we have three options with us :
> 1. Using SCTP instead of TCP at the transport level
> 2. Using Sigtran stack
> 3. Using UDP and develop some application level on it 
> 
> The problem is we don`t know which one is actually
> feasible. We are implementing the project in Linux. Is
> there any Linux Kernel that is supporting SCTP. Can
> you suggest any small module that is still to
> implemented?

The SIGTRAN WG studied using UDP and TCP for transport,
but decided neither was sufficient, so it developed
SCTP and the SIGTRAN UAs.  SCTP is being supported
with Linux Kernel 2.5 - SCTP is under development
in that kernel.  You may wish to check http://sourceforge.net/projects/lksctp

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



From mailnull@www1.ietf.org  Fri Jan  3 00:13: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 AAA22815
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 00:13:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h035Lbx19065
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 00:21:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h035LFJ19052;
	Fri, 3 Jan 2003 00:21:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h035KBJ19011
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 00:20:11 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22804
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 00:11:04 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:OwgUBFnOnhGBGD4pv25hLAb8VYYRoq/P@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h035EFD17474;
	Thu, 2 Jan 2003 22:14:15 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h035EFg06460;
	Thu, 2 Jan 2003 22:14:15 -0700
Date: Thu, 2 Jan 2003 22:14:15 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030102221415.B4832@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030102182526.K26898@openss7.org> <20030103033615.98167.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: <20030103033615.98167.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Thu, Jan 02, 2003 at 07:36:15PM -0800
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, 02 Jan 2003 19:36:15)
> [TOLGA] For example for the case Joe has presented,
> how it should work IMO with a pure M3UA solution is:
> CGB arrives. If the range spans multiple RKs, SG
> should generate multiple CGBs, pack them properly and
> send them to the corresponding ASPs serving the
> relevant AS.

This violates the MTP/MTP-User interface: one MTP-User message
is being delivered across multiple interfaces.  This is not the
MTP/MTP-User interface and is therefore not an M3UA interface.

> I agree, this is ugly and even arguably
> against the spirit of a layered approach, but if one
> wants to support RKs based on CIC ranges with M3UA,
> this is the solution.

But it is not an M3UA solution.  It violates M3UA's own
proclaimed architecture:

  "The M3UA Layer at an ASP or IPSP provides the equivalent set of
   primitives at its upper layer to the MTP3-Users as provided by the
   MTP level 3 to its local MTP3-Users at an SS7 SEP."

Any questions?

What you are proposing is as un-M3UA as it is un-MTP3.


> filter/generate ISUP/SCCP messages for management
> purposes to support CIC/SSN based routing. Where is
> the change to M3UA protocol and to the interface
> between SGP/ASP? 

Deliver one DATA message accross multiple interfaces?  It
shouldn't happen:

   "Routing Keys SHOULD be unique in the sense that each received SS7
    signalling message SHOULD have a full or partial match to a single
    routing result."

Sounds to me like you want to take one message and match it to
multiple results.  That is load-sharing not routing.

If you want more discussion on CIC, read that thread from July
2001 again.

AFAIC it not required in the RFC, it has no hope of
interoperability as a Routing Key (only useful for loadsharing),
and it will fall by the wayside anyway.

Even TALI (after which this CIC stuff was tailored) did a very
poor job of specifying any reasonable circuit management.

Not to mention that, as it stands, one has to turn down entire
trunk groups to add or remove a circuit, and I think it is well
on its way to being toast.

--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  Fri Jan  3 00:16:52 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 AAA22895
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 00:16:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h035PSh19316
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 00:25:28 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h035P5J19305;
	Fri, 3 Jan 2003 00:25:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h035OiJ19272
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 00:24:44 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22889
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 00:15:37 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:LOgrTCfxhz4KPzyNVjRed3XLTTsJgNSq@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h035ImD17524;
	Thu, 2 Jan 2003 22:18:48 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h035ImL06544;
	Thu, 2 Jan 2003 22:18:48 -0700
Date: Thu, 2 Jan 2003 22:18:48 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: amit somani <amitksomani@yahoo.co.in>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Query from a group of students
Message-ID: <20030102221848.C4832@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: amit somani <amitksomani@yahoo.co.in>, sigtran@ietf.org
References: <20030102192305.751.qmail@web8206.mail.in.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: <20030102192305.751.qmail@web8206.mail.in.yahoo.com>; from amitksomani@yahoo.co.in on Thu, Jan 02, 2003 at 07:23:05PM +0000
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>

Amit,

  http://www.sigtran.org/
  
  is a good place to start.

  You will find lots of implementations (mostly GPL)
  that run on Linux.

--brian

amit somani wrote:                                                                    (Thu, 02 Jan 2003 19:23:05)
> Hello everyone,
> 
> We are a group of 3 students, Anup Deshpande, Prasad
> Edlabadkar and Amit Somanai, from Pune Institute of
> Computer Technology ,Pune , India. We are studying in
> the 4th year(i.e. final year) of Electronics &
> Telecommunication Engineering. We have a thrust for
> cutting edge technology and love working on
> challenging projects. We also like working on
> innovative ideas. Right now we are working on our
> final year project. The basic Project idea was to
> transport SS7 signals using TCP. But then we came
> across the disadvantages of TCP.
> So we have three options with us :
> 1. Using SCTP instead of TCP at the transport level
> 2. Using Sigtran stack
> 3. Using UDP and develop some application level on it 
> 
> The problem is we don`t know which one is actually
> feasible. We are implementing the project in Linux. Is
> there any Linux Kernel that is supporting SCTP. Can
> you suggest any small module that is still to
> implemented?
> 
> amit. 
> 
> 
> ________________________________________________________________________
> Missed your favourite TV serial last night? Try the new, Yahoo! TV.
>        visit http://in.tv.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 Jan  3 01:30: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 BAA23819
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 01:30:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h036ci923430
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 01:38:44 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h036cNJ23400;
	Fri, 3 Jan 2003 01:38:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h036bQJ23271
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 01:37:26 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23782
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 01:28:17 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h036VSaN017728;
	Fri, 3 Jan 2003 00:31:28 -0600 (CST)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h036UsM25175;
	Fri, 3 Jan 2003 00:30:54 -0600 (CST)
Date: Fri, 3 Jan 2003 00:30:54 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
In-Reply-To: <20030102220153.A4832@openss7.org>
Message-ID: <Pine.SOL.4.10.10301022315470.1712-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>


Hi Brian,Tolga,

According to section 1.4.2.1
RC is an index into a sending node's message distribution table containing
the RK entries.

But section 4.4.1
The method of RC value assignment at SGP..
--

It is said that RC is within the scope of SGP so SGP1 and SGP2 can return 
the different RC for the same RK1.But each each SGP must maintain
different AS state machine.I dont think it is a problem.

If SGP1 and SGP2 return same RC for the single RK,.Here we should go
to the concept of 'centralization', but the problem(BIG) arises when
something goes wrong in the 'centralized database (may be due to
processor failure)'

So if we have M3UA running over different IP processor(SGP) ,it is better
to have SGP1 and SGP2 returning different RC for the same RK1.
 
--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, 2 Jan 2003, Brian F. G. Bidulock wrote:

> Tolga,
> 
> Tolga Asveren wrote:                                                                 (Thu, 02 Jan 2003 19:54:54)
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Tolga Asveren wrote:                                
> > >                                 (Thu, 02 Jan 2003
> > > 05:04:31)
> > > > Brian,
> > > > > Samuel,
> > > > > 
> > > > > Not necessarily.  They SHOULD return the same RC
> > > > > value.
> > > > [TOLGA] Why "SHOULD"? If SGPs are part of the same
> > > SG,
> > > > this would be probably the case, but why has it to
> > > be
> > > > a "SHOULD" from protocol point of view?
> > > 
> > > Because that was the consensus.
> > [TOLGA] Is this stated somewhere in the M3UA
> > documents?
> 
> No.  I asked for it to be removed because it was an operational
> consideration.
> 
> I can't see a case where any advantage would be gained by not
> making RC values consistent across SGP in the same SG.  Can you?
> What is the worth of useless flexibility?  It just creates more
> work in handling the atypical cases.
> 
> --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 mailnull@www1.ietf.org  Fri Jan  3 01:51:56 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 BAA23969
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 01:51:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0370Zi24146
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 02:00:35 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0370CJ24121;
	Fri, 3 Jan 2003 02:00:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h036xcJ24064
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 01:59:38 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23959
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 01:50:29 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h036rXaN019408;
	Fri, 3 Jan 2003 00:53:39 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id LAA10520; Fri, 3 Jan 2003 11:22:46 -0500 (GMT)
Message-ID: <3E153380.ACD487B0@axes-mach01.usa.alcatel.com>
Date: Fri, 03 Jan 2003 12:23:54 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: sigtran@ietf.org
Content-Type: multipart/alternative;
 boundary="------------28C8BC8D37052577D6CBD358"
Subject: [Sigtran] M2PA two out of three
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>


--------------28C8BC8D37052577D6CBD358
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 7bit

Brian,

    In Section 4.2.1 of M2PA Draft version 6, the following is observed.

"M2PA should follow the criterion of [2] Q.703, section 5.3.1 for
incorrect BSNs: If any two BSNs in three consecutively received User
Data messages are not the same as the previous one or any of the FSNs
of the User Data messages in the M2PA transmit buffer at the time they
are received, then MTP3 should be informed that the link is faulty."

The highlighted "or" should have been "and".

The same error "or" is carried from Q.703

--Srini

--------------28C8BC8D37052577D6CBD358
Content-Type: text/html; charset=x-user-defined
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Brian,
<p>&nbsp;&nbsp;&nbsp; In Section 4.2.1 of M2PA Draft version 6, the following
is observed.
<p>"M2PA should follow the criterion of [2] Q.703, section 5.3.1 for
<br>incorrect BSNs: If any two BSNs in three consecutively received User
<br>Data messages are not the same as the previous one <b><u>or</u></b>
any of the FSNs
<br>of the User Data messages in the M2PA transmit buffer at the time they
<br>are received, then MTP3 should be informed that the link is faulty."
<p>The highlighted "or" should have been "and".
<p>The same error "or" is carried from Q.703
<p>--Srini</html>

--------------28C8BC8D37052577D6CBD358--

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



From mailnull@www1.ietf.org  Fri Jan  3 03:23:23 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 DAA05013
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 03:23:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h038W4W07428
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 03:32:04 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h038VdJ07394;
	Fri, 3 Jan 2003 03:31:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h038UQJ07329
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 03:30:26 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04988
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 03:21:14 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Cd3JPIt5rn8aIiEmcjs+4hZW89FygAhp@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h038OQD20507;
	Fri, 3 Jan 2003 01:24:26 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h038OPP10997;
	Fri, 3 Jan 2003 01:24:25 -0700
Date: Fri, 3 Jan 2003 01:24:25 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Message-ID: <20030103012425.A10860@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <3E153380.ACD487B0@axes-mach01.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: <3E153380.ACD487B0@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Fri, Jan 03, 2003 at 12:23:54PM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: M2PA two out of three
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>

Srini,

"Or" and "and" (or "or" or "and") are not treated as logical or
and logical and when used in English. ;)

Nevertheless in this case, "or" is correct in both senses.

--brian

ksrinivas wrote:                                   (Fri, 03 Jan 2003 12:23:54)
> 
>    Brian,
> 
>         In  Section  4.2.1  of  M2PA  Draft  version  6, the following is
>    observed.
> 
>    "M2PA should follow the criterion of [2] Q.703, section 5.3.1 for
>    incorrect BSNs: If any two BSNs in three consecutively received User
>    Data messages are not the same as the previous one or any of the FSNs
>    of the User Data messages in the M2PA transmit buffer at the time they
>    are received, then MTP3 should be informed that the link is faulty."
> 
>    The highlighted "or" should have been "and".
> 
>    The same error "or" is carried from Q.703
> 
>    --Srini

-- 
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 Jan  3 03:24: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 DAA05040
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 03:24:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h038XE507481
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 03:33:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h038X5J07473;
	Fri, 3 Jan 2003 03:33:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h038WPJ07449
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 03:32:25 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05010
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 03:23:13 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:5kJC5apHMrgNEaVj+Lsu2h/lrVR6G7+Z@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h038QPD20534;
	Fri, 3 Jan 2003 01:26:25 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h038QOO11028;
	Fri, 3 Jan 2003 01:26:24 -0700
Date: Fri, 3 Jan 2003 01:26:24 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
Message-ID: <20030103012624.B10860@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030102220153.A4832@openss7.org> <Pine.SOL.4.10.10301022315470.1712-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.10301022315470.1712-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Jan 03, 2003 at 12:30:54AM -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,

Yes, I agree: it is an operational consideration.  That's why you don't
see it in the RFC.

--brian

Samuel Dur D. Jeyaseelan wrote:                        (Fri, 03 Jan 2003 00:30:54)
> 
> Hi Brian,Tolga,
> 
> According to section 1.4.2.1
> RC is an index into a sending node's message distribution table containing
> the RK entries.
> 
> But section 4.4.1
> The method of RC value assignment at SGP..
> --
> 
> It is said that RC is within the scope of SGP so SGP1 and SGP2 can return 
> the different RC for the same RK1.But each each SGP must maintain
> different AS state machine.I dont think it is a problem.
> 
> If SGP1 and SGP2 return same RC for the single RK,.Here we should go
> to the concept of 'centralization', but the problem(BIG) arises when
> something goes wrong in the 'centralized database (may be due to
> processor failure)'
> 
> So if we have M3UA running over different IP processor(SGP) ,it is better
> to have SGP1 and SGP2 returning different RC for the same RK1.
>  
> --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, 2 Jan 2003, Brian F. G. Bidulock wrote:
> 
> > Tolga,
> > 
> > Tolga Asveren wrote:                               (Thu, 02 Jan 2003 19:54:54)
> > > Brian,
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > wrote:
> > > > Tolga,
> > > > 
> > > > Tolga Asveren wrote:                                
> > > >                                 (Thu, 02 Jan 2003
> > > > 05:04:31)
> > > > > Brian,
> > > > > > Samuel,
> > > > > > 
> > > > > > Not necessarily.  They SHOULD return the same RC
> > > > > > value.
> > > > > [TOLGA] Why "SHOULD"? If SGPs are part of the same
> > > > SG,
> > > > > this would be probably the case, but why has it to
> > > > be
> > > > > a "SHOULD" from protocol point of view?
> > > > 
> > > > Because that was the consensus.
> > > [TOLGA] Is this stated somewhere in the M3UA
> > > documents?
> > 
> > No.  I asked for it to be removed because it was an operational
> > consideration.
> > 
> > I can't see a case where any advantage would be gained by not
> > making RC values consistent across SGP in the same SG.  Can you?
> > What is the worth of useless flexibility?  It just creates more
> > work in handling the atypical cases.
> > 
> > --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 mailnull@www1.ietf.org  Fri Jan  3 03:51: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 DAA05323
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 03:51:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0390Ta09144
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 04:00:29 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0390AJ09114;
	Fri, 3 Jan 2003 04:00:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h038xUJ09067
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 03:59:30 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05262
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 03:50:17 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h038rTBE022240;
	Fri, 3 Jan 2003 02:53:29 -0600 (CST)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h038rEM09729;
	Fri, 3 Jan 2003 02:53:14 -0600 (CST)
Date: Fri, 3 Jan 2003 02:53:14 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
In-Reply-To: <20030103012624.B10860@openss7.org>
Message-ID: <Pine.SOL.4.10.10301030249570.5784-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,
Why dont u change section 1.4.2.1 Overview

...The Routing Context therefore can be viewed as an index into a sending
node's Message Distribution Table containing the Routing Key entries.

to

...The Routing Context therefore can be viewed as an index into a sending
SGP's Message Distribution Table containing the Routing Key entries.

--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, 3 Jan 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> Yes, I agree: it is an operational consideration.  That's why you don't
> see it in the RFC.
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                        (Fri, 03 Jan 2003 00:30:54)
> > 
> > Hi Brian,Tolga,
> > 
> > According to section 1.4.2.1
> > RC is an index into a sending node's message distribution table containing
> > the RK entries.
> > 
> > But section 4.4.1
> > The method of RC value assignment at SGP..
> > --
> > 
> > It is said that RC is within the scope of SGP so SGP1 and SGP2 can return 
> > the different RC for the same RK1.But each each SGP must maintain
> > different AS state machine.I dont think it is a problem.
> > 
> > If SGP1 and SGP2 return same RC for the single RK,.Here we should go
> > to the concept of 'centralization', but the problem(BIG) arises when
> > something goes wrong in the 'centralized database (may be due to
> > processor failure)'
> > 
> > So if we have M3UA running over different IP processor(SGP) ,it is better
> > to have SGP1 and SGP2 returning different RC for the same RK1.
> >  
> > --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, 2 Jan 2003, Brian F. G. Bidulock wrote:
> > 
> > > Tolga,
> > > 
> > > Tolga Asveren wrote:                               (Thu, 02 Jan 2003 19:54:54)
> > > > Brian,
> > > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > wrote:
> > > > > Tolga,
> > > > > 
> > > > > Tolga Asveren wrote:                                
> > > > >                                 (Thu, 02 Jan 2003
> > > > > 05:04:31)
> > > > > > Brian,
> > > > > > > Samuel,
> > > > > > > 
> > > > > > > Not necessarily.  They SHOULD return the same RC
> > > > > > > value.
> > > > > > [TOLGA] Why "SHOULD"? If SGPs are part of the same
> > > > > SG,
> > > > > > this would be probably the case, but why has it to
> > > > > be
> > > > > > a "SHOULD" from protocol point of view?
> > > > > 
> > > > > Because that was the consensus.
> > > > [TOLGA] Is this stated somewhere in the M3UA
> > > > documents?
> > > 
> > > No.  I asked for it to be removed because it was an operational
> > > consideration.
> > > 
> > > I can't see a case where any advantage would be gained by not
> > > making RC values consistent across SGP in the same SG.  Can you?
> > > What is the worth of useless flexibility?  It just creates more
> > > work in handling the atypical cases.
> > > 
> > > --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 mailnull@www1.ietf.org  Fri Jan  3 04:12:52 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 EAA05601
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 04:12:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h039LXm10971
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 04:21:33 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h039LFJ10951;
	Fri, 3 Jan 2003 04:21:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h039KCJ10877
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 04:20:12 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05557
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 04:10:59 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h039E5aN029328;
	Fri, 3 Jan 2003 03:14:10 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id NAA13381; Fri, 3 Jan 2003 13:43:01 -0500 (GMT)
Message-ID: <3E155467.7E0C192E@axes-mach01.usa.alcatel.com>
Date: Fri, 03 Jan 2003 14:44:16 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M2PA two out of three
References: <3E153380.ACD487B0@axes-mach01.usa.alcatel.com> <20030103012425.A10860@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

      I understood the thing. But I still feel there is some relation between
logic and English. This can be felt from the De-Morgans law below.

____    _ _
A+B = A.B

where, A = the same as the previous one(BSNs),
           B = the same as any of the FSNs of the User Data messages in the M2PA
transmit buffer at
                  the time they are received.

Thanks & Regards,
Srini

"Brian F. G. Bidulock" wrote:

> Srini,
>
> "Or" and "and" (or "or" or "and") are not treated as logical or
> and logical and when used in English. ;)
>
> Nevertheless in this case, "or" is correct in both senses.
>
> --brian
>
> ksrinivas wrote:                                   (Fri, 03 Jan 2003 12:23:54)
> >
> >    Brian,
> >
> >         In  Section  4.2.1  of  M2PA  Draft  version  6, the following is
> >    observed.
> >
> >    "M2PA should follow the criterion of [2] Q.703, section 5.3.1 for
> >    incorrect BSNs: If any two BSNs in three consecutively received User
> >    Data messages are not the same as the previous one or any of the FSNs
> >    of the User Data messages in the M2PA transmit buffer at the time they
> >    are received, then MTP3 should be informed that the link is faulty."
> >
> >    The highlighted "or" should have been "and".
> >
> >    The same error "or" is carried from Q.703
> >
> >    --Srini
>
> --
> 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 mailnull@www1.ietf.org  Fri Jan  3 04:20: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 EAA05734
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 04:20:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h039TRE11280
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 04:29:27 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h039TAJ11263;
	Fri, 3 Jan 2003 04:29:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h039SRJ11229
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 04:28:27 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05712
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 04:19:13 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Dx44YsvN7IhIc1TpK3z1MxNzxBREmXfd@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h039MQD21385;
	Fri, 3 Jan 2003 02:22:26 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h039MQT12131;
	Fri, 3 Jan 2003 02:22:26 -0700
Date: Fri, 3 Jan 2003 02:22:25 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M2PA two out of three
Message-ID: <20030103022225.A11987@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <3E153380.ACD487B0@axes-mach01.usa.alcatel.com> <20030103012425.A10860@openss7.org> <3E155467.7E0C192E@axes-mach01.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: <3E155467.7E0C192E@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Fri, Jan 03, 2003 at 02:44:16PM +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>

Srini,

But there is the difference:
        _   _
I read  A + B.

The "not" in this case only applies to the immediate subject and _not_ the
entire sentence.

--brian

ksrinivas wrote:                                               (Fri, 03 Jan 2003 14:44:16)
> Brian,
> 
>       I understood the thing. But I still feel there is some relation between
> logic and English. This can be felt from the De-Morgans law below.
> 
> ____    _ _
> A+B = A.B
> 
> where, A = the same as the previous one(BSNs),
>            B = the same as any of the FSNs of the User Data messages in the M2PA
> transmit buffer at
>                   the time they are received.
> 
> Thanks & Regards,
> Srini
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Srini,
> >
> > "Or" and "and" (or "or" or "and") are not treated as logical or
> > and logical and when used in English. ;)
> >
> > Nevertheless in this case, "or" is correct in both senses.
> >
> > --brian
> >
> > ksrinivas wrote:                                   (Fri, 03 Jan 2003 12:23:54)
> > >
> > >    Brian,
> > >
> > >         In  Section  4.2.1  of  M2PA  Draft  version  6, the following is
> > >    observed.
> > >
> > >    "M2PA should follow the criterion of [2] Q.703, section 5.3.1 for
> > >    incorrect BSNs: If any two BSNs in three consecutively received User
> > >    Data messages are not the same as the previous one or any of the FSNs
> > >    of the User Data messages in the M2PA transmit buffer at the time they
> > >    are received, then MTP3 should be informed that the link is faulty."
> > >
> > >    The highlighted "or" should have been "and".
> > >
> > >    The same error "or" is carried from Q.703
> > >
> > >    --Srini
> >
> > --
> > 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 mailnull@www1.ietf.org  Fri Jan  3 04:21: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 EAA05756
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 04:21:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h039UHA11331
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 04:30:17 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h039U6J11324;
	Fri, 3 Jan 2003 04:30:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h039TwJ11301
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 04:29:58 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05733
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 04:20:44 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:jskUqYswV/eT7sOYD3bKvSVzIdWtk92M@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h039NuD21398;
	Fri, 3 Jan 2003 02:23:57 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h039NuG12153;
	Fri, 3 Jan 2003 02:23:56 -0700
Date: Fri, 3 Jan 2003 02:23:56 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
Message-ID: <20030103022356.B11987@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030103012624.B10860@openss7.org> <Pine.SOL.4.10.10301030249570.5784-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.10301030249570.5784-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Jan 03, 2003 at 02:53:14AM -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,

It's only an example of how to look at it: not a requirement-- node, SGP,
what's the difference?

--brian

Samuel Dur D. Jeyaseelan wrote:                                   (Fri, 03 Jan 2003 02:53:14)
> 
> Brian,
> Why dont u change section 1.4.2.1 Overview
> 
> ...The Routing Context therefore can be viewed as an index into a sending
> node's Message Distribution Table containing the Routing Key entries.
> 
> to
> 
> ...The Routing Context therefore can be viewed as an index into a sending
> SGP's Message Distribution Table containing the Routing Key entries.
> 
> --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, 3 Jan 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > Yes, I agree: it is an operational consideration.  That's why you don't
> > see it in the RFC.
> > 
> > --brian
> > 
> > Samuel Dur D. Jeyaseelan wrote:                        (Fri, 03 Jan 2003 00:30:54)
> > > 
> > > Hi Brian,Tolga,
> > > 
> > > According to section 1.4.2.1
> > > RC is an index into a sending node's message distribution table containing
> > > the RK entries.
> > > 
> > > But section 4.4.1
> > > The method of RC value assignment at SGP..
> > > --
> > > 
> > > It is said that RC is within the scope of SGP so SGP1 and SGP2 can return 
> > > the different RC for the same RK1.But each each SGP must maintain
> > > different AS state machine.I dont think it is a problem.
> > > 
> > > If SGP1 and SGP2 return same RC for the single RK,.Here we should go
> > > to the concept of 'centralization', but the problem(BIG) arises when
> > > something goes wrong in the 'centralized database (may be due to
> > > processor failure)'
> > > 
> > > So if we have M3UA running over different IP processor(SGP) ,it is better
> > > to have SGP1 and SGP2 returning different RC for the same RK1.
> > >  
> > > --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, 2 Jan 2003, Brian F. G. Bidulock wrote:
> > > 
> > > > Tolga,
> > > > 
> > > > Tolga Asveren wrote:                               (Thu, 02 Jan 2003 19:54:54)
> > > > > Brian,
> > > > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > wrote:
> > > > > > Tolga,
> > > > > > 
> > > > > > Tolga Asveren wrote:                                
> > > > > >                                 (Thu, 02 Jan 2003
> > > > > > 05:04:31)
> > > > > > > Brian,
> > > > > > > > Samuel,
> > > > > > > > 
> > > > > > > > Not necessarily.  They SHOULD return the same RC
> > > > > > > > value.
> > > > > > > [TOLGA] Why "SHOULD"? If SGPs are part of the same
> > > > > > SG,
> > > > > > > this would be probably the case, but why has it to
> > > > > > be
> > > > > > > a "SHOULD" from protocol point of view?
> > > > > > 
> > > > > > Because that was the consensus.
> > > > > [TOLGA] Is this stated somewhere in the M3UA
> > > > > documents?
> > > > 
> > > > No.  I asked for it to be removed because it was an operational
> > > > consideration.
> > > > 
> > > > I can't see a case where any advantage would be gained by not
> > > > making RC values consistent across SGP in the same SG.  Can you?
> > > > What is the worth of useless flexibility?  It just creates more
> > > > work in handling the atypical cases.
> > > > 
> > > > --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/
> > 

-- 
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 Jan  3 05:01: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 FAA06114
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 05:01:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03AAQZ13961
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 05:10:26 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03A9uJ13935;
	Fri, 3 Jan 2003 05:09:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03A8tJ13894
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 05:08:55 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06079
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 04:59:42 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h03A2oaN002858;
	Fri, 3 Jan 2003 04:02:51 -0600 (CST)
Received: from axsppc51 by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id OAA14859; Fri, 3 Jan 2003 14:31:46 -0500 (GMT)
Message-ID: <007a01c2b30f$8eaa6c10$6501ff0a@axsppc51>
From: "Manjunath" <manju@axes-mach01.usa.alcatel.com>
To: <bidulock@openss7.org>, "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
Cc: <sigtran@ietf.org>
References: <3E153380.ACD487B0@axes-mach01.usa.alcatel.com> <20030103012425.A10860@openss7.org> <3E155467.7E0C192E@axes-mach01.usa.alcatel.com> <20030103022225.A11987@openss7.org>
Subject: Re: [Sigtran] Re: M2PA two out of three
Date: Fri, 3 Jan 2003 15:34:30 +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.50.4133.2400
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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

Brain,
  We  feel what srini observed holds valid,

  M2PA should follow the criterion of [2] Q.703, section 5.3.1 for
incorrect BSNs: If (( any two BSNs in three consecutively received User
Data messages) are not the same ((as the previous one) or (any of the FSNs
of the User Data messages in the M2PA transmit buffer at the time they
are received))), then MTP3 should be informed that the link is faulty."
  If A is not same as B or C then D, it means that A is not same as B and A
is
not same as C then D proving De Morgan's law
           ____           _ _          _       _
     A.( B+C) = A.(B.C) = A.B . A.C

Is not what Srini stated valid??

thanks
manju/sibi




----- Original Message -----
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
Cc: <sigtran@ietf.org>
Sent: Friday, January 03, 2003 2:52 PM
Subject: Re: [Sigtran] Re: M2PA two out of three


> Srini,
>
> But there is the difference:
>         _   _
> I read  A + B.
>
> The "not" in this case only applies to the immediate subject and _not_ the
> entire sentence.
>
> --brian
>
> ksrinivas wrote:                                               (Fri, 03
Jan 2003 14:44:16)
> > Brian,
> >
> >       I understood the thing. But I still feel there is some relation
between
> > logic and English. This can be felt from the De-Morgans law below.
> >
> > ____    _ _
> > A+B = A.B
> >
> > where, A = the same as the previous one(BSNs),
> >            B = the same as any of the FSNs of the User Data messages in
the M2PA
> > transmit buffer at
> >                   the time they are received.
> >
> > Thanks & Regards,
> > Srini
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > Srini,
> > >
> > > "Or" and "and" (or "or" or "and") are not treated as logical or
> > > and logical and when used in English. ;)
> > >
> > > Nevertheless in this case, "or" is correct in both senses.
> > >
> > > --brian
> > >
> > > ksrinivas wrote:                                   (Fri, 03 Jan 2003
12:23:54)
> > > >
> > > >    Brian,
> > > >
> > > >         In  Section  4.2.1  of  M2PA  Draft  version  6, the
following is
> > > >    observed.
> > > >
> > > >    "M2PA should follow the criterion of [2] Q.703, section 5.3.1 for
> > > >    incorrect BSNs: If any two BSNs in three consecutively received
User
> > > >    Data messages are not the same as the previous one or any of the
FSNs
> > > >    of the User Data messages in the M2PA transmit buffer at the time
they
> > > >    are received, then MTP3 should be informed that the link is
faulty."
> > > >
> > > >    The highlighted "or" should have been "and".
> > > >
> > > >    The same error "or" is carried from Q.703
> > > >
> > > >    --Srini
> > >
> > > --
> > > 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 mailnull@www1.ietf.org  Fri Jan  3 10:06: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 KAA10421
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 10:06:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03FFcZ31359
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 10:15:38 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03FFAJ31304;
	Fri, 3 Jan 2003 10:15:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03FDmJ31235
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 10:13:48 -0500
Received: from revere.sonusnet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10354
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 10:04:27 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3.sonusnet.com [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h03F77S16149;
	Fri, 3 Jan 2003 10:07:07 -0500 (EST)
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19)
	id <Y68HRKWW>; Fri, 3 Jan 2003 10:07:36 -0500
Message-ID: <4CF48720B6E9D4118D040060CF2074E9072F6B94@sonusdc3.sonusnet.com>
From: "Wung, Joseph" <JWung@sonusnet.com>
To: "'Tolga Asveren'" <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
Date: Fri, 3 Jan 2003 10:07:35 -0500 
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>

Tolga,

You're proposing a solution that may work only in a case
where both ends of the M3UA interface, i.e., SGP and
ASP, are implemented by the same vendor.  Then why
bother to specify an interface as an IETF standard?

Joe

> [TOLGA] For example for the case Joe has presented,
> how it should work IMO with a pure M3UA solution is:
> CGB arrives. If the range spans multiple RKs, SG
> should generate multiple CGBs, pack them properly and
> send them to the corresponding ASPs serving the
> relevant AS. I agree, this is ugly and even arguably
> against the spirit of a layered approach, but if one
> wants to support RKs based on CIC ranges with M3UA,
> this is the solution. So, what SG is doing is
> filter/generate ISUP/SCCP messages for management
> purposes to support CIC/SSN based routing. Where is
> the change to M3UA protocol and to the interface
> between SGP/ASP? 
> 
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.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 Jan  3 11:34: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 LAA12447
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 11:34:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03Ggr805135
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 11:42:53 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03GgUJ05094;
	Fri, 3 Jan 2003 11:42:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03GfUJ05048
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 11:41:30 -0500
Received: from revere.sonusnet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12417
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 11:32:10 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3.sonusnet.com [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h03GYiS23980;
	Fri, 3 Jan 2003 11:34:44 -0500 (EST)
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19)
	id <Y68HRLDM>; Fri, 3 Jan 2003 11:35:13 -0500
Message-ID: <4CF48720B6E9D4118D040060CF2074E9072F6B98@sonusdc3.sonusnet.com>
From: "Wung, Joseph" <JWung@sonusnet.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
Date: Fri, 3 Jan 2003 11:35:13 -0500 
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,

Is there ISUA anywhere?

Joe

> You will need to describe all that M3UA lacks in support
> of CIC routing.  Once you are finished that exercise you
> will have ISUA.  (As mentioned on the original thread
> from July 2001.)
> 
> --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 mailnull@www1.ietf.org  Fri Jan  3 12:41: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 MAA14138
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 12:41:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03Ho4J10275
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 12:50:04 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03HnaJ10166;
	Fri, 3 Jan 2003 12:49:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03Hm6J10108
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 12:48:06 -0500
Received: from web12807.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA14015
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 12:38:44 -0500 (EST)
Message-ID: <20030103174155.63956.qmail@web12807.mail.yahoo.com>
Received: from [62.29.76.9] by web12807.mail.yahoo.com via HTTP; Fri, 03 Jan 2003 09:41:55 PST
Date: Fri, 3 Jan 2003 09:41:55 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <4CF48720B6E9D4118D040060CF2074E9072F6B94@sonusdc3.sonusnet.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>

Joe,
--- "Wung, Joseph" <JWung@sonusnet.com> wrote:
> Tolga,
> 
> You're proposing a solution that may work only in a
> case
> where both ends of the M3UA interface, i.e., SGP and
> ASP, are implemented by the same vendor.  Then why
> bother to specify an interface as an IETF standard?
[TOLGA] Why should they be implemented by the same
vendor? What I say is implementing necessary logic -if
possible- only on SG. I think this is doable for
class0/class1 SSN based RKs. For ISUP, I didn't think
in too much detail. But for example for the case you
presented, what special procedure should ASP follow to
make it work? AS will receive CGB and will reply it
with CGBA. It is responsibility of SG, to corraleta
the answers and pack them to a single reply. What
special procedure from M3UA point of view is
introduced?
> 
> Joe
> 
> > [TOLGA] For example for the case Joe has
> presented,
> > how it should work IMO with a pure M3UA solution
> is:
> > CGB arrives. If the range spans multiple RKs, SG
> > should generate multiple CGBs, pack them properly
> and
> > send them to the corresponding ASPs serving the
> > relevant AS. I agree, this is ugly and even
> arguably
> > against the spirit of a layered approach, but if
> one
> > wants to support RKs based on CIC ranges with
> M3UA,
> > this is the solution. So, what SG is doing is
> > filter/generate ISUP/SCCP messages for management
> > purposes to support CIC/SSN based routing. Where
> is
> > the change to M3UA protocol and to the interface
> > between SGP/ASP? 
> > 
> > 
> > __________________________________________________
> > Do you Yahoo!?
> > Yahoo! Mail Plus - Powerful. Affordable. Sign up
> now.
> > http://mailplus.yahoo.com
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jan  3 12:55: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 MAA14565
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 12:55:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03I4a311063
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 13:04:36 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03I3AJ10968;
	Fri, 3 Jan 2003 13:03:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03I2cJ10941
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 13:02:38 -0500
Received: from web12807.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA14484
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 12:53:14 -0500 (EST)
Message-ID: <20030103175626.66669.qmail@web12807.mail.yahoo.com>
Received: from [62.29.76.9] by web12807.mail.yahoo.com via HTTP; Fri, 03 Jan 2003 09:56:26 PST
Date: Fri, 3 Jan 2003 09:56:26 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <20030102221415.B4832@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, 02 Jan 2003
> 19:36:15)
> > [TOLGA] For example for the case Joe has
> presented,
> > how it should work IMO with a pure M3UA solution
> is:
> > CGB arrives. If the range spans multiple RKs, SG
> > should generate multiple CGBs, pack them properly
> and
> > send them to the corresponding ASPs serving the
> > relevant AS.
> 
> This violates the MTP/MTP-User interface: one
> MTP-User message
> is being delivered across multiple interfaces.  This
> is not the
> MTP/MTP-User interface and is therefore not an M3UA
> interface.
[TOLGA] This is far from being elegant but I wouldn't
think it as one MTP/MTP-User interface message being
delivered on multiple interfaces. What is happening is
that one ISUP message is mapped to multiple messages,
i.e. to multiple MTP/MTP-User messages and sent to the
reloevant ASPs. This is similar (I agree not the same,
happens one layer above) like one TFP is mapped to
multiple DUNA.
> 
> > I agree, this is ugly and even arguably
> > against the spirit of a layered approach, but if
> one
> > wants to support RKs based on CIC ranges with
> M3UA,
> > this is the solution.
> 
> But it is not an M3UA solution.  It violates M3UA's
> own
> proclaimed architecture:
> 
>   "The M3UA Layer at an ASP or IPSP provides the
> equivalent set of
>    primitives at its upper layer to the MTP3-Users
> as provided by the
>    MTP level 3 to its local MTP3-Users at an SS7
> SEP."
[TOLGA] IMO, this does not change the interface.
Generating/Filetering ISUP/SCCP messages or keeping
some management information is not exposed to SGP/ASP
interface.
> 
> Any questions?
> 
> What you are proposing is as un-M3UA as it is
> un-MTP3.
> 
> 
> > filter/generate ISUP/SCCP messages for management
> > purposes to support CIC/SSN based routing. Where
> is
> > the change to M3UA protocol and to the interface
> > between SGP/ASP? 
> 
> Deliver one DATA message accross multiple
> interfaces?  It
> shouldn't happen:
> 
>    "Routing Keys SHOULD be unique in the sense that
> each received SS7
>     signalling message SHOULD have a full or partial
> match to a single
>     routing result."
> 
> Sounds to me like you want to take one message and
> match it to
> multiple results.  That is load-sharing not routing.
[TOLGA] Not exacxtly. Mapping one message to multiple
messages happen on SCCP/ISUP level, not on M3UA level.
> 
> If you want more discussion on CIC, read that thread
> from July
> 2001 again.
> 
> AFAIC it not required in the RFC, it has no hope of
> interoperability as a Routing Key (only useful for
> loadsharing),
> and it will fall by the wayside anyway.
> 
> Even TALI (after which this CIC stuff was tailored)
> did a very
> poor job of specifying any reasonable circuit
> management.
> 
> Not to mention that, as it stands, one has to turn
> down entire
> trunk groups to add or remove a circuit, and I think
> it is well
> on its way to being toast.
[TOLGA] I don't say, it is easy/elegant to support
non-MTP3 constructs as RKs, but it migth be possible.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jan  3 15: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 PAA18519
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 15:33:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03KgPV23533
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 15:42:25 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03KfsJ23512;
	Fri, 3 Jan 2003 15:41:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03Ke1J23419
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 15:40:01 -0500
Received: from revere.sonusnet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18448
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 15:30:34 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3.sonusnet.com [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h03KXES13627;
	Fri, 3 Jan 2003 15:33:15 -0500 (EST)
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19)
	id <Y68HRMDP>; Fri, 3 Jan 2003 15:33:44 -0500
Message-ID: <4CF48720B6E9D4118D040060CF2074E9072F6B9F@sonusdc3.sonusnet.com>
From: "Wung, Joseph" <JWung@sonusnet.com>
To: "'Tolga Asveren'" <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
Date: Fri, 3 Jan 2003 15:33:43 -0500 
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>

Tolga,

> -----Original Message-----
> From: Tolga Asveren [mailto:tolga_asveren@yahoo.com]
> Sent: Friday, January 03, 2003 12:42 PM
> To: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA distributing ISUP group messages
> 
> 
> Joe,
> --- "Wung, Joseph" <JWung@sonusnet.com> wrote:
> > Tolga,
> > 
> > You're proposing a solution that may work only in a
> > case
> > where both ends of the M3UA interface, i.e., SGP and
> > ASP, are implemented by the same vendor.  Then why
> > bother to specify an interface as an IETF standard?
> [TOLGA] Why should they be implemented by the same
> vendor? What I say is implementing necessary logic -if
> possible- only on SG. I think this is doable for
> class0/class1 SSN based RKs. For ISUP, I didn't think
> in too much detail. But for example for the case you
> presented, what special procedure should ASP follow to
> make it work? AS will receive CGB and will reply it
> with CGBA. It is responsibility of SG, to corraleta
> the answers and pack them to a single reply. What
> special procedure from M3UA point of view is
> introduced?

There are no such procedures in M3UA as it stands that 
would enforce SG vendors to do so.  In addition, how is
the ASP that receives such CGB with CICs outside the 
range defined for the ASP to know that those CICs are 
NOT unequipped so it will not send UCIC messages in
response?

Joe
> > 
> > Joe
> > 
> > > [TOLGA] For example for the case Joe has
> > presented,
> > > how it should work IMO with a pure M3UA solution
> > is:
> > > CGB arrives. If the range spans multiple RKs, SG
> > > should generate multiple CGBs, pack them properly
> > and
> > > send them to the corresponding ASPs serving the
> > > relevant AS. I agree, this is ugly and even
> > arguably
> > > against the spirit of a layered approach, but if
> > one
> > > wants to support RKs based on CIC ranges with
> > M3UA,
> > > this is the solution. So, what SG is doing is
> > > filter/generate ISUP/SCCP messages for management
> > > purposes to support CIC/SSN based routing. Where
> > is
> > > the change to M3UA protocol and to the interface
> > > between SGP/ASP? 
> > > 
> > > 
> > > __________________________________________________
> > > Do you Yahoo!?
> > > Yahoo! Mail Plus - Powerful. Affordable. Sign up
> > now.
> > > http://mailplus.yahoo.com
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> 
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.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 Jan  3 17:06: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 RAA20189
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 17:06:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03MFlF29058
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 17:15:47 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03MFCJ29032;
	Fri, 3 Jan 2003 17:15:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03MCdJ28950
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 17:12:39 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20138
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 17:03:10 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:MWiauQfZ0iJyBayUM4TxoOqBYp+3jA0R@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h03M6ND01252;
	Fri, 3 Jan 2003 15:06:23 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h03M6Mq31504;
	Fri, 3 Jan 2003 15:06:22 -0700
Date: Fri, 3 Jan 2003 15:06:22 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Wung, Joseph" <JWung@sonusnet.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030103150622.B30997@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Wung, Joseph" <JWung@sonusnet.com>, sigtran@ietf.org
References: <4CF48720B6E9D4118D040060CF2074E9072F6B98@sonusdc3.sonusnet.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: <4CF48720B6E9D4118D040060CF2074E9072F6B98@sonusdc3.sonusnet.com>; from JWung@sonusnet.com on Fri, Jan 03, 2003 at 11:35:13AM -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>

Joseph,

I offerred to write one several times.  Nobody took me up
on my offer.

--brian

Wung, Joseph wrote:                      (Fri, 03 Jan 2003 11:35:13)
> Brian,
> 
> Is there ISUA anywhere?
> 
> Joe
> 
> > You will need to describe all that M3UA lacks in support
> > of CIC routing.  Once you are finished that exercise you
> > will have ISUA.  (As mentioned on the original thread
> > from July 2001.)
> > 
> > --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 mailnull@www1.ietf.org  Fri Jan  3 17:15: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 RAA20427
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 17:15:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03MOUg29401
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 17:24:30 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03MNpJ29378;
	Fri, 3 Jan 2003 17:23:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03MLgJ29306
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 17:21:42 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20323
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 17:12:12 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:+mwDaJsZf8DNCpHudk64xXx3f555UsGq@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h03MFPD01374;
	Fri, 3 Jan 2003 15:15:25 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h03MFPC31808;
	Fri, 3 Jan 2003 15:15:25 -0700
Date: Fri, 3 Jan 2003 15:15:25 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Manjunath <manju@axes-mach01.usa.alcatel.com>
Cc: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: M2PA two out of three
Message-ID: <20030103151525.C30997@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Manjunath <manju@axes-mach01.usa.alcatel.com>,
	ksrinivas <ksrini@axes-mach01.usa.alcatel.com>, sigtran@ietf.org
References: <3E153380.ACD487B0@axes-mach01.usa.alcatel.com> <20030103012425.A10860@openss7.org> <3E155467.7E0C192E@axes-mach01.usa.alcatel.com> <20030103022225.A11987@openss7.org> <007a01c2b30f$8eaa6c10$6501ff0a@axsppc51>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <007a01c2b30f$8eaa6c10$6501ff0a@axsppc51>; from manju@axes-mach01.usa.alcatel.com on Fri, Jan 03, 2003 at 03:34:30PM +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>

Manjunath,

You miss the efficiency in English of skipping qualifiers on the
second clause:

   If A is not the same as B or C then D.
=> If A is not the same as B or A is not the same as C then D.
=> If ((A is not the same as B) or (A is not the same as C)) then D.

--brian

Manjunath wrote:                                    (Fri, 03 Jan 2003 15:34:30)
> Brain,
>   We  feel what srini observed holds valid,
> 
>   M2PA should follow the criterion of [2] Q.703, section 5.3.1 for
> incorrect BSNs: If (( any two BSNs in three consecutively received User
> Data messages) are not the same ((as the previous one) or (any of the FSNs
> of the User Data messages in the M2PA transmit buffer at the time they
> are received))), then MTP3 should be informed that the link is faulty."
>   If A is not same as B or C then D, it means that A is not same as B and A
> is
> not same as C then D proving De Morgan's law
>            ____           _ _          _       _
>      A.( B+C) = A.(B.C) = A.B . A.C
> 
> Is not what Srini stated valid??
> 
> thanks
> manju/sibi
> 
> 
> 
> 
> ----- Original Message -----
> From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> To: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
> Cc: <sigtran@ietf.org>
> Sent: Friday, January 03, 2003 2:52 PM
> Subject: Re: [Sigtran] Re: M2PA two out of three
> 
> 
> > Srini,
> >
> > But there is the difference:
> >         _   _
> > I read  A + B.
> >
> > The "not" in this case only applies to the immediate subject and _not_ the
> > entire sentence.
> >
> > --brian
> >
> > ksrinivas wrote:                                               (Fri, 03
> Jan 2003 14:44:16)
> > > Brian,
> > >
> > >       I understood the thing. But I still feel there is some relation
> between
> > > logic and English. This can be felt from the De-Morgans law below.
> > >
> > > ____    _ _
> > > A+B = A.B
> > >
> > > where, A = the same as the previous one(BSNs),
> > >            B = the same as any of the FSNs of the User Data messages in
> the M2PA
> > > transmit buffer at
> > >                   the time they are received.
> > >
> > > Thanks & Regards,
> > > Srini
> > >
> > > "Brian F. G. Bidulock" wrote:
> > >
> > > > Srini,
> > > >
> > > > "Or" and "and" (or "or" or "and") are not treated as logical or
> > > > and logical and when used in English. ;)
> > > >
> > > > Nevertheless in this case, "or" is correct in both senses.
> > > >
> > > > --brian
> > > >
> > > > ksrinivas wrote:                                   (Fri, 03 Jan 2003
> 12:23:54)
> > > > >
> > > > >    Brian,
> > > > >
> > > > >         In  Section  4.2.1  of  M2PA  Draft  version  6, the
> following is
> > > > >    observed.
> > > > >
> > > > >    "M2PA should follow the criterion of [2] Q.703, section 5.3.1 for
> > > > >    incorrect BSNs: If any two BSNs in three consecutively received
> User
> > > > >    Data messages are not the same as the previous one or any of the
> FSNs
> > > > >    of the User Data messages in the M2PA transmit buffer at the time
> they
> > > > >    are received, then MTP3 should be informed that the link is
> faulty."
> > > > >
> > > > >    The highlighted "or" should have been "and".
> > > > >
> > > > >    The same error "or" is carried from Q.703
> > > > >
> > > > >    --Srini
> > > >
> > > > --
> > > > 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 mailnull@www1.ietf.org  Fri Jan  3 17:21: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 RAA20505
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 17:21:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03MUa929648
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 17:30:36 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03MTrJ29573;
	Fri, 3 Jan 2003 17:29:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03MRCJ29498
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 17:27:12 -0500
Received: from web12806.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA20455
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 17:17:42 -0500 (EST)
Message-ID: <20030103222055.83970.qmail@web12806.mail.yahoo.com>
Received: from [62.29.76.238] by web12806.mail.yahoo.com via HTTP; Fri, 03 Jan 2003 14:20:55 PST
Date: Fri, 3 Jan 2003 14:20:55 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <4CF48720B6E9D4118D040060CF2074E9072F6B9F@sonusdc3.sonusnet.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>

Joe,
--- "Wung, Joseph" <JWung@sonusnet.com> wrote:
> Tolga,
> 
> > -----Original Message-----
> > From: Tolga Asveren
> [mailto:tolga_asveren@yahoo.com]
> > Sent: Friday, January 03, 2003 12:42 PM
> > To: sigtran@ietf.org
> > Subject: RE: [Sigtran] M3UA distributing ISUP
> group messages
> > 
> > 
> > Joe,
> > --- "Wung, Joseph" <JWung@sonusnet.com> wrote:
> > > Tolga,
> > > 
> > > You're proposing a solution that may work only
> in a
> > > case
> > > where both ends of the M3UA interface, i.e., SGP
> and
> > > ASP, are implemented by the same vendor.  Then
> why
> > > bother to specify an interface as an IETF
> standard?
> > [TOLGA] Why should they be implemented by the same
> > vendor? What I say is implementing necessary logic
> -if
> > possible- only on SG. I think this is doable for
> > class0/class1 SSN based RKs. For ISUP, I didn't
> think
> > in too much detail. But for example for the case
> you
> > presented, what special procedure should ASP
> follow to
> > make it work? AS will receive CGB and will reply
> it
> > with CGBA. It is responsibility of SG, to
> corraleta
> > the answers and pack them to a single reply. What
> > special procedure from M3UA point of view is
> > introduced?
> 
> There are no such procedures in M3UA as it stands
> that 
> would enforce SG vendors to do so.  In addition, how
> is
> the ASP that receives such CGB with CICs outside the
> 
> range defined for the ASP to know that those CICs
> are 
> NOT unequipped so it will not send UCIC messages in
> response?
[TOLGA]I think I failed to explain what I mean. First,
such procedures don't need interaction between
SGP/ASP, so what one needs it to take ISUP spec and
implement it according to it. 
For your case, what I say is that one CGB maps to
multiple CGB is it spans multiple RKs. So, each AS
will receive just the part it is configured for. SG
should wait for CGBAs and should generate one CGBA
based ont he information received from them. So, there
is no change necessary to the M3UA protocol.
Everyhting is handled in SG, and the guideline is ISUP
spec.
Having said all of that, implementing such a logic on
SG is really ugly, but the point is, it does not
require something to be defined in the M3UA protocol
itself.
> 
> Joe
> > > 
> > > Joe
> > > 
> > > > [TOLGA] For example for the case Joe has
> > > presented,
> > > > how it should work IMO with a pure M3UA
> solution
> > > is:
> > > > CGB arrives. If the range spans multiple RKs,
> SG
> > > > should generate multiple CGBs, pack them
> properly
> > > and
> > > > send them to the corresponding ASPs serving
> the
> > > > relevant AS. I agree, this is ugly and even
> > > arguably
> > > > against the spirit of a layered approach, but
> if
> > > one
> > > > wants to support RKs based on CIC ranges with
> > > M3UA,
> > > > this is the solution. So, what SG is doing is
> > > > filter/generate ISUP/SCCP messages for
> management
> > > > purposes to support CIC/SSN based routing.
> Where
> > > is
> > > > the change to M3UA protocol and to the
> interface
> > > > between SGP/ASP? 
> > > > 
> > > > 
> > > >
> __________________________________________________
> > > > Do you Yahoo!?
> > > > Yahoo! Mail Plus - Powerful. Affordable. Sign
> up
> > > now.
> > > > http://mailplus.yahoo.com
> > > >
> _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > 
> > 
> > 
> > __________________________________________________
> > Do you Yahoo!?
> > Yahoo! Mail Plus - Powerful. Affordable. Sign up
> now.
> > http://mailplus.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


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jan  3 17:25:17 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 RAA20560
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 17:25:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03MYDT29812
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 17:34:13 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03MXoJ29791;
	Fri, 3 Jan 2003 17:33:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03MVoJ29742
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 17:31:50 -0500
Received: from web12805.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA20529
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 17:22:20 -0500 (EST)
Message-ID: <20030103222533.65841.qmail@web12805.mail.yahoo.com>
Received: from [62.29.76.238] by web12805.mail.yahoo.com via HTTP; Fri, 03 Jan 2003 14:25:33 PST
Date: Fri, 3 Jan 2003 14:25:33 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <4CF48720B6E9D4118D040060CF2074E9072F6B9F@sonusdc3.sonusnet.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>

Joe,
--- "Wung, Joseph" <JWung@sonusnet.com> wrote:
> Tolga,
> 
> > -----Original Message-----
> > From: Tolga Asveren
> [mailto:tolga_asveren@yahoo.com]
> > Sent: Friday, January 03, 2003 12:42 PM
> > To: sigtran@ietf.org
> > Subject: RE: [Sigtran] M3UA distributing ISUP
> group messages
> > 
> > 
> > Joe,
> > --- "Wung, Joseph" <JWung@sonusnet.com> wrote:
> > > Tolga,
> > > 
> > > You're proposing a solution that may work only
> in a
> > > case
> > > where both ends of the M3UA interface, i.e., SGP
> and
> > > ASP, are implemented by the same vendor.  Then
> why
> > > bother to specify an interface as an IETF
> standard?
> > [TOLGA] Why should they be implemented by the same
> > vendor? What I say is implementing necessary logic
> -if
> > possible- only on SG. I think this is doable for
> > class0/class1 SSN based RKs. For ISUP, I didn't
> think
> > in too much detail. But for example for the case
> you
> > presented, what special procedure should ASP
> follow to
> > make it work? AS will receive CGB and will reply
> it
> > with CGBA. It is responsibility of SG, to
> corraleta
> > the answers and pack them to a single reply. What
> > special procedure from M3UA point of view is
> > introduced?
> 
> There are no such procedures in M3UA as it stands
> that 
> would enforce SG vendors to do so.  In addition, how
> is
[TOLGA] Please also note that M3UA does not put any
restrictions on the type of rouye keys. So, it is SGs
responsibility to support necessary management for
them. Otherwise, we would need to explain for each and
every possible RK type, what to do. Of course M3UA
does not mandate SGs to support SSN/CIC based RKs. But
if one SG wants to support it (without any changes to
M3UA as defined in RFC/IG) it should be free to do so.
> the ASP that receives such CGB with CICs outside the
> 
> range defined for the ASP to know that those CICs
> are 
> NOT unequipped so it will not send UCIC messages in
> response?
> 
> Joe
> > > 
> > > Joe
> > > 
> > > > [TOLGA] For example for the case Joe has
> > > presented,
> > > > how it should work IMO with a pure M3UA
> solution
> > > is:
> > > > CGB arrives. If the range spans multiple RKs,
> SG
> > > > should generate multiple CGBs, pack them
> properly
> > > and
> > > > send them to the corresponding ASPs serving
> the
> > > > relevant AS. I agree, this is ugly and even
> > > arguably
> > > > against the spirit of a layered approach, but
> if
> > > one
> > > > wants to support RKs based on CIC ranges with
> > > M3UA,
> > > > this is the solution. So, what SG is doing is
> > > > filter/generate ISUP/SCCP messages for
> management
> > > > purposes to support CIC/SSN based routing.
> Where
> > > is
> > > > the change to M3UA protocol and to the
> interface
> > > > between SGP/ASP? 
> > > > 
> > > > 
> > > >
> __________________________________________________
> > > > Do you Yahoo!?
> > > > Yahoo! Mail Plus - Powerful. Affordable. Sign
> up
> > > now.
> > > > http://mailplus.yahoo.com
> > > >
> _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > 
> > 
> > 
> > __________________________________________________
> > Do you Yahoo!?
> > Yahoo! Mail Plus - Powerful. Affordable. Sign up
> now.
> > http://mailplus.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


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jan  3 17:51: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 RAA21008
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 17:51:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03N0ax31463
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 18:00:36 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03N0BJ31444;
	Fri, 3 Jan 2003 18:00:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03MxxJ31402
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 17:59:59 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20993
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 17:50:31 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:WosgBTpAlqesS0Ww1m2X4eMcpl5S1rGO@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h03MrgD01857;
	Fri, 3 Jan 2003 15:53:42 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h03MrgW00353;
	Fri, 3 Jan 2003 15:53:42 -0700
Date: Fri, 3 Jan 2003 15:53:42 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030103155342.D30997@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <4CF48720B6E9D4118D040060CF2074E9072F6B9F@sonusdc3.sonusnet.com> <20030103222055.83970.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: <20030103222055.83970.qmail@web12806.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jan 03, 2003 at 02:20:55PM -0800
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, 03 Jan 2003 14:20:55)
> [TOLGA]I think I failed to explain what I mean. First,
> such procedures don't need interaction between
> SGP/ASP, so what one needs it to take ISUP spec and
> implement it according to it. 
> For your case, what I say is that one CGB maps to
> multiple CGB is it spans multiple RKs. So, each AS
> will receive just the part it is configured for. SG
> should wait for CGBAs and should generate one CGBA
> based ont he information received from them. So, there
> is no change necessary to the M3UA protocol.
> Everyhting is handled in SG, and the guideline is ISUP spec.
> Having said all of that, implementing such a logic on
> SG is really ugly, but the point is, it does not
> require something to be defined in the M3UA protocol
> itself.

Two things:

(1) having the SG change the content of an MSU
    changes the on-the-wire protocol.  M3UA does not change the
    content of MSUs that it passes to an AS.  (See section
    1.3.1)

(2) If SG does not alter the circuit group message in this case,
    the ISUP user at the AS would need to be changed from the
    standard ISUP state machines, otherwise, the AS will respond
    to the _entire_ circuit group message as is required by the
    ISUP specifications.

So M3UA does not support what you propose.

--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  Fri Jan  3 17:58:50 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 RAA21114
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 17:58:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03N7lm32269
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 18:07:47 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03N7BJ31905;
	Fri, 3 Jan 2003 18:07:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03N6wJ31686
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 18:06:58 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21106
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 17:57:29 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:7wWzURK21ahU9gkTm+k8WSi5QIegE6xo@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h03N0eD01963;
	Fri, 3 Jan 2003 16:00:40 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h03N0e600486;
	Fri, 3 Jan 2003 16:00:40 -0700
Date: Fri, 3 Jan 2003 16:00:40 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030103160040.E30997@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <4CF48720B6E9D4118D040060CF2074E9072F6B9F@sonusdc3.sonusnet.com> <20030103222533.65841.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: <20030103222533.65841.qmail@web12805.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jan 03, 2003 at 02:25:33PM -0800
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, 03 Jan 2003 14:25:33)
> [TOLGA] Please also note that M3UA does not put any
> restrictions on the type of rouye keys. So, it is SGs
> responsibility to support necessary management for
> them. Otherwise, we would need to explain for each and
> every possible RK type, what to do. Of course M3UA
> does not mandate SGs to support SSN/CIC based RKs. But
> if one SG wants to support it (without any changes to
> M3UA as defined in RFC/IG) it should be free to do so.

The M3UA SG is not free to change the content of an MSU.

Also, we went to lengths to indicate that the functions of
the SCCP are not reproduced in M3UA (see Sections 1.3.1 and
section 1.5.3.)  The same applies to ISUP.

Also, read section 1.1 carefully.

  "The delivery mechanism should meet the following criteria:

   *  Support for the transfer of all SS7 MTP3-User Part
      messages (e.g. ISUP ...

Remember that "should" and "SHOULD" are the same thing.

--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  Fri Jan  3 18:03: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 SAA21241
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 18:03:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03NCXo32524
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 18:12:33 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03NC8J32505;
	Fri, 3 Jan 2003 18:12:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03NBvJ32490
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 18:11:57 -0500
Received: from web12804.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA21229
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 18:02:28 -0500 (EST)
Message-ID: <20030103230539.54279.qmail@web12804.mail.yahoo.com>
Received: from [62.29.76.238] by web12804.mail.yahoo.com via HTTP; Fri, 03 Jan 2003 15:05:39 PST
Date: Fri, 3 Jan 2003 15:05:39 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <20030103155342.D30997@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, 03
> Jan 2003 14:20:55)
> > [TOLGA]I think I failed to explain what I mean.
> First,
> > such procedures don't need interaction between
> > SGP/ASP, so what one needs it to take ISUP spec
> and
> > implement it according to it. 
> > For your case, what I say is that one CGB maps to
> > multiple CGB is it spans multiple RKs. So, each AS
> > will receive just the part it is configured for.
> SG
> > should wait for CGBAs and should generate one CGBA
> > based ont he information received from them. So,
> there
> > is no change necessary to the M3UA protocol.
> > Everyhting is handled in SG, and the guideline is
> ISUP spec.
> > Having said all of that, implementing such a logic
> on
> > SG is really ugly, but the point is, it does not
> > require something to be defined in the M3UA
> protocol
> > itself.
> 
> Two things:
> 
> (1) having the SG change the content of an MSU
>     changes the on-the-wire protocol.  M3UA does not
> change the
>     content of MSUs that it passes to an AS.  (See
> section
>     1.3.1)
[TOLGA] If message filtering/generation is done in
NIF, I wouldn't think this as a violation. IMO,
important is, whether some special behavior is
expected from the peer, i.e. from ASP. IMO anything
else is not a change to the on the wire protocol. 
> 
> (2) If SG does not alter the circuit group message
> in this case,
[TOLGA] It will alter.
>     the ISUP user at the AS would need to be changed
> from the
>     standard ISUP state machines, otherwise, the AS
> will respond
>     to the _entire_ circuit group message as is
> required by the
>     ISUP specifications.
> 
> So M3UA does not support what you propose.
[TOLGA] Of course nobody will force anybody to support
it, but if somebody can support it wothout any
additional requirements to the on the wire protocol,
this also should be allowed (in fact, what can we do,
put the guy to the jail or declare the SGP incompliant
with M3UA-although it is working fine with any M3UA
compliant ASP- because it claims to support CIC RKs?)

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jan  3 18:04: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 SAA21261
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 18:04:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03NDFP32568
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 18:13:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03ND5J32560;
	Fri, 3 Jan 2003 18:13:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03NCNJ32514
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 18:12:23 -0500
Received: from rainier.illuminet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21234
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 18:02:54 -0500 (EST)
Received: from olwinexsmtp01.corp.illuminet.com (olwinexsmtp01.corp.illuminet.com [10.55.13.9]) by rainier.illuminet.com (8.8.8/8.8.8) with ESMTP id PAA11273; Fri, 3 Jan 2003 15:05:55 -0800 (PST)
Received: by olwinexsmtp01.corp.illuminet.com with Internet Mail Service (5.5.2656.59)
	id <ZJBXWN6M>; Fri, 3 Jan 2003 15:05:55 -0800
Message-ID: <A86F11FA6A39AC4A82EC59DA3A6FA363454E49@atwinfs01.corp.illuminet.com>
From: James Doss <JDoss@verisign.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>,
        "Wung, Joseph"
	 <JWung@sonusnet.com>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
Date: Fri, 3 Jan 2003 15:05:53 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
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 Joseph/Brian,
I was thinking IETF has a separate RFC for ISUP.
Is it not a good idea to start one. That will help to reduce the
complexities in the M3UA.
So that the ISUP and SCCP support can be seperated.

James Doss
Verisign 



-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: Friday, January 03, 2003 5:06 PM
To: Wung, Joseph
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages


Joseph,

I offerred to write one several times.  Nobody took me up
on my offer.

--brian

Wung, Joseph wrote:                      (Fri, 03 Jan 2003 11:35:13)
> Brian,
> 
> Is there ISUA anywhere?
> 
> Joe
> 
> > You will need to describe all that M3UA lacks in support
> > of CIC routing.  Once you are finished that exercise you
> > will have ISUA.  (As mentioned on the original thread
> > from July 2001.)
> > 
> > --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
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jan  3 18:11: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 SAA21403
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 18:11:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03NK9100381
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 18:20:09 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03NJRJ32766;
	Fri, 3 Jan 2003 18:19:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03NIbJ32731
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 18:18:37 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21330
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 18:09:08 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:GhS6aDbR4dn6dbcDaQf9wA3UY2lVOuOZ@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h03NCJD02132;
	Fri, 3 Jan 2003 16:12:19 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h03NCJA01019;
	Fri, 3 Jan 2003 16:12:19 -0700
Date: Fri, 3 Jan 2003 16:12:19 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030103161219.A751@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030103155342.D30997@openss7.org> <20030103230539.54279.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: <20030103230539.54279.qmail@web12804.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jan 03, 2003 at 03:05:39PM -0800
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, 03 Jan 2003 15:05:39)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                     (Fri, 03
> > Jan 2003 14:20:55)
> > > [TOLGA]I think I failed to explain what I mean.
> > First,
> > > such procedures don't need interaction between
> > > SGP/ASP, so what one needs it to take ISUP spec
> > and
> > > implement it according to it. 
> > > For your case, what I say is that one CGB maps to
> > > multiple CGB is it spans multiple RKs. So, each AS
> > > will receive just the part it is configured for.
> > SG
> > > should wait for CGBAs and should generate one CGBA
> > > based ont he information received from them. So,
> > there
> > > is no change necessary to the M3UA protocol.
> > > Everyhting is handled in SG, and the guideline is
> > ISUP spec.
> > > Having said all of that, implementing such a logic
> > on
> > > SG is really ugly, but the point is, it does not
> > > require something to be defined in the M3UA
> > protocol
> > > itself.
> > 
> > Two things:
> > 
> > (1) having the SG change the content of an MSU
> >     changes the on-the-wire protocol.  M3UA does not
> > change the
> >     content of MSUs that it passes to an AS.  (See
> > section
> >     1.3.1)
> [TOLGA] If message filtering/generation is done in
> NIF, I wouldn't think this as a violation. IMO,
> important is, whether some special behavior is
> expected from the peer, i.e. from ASP. IMO anything
> else is not a change to the on the wire protocol. 

But it *is* a change to on-the-wire protocol making it
un-M3UA.

> > 
> > (2) If SG does not alter the circuit group message
> > in this case,
> [TOLGA] It will alter.
> >     the ISUP user at the AS would need to be changed
> > from the
> >     standard ISUP state machines, otherwise, the AS
> > will respond
> >     to the _entire_ circuit group message as is
> > required by the
> >     ISUP specifications.
> > 
> > So M3UA does not support what you propose.
> [TOLGA] Of course nobody will force anybody to support
> it, but if somebody can support it wothout any
> additional requirements to the on the wire protocol,

Changing MSU content is a change to the on-the-wire
protocol.

--brian

> this also should be allowed (in fact, what can we do,
> put the guy to the jail or declare the SGP incompliant
> with M3UA-although it is working fine with any M3UA
> compliant ASP- because it claims to support CIC RKs?)
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.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 Jan  3 18:17: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 SAA21492
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 18:17:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03NQm200729
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 18:26:48 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03NQ7J00690;
	Fri, 3 Jan 2003 18:26:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03NPfJ00671
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 18:25:41 -0500
Received: from web12806.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA21454
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 18:16:12 -0500 (EST)
Message-ID: <20030103231924.92746.qmail@web12806.mail.yahoo.com>
Received: from [62.29.76.238] by web12806.mail.yahoo.com via HTTP; Fri, 03 Jan 2003 15:19:24 PST
Date: Fri, 3 Jan 2003 15:19:24 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <20030103160040.E30997@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, 03
> Jan 2003 14:25:33)
> > [TOLGA] Please also note that M3UA does not put
> any
> > restrictions on the type of rouye keys. So, it is
> SGs
> > responsibility to support necessary management for
> > them. Otherwise, we would need to explain for each
> and
> > every possible RK type, what to do. Of course M3UA
> > does not mandate SGs to support SSN/CIC based RKs.
> But
> > if one SG wants to support it (without any changes
> to
> > M3UA as defined in RFC/IG) it should be free to do
> so.
> 
> The M3UA SG is not free to change the content of an
> MSU.
> 
> Also, we went to lengths to indicate that the
> functions of
> the SCCP are not reproduced in M3UA (see Sections
> 1.3.1 and
> section 1.5.3.)  The same applies to ISUP.
[TOLGA] They can be implemented in NIF (like all of
the other ugly procedures)

> 
> Also, read section 1.1 carefully.
> 
>   "The delivery mechanism should meet the following
> criteria:
> 
>    *  Support for the transfer of all SS7 MTP3-User
> Part
>       messages (e.g. ISUP ...
> 
> Remember that "should" and "SHOULD" are the same
> thing.
[TOLGA]My understanding of this sentence: Traffic for
any user part should be supported.
If I do a ISUP mapping in NIF, is there a problem from
protocol point of view? 

We have different opinion about what is on the wire
protocol. For example if a have a SGP changing the MSU
(which you don't like), will your ASP complain when
talking to this SGP?

Do I find supporting CIC/SSN based routing with M3UA
easy/nice/elegant? This is a different question.
> 
> --brian
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jan  3 18:35: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 SAA21736
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 18:35:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03Nic102029
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 18:44:38 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03Ni9J02010;
	Fri, 3 Jan 2003 18:44:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03Nh4J01985
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 18:43:04 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21700
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 18:33:35 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Lc49FxbZQ2AyJyqa9n4MUfO0pGye8cSd@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h03NakD02419;
	Fri, 3 Jan 2003 16:36:46 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h03NakU03848;
	Fri, 3 Jan 2003 16:36:46 -0700
Date: Fri, 3 Jan 2003 16:36:46 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030103163646.B751@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030103160040.E30997@openss7.org> <20030103231924.92746.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: <20030103231924.92746.qmail@web12806.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jan 03, 2003 at 03:19:24PM -0800
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, 03 Jan 2003 15:19:24)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                       (Fri, 03
> > Jan 2003 14:25:33)
> > > [TOLGA] Please also note that M3UA does not put
> > any
> > > restrictions on the type of rouye keys. So, it is
> > SGs
> > > responsibility to support necessary management for
> > > them. Otherwise, we would need to explain for each
> > and
> > > every possible RK type, what to do. Of course M3UA
> > > does not mandate SGs to support SSN/CIC based RKs.
> > But
> > > if one SG wants to support it (without any changes
> > to
> > > M3UA as defined in RFC/IG) it should be free to do
> > so.
> > 
> > The M3UA SG is not free to change the content of an
> > MSU.
> > 
> > Also, we went to lengths to indicate that the
> > functions of
> > the SCCP are not reproduced in M3UA (see Sections
> > 1.3.1 and
> > section 1.5.3.)  The same applies to ISUP.
> [TOLGA] They can be implemented in NIF (like all of
> the other ugly procedures)

It doen't matter where you change the MSU: it is not a 
matter of functional placement.  The point is that the
on-the-wire protocol betwen SG and ASP is changed.

> > 
> > Also, read section 1.1 carefully.
> > 
> >   "The delivery mechanism should meet the following
> > criteria:
> > 
> >    *  Support for the transfer of all SS7 MTP3-User
> > Part
> >       messages (e.g. ISUP ...
> > 
> > Remember that "should" and "SHOULD" are the same
> > thing.
> [TOLGA]My understanding of this sentence: Traffic for
> any user part should be supported.
> If I do a ISUP mapping in NIF, is there a problem from
> protocol point of view? 

The sentence says "transfer" not "traffic".


-- 
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 Jan  3 18:41: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 SAA21794
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 18:41:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h03Nog402181
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 18:50:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03No7J02141;
	Fri, 3 Jan 2003 18:50:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h03NnOJ02107
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 18:49:24 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21767
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 18:39:54 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:mbj4VumEkB6lWSKWTHPtD6wW6GnhzJJ0@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h03Nh6D02498;
	Fri, 3 Jan 2003 16:43:06 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h03Nh6N04619;
	Fri, 3 Jan 2003 16:43:06 -0700
Date: Fri, 3 Jan 2003 16:43:06 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030103164306.C751@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030103160040.E30997@openss7.org> <20030103231924.92746.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: <20030103231924.92746.qmail@web12806.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jan 03, 2003 at 03:19:24PM -0800
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,

Let's go one step further with this.

What happens when an AS across the circuit group split goes
AS-INACTIVE and the other is AS-ACTIVE?  What will the SG do?

In ISUP the entire User-Part is equipped or unequipped,
acessible or inaccessible.

What will the SG do when only a one part of a circuit range is
inaccessible?

--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  Fri Jan  3 19:08: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 TAA22067
	for <sigtran-archive@odin.ietf.org>; Fri, 3 Jan 2003 19:08:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h040HTN03510
	for sigtran-archive@odin.ietf.org; Fri, 3 Jan 2003 19:17:29 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h040H8J03495;
	Fri, 3 Jan 2003 19:17:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h040GTJ03479
	for <sigtran@optimus.ietf.org>; Fri, 3 Jan 2003 19:16:29 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22044
	for <sigtran@ietf.org>; Fri, 3 Jan 2003 19:06:58 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:QGX7BQlMBcu2QEN7pdTLOrEIwKDR2skH@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h040AAD02872;
	Fri, 3 Jan 2003 17:10:10 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h040A9T05342;
	Fri, 3 Jan 2003 17:10:09 -0700
Date: Fri, 3 Jan 2003 17:10:09 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030103171009.D751@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030103155342.D30997@openss7.org> <20030103230539.54279.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: <20030103230539.54279.qmail@web12804.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jan 03, 2003 at 03:05:39PM -0800
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, 03 Jan 2003 15:05:39)
> [TOLGA] If message filtering/generation is done in
> NIF, I wouldn't think this as a violation. IMO,
> important is, whether some special behavior is
> expected from the peer, i.e. from ASP. IMO anything
> else is not a change to the on the wire protocol. 

Filtering (message discrimination and routing) and
generation (of MTP management messages) are MTP Level
3 functions.  These do not reside in the NIF, they
reside in MTP Level 3.

Filtering and generation of ISUP messages is not an
MTP Level 3 function.  Placing these functions on an
SG result in the SG performing a part of the functions
of ISUP.  Unfortunately, to properly perform most ISUP
functions requires that the function be aware of
circuit-state.  M3UA protocol has no mechanism for
coordinating circuit state between SG and ASP.
Circuit state is the sole domain of ISUP at the ASP.

Trying to "fake out" ISUP state machines at the ASP
makes presumptions about ISUP implementation and ISUP
configuration at the ASP.  The only way to ensure that
these presumptions hold is to place requirements on
ISUP at the ASP.  It is not in fitting with M3UA's
purpose or intention to place requirements on ISUP
implementation or configuration at an ASP.

Routing on CIC requires that management functions
still interwork at the SG.  M3UA (by nature of the
MTP3 below it) has procedures when signalling point
codes change state (e.g. transfer-prohibited) and when
MTP-Users change state (e.g. user-part-unavailable),
but M3UA has no procedures to handle a CIC range
becoming unacessible (there is no such state for a
circuit).  Therefore M3UA is unequipped to deal with
CIC Routing.

On the other hand, M3UA is well equipped to perform
OPC/CIC load-sharing within an AS which only uses
DPC/SI as a routing key.  This is because either the
entire user part is available or it is unavailable.

One could even argue that M3UA can perform
load-sharing on CIC within an AS within a OPC/DPC/SI
routing key (presuming that an originating SS7 node
does not aggregate remote user state across multiple
OPCs).

When load-sharing, either the entire AS is available
or it is not.  M3UA can properly manage SPMC state as
well as user state witin the SPMC.

So, there is much more to consider than just faking
out circuit group messages.

Circuit-state is integral to all ISUP state machine
functions.  Experience has shown that when one
attempts to separate functions without regard to
circuit state, the result is hung circuits,
maintenance alarms and overhead, repeated and annoying
manual interventions, unnecessary cost and loss of
revenue.

--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  Sat Jan  4 08:41:57 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 IAA10668
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 08:41:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04DpDp19383
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 08:51:13 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04DonJ19372;
	Sat, 4 Jan 2003 08:50:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04DlIJ19295
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 08:47:18 -0500
Received: from web12801.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA10599
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 08:37:31 -0500 (EST)
Message-ID: <20030104134043.64635.qmail@web12801.mail.yahoo.com>
Received: from [62.29.64.35] by web12801.mail.yahoo.com via HTTP; Sat, 04 Jan 2003 05:40:43 PST
Date: Sat, 4 Jan 2003 05:40:43 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <20030103171009.D751@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,
> 03 Jan 2003 15:05:39)
> > [TOLGA] If message filtering/generation is done in
> > NIF, I wouldn't think this as a violation. IMO,
> > important is, whether some special behavior is
> > expected from the peer, i.e. from ASP. IMO
> anything
> > else is not a change to the on the wire protocol. 
> 
> Filtering (message discrimination and routing) and
> generation (of MTP management messages) are MTP
> Level
> 3 functions.  These do not reside in the NIF, they
> reside in MTP Level 3.
[TOLGA] You can filter/generate messages at any layer.
If you filter MTP3 messages it is done of course in
MTP3. If one is interested in ISUP messages, it is in
ISUP.
> 
> Filtering and generation of ISUP messages is not an
> MTP Level 3 function.  Placing these functions on an
> SG result in the SG performing a part of the
> functions
> of ISUP.  Unfortunately, to properly perform most
> ISUP
> functions requires that the function be aware of
> circuit-state.  M3UA protocol has no mechanism for
> coordinating circuit state between SG and ASP.
> Circuit state is the sole domain of ISUP at the ASP.
[TOLGA] I agree that SG will need to keep ISUP related
info and implement some ISUP logic in this case. But
the point is, no additon to M3UA is necessary. Based
on AS state and by checking ISUP messages necessary
information can be kept.
> 
> Trying to "fake out" ISUP state machines at the ASP
> makes presumptions about ISUP implementation and
> ISUP
> configuration at the ASP.  The only way to ensure
> that
> these presumptions hold is to place requirements on
> ISUP at the ASP.  It is not in fitting with M3UA's
> purpose or intention to place requirements on ISUP
> implementation or configuration at an ASP.
> 
> Routing on CIC requires that management functions
> still interwork at the SG.  M3UA (by nature of the
> MTP3 below it) has procedures when signalling point
> codes change state (e.g. transfer-prohibited) and
> when
> MTP-Users change state (e.g. user-part-unavailable),
> but M3UA has no procedures to handle a CIC range
> becoming unacessible (there is no such state for a
> circuit).  Therefore M3UA is unequipped to deal with
> CIC Routing.
[TOLGA] In such a case, I would think one can block
the circuit. Or alternatively, even when one AS
(serving a CIC range) goes inactive, SG declares user
part unavailable.
> 
> On the other hand, M3UA is well equipped to perform
> OPC/CIC load-sharing within an AS which only uses
> DPC/SI as a routing key.  This is because either the
> entire user part is available or it is unavailable.
[TOLGA] I also would prefer this method. As I said
several times, I don't consider CIC based RKs as a
good alternative and as elegant. But if one tries to
support them without an additional requirement to
M3UA, let them try it. Whether they succeed or fail is
their problem. Especially SSN based routing for
class0/class1 seems doable for me. There might be also
RK types, which require a managent logic to be
implemented in SG, IMO as long as it does not put
additonal requirement to M3UA, there is no problem. 
> 
> One could even argue that M3UA can perform
> load-sharing on CIC within an AS within a OPC/DPC/SI
> routing key (presuming that an originating SS7 node
> does not aggregate remote user state across multiple
> OPCs).
> 
> When load-sharing, either the entire AS is available
> or it is not.  M3UA can properly manage SPMC state
> as
> well as user state witin the SPMC.
> 
> So, there is much more to consider than just faking
> out circuit group messages.
> 
> Circuit-state is integral to all ISUP state machine
> functions.  Experience has shown that when one
> attempts to separate functions without regard to
> circuit state, the result is hung circuits,
> maintenance alarms and overhead, repeated and
> annoying
> manual interventions, unnecessary cost and loss of
> revenue.
> 
> --brian
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan  4 08:59: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 IAA10766
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 08:59:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04E8GI20433
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 09:08:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04E84J20419;
	Sat, 4 Jan 2003 09:08:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04E50J19747
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 09:05:00 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10749
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 08:55:11 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:q3hI1qCFyXjzpJZS63BflcIqewSJOwJV@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h04DwOD12873;
	Sat, 4 Jan 2003 06:58:24 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h04DwOo24061;
	Sat, 4 Jan 2003 06:58:24 -0700
Date: Sat, 4 Jan 2003 06:58:24 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030104065823.A23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030103171009.D751@openss7.org> <20030104134043.64635.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: <20030104134043.64635.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 04, 2003 at 05:40:43AM -0800
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, 04 Jan 2003 05:40:43)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                         (Fri,
> > 03 Jan 2003 15:05:39)
> > > [TOLGA] If message
> > > filtering/generation is done in NIF,
> > > I wouldn't think this as a
> > > violation. IMO, important is,
> > > whether some special behavior is
> > > expected from the peer, i.e. from
> > > ASP. IMO anything else is not a
> > > change to the on the wire protocol. 
> > 
> > Filtering (message discrimination and
> > routing) and generation (of MTP
> > management messages) are MTP Level 3
> > functions.  These do not reside in the
> > NIF, they reside in MTP Level 3.
> [TOLGA] You can filter/generate messages
> at any layer.  If you filter MTP3
> messages it is done of course in MTP3.
> If one is interested in ISUP messages,
> it is in ISUP.
> > 
> > Filtering and generation of ISUP
> > messages is not an MTP Level 3
> > function.  Placing these functions on
> > an SG result in the SG performing a
> > part of the functions of ISUP.
> > Unfortunately, to properly perform
> > most ISUP functions requires that the
> > function be aware of circuit-state.
> > M3UA protocol has no mechanism for
> > coordinating circuit state between SG
> > and ASP.  Circuit state is the sole
> > domain of ISUP at the ASP.
> [TOLGA] I agree that SG will need to
> keep ISUP related info and implement
> some ISUP logic in this case. But the
> point is, no additon to M3UA is
> necessary. Based on AS state and by
> checking ISUP messages necessary
> information can be kept.

M3UA is not just message syntax, it is
procedures.  By adding procedures, you are
changing M3UA.

> > 
> > Trying to "fake out" ISUP state
> > machines at the ASP makes presumptions
> > about ISUP implementation and ISUP
> > configuration at the ASP.  The only
> > way to ensure that these presumptions
> > hold is to place requirements on ISUP
> > at the ASP.  It is not in fitting with
> > M3UA's purpose or intention to place
> > requirements on ISUP implementation or
> > configuration at an ASP.
> > 
> > Routing on CIC requires that
> > management functions still interwork
> > at the SG.  M3UA (by nature of the
> > MTP3 below it) has procedures when
> > signalling point codes change state
> > (e.g. transfer-prohibited) and when
> > MTP-Users change state (e.g.
> > user-part-unavailable), but M3UA has
> > no procedures to handle a CIC range
> > becoming unacessible (there is no such
> > state for a circuit).  Therefore M3UA
> > is unequipped to deal with CIC
> > Routing.
> [TOLGA] In such a case, I would think
> one can block the circuit. Or
> alternatively, even when one AS (serving
> a CIC range) goes inactive, SG declares
> user part unavailable.

The circuit is neither blocked from a
hardware or a maintenance perspective.
The blocking state of the circuit is at
the ASP (not at the SG).  How can the SG
know whether the circuit is already
blocked or not?  If the SG blocks an
already blocked circuit, maintenance
alarms will trigger at the remote end on a
per-circuit basis.

Sending UPU is incorrect unless the other
AS based on routing key are taken out of
service as well (they cannot be allowed to
send messages when UPU is signalled).  How
will the SG know when they are available
again if it forces all the AS out of
service with, say, ASPIA ACK?  How does it
know when it can activate them again and
when to stop sending UPU?

You see, circuit blocking is incorrect
(because the SG does not know the circuit
state), and UPU is incorrect (because
routing is being performed sub SI).  This
is why M3UA has insufficient support for
CIC routing.

If one load-shares on CIC (rather than
routing) there is no problem.

> > 
> > On the other hand, M3UA is well
> > equipped to perform OPC/CIC
> > load-sharing within an AS which only
> > uses DPC/SI as a routing key.  This is
> > because either the entire user part is
> > available or it is unavailable.
> [TOLGA] I also would prefer this method.
> As I said several times, I don't
> consider CIC based RKs as a good
> alternative and as elegant. But if one
> tries to support them without an
> additional requirement to M3UA, let them
> try it.

Why?  If they want to experiment, let them
experiment outside the standard.

> Whether they succeed or fail is their
> problem.

Let them succeed or fail outside the
standard.

Besides, who are these people?  They do
not exist.

> Especially SSN based routing for
> class0/class1 seems doable for me.

Can't handle management either.  SUA is
the recommended way to transport
SCCP/SCCP-User interface.

> There might be also RK types, which
> require a managent logic to be
> implemented in SG, IMO as long as it
> does not put additonal requirement to
> M3UA, there is no problem. 

Adding procedures outside MTP3 is placing
additional requirement on M3UA (not to
mention placing requirement on the ASP),
so all of them have a problem.

--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  Sat Jan  4 09:16: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 JAA10918
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 09:16:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04EPZU20895
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 09:25:35 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04EPAJ20850;
	Sat, 4 Jan 2003 09:25:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04EMAJ20740
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 09:22:10 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10884
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 09:12:22 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:8ZKCkNSNs0SfF4HCEYJgnD2/x0upH2k6@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h04EFZD13098;
	Sat, 4 Jan 2003 07:15:35 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h04EFZZ24491;
	Sat, 4 Jan 2003 07:15:35 -0700
Date: Sat, 4 Jan 2003 07:15:35 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030104071535.B23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030103171009.D751@openss7.org> <20030104134043.64635.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: <20030104134043.64635.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 04, 2003 at 05:40:43AM -0800
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, 04 Jan 2003 05:40:43)
> [TOLGA] I agree that SG will need to keep ISUP related
> info and implement some ISUP logic in this case. But
> the point is, no additon to M3UA is necessary. Based
> on AS state and by checking ISUP messages necessary
> information can be kept.

Take a look at the AS to SG direction now:

I have two AS1 RK=5/6/CIC=0-23 and AS2
RK=5/6/CIC=32-54.

AS1 sends a maintenance oriented CGB
message for CIC=21-42 and expects an
identical range in CGBA.

It might happen that CIC=39 is either
unequipped or not under the control of
ISUP at the remote switch.

How does your SG get the correct messages
(possibly CGBA) back to AS1?

--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  Sat Jan  4 09:18: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 JAA10942
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 09:18:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04ES4P20965
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 09:28:04 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04ERsJ20947;
	Sat, 4 Jan 2003 09:27:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04EP5J20844
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 09:25:05 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10900
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 09:15:17 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:UTCQ9yyHmkQNchxj11+JJUvwBntOUtwi@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h04EIUD13128;
	Sat, 4 Jan 2003 07:18:30 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h04EITi24505;
	Sat, 4 Jan 2003 07:18:29 -0700
Date: Sat, 4 Jan 2003 07:18:29 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030104071829.C23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030103171009.D751@openss7.org> <20030104134043.64635.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: <20030104134043.64635.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 04, 2003 at 05:40:43AM -0800
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, 04 Jan 2003 05:40:43)
> [TOLGA] In such a case, I would think one can block
> the circuit. Or alternatively, even when one AS
> (serving a CIC range) goes inactive, SG declares user
> part unavailable.

If you block the circuits, what happens when
a test call (IAM) is received for one of the
circuits which has no active AS?

--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  Sat Jan  4 09:25:57 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 JAA11016
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 09:25:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04EZEr21174
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 09:35:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04EYtJ21150;
	Sat, 4 Jan 2003 09:34:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04EWoJ21111
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 09:32:50 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10981
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 09:23:02 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:XSwkKt0vkUPxpQxrEpqK5wxpGmBIdfMH@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h04EQFD13227;
	Sat, 4 Jan 2003 07:26:15 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h04EQEh24695;
	Sat, 4 Jan 2003 07:26:14 -0700
Date: Sat, 4 Jan 2003 07:26:14 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030104072614.D23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030103171009.D751@openss7.org> <20030104134043.64635.qmail@web12801.mail.yahoo.com> <20030104071829.C23879@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: <20030104071829.C23879@openss7.org>; from bidulock@openss7.org on Sat, Jan 04, 2003 at 07:18: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,

Brian F. G. Bidulock wrote:                                                          (Sat, 04 Jan 2003 07:18:29)
> Tolga,
> 
> Tolga Asveren wrote:                                                                 (Sat, 04 Jan 2003 05:40:43)
> > [TOLGA] In such a case, I would think one can block
> > the circuit. Or alternatively, even when one AS
> > (serving a CIC range) goes inactive, SG declares user
> > part unavailable.
> 
> If you block the circuits, what happens when
> a test call (IAM) is received for one of the
> circuits which has no active AS?
> 

The SG must not block unallocated circuits
within the CIC range.

How does the SG know when circuits have
been deallocated (no longer under ISUP
control)?

--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  Sat Jan  4 09:28: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 JAA11075
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 09:28:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04Ec4m21917
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 09:38:04 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04EbsJ21864;
	Sat, 4 Jan 2003 09:37:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04EZ6J21166
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 09:35:06 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10996
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 09:25:18 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:C8toeAsH0WMLa4pIbY46XKYOb3vPqkgH@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h04ESVD13246;
	Sat, 4 Jan 2003 07:28:31 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h04ESUr24707;
	Sat, 4 Jan 2003 07:28:30 -0700
Date: Sat, 4 Jan 2003 07:28:30 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030104072830.E23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030103171009.D751@openss7.org> <20030104134043.64635.qmail@web12801.mail.yahoo.com> <20030104071829.C23879@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: <20030104071829.C23879@openss7.org>; from bidulock@openss7.org on Sat, Jan 04, 2003 at 07:18: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,

Brian F. G. Bidulock wrote:                                                          (Sat, 04 Jan 2003 07:18:29)
> Tolga,
> 
> Tolga Asveren wrote:                                                                 (Sat, 04 Jan 2003 05:40:43)
> > [TOLGA] In such a case, I would think one can block
> > the circuit. Or alternatively, even when one AS
> > (serving a CIC range) goes inactive, SG declares user
> > part unavailable.
> 
> If you block the circuits, what happens when
> a test call (IAM) is received for one of the
> circuits which has no active AS?
> 

When an AS is down, how does your SG respond to
circuit query messages?

--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  Sat Jan  4 09:31:57 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 JAA11136
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 09:31:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04EfEp22046
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 09:41:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04EeuJ22029;
	Sat, 4 Jan 2003 09:40:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04EctJ21958
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 09:38:55 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11097
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 09:29:07 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:q+bYc6xQSyWG4n/020RXo/4o3+1xwhan@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h04EWKD13315;
	Sat, 4 Jan 2003 07:32:20 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h04EWJs24881;
	Sat, 4 Jan 2003 07:32:19 -0700
Date: Sat, 4 Jan 2003 07:32:19 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030104073219.F23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030103171009.D751@openss7.org> <20030104134043.64635.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: <20030104134043.64635.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 04, 2003 at 05:40:43AM -0800
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, 04 Jan 2003 05:40:43)
> [TOLGA] In such a case, I would think one can block
> the circuit. Or alternatively, even when one AS
> (serving a CIC range) goes inactive, SG declares user
> part unavailable.

Does the SG deactivate the other AS?

Must all the AS either be active or inactive together?

How are the AS brought active in the first place?  Must
they all be activated at the same time?

--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  Sat Jan  4 09:35:56 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 JAA11253
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 09:35:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04EjDl22226
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 09:45:13 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04EitJ22193;
	Sat, 4 Jan 2003 09:44:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04EgYJ22116
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 09:42:34 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11167
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 09:32:45 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:KPk711AqONST1UGuZj1QLVkr5sCaOERd@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h04EZwD13353;
	Sat, 4 Jan 2003 07:35:58 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h04EZwr24929;
	Sat, 4 Jan 2003 07:35:58 -0700
Date: Sat, 4 Jan 2003 07:35:58 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030104073558.G23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030103171009.D751@openss7.org> <20030104134043.64635.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: <20030104134043.64635.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 04, 2003 at 05:40:43AM -0800
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,

How does your SG handle circuit group messages that have
ANSI pre-arranged circuit groups?  (These are circuit
group messages that have one CIC in the label and a range
of zero, where the actual members of the group are
configured at the receiving switch.)  How does your SG
know which circuits are in the pre-arranged group?

--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  Sat Jan  4 09:42: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 JAA11394
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 09:42:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04Epkq22493
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 09:51:46 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04EpSJ22463;
	Sat, 4 Jan 2003 09:51:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04EmGJ22349
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 09:48:16 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11343
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 09:38:27 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:9fevICLuUVz44nzkR2YrhbRacgStLBqF@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h04EfeD13415;
	Sat, 4 Jan 2003 07:41:40 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h04Efeg25011;
	Sat, 4 Jan 2003 07:41:40 -0700
Date: Sat, 4 Jan 2003 07:41:40 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030104074140.H23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030103171009.D751@openss7.org> <20030104134043.64635.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: <20030104134043.64635.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 04, 2003 at 05:40:43AM -0800
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,

When a circuit within an existing
CIC-range is taken out of service
(permanently and no longer under the
control of ISUP), how does your SG know
that this has happened?

--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  Sat Jan  4 09:44: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 JAA11443
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 09:44:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04Es5N22628
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 09:54:05 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04ErtJ22594;
	Sat, 4 Jan 2003 09:53:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04EpuJ22514
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 09:51:56 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11388
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 09:42:07 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Iqyhg8JOl39tEzZegq8tc27Fq3dDIDCL@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h04EjKD13458;
	Sat, 4 Jan 2003 07:45:20 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h04EjKg25049;
	Sat, 4 Jan 2003 07:45:20 -0700
Date: Sat, 4 Jan 2003 07:45:20 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030104074520.I23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030103171009.D751@openss7.org> <20030104134043.64635.qmail@web12801.mail.yahoo.com> <20030104071829.C23879@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: <20030104071829.C23879@openss7.org>; from bidulock@openss7.org on Sat, Jan 04, 2003 at 07:18: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,

Brian F. G. Bidulock wrote:                                                          (Sat, 04 Jan 2003 07:18:29)
> Tolga,
> 
> Tolga Asveren wrote:                                                                 (Sat, 04 Jan 2003 05:40:43)
> > [TOLGA] In such a case, I would think one can block
> > the circuit. Or alternatively, even when one AS
> > (serving a CIC range) goes inactive, SG declares user
> > part unavailable.
> 
> If you block the circuits, what happens when
> a test call (IAM) is received for one of the
> circuits which has no active AS?
> 

What happens if you get a CCR for one of these
circuits?

--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  Sat Jan  4 11:20: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 LAA12970
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 11:20:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04GUFB27298
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 11:30:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04GTsJ27263;
	Sat, 4 Jan 2003 11:29:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04GQoJ27186
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 11:26:50 -0500
Received: from web12801.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA12932
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 11:16:59 -0500 (EST)
Message-ID: <20030104162013.83379.qmail@web12801.mail.yahoo.com>
Received: from [62.29.64.35] by web12801.mail.yahoo.com via HTTP; Sat, 04 Jan 2003 08:20:13 PST
Date: Sat, 4 Jan 2003 08:20:13 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <20030104065823.A23879@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,
[... a lot of snipping here...]
> Adding procedures outside MTP3 is placing
> additional requirement on M3UA (not to
> mention placing requirement on the ASP),
> so all of them have a problem.
[TOLGA] I will not try to answer your list of ISUP
related questions, they might be problems which might
be solved or not and I am not planning to implement it
now and I believe here we are discussing what
implications it might have on M3UA itself. Your
questions are related with the part outside of the
scope of M3UA. The key point is that you think SG only
as MTP3 and M3UA. This is not my view. It has a big
fat NIF inside. And I can also put whatever I want
there, as long as it can interoperate with M3UA
compliant ASPs. So, in fact there is no point to
discuss this, your ASP even won't feel it(if it feels
then of course you can complain). You say let the
people experiment outside of the protocol, this is
also what I am saying. As long as necessary logic is
kept only in SG and existing M3UA protocol is used,
there is no problem from M3UA point of view. So,
please keep it as it is, no restriction on RKs for
static case (especially SSN based for class0/class1
seems implementable to me for now, but this is besides
the point, easy or difficult, it is outside of M3UA
protocol itself and is a problem for persons, which
want to implement it)

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan  4 11:40: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 LAA13230
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 11:40:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04GnWU28537
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 11:49:32 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04GmuJ28524;
	Sat, 4 Jan 2003 11:48:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04GktJ28465
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 11:46:55 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13174
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 11:37:03 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:EyXByjHvOf7JWRbmURrKhAQBny0JLsj3@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h04GeHD14786;
	Sat, 4 Jan 2003 09:40:17 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h04GeGI27292;
	Sat, 4 Jan 2003 09:40:16 -0700
Date: Sat, 4 Jan 2003 09:40:16 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030104094016.J23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030104065823.A23879@openss7.org> <20030104162013.83379.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: <20030104162013.83379.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 04, 2003 at 08:20:13AM -0800
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, 04 Jan 2003 08:20:13)
> Brian,
> [... a lot of snipping here...]
> > Adding procedures outside MTP3 is placing
> > additional requirement on M3UA (not to
> > mention placing requirement on the ASP),
> > so all of them have a problem.
> [TOLGA] I will not try to answer your list of ISUP
> related questions, they might be problems which might
> be solved or not and I am not planning to implement it
> now and I believe here we are discussing what
> implications it might have on M3UA itself. Your
> questions are related with the part outside of the
> scope of M3UA. The key point is that you think SG only
> as MTP3 and M3UA. This is not my view. It has a big
> fat NIF inside. And I can also put whatever I want
> there, as long as it can interoperate with M3UA
> compliant ASPs. So, in fact there is no point to
> discuss this, your ASP even won't feel it(if it feels
> then of course you can complain). You say let the
> people experiment outside of the protocol, this is
> also what I am saying. As long as necessary logic is
> kept only in SG and existing M3UA protocol is used,
> there is no problem from M3UA point of view. So,
> please keep it as it is, no restriction on RKs for
> static case (especially SSN based for class0/class1
> seems implementable to me for now, but this is besides
> the point, easy or difficult, it is outside of M3UA
> protocol itself and is a problem for persons, which
> want to implement it)

I'm afraid you will have to answer the AS state related
questions if you wish to maintain the position that
M3UA "supports" CIC routing keys.

The list of questions serve to illustrate the many ways
in which CIC routing keys break interoperability.

Also, here is another:

The ASP is under no requirement to send the ack messages
to the same SG from which it received the blocking message.

How does your message splitting algorithm work when
multiple SG's are involved?

--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  Sat Jan  4 12:01: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 MAA13461
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 12:01:13 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04HAYr29892
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 12:10:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04HA0J29857;
	Sat, 4 Jan 2003 12:10:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04H6aJ29109
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 12:06:36 -0500
Received: from web12808.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA13387
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 11:56:44 -0500 (EST)
Message-ID: <20030104165958.28227.qmail@web12808.mail.yahoo.com>
Received: from [62.29.64.35] by web12808.mail.yahoo.com via HTTP; Sat, 04 Jan 2003 08:59:58 PST
Date: Sat, 4 Jan 2003 08:59:58 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <20030104094016.J23879@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:                                
>                                 (Sat, 04 Jan 2003
> 08:20:13)
> > Brian,
> > [... a lot of snipping here...]
> > > Adding procedures outside MTP3 is placing
> > > additional requirement on M3UA (not to
> > > mention placing requirement on the ASP),
> > > so all of them have a problem.
> > [TOLGA] I will not try to answer your list of ISUP
> > related questions, they might be problems which
> might
> > be solved or not and I am not planning to
> implement it
> > now and I believe here we are discussing what
> > implications it might have on M3UA itself. Your
> > questions are related with the part outside of the
> > scope of M3UA. The key point is that you think SG
> only
> > as MTP3 and M3UA. This is not my view. It has a
> big
> > fat NIF inside. And I can also put whatever I want
> > there, as long as it can interoperate with M3UA
> > compliant ASPs. So, in fact there is no point to
> > discuss this, your ASP even won't feel it(if it
> feels
> > then of course you can complain). You say let the
> > people experiment outside of the protocol, this is
> > also what I am saying. As long as necessary logic
> is
> > kept only in SG and existing M3UA protocol is
> used,
> > there is no problem from M3UA point of view. So,
> > please keep it as it is, no restriction on RKs for
> > static case (especially SSN based for
> class0/class1
> > seems implementable to me for now, but this is
> besides
> > the point, easy or difficult, it is outside of
> M3UA
> > protocol itself and is a problem for persons,
> which
> > want to implement it)
> 
> I'm afraid you will have to answer the AS state
> related
> questions if you wish to maintain the position that
> M3UA "supports" CIC routing keys.
[TOLGA] Answer for all of your AS related questions
is, if one wants to support CIC based RK with M3UA,
then they should comply with what it stands in M3UA,
so whatever they do, they shouldn't violate RFC/IG,
i.e. AS related procedures there. And also I believe
it is left to the implementors, which types of RKs
they want to "support", as long as they are compliant
with M3UA.  
> 
> The list of questions serve to illustrate the many
> ways
> in which CIC routing keys break interoperability.
[TOLGA] Your questions are related with ISUP. If one
tries to solve them by putting additional requirements
on M3UA itself, then this would break the
interoperability.
> 
> Also, here is another:
> 
> The ASP is under no requirement to send the ack
> messages
> to the same SG from which it received the blocking
> message.
> 
> How does your message splitting algorithm work when
> multiple SG's are involved?
[TOLGA[ Do you think multiple SG case is handled
properly even for DPC+SI based RKs? So the answer
would be, only connection to one SG is supported (well
I couldn't stop myself and answered, because multiple
SG with ASP/SGP scenario is not my favorite model)

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan  4 12:26: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 MAA13738
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 12:26:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04HZd130499
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 12:35:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04HZKJ30478;
	Sat, 4 Jan 2003 12:35:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04HW4J30407
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 12:32:04 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13696
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 12:22:12 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:ng0/XzFzMM0MSSL+XP/tG5ypJLogENsa@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h04HPOD15275;
	Sat, 4 Jan 2003 10:25:24 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h04HPOf27960;
	Sat, 4 Jan 2003 10:25:24 -0700
Date: Sat, 4 Jan 2003 10:25:24 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030104102524.K23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030104094016.J23879@openss7.org> <20030104165958.28227.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: <20030104165958.28227.qmail@web12808.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 04, 2003 at 08:59:58AM -0800
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, 04 Jan 2003 08:59:58)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Sat, 04 Jan 2003
> > 08:20:13)
> > > Brian,
> > > [... a lot of snipping here...]
> > > > Adding procedures outside MTP3 is placing
> > > > additional requirement on M3UA (not to
> > > > mention placing requirement on the ASP),
> > > > so all of them have a problem.
> > > [TOLGA] I will not try to answer your list of ISUP
> > > related questions, they might be problems which
> > might
> > > be solved or not and I am not planning to
> > implement it
> > > now and I believe here we are discussing what
> > > implications it might have on M3UA itself. Your
> > > questions are related with the part outside of the
> > > scope of M3UA. The key point is that you think SG
> > only
> > > as MTP3 and M3UA. This is not my view. It has a
> > big
> > > fat NIF inside. And I can also put whatever I want
> > > there, as long as it can interoperate with M3UA
> > > compliant ASPs. So, in fact there is no point to
> > > discuss this, your ASP even won't feel it(if it
> > feels
> > > then of course you can complain). You say let the
> > > people experiment outside of the protocol, this is
> > > also what I am saying. As long as necessary logic
> > is
> > > kept only in SG and existing M3UA protocol is
> > used,
> > > there is no problem from M3UA point of view. So,
> > > please keep it as it is, no restriction on RKs for
> > > static case (especially SSN based for
> > class0/class1
> > > seems implementable to me for now, but this is
> > besides
> > > the point, easy or difficult, it is outside of
> > M3UA
> > > protocol itself and is a problem for persons,
> > which
> > > want to implement it)
> > 
> > I'm afraid you will have to answer the AS state
> > related
> > questions if you wish to maintain the position that
> > M3UA "supports" CIC routing keys.
> [TOLGA] Answer for all of your AS related questions
> is, if one wants to support CIC based RK with M3UA,
> then they should comply with what it stands in M3UA,
> so whatever they do, they shouldn't violate RFC/IG,
> i.e. AS related procedures there. And also I believe
> it is left to the implementors, which types of RKs
> they want to "support", as long as they are compliant
> with M3UA.  

So I take it you can't figure out how any of these
would work.  As there is no basis for interoperability,
(not even one way that things can work), it is certainly
not supported by M3UA.

> > 
> > The list of questions serve to illustrate the many
> > ways
> > in which CIC routing keys break interoperability.
> [TOLGA] Your questions are related with ISUP. If one
> tries to solve them by putting additional requirements
> on M3UA itself, then this would break the
> interoperability.

And that is why M3UA does not support CIC Routing Keys,
because, solving the problems it creates would break
interoperability.

> > 
> > Also, here is another:
> > 
> > The ASP is under no requirement to send the ack
> > messages
> > to the same SG from which it received the blocking
> > message.
> > 
> > How does your message splitting algorithm work when
> > multiple SG's are involved?
> [TOLGA[ Do you think multiple SG case is handled
> properly even for DPC+SI based RKs?

Yes.

> So the answer would be, only connection to one SG is
> supported (well I couldn't stop myself and answered,
> because multiple SG with ASP/SGP scenario is not my
> favorite model)

So where in the RFC does it say that only one SG can
be supported for CIC Routing Keys?

Now how about multiple SGP in the same SG?  Because
certainly the ack might go back to a different SGP
that the one which split the group message.

So, are CIC Routing Keys only supported on a single SG
made up of a single SGP?

And you never answered the question of the AS sending
the circuit group message spanning Routing Contexts to
the SG.  The SG cannot split these, how, is it to get
the (correct) response back to the correct place?

Also, you didn't say how your splitting algorithm is
going to split pre-arranged circuit group messages...

--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  Sat Jan  4 15:04: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 PAA15226
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 15:04:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04KE4h05488
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 15:14:04 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04KDbJ05471;
	Sat, 4 Jan 2003 15:13:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04KAwJ05420
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 15:10:58 -0500
Received: from web12807.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA15210
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 15:01:03 -0500 (EST)
Message-ID: <20030104200416.59789.qmail@web12807.mail.yahoo.com>
Received: from [62.29.65.171] by web12807.mail.yahoo.com via HTTP; Sat, 04 Jan 2003 12:04:16 PST
Date: Sat, 4 Jan 2003 12:04:16 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <20030104102524.K23879@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:                                
>                                 (Sat, 04 Jan 2003
> 08:59:58)
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Tolga Asveren wrote:                            
>    
> > >                                 (Sat, 04 Jan
> 2003
> > > 08:20:13)
> > > > Brian,
> > > > [... a lot of snipping here...]
> > > > > Adding procedures outside MTP3 is placing
> > > > > additional requirement on M3UA (not to
> > > > > mention placing requirement on the ASP),
> > > > > so all of them have a problem.
> > > > [TOLGA] I will not try to answer your list of
> ISUP
> > > > related questions, they might be problems
> which
> > > might
> > > > be solved or not and I am not planning to
> > > implement it
> > > > now and I believe here we are discussing what
> > > > implications it might have on M3UA itself.
> Your
> > > > questions are related with the part outside of
> the
> > > > scope of M3UA. The key point is that you think
> SG
> > > only
> > > > as MTP3 and M3UA. This is not my view. It has
> a
> > > big
> > > > fat NIF inside. And I can also put whatever I
> want
> > > > there, as long as it can interoperate with
> M3UA
> > > > compliant ASPs. So, in fact there is no point
> to
> > > > discuss this, your ASP even won't feel it(if
> it
> > > feels
> > > > then of course you can complain). You say let
> the
> > > > people experiment outside of the protocol,
> this is
> > > > also what I am saying. As long as necessary
> logic
> > > is
> > > > kept only in SG and existing M3UA protocol is
> > > used,
> > > > there is no problem from M3UA point of view.
> So,
> > > > please keep it as it is, no restriction on RKs
> for
> > > > static case (especially SSN based for
> > > class0/class1
> > > > seems implementable to me for now, but this is
> > > besides
> > > > the point, easy or difficult, it is outside of
> > > M3UA
> > > > protocol itself and is a problem for persons,
> > > which
> > > > want to implement it)
> > > 
> > > I'm afraid you will have to answer the AS state
> > > related
> > > questions if you wish to maintain the position
> that
> > > M3UA "supports" CIC routing keys.
> > [TOLGA] Answer for all of your AS related
> questions
> > is, if one wants to support CIC based RK with
> M3UA,
> > then they should comply with what it stands in
> M3UA,
> > so whatever they do, they shouldn't violate
> RFC/IG,
> > i.e. AS related procedures there. And also I
> believe
> > it is left to the implementors, which types of RKs
> > they want to "support", as long as they are
> compliant
> > with M3UA.  
> 
> So I take it you can't figure out how any of these
> would work.  As there is no basis for
> interoperability,
> (not even one way that things can work), it is
> certainly
> not supported by M3UA.
[TOLGA] You can think whatever you want but I don't
want to dig in into ISUP specs to discuss some
implementation dependent ISUP management
functionality.The key point is that any necessary
management functionality to be implemented to support
different RKs is not part of M3UA protocol (and you
keep asking me about this implementation dependent
logic, which I am not interested in)
> 
> > > 
> > > The list of questions serve to illustrate the
> many
> > > ways
> > > in which CIC routing keys break
> interoperability.
> > [TOLGA] Your questions are related with ISUP. If
> one
> > tries to solve them by putting additional
> requirements
> > on M3UA itself, then this would break the
> > interoperability.
> 
> And that is why M3UA does not support CIC Routing
> Keys,
> because, solving the problems it creates would break
> interoperability.
[TOLGA] Even the question whether M3UA does support
CIC based RKs or not is absurd IMO. How M3UA works is
clear. That you (or I) can't solve some
implelementation dependent problems does not proove
nobody else can do it(if you say it is not suitanle in
your opinion this is a different story). But of
course, if you like for each and every possible
protocol you can do some anlysis and say your opinion
whether M3UA is suitable for RKs based on constructs
of those protocols or not.
> 
> > > 
> > > Also, here is another:
> > > 
> > > The ASP is under no requirement to send the ack
> > > messages
> > > to the same SG from which it received the
> blocking
> > > message.
> > > 
> > > How does your message splitting algorithm work
> when
> > > multiple SG's are involved?
> > [TOLGA[ Do you think multiple SG case is handled
> > properly even for DPC+SI based RKs?
> 
> Yes.
> 
> > So the answer would be, only connection to one SG
> is
> > supported (well I couldn't stop myself and
> answered,
> > because multiple SG with ASP/SGP scenario is not
> my
> > favorite model)
> 
> So where in the RFC does it say that only one SG can
> be supported for CIC Routing Keys?
> 
> Now how about multiple SGP in the same SG?  Because
> certainly the ack might go back to a different SGP
> that the one which split the group message.
> 
> So, are CIC Routing Keys only supported on a single
> SG
> made up of a single SGP?
> 
> And you never answered the question of the AS
> sending
> the circuit group message spanning Routing Contexts
> to
> the SG.  The SG cannot split these, how, is it to
> get
> the (correct) response back to the correct place?
[TOLGA] If it is configured as different AS, then I
wouldn't expect this to happen (sorry I again answered
one non-M3UA related question)
> 
> Also, you didn't say how your splitting algorithm is
> going to split pre-arranged circuit group
> messages...
> 
> --brian
> 
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan  4 15:15:57 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 PAA15386
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 15:15:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04KPLA05815
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 15:25:21 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04KP2J05799;
	Sat, 4 Jan 2003 15:25:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04KJjJ05617
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 15:19:45 -0500
Received: from web12806.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA15305
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 15:09:50 -0500 (EST)
Message-ID: <20030104201303.50466.qmail@web12806.mail.yahoo.com>
Received: from [62.29.65.171] by web12806.mail.yahoo.com via HTTP; Sat, 04 Jan 2003 12:13:03 PST
Date: Sat, 4 Jan 2003 12:13:03 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
To: sigtran@ietf.org
In-Reply-To: <20030104102524.K23879@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Sigtran] m3ua: multiple SG with DPC+SI RKs
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,
> > [TOLGA[ Do you think multiple SG case is handled
> > properly even for DPC+SI based RKs?
> 
> Yes.
Let's consider the following scenario:

 AS1:1-1-1 ISUP     AS2:1-1-1 SCCP
 +------+           +------+
 |ASP1  |           |ASP2  |
 |      |           |      |
 +-+-+--+           +----+++
   | |                   ||
   | +----------X------+ ||
   |                   | ||
   |  +----------------+-+|
 +-+--+-+           +--+--++
 | SG1  |           | SG2  |
 |      |           |      |
 +---+--+           +---+--+
     |                  |
     |                  |
     |                  |

Messages coming dor ISUP 1-1-1 to SG2 are replied with
UPU whereas the ones arriving to SG1 are routed to
ASP1.
Is it ever possible on TDM based SS7 that this
happens?The problem is, there can be only one layer3
for one entity (migth be distributed on different
hosts if they are synchronized) but in this scenario
each layer3 for 1-1-1 on SG1 and SG2 are acting
independently.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan  4 15:22: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 PAA15439
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 15:22:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04KVPm05993
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 15:31:25 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04KUuJ05960;
	Sat, 4 Jan 2003 15:30:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04KSnJ05925
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 15:28:49 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15426
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 15:18:54 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:RLb/nJQh5UI432jFqkPwt94ILz9UySvl@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h04KM6D17291;
	Sat, 4 Jan 2003 13:22:06 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h04KM6q30726;
	Sat, 4 Jan 2003 13:22:06 -0700
Date: Sat, 4 Jan 2003 13:22:06 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030104132206.L23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030104102524.K23879@openss7.org> <20030104200416.59789.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: <20030104200416.59789.qmail@web12807.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 04, 2003 at 12:04:16PM -0800
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, 04 Jan 2003 12:04:16)
> [TOLGA] You can think whatever you want
> but I don't want to dig in into ISUP
> specs to discuss some implementation
> dependent ISUP management
> functionality.The key point is that any
> necessary management functionality to be
> implemented to support different RKs is
> not part of M3UA protocol (and you keep
> asking me about this implementation
> dependent logic, which I am not
> interested in)

Then why did you say that the SG could
split up CGB messages?  This is an ISUP
procedure.  Did you not consult the ISUP
specs when you recommended this approach?
Do you agree now that the approach that
you proposed is flawed?

> [TOLGA] Even the question whether M3UA
> does support CIC based RKs or not is
> absurd IMO. How M3UA works is clear.
> That you (or I) can't solve some
> implelementation dependent problems does
> not proove nobody else can do it(if you
> say it is not suitanle in your opinion
> this is a different story). But of
> course, if you like for each and every
> possible protocol you can do some
> anlysis and say your opinion whether
> M3UA is suitable for RKs based on
> constructs of those protocols or not.

It is quite clear to me that routing keys
based on MTP Level 3 information is the
only routing key that M3UA can support.
When you use a routing key such as SSN or
CIC and accept the boundary violation of
an MTP3 layer examining upper layer PDUs,
you must address the interworking of the
upper layer peers to show that
interoperability exists.

Now if you say that CIC Routing Keys are
implementation dependent, then why are
they right there in the Routing Key?
Nowhere in the RFC does it say that the
use of CIC Routing Keys is implementation
dependent, yet the RFC has no support for
them.

I propose that CIC be removed from the
Routing Key.

> > So where in the RFC does it say that
> > only one SG can be supported for CIC
> > Routing Keys?
> > 
> > Now how about multiple SGP in the same
> > SG?  Because certainly the ack might
> > go back to a different SGP that the
> > one which split the group message.
> > 
> > So, are CIC Routing Keys only
> > supported on a single SG made up of a
> > single SGP?
> > 
> > And you never answered the question of
> > the AS sending the circuit group
> > message spanning Routing Contexts to
> > the SG.  The SG cannot split these,
> > how, is it to get the (correct)
> > response back to the correct place?
> [TOLGA] If it is configured as different
> AS, then I wouldn't expect this to
> happen (sorry I again answered one
> non-M3UA related question)

You call this a non-M3UA related question
an yet you say that M3UA has support for
CIC Routing Keys and propose that M3UA NIF
split up CGB messages?  You started the
boundary violation: admit that M3UA cannot
support CIC Routing Keys, particularly in
the fashion that you proposed.

--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  Sat Jan  4 15:28: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 PAA15486
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 15:28:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04KcF006765
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 15:38:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04KbvJ06755;
	Sat, 4 Jan 2003 15:37:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04KZtJ06100
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 15:35:55 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15479
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 15:25:59 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:jHBGpOMLtOt01RI2jeLGqVQvzKq5UJHp@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h04KTCD17366;
	Sat, 4 Jan 2003 13:29:12 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h04KTCo30816;
	Sat, 4 Jan 2003 13:29:12 -0700
Date: Sat, 4 Jan 2003 13:29:11 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
Message-ID: <20030104132911.M23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030104102524.K23879@openss7.org> <20030104201303.50466.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: <20030104201303.50466.qmail@web12806.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 04, 2003 at 12:13:03PM -0800
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, 04 Jan 2003 12:13:03)
> Brian,
> > > [TOLGA[ Do you think multiple SG
> > > case is handled properly even for
> > > DPC+SI based RKs?
> > 
> > Yes.
> Let's consider the following scenario:
> 
>  AS1:1-1-1 ISUP     AS2:1-1-1 SCCP
>  +------+           +------+
>  |ASP1  |           |ASP2  |
>  |      |           |      |
>  +-+-+--+           +----+++
>    | |                   ||
>    | +----------X------+ ||
>    |                   | ||
>    |  +----------------+-+|
>  +-+--+-+           +--+--++
>  | SG1  |           | SG2  |
>  |      |           |      |
>  +---+--+           +---+--+
>      |                  |
>      |                  |
>      |                  |
> 
> Messages coming dor ISUP 1-1-1 to SG2
> are replied with UPU whereas the ones
> arriving to SG1 are routed to ASP1.
>
> Is it ever possible on TDM based SS7
> that this happens?

No, in SS7 it cannot happen.

> The problem is, there can be only one
> layer3 for one entity (migth be
> distributed on different hosts if they
> are synchronized) but in this scenario
> each layer3 for 1-1-1 on SG1 and SG2 are
> acting independently.

Put C-Links between SG1 and SG2 and then
SG2 can route ISUP messages over C-Links
and perform transfer-restricted procedures
towards the network.

But if you break ISUP into CIC ranges you
cannot solve the problem with C-Links
because MTP3 cannot route on CIC.

--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  Sat Jan  4 15:34: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 PAA15559
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 15:34:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04KiNo06969
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 15:44:23 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04KhvJ06940;
	Sat, 4 Jan 2003 15:43:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04KfJJ06866
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 15:41:19 -0500
Received: from web12802.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA15518
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 15:31:23 -0500 (EST)
Message-ID: <20030104203436.37077.qmail@web12802.mail.yahoo.com>
Received: from [62.29.65.171] by web12802.mail.yahoo.com via HTTP; Sat, 04 Jan 2003 12:34:36 PST
Date: Sat, 4 Jan 2003 12:34:36 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <20030104132206.L23879@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,
> Tolga Asveren wrote:                           
> (Sat, 04 Jan 2003 12:04:16)
> > [TOLGA] You can think whatever you want
> > but I don't want to dig in into ISUP
> > specs to discuss some implementation
> > dependent ISUP management
> > functionality.The key point is that any
> > necessary management functionality to be
> > implemented to support different RKs is
> > not part of M3UA protocol (and you keep
> > asking me about this implementation
> > dependent logic, which I am not
> > interested in)
> 
> Then why did you say that the SG could
> split up CGB messages?  This is an ISUP
> procedure.  Did you not consult the ISUP
> specs when you recommended this approach?
> Do you agree now that the approach that
> you proposed is flawed?
[TOLGA] I don't have any problem by agreeing with this
(till the concerns you raised are addressed). But if
it is said that it would bring interoperability
problems,  I don't agree. The problems are related
with an entity outside of M3UA itself.
> 
> > [TOLGA] Even the question whether M3UA
> > does support CIC based RKs or not is
> > absurd IMO. How M3UA works is clear.
> > That you (or I) can't solve some
> > implelementation dependent problems does
> > not proove nobody else can do it(if you
> > say it is not suitanle in your opinion
> > this is a different story). But of
> > course, if you like for each and every
> > possible protocol you can do some
> > anlysis and say your opinion whether
> > M3UA is suitable for RKs based on
> > constructs of those protocols or not.
> 
> It is quite clear to me that routing keys
> based on MTP Level 3 information is the
> only routing key that M3UA can support.
> When you use a routing key such as SSN or
> CIC and accept the boundary violation of
> an MTP3 layer examining upper layer PDUs,
> you must address the interworking of the
> upper layer peers to show that
> interoperability exists.
[TOLGA] For that I agree. Any RK based on non-MTP3
contructs will result in implementing necessary
management functionality.
> 
> Now if you say that CIC Routing Keys are
> implementation dependent, then why are
> they right there in the Routing Key?
> Nowhere in the RFC does it say that the
> use of CIC Routing Keys is implementation
> dependent, yet the RFC has no support for
> them.
> 
> I propose that CIC be removed from the
> Routing Key.
[TOLGA] Again for that I tend to agree. Either also
include SSN again or don't include both of them.
Although again one can argue it is difficult(or even
maybe impossible) to support such RK types, SGP can
reply with an error message. But then somebody might
ask also for other RKs based on constructs of other
protocols.
> 
> > > So where in the RFC does it say that
> > > only one SG can be supported for CIC
> > > Routing Keys?
> > > 
> > > Now how about multiple SGP in the same
> > > SG?  Because certainly the ack might
> > > go back to a different SGP that the
> > > one which split the group message.
> > > 
> > > So, are CIC Routing Keys only
> > > supported on a single SG made up of a
> > > single SGP?
> > > 
> > > And you never answered the question of
> > > the AS sending the circuit group
> > > message spanning Routing Contexts to
> > > the SG.  The SG cannot split these,
> > > how, is it to get the (correct)
> > > response back to the correct place?
> > [TOLGA] If it is configured as different
> > AS, then I wouldn't expect this to
> > happen (sorry I again answered one
> > non-M3UA related question)
> 
> You call this a non-M3UA related question
> an yet you say that M3UA has support for
> CIC Routing Keys and propose that M3UA NIF
> split up CGB messages?  You started the
> boundary violation: admit that M3UA cannot
> support CIC Routing Keys, particularly in
> the fashion that you proposed.
[TOLGA] What I am saying is that even the concept of
M3UA supporting CIC based (or based on a construct of
another upper layer) RKs does not sound very logical
to me. Anyhting related with those RKs is to be
implemented -if possible- outside of M3UA protocol and
IMO is totally implementation dependent.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan  4 15:38: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 PAA15606
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 15:38:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04KmOL07123
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 15:48:24 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04KlsJ07095;
	Sat, 4 Jan 2003 15:47:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04Kj3J07021
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 15:45:03 -0500
Received: from web12808.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA15575
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 15:35:07 -0500 (EST)
Message-ID: <20030104203820.55143.qmail@web12808.mail.yahoo.com>
Received: from [62.29.65.171] by web12808.mail.yahoo.com via HTTP; Sat, 04 Jan 2003 12:38:20 PST
Date: Sat, 4 Jan 2003 12:38:20 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
To: sigtran@ietf.org
In-Reply-To: <20030104132911.M23879@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,
> Tolga,
> 
> Tolga Asveren wrote:                                
>                                 (Sat, 04 Jan 2003
> 12:13:03)
> > Brian,
> > > > [TOLGA[ Do you think multiple SG
> > > > case is handled properly even for
> > > > DPC+SI based RKs?
> > > 
> > > Yes.
> > Let's consider the following scenario:
> > 
> >  AS1:1-1-1 ISUP     AS2:1-1-1 SCCP
> >  +------+           +------+
> >  |ASP1  |           |ASP2  |
> >  |      |           |      |
> >  +-+-+--+           +----+++
> >    | |                   ||
> >    | +----------X------+ ||
> >    |                   | ||
> >    |  +----------------+-+|
> >  +-+--+-+           +--+--++
> >  | SG1  |           | SG2  |
> >  |      |           |      |
> >  +---+--+           +---+--+
> >      |                  |
> >      |                  |
> >      |                  |
> > 
> > Messages coming dor ISUP 1-1-1 to SG2
> > are replied with UPU whereas the ones
> > arriving to SG1 are routed to ASP1.
> >
> > Is it ever possible on TDM based SS7
> > that this happens?
> 
> No, in SS7 it cannot happen.
> 
> > The problem is, there can be only one
> > layer3 for one entity (migth be
> > distributed on different hosts if they
> > are synchronized) but in this scenario
> > each layer3 for 1-1-1 on SG1 and SG2 are
> > acting independently.
> 
> Put C-Links between SG1 and SG2 and then
> SG2 can route ISUP messages over C-Links
> and perform transfer-restricted procedures
> towards the network.
> 
> But if you break ISUP into CIC ranges you
> cannot solve the problem with C-Links
> because MTP3 cannot route on CIC.
[TOLGA] But MTP3 does not route based on user parts
either. A destination PC is either reachable or not.
And in this scenario it 1-1-1 is reachable from SG2. 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan  4 16:25: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 QAA16085
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 16:25:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04LZ4g08757
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 16:35:04 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04LYZJ08738;
	Sat, 4 Jan 2003 16:34:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04LVKJ08662
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 16:31:20 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16067
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 16:21:23 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:lwsSBHIuPzrHZL0FUVxp/pykSHTNwvUU@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h04LOaD18016;
	Sat, 4 Jan 2003 14:24:36 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h04LOaj31890;
	Sat, 4 Jan 2003 14:24:36 -0700
Date: Sat, 4 Jan 2003 14:24:36 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030104142436.N23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030104132206.L23879@openss7.org> <20030104203436.37077.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: <20030104203436.37077.qmail@web12802.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 04, 2003 at 12:34:36PM -0800
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, 04 Jan 2003 12:34:36)
> [TOLGA] I don't have any problem by agreeing with this
> (till the concerns you raised are addressed). But if
> it is said that it would bring interoperability
> problems,  I don't agree. The problems are related
> with an entity outside of M3UA itself.

What entity outside of M3UA?  It is your M3UA that is
mucking with the CGB messages instead of passing them
on.  If you M3UA doesn't much with the messages (or
try to route on information not contained in the MTP3
header) there is never a problem.

> [TOLGA] For that I agree. Any RK based on non-MTP3
> contructs will result in implementing necessary
> management functionality.

And unless specified will not be operable and so
there is no reaons to route on CIC in M3UA spec.

> > I propose that CIC be removed from the
> > Routing Key.
> [TOLGA] Again for that I tend to agree. Either also
> include SSN again or don't include both of them.
> Although again one can argue it is difficult(or even
> maybe impossible) to support such RK types, SGP can
> reply with an error message. But then somebody might
> ask also for other RKs based on constructs of other
> protocols.

Removing it would keep people from chasing wild geese
and confusing them into thinking that M3UA was designed
to support this kind of routing.

> > You call this a non-M3UA related question
> > an yet you say that M3UA has support for
> > CIC Routing Keys and propose that M3UA NIF
> > split up CGB messages?  You started the
> > boundary violation: admit that M3UA cannot
> > support CIC Routing Keys, particularly in
> > the fashion that you proposed.
> [TOLGA] What I am saying is that even the concept of
> M3UA supporting CIC based (or based on a construct of
> another upper layer) RKs does not sound very logical
> to me. Anyhting related with those RKs is to be
> implemented -if possible- outside of M3UA protocol and
> IMO is totally implementation dependent.

Totally implementation depedent => non-standard
=> not supported by M3UA => remove it from M3UA spec.

--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  Sat Jan  4 16:29: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 QAA16125
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 16:29:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04LdOw09484
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 16:39:24 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04LcrJ09465;
	Sat, 4 Jan 2003 16:38:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04LamJ08808
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 16:36:48 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16102
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 16:26:51 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:yf8fSmoRVbGqAYugvyoHLXacDwBtaaRi@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h04LU4D18099;
	Sat, 4 Jan 2003 14:30:04 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h04LU4531964;
	Sat, 4 Jan 2003 14:30:04 -0700
Date: Sat, 4 Jan 2003 14:30:03 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
Message-ID: <20030104143003.O23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030104132911.M23879@openss7.org> <20030104203820.55143.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: <20030104203820.55143.qmail@web12808.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 04, 2003 at 12:38:20PM -0800
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, 04 Jan 2003 12:38:20)
> [TOLGA] But MTP3 does not route based on user parts
> either. A destination PC is either reachable or not.
> And in this scenario it 1-1-1 is reachable from SG2. 

See SCCP alias point codes in MTP (ANSI
T1.111.4/2000).  MTP routes across C-Links
on the basis of the inaccessibility of a
local MTP-User (SCCP) precisely as I
described (including provision for
transfer-restricted procedures as well).

--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  Sat Jan  4 17:20:02 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 RAA16739
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 17:20:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04MTTq11761
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 17:29:29 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04MT4J11751;
	Sat, 4 Jan 2003 17:29:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04MQvJ11709
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 17:26:57 -0500
Received: from web12804.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA16730
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 17:16:59 -0500 (EST)
Message-ID: <20030104222012.12088.qmail@web12804.mail.yahoo.com>
Received: from [62.29.78.164] by web12804.mail.yahoo.com via HTTP; Sat, 04 Jan 2003 14:20:12 PST
Date: Sat, 4 Jan 2003 14:20:12 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
To: sigtran@ietf.org
In-Reply-To: <20030104143003.O23879@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:               (Sat, 04 Jan 2003
> 12:38:20)
> > [TOLGA] But MTP3 does not route based on user
> parts
> > either. A destination PC is either reachable or
> not.
> > And in this scenario it 1-1-1 is reachable from
> SG2. 
> 
> See SCCP alias point codes in MTP (ANSI
> T1.111.4/2000).  MTP routes across C-Links
> on the basis of the inaccessibility of a
> local MTP-User (SCCP) precisely as I
> described (including provision for
> transfer-restricted procedures as well).
[TOLGA] So, only alias point code configurations are
supported? What about ITU networks? What about the
case, where ISUP is also inaccessible from SG1, are we
going to keep hop counters to prevent ping-pong
scenarios?
To me, it is obvious that this is a problem scenario
and it is not a suprise: there are two MTP3 logic for
1-1-1 which are working independently.

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan  4 17: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 RAA16804
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 17:26:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h04Ma2211936
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 17:36:02 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04MZhJ11903;
	Sat, 4 Jan 2003 17:35:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h04MWOJ11825
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 17:32:24 -0500
Received: from web12806.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA16766
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 17:22:25 -0500 (EST)
Message-ID: <20030104222539.67706.qmail@web12806.mail.yahoo.com>
Received: from [62.29.78.164] by web12806.mail.yahoo.com via HTTP; Sat, 04 Jan 2003 14:25:39 PST
Date: Sat, 4 Jan 2003 14:25:39 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <20030104142436.N23879@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,
> > [TOLGA] I don't have any problem by agreeing with
> this
> > (till the concerns you raised are addressed). But
> if
> > it is said that it would bring interoperability
> > problems,  I don't agree. The problems are related
> > with an entity outside of M3UA itself.
> 
> What entity outside of M3UA?  It is your M3UA that
> is
> mucking with the CGB messages instead of passing
> them
> on.  If you M3UA doesn't much with the messages (or
> try to route on information not contained in the
> MTP3
> header) there is never a problem.
[TOLGA] Any management functionality necessary to
support non-MTP3 based RKs shoul dbe done in NIF, i.e.
it is not in M3UA.
> 
> > [TOLGA] For that I agree. Any RK based on non-MTP3
> > contructs will result in implementing necessary
> > management functionality.
> 
> And unless specified will not be operable and so
> there is no reaons to route on CIC in M3UA spec.
[TOLGA] I disagree. If it does not require any change
to M3UA and does not expect some special behavior from
peers, it is not a problem.
> 
> > > I propose that CIC be removed from the
> > > Routing Key.
> > [TOLGA] Again for that I tend to agree. Either
> also
> > include SSN again or don't include both of them.
> > Although again one can argue it is difficult(or
> even
> > maybe impossible) to support such RK types, SGP
> can
> > reply with an error message. But then somebody
> might
> > ask also for other RKs based on constructs of
> other
> > protocols.
> 
> Removing it would keep people from chasing wild
> geese
> and confusing them into thinking that M3UA was
> designed
> to support this kind of routing.
> 
> > > You call this a non-M3UA related question
> > > an yet you say that M3UA has support for
> > > CIC Routing Keys and propose that M3UA NIF
> > > split up CGB messages?  You started the
> > > boundary violation: admit that M3UA cannot
> > > support CIC Routing Keys, particularly in
> > > the fashion that you proposed.
> > [TOLGA] What I am saying is that even the concept
> of
> > M3UA supporting CIC based (or based on a construct
> of
> > another upper layer) RKs does not sound very
> logical
> > to me. Anyhting related with those RKs is to be
> > implemented -if possible- outside of M3UA protocol
> and
> > IMO is totally implementation dependent.
> 
> Totally implementation depedent => non-standard
> => not supported by M3UA => remove it from M3UA
> spec.
[TOLGA] Implementation dependent does not mean not
supported by M3UA. NIF is implementation dependent, so
does it mean to have NIF is violating M3UA?


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan  4 19:49:19 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 TAA17883
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 19:49:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h050wm517738
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 19:58:48 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h050w5J17720;
	Sat, 4 Jan 2003 19:58:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h050sDJ17656
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 19:54:13 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17848
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 19:44:13 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:IDQpQKfCzGuAqnnz1LogoIYvFZ0/Q3+U@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h050lPD20399;
	Sat, 4 Jan 2003 17:47:25 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h050lPc03184;
	Sat, 4 Jan 2003 17:47:25 -0700
Date: Sat, 4 Jan 2003 17:47:25 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
Message-ID: <20030104174725.P23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030104143003.O23879@openss7.org> <20030104222012.12088.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: <20030104222012.12088.qmail@web12804.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 04, 2003 at 02:20:12PM -0800
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, 04 Jan 2003 14:20:12)
> [TOLGA] So, only alias point code
> configurations are supported? What
> about ITU networks? What about the
> case, where ISUP is also inaccessible
> from SG1, are we going to keep hop
> counters to prevent ping-pong
> scenarios?

Hop counters?  Ridiculous: you should
know that the transfer-prohibited
procedure prevents the other STP from
routing back.  An STP never sends
traffic to its mate without first
sending transfer-prohibited to the mate
with regard to the same traffic.

> To me, it is obvious that this is a
> problem scenario and it is not a
> suprise: there are two MTP3 logic for
> 1-1-1 which are working independently.

Don't worry, those that know how to
build STPs also know how to do this
correctly.  Where do you thing alias
point code came from?

--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  Sat Jan  4 20:09: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 UAA18055
	for <sigtran-archive@odin.ietf.org>; Sat, 4 Jan 2003 20:09:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h051Iaf18799
	for sigtran-archive@odin.ietf.org; Sat, 4 Jan 2003 20:18:36 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h051HvJ18781;
	Sat, 4 Jan 2003 20:17:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h051BYJ18653
	for <sigtran@optimus.ietf.org>; Sat, 4 Jan 2003 20:11:34 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18015
	for <sigtran@ietf.org>; Sat, 4 Jan 2003 20:01:33 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:20grvkrObHgYArgxQdaCR8xGA6QRyVGj@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0514kD20610;
	Sat, 4 Jan 2003 18:04:46 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0514k803598;
	Sat, 4 Jan 2003 18:04:46 -0700
Date: Sat, 4 Jan 2003 18:04:46 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030104180446.Q23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030104142436.N23879@openss7.org> <20030104222539.67706.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: <20030104222539.67706.qmail@web12806.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 04, 2003 at 02:25:39PM -0800
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, 04 Jan 2003 14:25:39)
> [TOLGA] Any management functionality
> necessary to support non-MTP3 based RKs
> shoul dbe done in NIF, i.e.  it is not
> in M3UA.

Just because the NIF was left
implementation dependent does not mean
that you can jam anything you like in
there (like half an ISUP stack).  The NIF
was left implementation dependent to
permit implementors the leeway necessary
to meet SS7 MTP requirements.  Read the
RFC again, particularly the opening
passages.  The NIF adapts an
implementation specific MTP/MTP-User
interface to M3UA so that M3UA at the SG
can transport it to the ASP.  It isn't the
dumping ground for all manner of boundary
violation junk.  The obligation is on the
SG implementor to meet SS7 requirements
(and that includes not breaking ISUP while
they are at it).

But such broken implementations are
unlikely to ever be connected to a real
SS7 network anyway (even if they do, not
for long before they are fork lifted out
the window to the trash bins from the 4th
floor).

> [TOLGA] I disagree. If it does not
> require any change to M3UA and does not
> expect some special behavior from peers,
> it is not a problem.

You did not answer the question how the AS
gets the response to its CGB to the
correct place.  This will take the
cooperation of the ASP which requires
interoperability.  If you still think that
the ASP need do nothing special, answer
the questions. ;)

> > > to me. Anyhting related with those
> > > RKs is to be implemented -if
> > > possible- outside of M3UA protocol
> > > and IMO is totally implementation
> > > dependent.
> > 
> > Totally implementation depedent =>
> > non-standard => not supported by M3UA
> > => remove it from M3UA spec.
> [TOLGA] Implementation dependent does
> not mean not supported by M3UA. NIF is
> implementation dependent, so does it
> mean to have NIF is violating M3UA?

NIF is not "totally" implementation
dependent.  Requirements are placed on the
NIF by the M3UA RFC.  What you propose to
place in it is, as you say, "totally"
implementation dependent and, as such, has
no basis for interoperability.  Something
which is completely unstandardized,
doesn't have a single documented workable
solution, doesn't even have a glint of a
change of being interoperable.

--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  Sun Jan  5 07:00: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 HAA04308
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 07:00:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05CALK29286
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 07:10:21 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05C9tJ29268;
	Sun, 5 Jan 2003 07:09:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05C6JJ28568
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 07:06:19 -0500
Received: from web12802.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA04268
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 06:56:04 -0500 (EST)
Message-ID: <20030105115918.29217.qmail@web12802.mail.yahoo.com>
Received: from [62.29.84.200] by web12802.mail.yahoo.com via HTTP; Sun, 05 Jan 2003 03:59:18 PST
Date: Sun, 5 Jan 2003 03:59:18 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
To: sigtran@ietf.org
In-Reply-To: <20030104174725.P23879@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:                                
>                                 (Sat, 04 Jan 2003
> 14:20:12)
> > [TOLGA] So, only alias point code
> > configurations are supported? What
> > about ITU networks? What about the
> > case, where ISUP is also inaccessible
> > from SG1, are we going to keep hop
> > counters to prevent ping-pong
> > scenarios?
> 
> Hop counters?  Ridiculous: you should
> know that the transfer-prohibited
> procedure prevents the other STP from
> routing back.  An STP never sends
> traffic to its mate without first
> sending transfer-prohibited to the mate
> with regard to the same traffic.
[TOLGA] For the case where ISUP is inaccessible from
both of the SGs but SCCP is accessible (the case I am
referring to), will they send TFP to each other?  
Does MTP route also for ISUP based on accessibility
status for the user part? Also for ITU?
> 
> > To me, it is obvious that this is a
> > problem scenario and it is not a
> > suprise: there are two MTP3 logic for
> > 1-1-1 which are working independently.
> 
> Don't worry, those that know how to
> build STPs also know how to do this
> correctly.  Where do you thing alias
> point code came from?
[TOLGA]Is this stated somewhere in the RFC/IG? For
some other minor things, clarifications are added. 
IMO, from architecture point of view this is still a
problem scenario.

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sun Jan  5 07:10: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 HAA04393
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 07:10:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05CKLt29518
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 07:20:21 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05CJxJ29474;
	Sun, 5 Jan 2003 07:19:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05CHRJ29434
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 07:17:27 -0500
Received: from web12801.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA04370
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 07:07:13 -0500 (EST)
Message-ID: <20030105121025.10418.qmail@web12801.mail.yahoo.com>
Received: from [62.29.84.200] by web12801.mail.yahoo.com via HTTP; Sun, 05 Jan 2003 04:10:25 PST
Date: Sun, 5 Jan 2003 04:10:25 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <20030104180446.Q23879@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,

Last message of this thread from my point of view
because I think I already expressed my opinions (some
of them several times) and I don't want to thrash the
list.
Comments are inline below.

--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> Tolga Asveren wrote:                                
>                                 (Sat, 04 Jan 2003
> 14:25:39)
> > [TOLGA] Any management functionality
> > necessary to support non-MTP3 based RKs
> > shoul dbe done in NIF, i.e.  it is not
> > in M3UA.
> 
> Just because the NIF was left
> implementation dependent does not mean
> that you can jam anything you like in
> there (like half an ISUP stack).  The NIF
> was left implementation dependent to
> permit implementors the leeway necessary
> to meet SS7 MTP requirements.  Read the
> RFC again, particularly the opening
> passages.  The NIF adapts an
> implementation specific MTP/MTP-User
> interface to M3UA so that M3UA at the SG
> can transport it to the ASP.  It isn't the
> dumping ground for all manner of boundary
> violation junk.  The obligation is on the
> SG implementor to meet SS7 requirements
> (and that includes not breaking ISUP while
> they are at it).
> 
> But such broken implementations are
> unlikely to ever be connected to a real
> SS7 network anyway (even if they do, not
> for long before they are fork lifted out
> the window to the trash bins from the 4th
> floor).
> 
> > [TOLGA] I disagree. If it does not
> > require any change to M3UA and does not
> > expect some special behavior from peers,
> > it is not a problem.
> 
> You did not answer the question how the AS
> gets the response to its CGB to the
> correct place.  This will take the
> cooperation of the ASP which requires
> interoperability.  If you still think that
> the ASP need do nothing special, answer
> the questions. ;)
[TOLGA] I feel I really fail to explain what I mean.
The real point is, if somebody can do it without
interoperability problems, let them do it. And for
some RK type even if it is really impossible, why us
this related with M3UA itself? It is clear that for
non-MTP3 RKs some management logic needs to be
implemented and without violating the protocol. IMO,
this is the only relevant thing from M3UA point of
view.
> 
> > > > to me. Anyhting related with those
> > > > RKs is to be implemented -if
> > > > possible- outside of M3UA protocol
> > > > and IMO is totally implementation
> > > > dependent.
> > > 
> > > Totally implementation depedent =>
> > > non-standard => not supported by M3UA
> > > => remove it from M3UA spec.
> > [TOLGA] Implementation dependent does
> > not mean not supported by M3UA. NIF is
> > implementation dependent, so does it
> > mean to have NIF is violating M3UA?
> 
> NIF is not "totally" implementation
> dependent.  Requirements are placed on the
> NIF by the M3UA RFC.  What you propose to
> place in it is, as you say, "totally"
> implementation dependent and, as such, has
> no basis for interoperability.  Something
> which is completely unstandardized,
> doesn't have a single documented workable
> solution, doesn't even have a glint of a
> change of being interoperable.
[TOLGA] For me the guideline is RFC/IG. As long as one
does not violate it, she/he is free to do anyhting. I
agree, the same applies to NIF, never violate the
protocol. This is also my opinion for non-MTP3 RKs, if
one can support them by not breaking the protocol,
they are free to do it.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sun Jan  5 07:38: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 HAA04667
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 07:38:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05CmGK30754
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 07:48:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05ClsJ30734;
	Sun, 5 Jan 2003 07:47:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05CjwJ30702
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 07:45:58 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04647
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 07:35:43 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:VJVzOotXIvoaHkLFU9DdPTat/bmwO9U2@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h05CcuD01674;
	Sun, 5 Jan 2003 05:38:56 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h05CctY23858;
	Sun, 5 Jan 2003 05:38:55 -0700
Date: Sun, 5 Jan 2003 05:38:55 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
Message-ID: <20030105053855.R23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030104174725.P23879@openss7.org> <20030105115918.29217.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: <20030105115918.29217.qmail@web12802.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sun, Jan 05, 2003 at 03:59:18AM -0800
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:                                                                 (Sun, 05 Jan 2003 03:59:18)
> [TOLGA] For the case where ISUP is inaccessible from
> both of the SGs but SCCP is accessible (the case I am
> referring to), will they send TFP to each other?  

Yes.  When one SG receives TFP from the other
with respect to the 1-1-1 point code, it can combine
the inaccessibility of ISUP with the TFP to send UPU
for ISUP and send TFP to its mate.  If one of the SGs
should then lose SCCP, it can send TFP to the network
and the network will reroute to the alternate SG if
it still has access to SCCP.

> Does MTP route also for ISUP based on accessibility
> status for the user part? Also for ITU?

There is nothing in ITU specs that preclude this (or
the Alias Point Code) behavior.

Besides, this is what you argued for on the DUPU threads.

--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  Sun Jan  5 08:12: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 IAA05046
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 08:12:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05DLli32046
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 08:21:47 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05DLOJ32033;
	Sun, 5 Jan 2003 08:21:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05DIvJ31969
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 08:18:57 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05025
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 08:08:41 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:QNnoMIQ3nsU62MVr5ycSUBBOG08rWUyZ@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h05DBsD02100;
	Sun, 5 Jan 2003 06:11:54 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h05DBs024531;
	Sun, 5 Jan 2003 06:11:54 -0700
Date: Sun, 5 Jan 2003 06:11:54 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030105061154.S23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030104180446.Q23879@openss7.org> <20030105121025.10418.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: <20030105121025.10418.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sun, Jan 05, 2003 at 04:10:25AM -0800
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:                                                                 (Sun, 05 Jan 2003 04:10:25)
> [TOLGA] I feel I really fail to explain
> what I mean.  The real point is, if
> somebody can do it without
> interoperability problems, let them do
> it.

Let them do it outside of the standard
unless they can (at least logically)
demonstrate interoperability.

> And for some RK type even if it is
> really impossible, why us this related
> with M3UA itself? It is clear that for
> non-MTP3 RKs some management logic needs
> to be implemented and without violating
> the protocol. IMO, this is the only
> relevant thing from M3UA point of view.

Section 3.3.1:

  "The DATA message contains the SS7
  MTP3-User protocol data, which is an
  MTP-TRANSFER primitive, including the
  complete MTP3 Routing Label."

Split CGBs are not MTP-TRANSFER
primitives.

Section 3.3.1:

  "The Protocol Data parameter contains
  the original SS7 MTP3 message, including
  the Service Information Octet and
  Routing Label."

Split CGBs are not the "original SS7
MTP3 message".

Section 3.3.1:

  "The User Protocol Data field contains
  a byte string of MTP-User information
  from the original SS7 message starting
  with the first byte of the original SS7
  message following the Routing Label."

Split CGBs do not contain the original
SS7 byte for byte as indicated here.

Section 1.5.1

  "For internal SGP modeling purposes, at
  the NIF level, SS7 signalling messages
  that are destined to the MGC are
  received as MTP-TRANSFER indication
  primitives from the MTP Level 3 upper
  layer interface, translated to
  MTP-TRANSFER request primitives, and
  sent to the local M3UA-resident message
  distribution function for outgoing
  routing to the final IP destination.
  Messages received from the local M3UA
  network address translations and mapping
  function as MTP-TRANSFER indication
  primitives ar esent to the MTP Level 3
  upper layer interface as MTP-TRANSFER
  request primitives for outgoing MTP
  Level 3 routing to an SS7 SEP."

The message distribution function and
network address translations (routing) is
M3UA-resident (it is not in the NIF).

(Note that the above was also the only
ISUP example in the spec.)

Section 4.1.1:

  "The M3UA peer receiving the DATA
  message sends a MTP-TRANSFER indication
  primitive to the upper layer."

  "The M3UA message distribution function
  (see Section 1.4.2.1) determins the
  Application Server (AS) based on
  comparing the information in the
  MTP-TRANSFER request primitive with a
  provisioned Routing Key."

Comparison with Routing Keys occurs in the
M3UA, not the NIF.

Section 5.4.2.1:

  "When the M3UA layer at the SGP has
  received DATA messages from its peer
  destined to the SS7 network it will do
  the following:

  - Evaluate the optional fields of the
    DATA message, if present, to determine
    the Network Appearance;

  - Map the Protocol data field of the
    DATA message into an MTP-TRANSFER
    request primitive;

  - Pass the MTP-TRANSFER request
    primitive to the MTP3 of the concerned
    Network Appearance."

Aggregating CGBA responses would violate
this procedure.

> [TOLGA] For me the guideline is RFC/IG.
> As long as one does not violate it,
> she/he is free to do anyhting. I agree,
> the same applies to NIF, never violate
> the protocol. This is also my opinion
> for non-MTP3 RKs, if one can support
> them by not breaking the protocol, they
> are free to do it.

Who is "they?"

For CIC routing keys, the only current
propsal that does not violate the protocol
is to ensure than no circuit groups span
routing keys, ensuring that there is
always a default AS, and arranging
circuits and trunks such that a circuit
group message will never be generated that
spans the routing keys.

(Which is what I was telling Joseph when
you proposed your splitting algorithm
which violates all of the above.)

The fully interoperable way to acheive
what is being attempted with CIC routing
keys (but fails dismally) is by
_load-sharing_ on CIC ranges rather than
_routing_ on CIC ranges.

Why would anyone want to court a
proprietary solution (CIC routing) when an
interoperable solution (CIC load-sharing)
exists? 

I don't see any problem saying that M3UA
MUST use CIC load-sharing, which is
demonstrably interoperable, and MUST NOT
use CIC routing keys which cannot (any
time soon) be demonstrated  to
interoperate.

--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  Sun Jan  5 08:55: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 IAA05374
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 08:55:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05E5Ws01005
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 09:05:32 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05E59J00989;
	Sun, 5 Jan 2003 09:05:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05E2bJ00928
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 09:02:37 -0500
Received: from web12802.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA05352
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 08:52:21 -0500 (EST)
Message-ID: <20030105135534.40003.qmail@web12802.mail.yahoo.com>
Received: from [62.29.76.160] by web12802.mail.yahoo.com via HTTP; Sun, 05 Jan 2003 05:55:34 PST
Date: Sun, 5 Jan 2003 05:55:34 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
To: sigtran@ietf.org
In-Reply-To: <20030105053855.R23879@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:                                
>                                 (Sun, 05 Jan 2003
> 03:59:18)
> > [TOLGA] For the case where ISUP is inaccessible
> from
> > both of the SGs but SCCP is accessible (the case I
> am
> > referring to), will they send TFP to each other?  
> 
> Yes.  When one SG receives TFP from the other
> with respect to the 1-1-1 point code, it can combine
> the inaccessibility of ISUP with the TFP to send UPU
> for ISUP and send TFP to its mate.  If one of the
> SGs
> should then lose SCCP, it can send TFP to the
> network
> and the network will reroute to the alternate SG if
> it still has access to SCCP.
[TOLGA] I think I failed to explain what I mean:
  1-1-1 ISUP              1-1-1 SCCP
    +-------+             +-------+
    |ASP1   |             |ASP2   |
    |       |             |       |
    ++-+----+             +--+---++
     | |                     |   |
     | | +--------X----------+   X
     | | |                       |
     | +-+---------------------+ |
    ++---+--+             +----+-++
    |  SG1  |             |  SG2  |
    |       +-------------+       |
    +---+---+             +----+--+
        |                      |
Now when SCCP becomes unavailable, will SG1 send UPU
to SG2? In such a case they should keep reachability
info per user part for their peers, with which they
have alias point code relationship unless number of
such nodes are restricted to two (probably this is the
case with alias point codes (?) )
But is there a restriction in M3UA restricting number
of SGs for DPC+SI based RKs to 2? 
> 
> > Does MTP route also for ISUP based on
> accessibility
> > status for the user part? Also for ITU?
> 
> There is nothing in ITU specs that preclude this (or
> the Alias Point Code) behavior.
[TOLGA] So, it is not defined(?) and routing is based
only on PC.
> 
> Besides, this is what you argued for on the DUPU
> threads.
[TOLGA] No. My position for DUPU from ASP to SGP is,
it is not necessary because this is a MTP3/MTP3-User
interface and if one wants User Part granularity, the
way to achieve this is defining AS per user part. 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sun Jan  5 10:34: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 KAA06563
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 10:34:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05Fhq306056
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 10:43:52 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05FhFJ06044;
	Sun, 5 Jan 2003 10:43:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05FdkJ05869
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 10:39:46 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06452
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 10:29:27 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:HpocXOfrhwqvfxsYCY/QMWGjm2DN/fUL@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h05FWeD03705;
	Sun, 5 Jan 2003 08:32:40 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h05FWeD27184;
	Sun, 5 Jan 2003 08:32:40 -0700
Date: Sun, 5 Jan 2003 08:32:40 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
Message-ID: <20030105083240.T23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030105053855.R23879@openss7.org> <20030105135534.40003.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: <20030105135534.40003.qmail@web12802.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sun, Jan 05, 2003 at 05:55:34AM -0800
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:                                                                 (Sun, 05 Jan 2003 05:55:34)
> [TOLGA] I think I failed to explain what I mean:
>   1-1-1 ISUP              1-1-1 SCCP
>     +-------+             +-------+
>     |ASP1   |             |ASP2   |
>     |       |             |       |
>     ++-+----+             +--+---++
>      | |                     |   |
>      | | +--------X----------+   X
>      | | |                       |
>      | +-+---------------------+ |
>     ++---+--+             +----+-++
>     |  SG1  |             |  SG2  |
>     |       +-------------+       |
>     +---+---+             +----+--+
>         |                      |
> Now when SCCP becomes unavailable, will
> SG1 send UPU to SG2? In such a case they
> should keep reachability info per user
> part for their peers, with which they
> have alias point code relationship
> unless number of such nodes are
> restricted to two (probably this is the
> case with alias point codes (?) ) But is
> there a restriction in M3UA restricting
> number of SGs for DPC+SI based RKs to 2? 

When SCCP becomes unavailable at SG1, SG1
sends TFP to SG2 for 1-1-1 and sends SCCP
traffic to SG2.  It could still process
ISUP traffic locally.

Why does not ASP1 also support SCCP?  Or
at least why does it not pass traffic to
ASP2?  ISUP and SCCP have to work together
closely in a switch (single point code)
and it is inconceivable that they are so
separated that they are not in the same
room.

Do you have a real world example where one
would want to separate ISUP and SCCP like
this on the same point code?

--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  Sun Jan  5 10:41:56 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 KAA06620
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 10:41:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05FpiN06182
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 10:51:44 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05FpAJ06170;
	Sun, 5 Jan 2003 10:51:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05FmaJ06122
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 10:48:36 -0500
Received: from web12801.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA06599
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 10:38:17 -0500 (EST)
Message-ID: <20030105154131.30739.qmail@web12801.mail.yahoo.com>
Received: from [62.29.64.142] by web12801.mail.yahoo.com via HTTP; Sun, 05 Jan 2003 07:41:31 PST
Date: Sun, 5 Jan 2003 07:41:31 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
To: sigtran@ietf.org
In-Reply-To: <20030105083240.T23879@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:                                
>                                 (Sun, 05 Jan 2003
> 05:55:34)
> > [TOLGA] I think I failed to explain what I mean:
> >   1-1-1 ISUP              1-1-1 SCCP
> >     +-------+             +-------+
> >     |ASP1   |             |ASP2   |
> >     |       |             |       |
> >     ++-+----+             +--+---++
> >      | |                     |   |
> >      | | +--------X----------+   X
> >      | | |                       |
> >      | +-+---------------------+ |
> >     ++---+--+             +----+-++
> >     |  SG1  |             |  SG2  |
> >     |       +-------------+       |
> >     +---+---+             +----+--+
> >         |                      |
> > Now when SCCP becomes unavailable, will
> > SG1 send UPU to SG2? In such a case they
> > should keep reachability info per user
> > part for their peers, with which they
> > have alias point code relationship
> > unless number of such nodes are
> > restricted to two (probably this is the
> > case with alias point codes (?) ) But is
> > there a restriction in M3UA restricting
> > number of SGs for DPC+SI based RKs to 2? 
> 
> When SCCP becomes unavailable at SG1, SG1
> sends TFP to SG2 for 1-1-1 and sends SCCP
> traffic to SG2.  It could still process
> ISUP traffic locally.
[TOLGA] Why does SG1 send TFP for 1-1-1 in such a
case? ISUP is still available. IMO, 1-1-1 is still
available -all traffic is handled locally- or 1-1-1 is
not available -all traffic for 1-1-1 is routed to SG2-
from MTP3 of SG1 point of view.
> 
> Why does not ASP1 also support SCCP?  Or
> at least why does it not pass traffic to
> ASP2?  ISUP and SCCP have to work together
> closely in a switch (single point code)
> and it is inconceivable that they are so
> separated that they are not in the same
> room.
> 
> Do you have a real world example where one
> would want to separate ISUP and SCCP like
> this on the same point code?
[TOLGA]The point is, whether such a configuration is
properly supported or not with the current ASP/SGP
architecture. IMO, it is not supported (I also don't
see the need to support it with ASP/SGP model).

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sun Jan  5 10:47: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 KAA06690
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 10:47:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05FvGp06312
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 10:57:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05FuvJ06298;
	Sun, 5 Jan 2003 10:56:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05FsqJ06244
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 10:54:52 -0500
Received: from web12802.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA06669
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 10:44:33 -0500 (EST)
Message-ID: <20030105154747.52061.qmail@web12802.mail.yahoo.com>
Received: from [62.29.64.142] by web12802.mail.yahoo.com via HTTP; Sun, 05 Jan 2003 07:47:47 PST
Date: Sun, 5 Jan 2003 07:47:47 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
To: sigtran@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Sigtran] m3ua IGv02: typo in 3.7.2
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/Ken,

m3uaIGv02 3.7.2:
"If the SG determines that the received RK was already
registered, the
    SGP returns a Registration Response message to the
ASP, containing a
    Registration Result "Error - Cannot Support Unique
Routing"."

I think SG in the first sentence should be SGP.

   Regards,
   Tolga



__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sun Jan  5 10:58:02 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 KAA06802
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 10:58:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05G7o007230
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 11:07:50 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05G75J06663;
	Sun, 5 Jan 2003 11:07:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05G4wJ06536
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 11:04:58 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06786
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 10:54:38 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:zMr7Bdu3F/4khTfxVJU8SYVN+jhAy7nk@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h05FvqD03977;
	Sun, 5 Jan 2003 08:57:52 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h05Fvpu27593;
	Sun, 5 Jan 2003 08:57:51 -0700
Date: Sun, 5 Jan 2003 08:57:51 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
Message-ID: <20030105085751.U23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030105083240.T23879@openss7.org> <20030105154131.30739.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: <20030105154131.30739.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sun, Jan 05, 2003 at 07:41:31AM -0800
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:                                                                 (Sun, 05 Jan 2003 07:41:31)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Sun, 05 Jan 2003
> > 05:55:34)
> > > [TOLGA] I think I failed to explain what I mean:
> > >   1-1-1 ISUP              1-1-1 SCCP
> > >     +-------+             +-------+
> > >     |ASP1   |             |ASP2   |
> > >     |       |             |       |
> > >     ++-+----+             +--+---++
> > >      | |                     |   |
> > >      | | +--------X----------+   X
> > >      | | |                       |
> > >      | +-+---------------------+ |
> > >     ++---+--+             +----+-++
> > >     |  SG1  |             |  SG2  |
> > >     |       +-------------+       |
> > >     +---+---+             +----+--+
> > >         |                      |
> > > Now when SCCP becomes unavailable, will
> > > SG1 send UPU to SG2? In such a case they
> > > should keep reachability info per user
> > > part for their peers, with which they
> > > have alias point code relationship
> > > unless number of such nodes are
> > > restricted to two (probably this is the
> > > case with alias point codes (?) ) But is
> > > there a restriction in M3UA restricting
> > > number of SGs for DPC+SI based RKs to 2? 
> > 
> > When SCCP becomes unavailable at SG1, SG1
> > sends TFP to SG2 for 1-1-1 and sends SCCP
> > traffic to SG2.  It could still process
> > ISUP traffic locally.
> [TOLGA] Why does SG1 send TFP for 1-1-1 in such a
> case? ISUP is still available. IMO, 1-1-1 is still
> available -all traffic is handled locally- or 1-1-1 is
> not available -all traffic for 1-1-1 is routed to SG2-
> from MTP3 of SG1 point of view.
> > 
> > Why does not ASP1 also support SCCP?  Or
> > at least why does it not pass traffic to
> > ASP2?  ISUP and SCCP have to work together
> > closely in a switch (single point code)
> > and it is inconceivable that they are so
> > separated that they are not in the same
> > room.
> > 
> > Do you have a real world example where one
> > would want to separate ISUP and SCCP like
> > this on the same point code?
> [TOLGA]The point is, whether such a configuration is
> properly supported or not with the current ASP/SGP
> architecture. IMO, it is not supported (I also don't
> see the need to support it with ASP/SGP model).

It is not a realistic example.  We
discussed this at great lenth under "SGP
partitioning" as well.  Just relabel SG1
and SG2 as SGP1 and SGP2 and break the
connection between SGP1 and SGP2.  It is
the same situation.

   1-1-1 ISUP              1-1-1 SCCP
     +-------+             +-------+
     |ASP1   |             |ASP2   |
     |       |             |       |
     ++-+----+             +--+---++
      | |                     |   |
      | | +--------X----------+   X
      | | |                       |
      | +-+---------------------+ |
     ++---+--+             +----+-++
     | SGP1  |             | SGP2  |
     |       +-----X-------+       |
     +---+---+             +----+--+
         |                      |

At some point the ASP configuration is so
poorly engineered that the SGP has to take
down the entire point code to the network
due to partial failures.

A real-world arrangement would be as
follows:

   1-1-1 ISUP              1-1-1 ISUP
   1-1-1 SCCP              1-1-1 SCCP
     +-------+             +-------+
     |ASP1   |             |ASP2   |
     |       |             |       |
     ++-+----+             +--+---++
      | |                     |   |
      | | +--------X----------+   X
      | | |                       |
      | +-+--------X------------+ |
     ++---+--+             +----+-++
     | SGP1  |             | SGP2  |
     |or SG1 +-----X-------+or SG2 |
     +---+---+             +----+--+
         |                      |

In which case there is no problem.  It is
correctly engineered and the last
communication link has to fail before any
traffic will be lost.

--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  Sun Jan  5 11:08: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 LAA07152
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 11:08:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05GI0T07499
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 11:18:00 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05GHJJ07479;
	Sun, 5 Jan 2003 11:17:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05GETJ07394
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 11:14:29 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07063
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 11:04:09 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:/2fzkKuDYDeIddTh82Wubx3FRD1SD8/3@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h05G7ND04118;
	Sun, 5 Jan 2003 09:07:23 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h05G7NE27898;
	Sun, 5 Jan 2003 09:07:23 -0700
Date: Sun, 5 Jan 2003 09:07:23 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua IGv02: typo in 3.7.2
Message-ID: <20030105090723.V23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030105154747.52061.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: <20030105154747.52061.qmail@web12802.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sun, Jan 05, 2003 at 07:47:47AM -0800
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 get pendantic, get a load of this:

|      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
|      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|      |    Version    |   Reserved    | Message Class | Message Type  |
|      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|      |                        Message Length                         |
|      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|      \                                                               \
|      /                                                               /

Above, the bit number labels are staggered by one character.

Below, the tag is 17 bits and the length is only 15 bits.

|      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 =0x0004             |             Length          |
|     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     \                                                               \
|     /                          INFO String                          /
|     \                                                               \
|     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

But, of course, the length bits are more than regained here:

|      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 = 0x020a        |          Length = 8             |
|     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     |                  Local-RK-Identifier value                    |
|     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     |           Tag = 0x0212      |          Length = 8             |
|     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     |                      Registration Status                      |
|     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     |           Tag = 0x0006      |          Length = 8             |
|     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     |                        Routing Context                        |
|     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

where all the tags are 15 bits and the lengths are 17.

--brian


Tolga Asveren wrote:                 (Sun, 05 Jan 2003 07:47:47)
> Hi Javier/Ken,
> 
> m3uaIGv02 3.7.2:
> "If the SG determines that the received RK was already
> registered, the
>     SGP returns a Registration Response message to the
> ASP, containing a
>     Registration Result "Error - Cannot Support Unique
> Routing"."
> 
> I think SG in the first sentence should be SGP.
> 
>    Regards,
>    Tolga
> 
> 
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.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  Sun Jan  5 11:14: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 LAA07287
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 11:14:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05GOHp07714
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 11:24:17 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05GNvJ07701;
	Sun, 5 Jan 2003 11:23:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05GLsJ07642
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 11:21:54 -0500
Received: from web12807.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA07235
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 11:11:34 -0500 (EST)
Message-ID: <20030105161448.83342.qmail@web12807.mail.yahoo.com>
Received: from [62.29.64.142] by web12807.mail.yahoo.com via HTTP; Sun, 05 Jan 2003 08:14:48 PST
Date: Sun, 5 Jan 2003 08:14:48 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
To: sigtran@ietf.org
In-Reply-To: <20030105085751.U23879@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:                                
>                                 (Sun, 05 Jan 2003
> 07:41:31)
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Tolga Asveren wrote:                            
>    
> > >                                 (Sun, 05 Jan
> 2003
> > > 05:55:34)
> > > > [TOLGA] I think I failed to explain what I
> mean:
> > > >   1-1-1 ISUP              1-1-1 SCCP
> > > >     +-------+             +-------+
> > > >     |ASP1   |             |ASP2   |
> > > >     |       |             |       |
> > > >     ++-+----+             +--+---++
> > > >      | |                     |   |
> > > >      | | +--------X----------+   X
> > > >      | | |                       |
> > > >      | +-+---------------------+ |
> > > >     ++---+--+             +----+-++
> > > >     |  SG1  |             |  SG2  |
> > > >     |       +-------------+       |
> > > >     +---+---+             +----+--+
> > > >         |                      |
> > > > Now when SCCP becomes unavailable, will
> > > > SG1 send UPU to SG2? In such a case they
> > > > should keep reachability info per user
> > > > part for their peers, with which they
> > > > have alias point code relationship
> > > > unless number of such nodes are
> > > > restricted to two (probably this is the
> > > > case with alias point codes (?) ) But is
> > > > there a restriction in M3UA restricting
> > > > number of SGs for DPC+SI based RKs to 2? 
> > > 
> > > When SCCP becomes unavailable at SG1, SG1
> > > sends TFP to SG2 for 1-1-1 and sends SCCP
> > > traffic to SG2.  It could still process
> > > ISUP traffic locally.
> > [TOLGA] Why does SG1 send TFP for 1-1-1 in such a
> > case? ISUP is still available. IMO, 1-1-1 is still
> > available -all traffic is handled locally- or
> 1-1-1 is
> > not available -all traffic for 1-1-1 is routed to
> SG2-
> > from MTP3 of SG1 point of view.
> > > 
> > > Why does not ASP1 also support SCCP?  Or
> > > at least why does it not pass traffic to
> > > ASP2?  ISUP and SCCP have to work together
> > > closely in a switch (single point code)
> > > and it is inconceivable that they are so
> > > separated that they are not in the same
> > > room.
> > > 
> > > Do you have a real world example where one
> > > would want to separate ISUP and SCCP like
> > > this on the same point code?
> > [TOLGA]The point is, whether such a configuration
> is
> > properly supported or not with the current ASP/SGP
> > architecture. IMO, it is not supported (I also
> don't
> > see the need to support it with ASP/SGP model).
> 
> It is not a realistic example.  We
> discussed this at great lenth under "SGP
> partitioning" as well.  Just relabel SG1
> and SG2 as SGP1 and SGP2 and break the
> connection between SGP1 and SGP2.  It is
> the same situation.
> 
>    1-1-1 ISUP              1-1-1 SCCP
>      +-------+             +-------+
>      |ASP1   |             |ASP2   |
>      |       |             |       |
>      ++-+----+             +--+---++
>       | |                     |   |
>       | | +--------X----------+   X
>       | | |                       |
>       | +-+---------------------+ |
>      ++---+--+             +----+-++
>      | SGP1  |             | SGP2  |
>      |       +-----X-------+       |
>      +---+---+             +----+--+
>          |                      |
> 
> At some point the ASP configuration is so
> poorly engineered that the SGP has to take
> down the entire point code to the network
> due to partial failures.
> 
> A real-world arrangement would be as
> follows:
> 
>    1-1-1 ISUP              1-1-1 ISUP
>    1-1-1 SCCP              1-1-1 SCCP
>      +-------+             +-------+
>      |ASP1   |             |ASP2   |
>      |       |             |       |
>      ++-+----+             +--+---++
>       | |                     |   |
>       | | +--------X----------+   X
>       | | |                       |
>       | +-+--------X------------+ |
>      ++---+--+             +----+-++
>      | SGP1  |             | SGP2  |
>      |or SG1 +-----X-------+or SG2 |
>      +---+---+             +----+--+
>          |                      |
> 
> In which case there is no problem.  It is
> correctly engineered and the last
> communication link has to fail before any
> traffic will be lost.
[TOLGA] So, you propose the above configuration as
solution. Fine, no problem. So, the configuration I
presented is not supported properly with ASP/SGP
model. BTW, even for your configuration, what will
happen if one AS is not ACTIVE? So, should SGP wait
for all AS of the same SPMC to be ACTIVE? The source
of the problem is clear: to have two separate MTP3
logic for the same PC, working independently, which
IMO is not very correct from architecture point of
view. Mines was just an example to show this, and as I
said, I think M3UA should not try to support such a
configuration with ASP/SGP model.
Maybe not exactly the topic of this discussion, but I
have one comment about the scenario, where you
replaced SGs with SGPs. Once the syncronization
between MTP3 of SGPs is broken, I wouldn't consider SG
as operational.Afterall it is the single MTP3 entity,
which makes them to be called SGPs of the same SG.

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sun Jan  5 11:51: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 LAA07895
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 11:51:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05H1QD09044
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 12:01:26 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05H0iJ09007;
	Sun, 5 Jan 2003 12:00:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05GvkJ08904
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 11:57:46 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07703
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 11:47:25 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:bH1Fv90SeIc9z4QPkwtGqkC/psEV9dGT@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h05GodD04645;
	Sun, 5 Jan 2003 09:50:39 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h05Gocs29245;
	Sun, 5 Jan 2003 09:50:38 -0700
Date: Sun, 5 Jan 2003 09:50:38 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
Message-ID: <20030105095038.W23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030105085751.U23879@openss7.org> <20030105161448.83342.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: <20030105161448.83342.qmail@web12807.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sun, Jan 05, 2003 at 08:14:48AM -0800
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:                                                                 (Sun, 05 Jan 2003 08:14:48)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Sun, 05 Jan 2003
> > 07:41:31)
> > > Brian,
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > wrote:
> > > > Tolga,
> > > > 
> > > > Tolga Asveren wrote:                            
> >    
> > > >                                 (Sun, 05 Jan
> > 2003
> > > > 05:55:34)
> > > > > [TOLGA] I think I failed to explain what I
> > mean:
> > > > >   1-1-1 ISUP              1-1-1 SCCP
> > > > >     +-------+             +-------+
> > > > >     |ASP1   |             |ASP2   |
> > > > >     |       |             |       |
> > > > >     ++-+----+             +--+---++
> > > > >      | |                     |   |
> > > > >      | | +--------X----------+   X
> > > > >      | | |                       |
> > > > >      | +-+---------------------+ |
> > > > >     ++---+--+             +----+-++
> > > > >     |  SG1  |             |  SG2  |
> > > > >     |       +-------------+       |
> > > > >     +---+---+             +----+--+
> > > > >         |                      |
> > > > > Now when SCCP becomes unavailable, will
> > > > > SG1 send UPU to SG2? In such a case they
> > > > > should keep reachability info per user
> > > > > part for their peers, with which they
> > > > > have alias point code relationship
> > > > > unless number of such nodes are
> > > > > restricted to two (probably this is the
> > > > > case with alias point codes (?) ) But is
> > > > > there a restriction in M3UA restricting
> > > > > number of SGs for DPC+SI based RKs to 2? 
> > > > 
> > > > When SCCP becomes unavailable at SG1, SG1
> > > > sends TFP to SG2 for 1-1-1 and sends SCCP
> > > > traffic to SG2.  It could still process
> > > > ISUP traffic locally.
> > > [TOLGA] Why does SG1 send TFP for 1-1-1 in such a
> > > case? ISUP is still available. IMO, 1-1-1 is still
> > > available -all traffic is handled locally- or
> > 1-1-1 is
> > > not available -all traffic for 1-1-1 is routed to
> > SG2-
> > > from MTP3 of SG1 point of view.
> > > > 
> > > > Why does not ASP1 also support SCCP?  Or
> > > > at least why does it not pass traffic to
> > > > ASP2?  ISUP and SCCP have to work together
> > > > closely in a switch (single point code)
> > > > and it is inconceivable that they are so
> > > > separated that they are not in the same
> > > > room.
> > > > 
> > > > Do you have a real world example where one
> > > > would want to separate ISUP and SCCP like
> > > > this on the same point code?
> > > [TOLGA]The point is, whether such a configuration
> > is
> > > properly supported or not with the current ASP/SGP
> > > architecture. IMO, it is not supported (I also
> > don't
> > > see the need to support it with ASP/SGP model).
> > 
> > It is not a realistic example.  We
> > discussed this at great lenth under "SGP
> > partitioning" as well.  Just relabel SG1
> > and SG2 as SGP1 and SGP2 and break the
> > connection between SGP1 and SGP2.  It is
> > the same situation.
> > 
> >    1-1-1 ISUP              1-1-1 SCCP
> >      +-------+             +-------+
> >      |ASP1   |             |ASP2   |
> >      |       |             |       |
> >      ++-+----+             +--+---++
> >       | |                     |   |
> >       | | +--------X----------+   X
> >       | | |                       |
> >       | +-+---------------------+ |
> >      ++---+--+             +----+-++
> >      | SGP1  |             | SGP2  |
> >      |       +-----X-------+       |
> >      +---+---+             +----+--+
> >          |                      |
> > 
> > At some point the ASP configuration is so
> > poorly engineered that the SGP has to take
> > down the entire point code to the network
> > due to partial failures.
> > 
> > A real-world arrangement would be as
> > follows:
> > 
> >    1-1-1 ISUP              1-1-1 ISUP
> >    1-1-1 SCCP              1-1-1 SCCP
> >      +-------+             +-------+
> >      |ASP1   |             |ASP2   |
> >      |       |             |       |
> >      ++-+----+             +--+---++
> >       | |                     |   |
> >       | | +--------X----------+   X
> >       | | |                       |
> >       | +-+--------X------------+ |
> >      ++---+--+             +----+-++
> >      | SGP1  |             | SGP2  |
> >      |or SG1 +-----X-------+or SG2 |
> >      +---+---+             +----+--+
> >          |                      |
> > 
> > In which case there is no problem.  It is
> > correctly engineered and the last
> > communication link has to fail before any
> > traffic will be lost.
> [TOLGA] So, you propose the above
> configuration as solution. Fine, no
> problem. So, the configuration I
> presented is not supported properly with
> ASP/SGP model.

No, the configuration you presented is
just more brittle.  When part of it
breaks, it all breaks.  There is nothing
stopping the SG from saying that because
one AS is down, that the whole SPMC is
down.  It is even permitted to send ASPIA
Ack and ASPDN Ack under partial or
complete failure scenarios.  If you
want more reliability than that, design
your configuration better.


> BTW, even for your
> configuration, what will happen if one
> AS is not ACTIVE? So, should SGP wait
> for all AS of the same SPMC to be
> ACTIVE?

Sure, why not?  It is up the SG to
determine when the SPMC is active or not.
In the SG case, SG1 does not send TFA
until both ISUP and SCCP are up.  It can
also withold MTP-RESUME from the ASP until
both users are active.

> The source of the problem is clear: to
> have two separate MTP3 logic for the
> same PC, working independently, which
> IMO is not very correct from
> architecture point of view.

It makes perfect architectural sense.
That's how SS7 works.  Almost all SS7
nodes today distribute MTP over multiple
processors. It is just foolish to split
between users.

> Mines was just an example to show this,
> and as I said, I think M3UA should not
> try to support such a configuration with
> ASP/SGP model.

It supports it.  You just get different
failure response in different situations,
none of which has to violate any M3UA
or SS7 network requirements.

> Maybe not exactly the topic of this
> discussion, but I have one comment about
> the scenario, where you replaced SGs
> with SGPs. Once the syncronization
> between MTP3 of SGPs is broken, I
> wouldn't consider SG as operational.
> Afterall it is the single MTP3 entity,
> which makes them to be called SGPs of
> the same SG.

Modern SS7 nodes can suffer partitioning
and function quite well.

--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  Sun Jan  5 12:12: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 MAA08211
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 12:12:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05HMD810320
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 12:22:13 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05HLcJ10256;
	Sun, 5 Jan 2003 12:21:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05HATJ09942
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 12:10:29 -0500
Received: from web12806.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA08065
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 12:00:08 -0500 (EST)
Message-ID: <20030105170322.90215.qmail@web12806.mail.yahoo.com>
Received: from [62.29.65.139] by web12806.mail.yahoo.com via HTTP; Sun, 05 Jan 2003 09:03:22 PST
Date: Sun, 5 Jan 2003 09:03:22 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
To: sigtran@ietf.org
In-Reply-To: <20030105095038.W23879@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.....]
>> The source of the problem is clear: to
>> have two separate MTP3 logic for the
>> same PC, working independently, which
>> IMO is not very correct from
>> architecture point of view.
>
>It makes perfect architectural sense.
>That's how SS7 works.  Almost all SS7
>nodes today distribute MTP over multiple
>processors. It is just foolish to split
>between users.
[TOLGA] The problem is not to use multiple
processors/hosts, but not to synchronize them and make
them work as a separate entities, which is the case
whith multiple SG configurations.

[...snip...]
>> Maybe not exactly the topic of this
>> discussion, but I have one comment about
>> the scenario, where you replaced SGs
>> with SGPs. Once the syncronization
>> between MTP3 of SGPs is broken, I
>> wouldn't consider SG as operational.
>> Afterall it is the single MTP3 entity,
>> which makes them to be called SGPs of
>> the same SG.
>
>Modern SS7 nodes can suffer partitioning
>and function quite well.
[TOLGA] It is not logical to think multiple SGPs with
separate MTP3 logic as parts of the same SG. 





__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sun Jan  5 12:19: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 MAA08334
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 12:19:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05HTSo10474
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 12:29:28 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05HSuJ10453;
	Sun, 5 Jan 2003 12:28:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05HQ4J10409
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 12:26:04 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08250
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 12:15:42 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:4Tdge7K04yK6dj5gkBkFBiej0zbIMt/a@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h05HIuD04963;
	Sun, 5 Jan 2003 10:18:56 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h05HIuO29746;
	Sun, 5 Jan 2003 10:18:56 -0700
Date: Sun, 5 Jan 2003 10:18:56 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
Message-ID: <20030105101856.X23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030105095038.W23879@openss7.org> <20030105170322.90215.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: <20030105170322.90215.qmail@web12806.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sun, Jan 05, 2003 at 09:03:22AM -0800
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:                                                                 (Sun, 05 Jan 2003 09:03:22)
> Brian,
> [...snip.....]
> >> The source of the problem is clear:
> >> to have two separate MTP3 logic for
> >> the same PC, working independently,
> >> which IMO is not very correct from
> >> architecture point of view.
> >
> >It makes perfect architectural sense.
> >That's how SS7 works.  Almost all SS7
> >nodes today distribute MTP over
> >multiple processors. It is just
> >foolish to split between users.
> [TOLGA] The problem is not to use
> multiple processors/hosts, but not to
> synchronize them and make them work as
> a separate entities, which is the case
> whith multiple SG configurations.

Multiple SG as STP is a natural
architectural component of SS7: it is
the associated pair of STPs.

> 
> [...snip...]
> >> Maybe not exactly the topic of this
> >> discussion, but I have one comment
> >> about the scenario, where you
> >> replaced SGs with SGPs. Once the
> >> syncronization between MTP3 of SGPs
> >> is broken, I wouldn't consider SG
> >> as operational.  Afterall it is the
> >> single MTP3 entity, which makes
> >> them to be called SGPs of the same
> >> SG.
> >
> >Modern SS7 nodes can suffer
> >partitioning and function quite well.
> [TOLGA] It is not logical to think
> multiple SGPs with separate MTP3 logic
> as parts of the same SG. 

Yes, they are part of the same SG, the
SG just happes to be temporariliy
"partitioned".

--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  Sun Jan  5 12:49: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 MAA08628
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 12:49:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05HxYw11810
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 12:59:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05HwxJ11789;
	Sun, 5 Jan 2003 12:58:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05HtGJ11687
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 12:55:16 -0500
Received: from web12802.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA08584
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 12:44:53 -0500 (EST)
Message-ID: <20030105174808.65853.qmail@web12802.mail.yahoo.com>
Received: from [62.29.81.14] by web12802.mail.yahoo.com via HTTP; Sun, 05 Jan 2003 09:48:08 PST
Date: Sun, 5 Jan 2003 09:48:08 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
To: sigtran@ietf.org
In-Reply-To: <20030105101856.X23879@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:                                
>                                 (Sun, 05 Jan 2003
> 09:03:22)
> > Brian,
> > [...snip.....]
> > >> The source of the problem is clear:
> > >> to have two separate MTP3 logic for
> > >> the same PC, working independently,
> > >> which IMO is not very correct from
> > >> architecture point of view.
> > >
> > >It makes perfect architectural sense.
> > >That's how SS7 works.  Almost all SS7
> > >nodes today distribute MTP over
> > >multiple processors. It is just
> > >foolish to split between users.
> > [TOLGA] The problem is not to use
> > multiple processors/hosts, but not to
> > synchronize them and make them work as
> > a separate entities, which is the case
> > whith multiple SG configurations.
> 
> Multiple SG as STP is a natural
> architectural component of SS7: it is
> the associated pair of STPs.
[TOLGA] Problem is not the local MTP3 of SG itself (it
has different PC and so a different entity for each SG
anyway) The problem is because of the MTP3 logic
running on behalf of the AS on SGs. With multiple SGs,
one has separate MTP3 entities for the same PC, if
those SGs control the same SPMC.
> 
> > 
> > [...snip...]
> > >> Maybe not exactly the topic of this
> > >> discussion, but I have one comment
> > >> about the scenario, where you
> > >> replaced SGs with SGPs. Once the
> > >> syncronization between MTP3 of SGPs
> > >> is broken, I wouldn't consider SG
> > >> as operational.  Afterall it is the
> > >> single MTP3 entity, which makes
> > >> them to be called SGPs of the same
> > >> SG.
> > >
> > >Modern SS7 nodes can suffer
> > >partitioning and function quite well.
> > [TOLGA] It is not logical to think
> > multiple SGPs with separate MTP3 logic
> > as parts of the same SG. 
> 
> Yes, they are part of the same SG, the
> SG just happes to be temporariliy
> "partitioned".

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sun Jan  5 13:54: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 NAA09318
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 13:54:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05J4AT14750
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 14:04:10 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05J3SJ14673;
	Sun, 5 Jan 2003 14:03:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05J0tJ14573
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 14:00:55 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09231
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 13:50:33 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:xvtIfnFy9iYewiQuDmJ86lBcHjLfYlCZ@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h05IrjD06073;
	Sun, 5 Jan 2003 11:53:45 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h05IrjS31253;
	Sun, 5 Jan 2003 11:53:45 -0700
Date: Sun, 5 Jan 2003 11:53:45 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
Message-ID: <20030105115345.A30268@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030105101856.X23879@openss7.org> <20030105174808.65853.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: <20030105174808.65853.qmail@web12802.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sun, Jan 05, 2003 at 09:48:08AM -0800
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:                                                                 (Sun, 05 Jan 2003 09:48:08)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Sun, 05 Jan 2003
> > 09:03:22)
> > > Brian,
> > > [...snip.....]
> > > >> The source of the problem is clear:
> > > >> to have two separate MTP3 logic for
> > > >> the same PC, working independently,
> > > >> which IMO is not very correct from
> > > >> architecture point of view.
> > > >
> > > >It makes perfect architectural sense.
> > > >That's how SS7 works.  Almost all SS7
> > > >nodes today distribute MTP over
> > > >multiple processors. It is just
> > > >foolish to split between users.
> > > [TOLGA] The problem is not to use
> > > multiple processors/hosts, but not to
> > > synchronize them and make them work as
> > > a separate entities, which is the case
> > > whith multiple SG configurations.
> > 
> > Multiple SG as STP is a natural
> > architectural component of SS7: it is
> > the associated pair of STPs.
> [TOLGA] Problem is not the local MTP3 of SG itself (it
> has different PC and so a different entity for each SG
> anyway) The problem is because of the MTP3 logic
> running on behalf of the AS on SGs. With multiple SGs,
> one has separate MTP3 entities for the same PC, if
> those SGs control the same SPMC.

There is no problem because the SS7 network has a
independent view of the accessibility of the SPMC
via each SG acting as an STP.  So the view each SG
presents is independent anyway.

--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  Sun Jan  5 14:48: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 OAA09919
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 14:48:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h05Jvxr17289
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 14:57:59 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05JvIJ17266;
	Sun, 5 Jan 2003 14:57:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05JsFJ17189
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 14:54:15 -0500
Received: from web12802.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA09883
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 14:43:51 -0500 (EST)
Message-ID: <20030105194704.80452.qmail@web12802.mail.yahoo.com>
Received: from [62.29.77.38] by web12802.mail.yahoo.com via HTTP; Sun, 05 Jan 2003 11:47:04 PST
Date: Sun, 5 Jan 2003 11:47:04 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
To: sigtran@ietf.org
In-Reply-To: <20030105115345.A30268@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:                                
>                                 (Sun, 05 Jan 2003
> 09:48:08)
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Tolga Asveren wrote:                            
>    
> > >                                 (Sun, 05 Jan
> 2003
> > > 09:03:22)
> > > > Brian,
> > > > [...snip.....]
> > > > >> The source of the problem is clear:
> > > > >> to have two separate MTP3 logic for
> > > > >> the same PC, working independently,
> > > > >> which IMO is not very correct from
> > > > >> architecture point of view.
> > > > >
> > > > >It makes perfect architectural sense.
> > > > >That's how SS7 works.  Almost all SS7
> > > > >nodes today distribute MTP over
> > > > >multiple processors. It is just
> > > > >foolish to split between users.
> > > > [TOLGA] The problem is not to use
> > > > multiple processors/hosts, but not to
> > > > synchronize them and make them work as
> > > > a separate entities, which is the case
> > > > whith multiple SG configurations.
> > > 
> > > Multiple SG as STP is a natural
> > > architectural component of SS7: it is
> > > the associated pair of STPs.
> > [TOLGA] Problem is not the local MTP3 of SG itself
> (it
> > has different PC and so a different entity for
> each SG
> > anyway) The problem is because of the MTP3 logic
> > running on behalf of the AS on SGs. With multiple
> SGs,
> > one has separate MTP3 entities for the same PC, if
> > those SGs control the same SPMC.
> 
> There is no problem because the SS7 network has a
> independent view of the accessibility of the SPMC
> via each SG acting as an STP.  So the view each SG
> presents is independent anyway.
[TOLGA] Accessibility/inaccessibility/restriction of
the SPMC is announced to the network by the local MTP3
of SG. For them, there is no problem. Problem is for
user part unavailability, because it is decided by the
MTP3 logic running for SPMC on SG. When those two
MTP3s -which in fact have the same PC- have different
views for user part availability problem happens.

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sun Jan  5 21:37: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 VAA13880
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 21:37:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h062lFx03631
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 21:47:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h062ksJ03608;
	Sun, 5 Jan 2003 21:46:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h062jtJ03574
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 21:45:55 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13851
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 21:35:23 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Oi8BUqj7eZ1ATc3MbRE5SnDUc2Ez3KmD@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h062caD11984;
	Sun, 5 Jan 2003 19:38:36 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h062caA07542;
	Sun, 5 Jan 2003 19:38:36 -0700
Date: Sun, 5 Jan 2003 19:38:35 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua: multiple SG with DPC+SI RKs
Message-ID: <20030105193835.B30268@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030105115345.A30268@openss7.org> <20030105194704.80452.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: <20030105194704.80452.qmail@web12802.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sun, Jan 05, 2003 at 11:47:04AM -0800
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:                                                                 (Sun, 05 Jan 2003 11:47:04)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Sun, 05 Jan 2003
> > 09:48:08)
> > > Brian,
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > wrote:
> > > > Tolga,
> > > > 
> > > > Tolga Asveren wrote:                            
> >    
> > > >                                 (Sun, 05 Jan
> > 2003
> > > > 09:03:22)
> > > > > Brian,
> > > > > [...snip.....]
> > > > > >> The source of the problem is clear:
> > > > > >> to have two separate MTP3 logic for
> > > > > >> the same PC, working independently,
> > > > > >> which IMO is not very correct from
> > > > > >> architecture point of view.
> > > > > >
> > > > > >It makes perfect architectural sense.
> > > > > >That's how SS7 works.  Almost all SS7
> > > > > >nodes today distribute MTP over
> > > > > >multiple processors. It is just
> > > > > >foolish to split between users.
> > > > > [TOLGA] The problem is not to use
> > > > > multiple processors/hosts, but not to
> > > > > synchronize them and make them work as
> > > > > a separate entities, which is the case
> > > > > whith multiple SG configurations.
> > > > 
> > > > Multiple SG as STP is a natural
> > > > architectural component of SS7: it is
> > > > the associated pair of STPs.
> > > [TOLGA] Problem is not the local MTP3 of SG itself
> > (it
> > > has different PC and so a different entity for
> > each SG
> > > anyway) The problem is because of the MTP3 logic
> > > running on behalf of the AS on SGs. With multiple
> > SGs,
> > > one has separate MTP3 entities for the same PC, if
> > > those SGs control the same SPMC.
> > 
> > There is no problem because the SS7 network has a
> > independent view of the accessibility of the SPMC
> > via each SG acting as an STP.  So the view each SG
> > presents is independent anyway.
> [TOLGA] Accessibility/inaccessibility/restriction of
> the SPMC is announced to the network by the local MTP3
> of SG. For them, there is no problem. Problem is for
> user part unavailability, because it is decided by the
> MTP3 logic running for SPMC on SG. When those two
> MTP3s -which in fact have the same PC- have different
> views for user part availability problem happens.

So when you configure things with insufficient redundancy
the SG is sometimes forced to place the entire SPMC in
the inaccessible state.  So what?  Don't build things
that way and you won't have a problem.

--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  Sun Jan  5 23:49:02 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 XAA15948
	for <sigtran-archive@odin.ietf.org>; Sun, 5 Jan 2003 23:49:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h064x6R10161
	for sigtran-archive@odin.ietf.org; Sun, 5 Jan 2003 23:59:06 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h064wMJ10130;
	Sun, 5 Jan 2003 23:58:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h064uJJ10086
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 23:56:19 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15933
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 23:45:43 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h064mvaN019888;
	Sun, 5 Jan 2003 22:48:57 -0600 (CST)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h064mEM08080;
	Sun, 5 Jan 2003 22:48:14 -0600 (CST)
Date: Sun, 5 Jan 2003 22:48:14 -0600 (CST)
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]1 AS and 1 ASP
In-Reply-To: <20030103022356.B11987@openss7.org>
Message-ID: <Pine.SOL.4.10.10301052241540.5784-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,
 Good explanation.As a reader of RFC i agree with you but as an
implementor i dont.Because it leads me to think that RC is within
the scope of SG but which is false as we discussed already.

--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, 3 Jan 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> It's only an example of how to look at it: not a requirement-- node, SGP,
> what's the difference?
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                                   (Fri, 03 Jan 2003 02:53:14)
> > 
> > Brian,
> > Why dont u change section 1.4.2.1 Overview
> > 
> > ...The Routing Context therefore can be viewed as an index into a sending
> > node's Message Distribution Table containing the Routing Key entries.
> > 
> > to
> > 
> > ...The Routing Context therefore can be viewed as an index into a sending
> > SGP's Message Distribution Table containing the Routing Key entries.
> > 
> > --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, 3 Jan 2003, Brian F. G. Bidulock wrote:
> > 
> > > Samuel,
> > > 
> > > Yes, I agree: it is an operational consideration.  That's why you don't
> > > see it in the RFC.
> > > 
> > > --brian
> > > 
> > > Samuel Dur D. Jeyaseelan wrote:                        (Fri, 03 Jan 2003 00:30:54)
> > > > 
> > > > Hi Brian,Tolga,
> > > > 
> > > > According to section 1.4.2.1
> > > > RC is an index into a sending node's message distribution table containing
> > > > the RK entries.
> > > > 
> > > > But section 4.4.1
> > > > The method of RC value assignment at SGP..
> > > > --
> > > > 
> > > > It is said that RC is within the scope of SGP so SGP1 and SGP2 can return 
> > > > the different RC for the same RK1.But each each SGP must maintain
> > > > different AS state machine.I dont think it is a problem.
> > > > 
> > > > If SGP1 and SGP2 return same RC for the single RK,.Here we should go
> > > > to the concept of 'centralization', but the problem(BIG) arises when
> > > > something goes wrong in the 'centralized database (may be due to
> > > > processor failure)'
> > > > 
> > > > So if we have M3UA running over different IP processor(SGP) ,it is better
> > > > to have SGP1 and SGP2 returning different RC for the same RK1.
> > > >  
> > > > --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, 2 Jan 2003, Brian F. G. Bidulock wrote:
> > > > 
> > > > > Tolga,
> > > > > 
> > > > > Tolga Asveren wrote:                               (Thu, 02 Jan 2003 19:54:54)
> > > > > > Brian,
> > > > > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > wrote:
> > > > > > > Tolga,
> > > > > > > 
> > > > > > > Tolga Asveren wrote:                                
> > > > > > >                                 (Thu, 02 Jan 2003
> > > > > > > 05:04:31)
> > > > > > > > Brian,
> > > > > > > > > Samuel,
> > > > > > > > > 
> > > > > > > > > Not necessarily.  They SHOULD return the same RC
> > > > > > > > > value.
> > > > > > > > [TOLGA] Why "SHOULD"? If SGPs are part of the same
> > > > > > > SG,
> > > > > > > > this would be probably the case, but why has it to
> > > > > > > be
> > > > > > > > a "SHOULD" from protocol point of view?
> > > > > > > 
> > > > > > > Because that was the consensus.
> > > > > > [TOLGA] Is this stated somewhere in the M3UA
> > > > > > documents?
> > > > > 
> > > > > No.  I asked for it to be removed because it was an operational
> > > > > consideration.
> > > > > 
> > > > > I can't see a case where any advantage would be gained by not
> > > > > making RC values consistent across SGP in the same SG.  Can you?
> > > > > What is the worth of useless flexibility?  It just creates more
> > > > > work in handling the atypical cases.
> > > > > 
> > > > > --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/
> > > 
> 
> -- 
> 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 mailnull@www1.ietf.org  Mon Jan  6 00:01: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 AAA16232
	for <sigtran-archive@odin.ietf.org>; Mon, 6 Jan 2003 00:01:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h065Bq911207
	for sigtran-archive@odin.ietf.org; Mon, 6 Jan 2003 00:11:52 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h065BCJ11192;
	Mon, 6 Jan 2003 00:11:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h065AtJ11161
	for <sigtran@optimus.ietf.org>; Mon, 6 Jan 2003 00:10:55 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16204
	for <sigtran@ietf.org>; Mon, 6 Jan 2003 00:00:19 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:vCkRXTY7Z3bDN35L69MOqYLMzQYLWG6q@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0653XD14465;
	Sun, 5 Jan 2003 22:03:33 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0653XL10730;
	Sun, 5 Jan 2003 22:03:33 -0700
Date: Sun, 5 Jan 2003 22:03:33 -0700
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]1 AS and 1 ASP
Message-ID: <20030105220333.A7546@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030103022356.B11987@openss7.org> <Pine.SOL.4.10.10301052241540.5784-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.10301052241540.5784-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Sun, Jan 05, 2003 at 10:48:14PM -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,

Yes, change node to SGP.  I don't have control over the document
or I would do it for you.  Ask Javier or Ken to include it in the IG.

--brian

Samuel Dur D. Jeyaseelan wrote:                           (Sun, 05 Jan 2003 22:48:14)
> 
> Brian,
>  Good explanation.As a reader of RFC i agree with you but as an
> implementor i dont.Because it leads me to think that RC is within
> the scope of SG but which is false as we discussed already.
> 
> --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, 3 Jan 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > It's only an example of how to look at it: not a requirement-- node, SGP,
> > what's the difference?
> > 
> > --brian
> > 
> > Samuel Dur D. Jeyaseelan wrote:                        (Fri, 03 Jan 2003 02:53:14)
> > > 
> > > Brian,
> > > Why dont u change section 1.4.2.1 Overview
> > > 
> > > ...The Routing Context therefore can be viewed as an index into a sending
> > > node's Message Distribution Table containing the Routing Key entries.
> > > 
> > > to
> > > 
> > > ...The Routing Context therefore can be viewed as an index into a sending
> > > SGP's Message Distribution Table containing the Routing Key entries.
> > > 
> > > --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. *******
> > > 

-- 
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 Jan  6 00:18: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 AAA16477
	for <sigtran-archive@odin.ietf.org>; Mon, 6 Jan 2003 00:18:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h065SdO11844
	for sigtran-archive@odin.ietf.org; Mon, 6 Jan 2003 00:28:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h065SEJ11832;
	Mon, 6 Jan 2003 00:28:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h065RjJ11775
	for <sigtran@optimus.ietf.org>; Mon, 6 Jan 2003 00:27:45 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16469
	for <sigtran@ietf.org>; Mon, 6 Jan 2003 00:17:08 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h065JvBW018645;
	Sun, 5 Jan 2003 23:20:14 -0600 (CST)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h065JHM21623;
	Sun, 5 Jan 2003 23:19:17 -0600 (CST)
Date: Sun, 5 Jan 2003 23:19:17 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: javier.pastor-balbas@ece.ericsson.se, kmorneau@cisco.com
cc: "Brian F. G. Bidulock" <bidulock@openss7.org>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
In-Reply-To: <20030105220333.A7546@openss7.org>
Message-ID: <Pine.SOL.4.10.10301052311110.584-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>

Javier,Ken,

section 1.4.2.1 Overview

...The Routing Context therefore can be viewed as an index into a sending
node's Message Distribution Table containing the Routing Key entries.

Please change this to [ in IG]

...The Routing Context therefore can be viewed as an index into a sending 
SGP's or Signaling Peer process's Message Distribution Table containing
the Routing Key entries.

--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 Sun, 5 Jan 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> Yes, change node to SGP.  I don't have control over the document
> or I would do it for you.  Ask Javier or Ken to include it in the IG.
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                           (Sun, 05 Jan 2003 22:48:14)
> > 
> > Brian,
> >  Good explanation.As a reader of RFC i agree with you but as an
> > implementor i dont.Because it leads me to think that RC is within
> > the scope of SG but which is false as we discussed already.
> > 
> > --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, 3 Jan 2003, Brian F. G. Bidulock wrote:
> > 
> > > Samuel,
> > > 
> > > It's only an example of how to look at it: not a requirement-- node, SGP,
> > > what's the difference?
> > > 
> > > --brian
> > > 
> > > Samuel Dur D. Jeyaseelan wrote:                        (Fri, 03 Jan 2003 02:53:14)
> > > > 
> > > > Brian,
> > > > Why dont u change section 1.4.2.1 Overview
> > > > 
> > > > ...The Routing Context therefore can be viewed as an index into a sending
> > > > node's Message Distribution Table containing the Routing Key entries.
> > > > 
> > > > to
> > > > 
> > > > ...The Routing Context therefore can be viewed as an index into a sending
> > > > SGP's Message Distribution Table containing the Routing Key entries.
> > > > 
> > > > --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. *******
> > > > 
> 
> -- 
> 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 Jan  6 02:27: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 CAA28041
	for <sigtran-archive@odin.ietf.org>; Mon, 6 Jan 2003 02:27:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h067b7e29044
	for sigtran-archive@odin.ietf.org; Mon, 6 Jan 2003 02:37:07 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h067adJ28908;
	Mon, 6 Jan 2003 02:36:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h067ZJJ28850
	for <sigtran@optimus.ietf.org>; Mon, 6 Jan 2003 02:35:19 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28011
	for <sigtran@ietf.org>; Mon, 6 Jan 2003 02:24:41 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h067RoBE026924;
	Mon, 6 Jan 2003 01:27:52 -0600 (CST)
Received: from axsppc51 by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id LAA23894; Mon, 6 Jan 2003 11:56:55 -0500 (GMT)
Message-ID: <012f01c2b555$801395d0$6501ff0a@axsppc51>
From: "Manjunath" <manju@axes-mach01.usa.alcatel.com>
To: <bidulock@openss7.org>
Cc: <sigtran@ietf.org>
References: <3E153380.ACD487B0@axes-mach01.usa.alcatel.com> <20030103012425.A10860@openss7.org> <3E155467.7E0C192E@axes-mach01.usa.alcatel.com> <20030103022225.A11987@openss7.org> <007a01c2b30f$8eaa6c10$6501ff0a@axsppc51> <20030103151525.C30997@openss7.org>
Subject: Re: [Sigtran] Re: M2PA two out of three
Date: Mon, 6 Jan 2003 13:00:16 +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.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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


  If I say i dont want coffee or tea doesnot it mean
    that i dont want coffee and i dont want tea....
  in another context
   if i say 5 is not equal to 2 or 3 ,doesnot it mean
   5 is not equal to 3 and 5 is not equal to 2 .
  Is not that what even demorgan proved
  _____      _    _
  A + B  =  A . B,
   If what you state is true the link has
 to be treated as faulty if either of the two
condition is true and the following becomes
apparent

 If any two BSNs in three consecutively received User
 Data messages are not the same as the previous one or if any two BSNs
  in three consecutively received User  Data messages are not the same
as any of the FSNs  of the User Data messages in the M2PA transmit buffer
at the time they are received, then MTP3 should be informed that the link is
faulty.

please clarify..

--manju/sibi

----- Original Message -----
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Manjunath" <manju@axes-mach01.usa.alcatel.com>
Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>; <sigtran@ietf.org>
Sent: Saturday, January 04, 2003 3:45 AM
Subject: Re: [Sigtran] Re: M2PA two out of three


> Manjunath,
>
> You miss the efficiency in English of skipping qualifiers on the
> second clause:
>
>    If A is not the same as B or C then D.
> => If A is not the same as B or A is not the same as C then D.
> => If ((A is not the same as B) or (A is not the same as C)) then D.
>
> --brian
>
> Manjunath wrote:                                    (Fri, 03 Jan 2003
15:34:30)
> > Brain,
> >   We  feel what srini observed holds valid,
> >
> >   M2PA should follow the criterion of [2] Q.703, section 5.3.1 for
> > incorrect BSNs: If (( any two BSNs in three consecutively received User
> > Data messages) are not the same ((as the previous one) or (any of the
FSNs
> > of the User Data messages in the M2PA transmit buffer at the time they
> > are received))), then MTP3 should be informed that the link is faulty."
> >   If A is not same as B or C then D, it means that A is not same as B
and A
> > is
> > not same as C then D proving De Morgan's law
> >            ____           _ _          _       _
> >      A.( B+C) = A.(B.C) = A.B . A.C
> >
> > Is not what Srini stated valid??
> >
> > thanks
> > manju/sibi
> >
> >
> >
> >
> > ----- Original Message -----
> > From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > To: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
> > Cc: <sigtran@ietf.org>
> > Sent: Friday, January 03, 2003 2:52 PM
> > Subject: Re: [Sigtran] Re: M2PA two out of three
> >
> >
> > > Srini,
> > >
> > > But there is the difference:
> > >         _   _
> > > I read  A + B.
> > >
> > > The "not" in this case only applies to the immediate subject and _not_
the
> > > entire sentence.
> > >
> > > --brian
> > >
> > > ksrinivas wrote:                                               (Fri,
03
> > Jan 2003 14:44:16)
> > > > Brian,
> > > >
> > > >       I understood the thing. But I still feel there is some
relation
> > between
> > > > logic and English. This can be felt from the De-Morgans law below.
> > > >
> > > > ____    _ _
> > > > A+B = A.B
> > > >
> > > > where, A = the same as the previous one(BSNs),
> > > >            B = the same as any of the FSNs of the User Data messages
in
> > the M2PA
> > > > transmit buffer at
> > > >                   the time they are received.
> > > >
> > > > Thanks & Regards,
> > > > Srini
> > > >
> > > > "Brian F. G. Bidulock" wrote:
> > > >
> > > > > Srini,
> > > > >
> > > > > "Or" and "and" (or "or" or "and") are not treated as logical or
> > > > > and logical and when used in English. ;)
> > > > >
> > > > > Nevertheless in this case, "or" is correct in both senses.
> > > > >
> > > > > --brian
> > > > >
> > > > > ksrinivas wrote:                                   (Fri, 03 Jan
2003
> > 12:23:54)
> > > > > >
> > > > > >    Brian,
> > > > > >
> > > > > >         In  Section  4.2.1  of  M2PA  Draft  version  6, the
> > following is
> > > > > >    observed.
> > > > > >
> > > > > >    "M2PA should follow the criterion of [2] Q.703, section 5.3.1
for
> > > > > >    incorrect BSNs: If any two BSNs in three consecutively
received
> > User
> > > > > >    Data messages are not the same as the previous one or any of
the
> > FSNs
> > > > > >    of the User Data messages in the M2PA transmit buffer at the
time
> > they
> > > > > >    are received, then MTP3 should be informed that the link is
> > faulty."
> > > > > >
> > > > > >    The highlighted "or" should have been "and".
> > > > > >
> > > > > >    The same error "or" is carried from Q.703
> > > > > >
> > > > > >    --Srini
> > > > >
> > > > > --
> > > > > 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 mailnull@www1.ietf.org  Mon Jan  6 02:28: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 CAA28080
	for <sigtran-archive@odin.ietf.org>; Mon, 6 Jan 2003 02:28:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h067cIG29651
	for sigtran-archive@odin.ietf.org; Mon, 6 Jan 2003 02:38:18 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h067c6J29623;
	Mon, 6 Jan 2003 02:38:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h067bXJ29479
	for <sigtran@optimus.ietf.org>; Mon, 6 Jan 2003 02:37:33 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28037
	for <sigtran@ietf.org>; Mon, 6 Jan 2003 02:26:55 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h067TxBE027037;
	Mon, 6 Jan 2003 01:30:01 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id LAA23939; Mon, 6 Jan 2003 11:58:39 -0500 (GMT)
Message-ID: <3E193095.BAFC0B1D@axes-mach01.usa.alcatel.com>
Date: Mon, 06 Jan 2003 13:00:30 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M2PA two out of three
References: <3E153380.ACD487B0@axes-mach01.usa.alcatel.com> <20030103012425.A10860@openss7.org> <3E155467.7E0C192E@axes-mach01.usa.alcatel.com> <20030103022225.A11987@openss7.org>
Content-Type: multipart/alternative;
 boundary="------------D29BE45089A119409E5B4D72"
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>


--------------D29BE45089A119409E5B4D72
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 7bit

Brian,
                                                _    _
     If one reads the sentence as A + B, then the following can be interpreted.

Fail the link, if

      either
      any two BSNs in three consecutively received User Data messages are not the same as the
previous one
      or
     not the same as any of the FSNs of the User Data messages in the M2PA transmit buffer at
the time they are received


_  _
But I feel this is mis-leading, We should fail the link only when both the conditions(A.B) are
met.

--Srini

"Brian F. G. Bidulock" wrote:

> Srini,
>
> But there is the difference:
>         _   _
> I read  A + B.
>
> The "not" in this case only applies to the immediate subject and _not_ the
> entire sentence.
>
> --brian
>
> ksrinivas wrote:                                               (Fri, 03 Jan 2003 14:44:16)
> > Brian,
> >
> >       I understood the thing. But I still feel there is some relation between
> > logic and English. This can be felt from the De-Morgans law below.
> >
> > ____    _ _
> > A+B = A.B
> >
> > where, A = the same as the previous one(BSNs),
> >            B = the same as any of the FSNs of the User Data messages in the M2PA
> > transmit buffer at
> >                   the time they are received.
> >
> > Thanks & Regards,
> > Srini
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > Srini,
> > >
> > > "Or" and "and" (or "or" or "and") are not treated as logical or
> > > and logical and when used in English. ;)
> > >
> > > Nevertheless in this case, "or" is correct in both senses.
> > >
> > > --brian
> > >
> > > ksrinivas wrote:                                   (Fri, 03 Jan 2003 12:23:54)
> > > >
> > > >    Brian,
> > > >
> > > >         In  Section  4.2.1  of  M2PA  Draft  version  6, the following is
> > > >    observed.
> > > >
> > > >    "M2PA should follow the criterion of [2] Q.703, section 5.3.1 for
> > > >    incorrect BSNs: If any two BSNs in three consecutively received User
> > > >    Data messages are not the same as the previous one or any of the FSNs
> > > >    of the User Data messages in the M2PA transmit buffer at the time they
> > > >    are received, then MTP3 should be informed that the link is faulty."
> > > >
> > > >    The highlighted "or" should have been "and".
> > > >
> > > >    The same error "or" is carried from Q.703
> > > >
> > > >    --Srini
> > >
> > > --
> > > 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

--------------D29BE45089A119409E5B4D72
Content-Type: text/html; charset=x-user-defined
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Brian,
<br>&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;&nbsp;&nbsp;&nbsp;
_&nbsp;&nbsp;&nbsp; _
<br>&nbsp;&nbsp;&nbsp;&nbsp; If one reads the sentence as A + B, then the
following can be interpreted.
<p>Fail the link, if
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; either
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; any two BSNs in three consecutively
received User Data messages are <b>not</b> the same as the previous one
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or
<br>&nbsp;&nbsp;&nbsp;&nbsp; <b>not</b> the same as any of the FSNs of
the User Data messages in the M2PA transmit buffer at the time they are
received
<p>&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;&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;&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; _
<br>But I feel this is mis-leading, We should fail the link only when both
the conditions(A.B) are met.
<p>--Srini
<p>"Brian F. G. Bidulock" wrote:
<blockquote TYPE=CITE>Srini,
<p>But there is the difference:
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; _&nbsp;&nbsp; _
<br>I read&nbsp; A + B.
<p>The "not" in this case only applies to the immediate subject and _not_
the
<br>entire sentence.
<p>--brian
<p>ksrinivas wrote:&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;&nbsp;&nbsp;
(Fri, 03 Jan 2003 14:44:16)
<br>> Brian,
<br>>
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I understood the thing. But I
still feel there is some relation between
<br>> logic and English. This can be felt from the De-Morgans law below.
<br>>
<br>> ____&nbsp;&nbsp;&nbsp; _ _
<br>> A+B = A.B
<br>>
<br>> where, A = the same as the previous one(BSNs),
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
B = the same as any of the FSNs of the User Data messages in the M2PA
<br>> transmit buffer at
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
the time they are received.
<br>>
<br>> Thanks &amp; Regards,
<br>> Srini
<br>>
<br>> "Brian F. G. Bidulock" wrote:
<br>>
<br>> > Srini,
<br>> >
<br>> > "Or" and "and" (or "or" or "and") are not treated as logical or
<br>> > and logical and when used in English. ;)
<br>> >
<br>> > Nevertheless in this case, "or" is correct in both senses.
<br>> >
<br>> > --brian
<br>> >
<br>> > ksrinivas wrote:&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;
(Fri, 03 Jan 2003 12:23:54)
<br>> > >
<br>> > >&nbsp;&nbsp;&nbsp; Brian,
<br>> > >
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In&nbsp; Section&nbsp;
4.2.1&nbsp; of&nbsp; M2PA&nbsp; Draft&nbsp; version&nbsp; 6, the following
is
<br>> > >&nbsp;&nbsp;&nbsp; observed.
<br>> > >
<br>> > >&nbsp;&nbsp;&nbsp; "M2PA should follow the criterion of [2] Q.703,
section 5.3.1 for
<br>> > >&nbsp;&nbsp;&nbsp; incorrect BSNs: If any two BSNs in three consecutively
received User
<br>> > >&nbsp;&nbsp;&nbsp; Data messages are not the same as the previous
one or any of the FSNs
<br>> > >&nbsp;&nbsp;&nbsp; of the User Data messages in the M2PA transmit
buffer at the time they
<br>> > >&nbsp;&nbsp;&nbsp; are received, then MTP3 should be informed
that the link is faulty."
<br>> > >
<br>> > >&nbsp;&nbsp;&nbsp; The highlighted "or" should have been "and".
<br>> > >
<br>> > >&nbsp;&nbsp;&nbsp; The same error "or" is carried from Q.703
<br>> > >
<br>> > >&nbsp;&nbsp;&nbsp; --Srini
<br>> >
<br>> > --
<br>> > Brian F. G. Bidulock
<br>> > bidulock@openss7.org
<br>> > <a href="http://www.openss7.org/">http://www.openss7.org/</a>
<br>> > _______________________________________________
<br>> > Sigtran mailing list
<br>> > Sigtran@ietf.org
<br>> > <a href="https://www1.ietf.org/mailman/listinfo/sigtran">https://www1.ietf.org/mailman/listinfo/sigtran</a>
<p>--
<br>Brian F. G. Bidulock
<br>bidulock@openss7.org
<br><a href="http://www.openss7.org/">http://www.openss7.org/</a>
<br>_______________________________________________
<br>Sigtran mailing list
<br>Sigtran@ietf.org
<br><a href="https://www1.ietf.org/mailman/listinfo/sigtran">https://www1.ietf.org/mailman/listinfo/sigtran</a></blockquote>
</html>

--------------D29BE45089A119409E5B4D72--

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



From mailnull@www1.ietf.org  Mon Jan  6 02:52: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 CAA28742
	for <sigtran-archive@odin.ietf.org>; Mon, 6 Jan 2003 02:52:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0682b830963
	for sigtran-archive@odin.ietf.org; Mon, 6 Jan 2003 03:02:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0682AJ30944;
	Mon, 6 Jan 2003 03:02:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0681ZJ30914
	for <sigtran@optimus.ietf.org>; Mon, 6 Jan 2003 03:01:35 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28717
	for <sigtran@ietf.org>; Mon, 6 Jan 2003 02:50:57 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:78VaPOCcgwfEjCtM/dKGTmFxIaJms+WJ@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h067sAD16720;
	Mon, 6 Jan 2003 00:54:10 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h067sAE13721;
	Mon, 6 Jan 2003 00:54:10 -0700
Date: Mon, 6 Jan 2003 00:54:10 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M2PA two out of three
Message-ID: <20030106005410.B7546@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <3E153380.ACD487B0@axes-mach01.usa.alcatel.com> <20030103012425.A10860@openss7.org> <3E155467.7E0C192E@axes-mach01.usa.alcatel.com> <20030103022225.A11987@openss7.org> <3E193095.BAFC0B1D@axes-mach01.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: <3E193095.BAFC0B1D@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Mon, Jan 06, 2003 at 01:00:30PM +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>

Srini,

In fact, if the BSNR is outside the range (inclusive) from FSNF-1 to FSNT
twice consecutively, then the link should fail.  Note that FSNT is always
set to the last correct BSNR.  See the SDLs in Q.703 or T1.111.

I would agree that M2PA should not repeat statements from these
specifications, but should merely reference them.  (Particularly as some
corrections were made to SDLs in the Q.703 IG.)

--brian

ksrinivas wrote:                               (Mon, 06 Jan 2003 13:00:30)
> 
>    Brian,
>                                                    _    _
>          If  one  reads  the sentence as A + B, then the following can be
>    interpreted.
> 
>    Fail the link, if
> 
>          either
>           any two BSNs in three consecutively received User Data messages
>    are not the same as the previous one
>          or
>          not the same as any of the FSNs of the User Data messages in the
>    M2PA transmit buffer at the time they are received
> 
> 
>                                                         _  _
>    But I feel this is mis-leading, We should fail the link only when both
>    the conditions(A.B) are met.
> 
>    --Srini
> 

-- 
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 Jan  6 04:21: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 EAA29953
	for <sigtran-archive@odin.ietf.org>; Mon, 6 Jan 2003 04:21:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h069W3l03938
	for sigtran-archive@odin.ietf.org; Mon, 6 Jan 2003 04:32:03 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h069VaJ03904;
	Mon, 6 Jan 2003 04:31:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h069U7J03844
	for <sigtran@optimus.ietf.org>; Mon, 6 Jan 2003 04:30:07 -0500
Received: from tank.fr.ulticom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29910
	for <sigtran@ietf.org>; Mon, 6 Jan 2003 04:19:26 -0500 (EST)
Received: from PCGASTAUDL (pc-gastaud-l.fr.ulticom.com [172.26.32.87])
	by tank.fr.ulticom.com (8.8.8+Sun/8.8.8) with SMTP id KAA16940;
	Mon, 6 Jan 2003 10:22:18 +0100 (MET)
From: "Valerie Gastaud" <valerie.gastaud@ulticom.com>
To: <bidulock@openss7.org>, "Tolga Asveren" <tolga_asveren@yahoo.com>
Cc: <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
Date: Mon, 6 Jan 2003 10:46:25 +0100
Message-ID: <NDBBIHAOCKGAMIKNLALOIEPEDJAA.valerie.gastaud@ulticom.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: <20030105061154.S23879@openss7.org>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
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, Brian,

Very interesting thread...
To me the point is that if it stays in the RFC, people will try to support
CIC range based RK. If there is a conscensus that this is a nonsense because
this will lead to interoperability problems, then it must be removed from
the RFC.
I would tend to agree with you that M3UA, as a level 3 protocol, must only
route on level 3 available information, such as DPC and SIO.
If it is to route on CIC (or SSN), this means that NIF has to have some sort
of level 4 functionality (ISUP or SCCP management) that must be identified
and specified. Also the limitations should be listed, such as pre-arranged
circuit groups for example.

Valerie

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
Brian F. G. Bidulock
Sent: dimanche 5 janvier 2003 14:12
To: Tolga Asveren
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages


Tolga,

Tolga Asveren wrote:
(Sun, 05 Jan 2003 04:10:25)
> [TOLGA] I feel I really fail to explain
> what I mean.  The real point is, if
> somebody can do it without
> interoperability problems, let them do
> it.

Let them do it outside of the standard
unless they can (at least logically)
demonstrate interoperability.

> And for some RK type even if it is
> really impossible, why us this related
> with M3UA itself? It is clear that for
> non-MTP3 RKs some management logic needs
> to be implemented and without violating
> the protocol. IMO, this is the only
> relevant thing from M3UA point of view.

Section 3.3.1:

  "The DATA message contains the SS7
  MTP3-User protocol data, which is an
  MTP-TRANSFER primitive, including the
  complete MTP3 Routing Label."

Split CGBs are not MTP-TRANSFER
primitives.

Section 3.3.1:

  "The Protocol Data parameter contains
  the original SS7 MTP3 message, including
  the Service Information Octet and
  Routing Label."

Split CGBs are not the "original SS7
MTP3 message".

Section 3.3.1:

  "The User Protocol Data field contains
  a byte string of MTP-User information
  from the original SS7 message starting
  with the first byte of the original SS7
  message following the Routing Label."

Split CGBs do not contain the original
SS7 byte for byte as indicated here.

Section 1.5.1

  "For internal SGP modeling purposes, at
  the NIF level, SS7 signalling messages
  that are destined to the MGC are
  received as MTP-TRANSFER indication
  primitives from the MTP Level 3 upper
  layer interface, translated to
  MTP-TRANSFER request primitives, and
  sent to the local M3UA-resident message
  distribution function for outgoing
  routing to the final IP destination.
  Messages received from the local M3UA
  network address translations and mapping
  function as MTP-TRANSFER indication
  primitives ar esent to the MTP Level 3
  upper layer interface as MTP-TRANSFER
  request primitives for outgoing MTP
  Level 3 routing to an SS7 SEP."

The message distribution function and
network address translations (routing) is
M3UA-resident (it is not in the NIF).

(Note that the above was also the only
ISUP example in the spec.)

Section 4.1.1:

  "The M3UA peer receiving the DATA
  message sends a MTP-TRANSFER indication
  primitive to the upper layer."

  "The M3UA message distribution function
  (see Section 1.4.2.1) determins the
  Application Server (AS) based on
  comparing the information in the
  MTP-TRANSFER request primitive with a
  provisioned Routing Key."

Comparison with Routing Keys occurs in the
M3UA, not the NIF.

Section 5.4.2.1:

  "When the M3UA layer at the SGP has
  received DATA messages from its peer
  destined to the SS7 network it will do
  the following:

  - Evaluate the optional fields of the
    DATA message, if present, to determine
    the Network Appearance;

  - Map the Protocol data field of the
    DATA message into an MTP-TRANSFER
    request primitive;

  - Pass the MTP-TRANSFER request
    primitive to the MTP3 of the concerned
    Network Appearance."

Aggregating CGBA responses would violate
this procedure.

> [TOLGA] For me the guideline is RFC/IG.
> As long as one does not violate it,
> she/he is free to do anyhting. I agree,
> the same applies to NIF, never violate
> the protocol. This is also my opinion
> for non-MTP3 RKs, if one can support
> them by not breaking the protocol, they
> are free to do it.

Who is "they?"

For CIC routing keys, the only current
propsal that does not violate the protocol
is to ensure than no circuit groups span
routing keys, ensuring that there is
always a default AS, and arranging
circuits and trunks such that a circuit
group message will never be generated that
spans the routing keys.

(Which is what I was telling Joseph when
you proposed your splitting algorithm
which violates all of the above.)

The fully interoperable way to acheive
what is being attempted with CIC routing
keys (but fails dismally) is by
_load-sharing_ on CIC ranges rather than
_routing_ on CIC ranges.

Why would anyone want to court a
proprietary solution (CIC routing) when an
interoperable solution (CIC load-sharing)
exists?

I don't see any problem saying that M3UA
MUST use CIC load-sharing, which is
demonstrably interoperable, and MUST NOT
use CIC routing keys which cannot (any
time soon) be demonstrated  to
interoperate.

--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 mailnull@www1.ietf.org  Mon Jan  6 05:05: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 FAA00482
	for <sigtran-archive@odin.ietf.org>; Mon, 6 Jan 2003 05:05:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h06AG3c06582
	for sigtran-archive@odin.ietf.org; Mon, 6 Jan 2003 05:16:03 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h06AFWJ06562;
	Mon, 6 Jan 2003 05:15:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h06AEHJ06526
	for <sigtran@optimus.ietf.org>; Mon, 6 Jan 2003 05:14:17 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00471
	for <sigtran@ietf.org>; Mon, 6 Jan 2003 05:03:34 -0500 (EST)
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFEB629C01.912693C3-ONC2256CA6.00365337@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Mon, 6 Jan 2003 12:03:28 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/06/2003
 12:03:31 PM
MIME-Version: 1.0
Content-type: text/plain; charset=Windows-1254
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h06AEHJ06527
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


Valerie,

I agree that one might think any ISUP/SCCP functionality on SG as a
violation of a layered approach and this is not nice at all. It is obvious
that for non-MTP3 RKs, one migth need a management logic and such RKs are
not very suitable to be supported with a M3UA based SG. But I disagree with
a preassumption that any of those functionalities will bring
interoperability problems.
Another point is, if we want to keep the flexibility that RK types are not
limited, then it might be good to add a few sentences saying that
management functionality needed to support such RK types might require
message filterýng/generation on the level of the corresponding protocol.
This will address also some of the concerns Brian has pointed out.

         Tolga



                                                                                                                   
                    "Valerie Gastaud"                                                                              
                    <valerie.gastaud@ul       To:     <bidulock@openss7.org>, "Tolga Asveren"                      
                    ticom.com>                 <tolga_asveren@yahoo.com>                                           
                    Sent by:                  cc:     <sigtran@ietf.org>                                           
                    sigtran-admin@ietf.       Subject:     RE: [Sigtran] M3UA distributing ISUP group messages     
                    org                                                                                            
                                                                                                                   
                                                                                                                   
                    06.01.2003 11:46                                                                               
                                                                                                                   
                                                                                                                   




Tolga, Brian,

Very interesting thread...
To me the point is that if it stays in the RFC, people will try to support
CIC range based RK. If there is a conscensus that this is a nonsense
because
this will lead to interoperability problems, then it must be removed from
the RFC.
I would tend to agree with you that M3UA, as a level 3 protocol, must only
route on level 3 available information, such as DPC and SIO.
If it is to route on CIC (or SSN), this means that NIF has to have some
sort
of level 4 functionality (ISUP or SCCP management) that must be identified
and specified. Also the limitations should be listed, such as pre-arranged
circuit groups for example.

Valerie

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
Brian F. G. Bidulock
Sent: dimanche 5 janvier 2003 14:12
To: Tolga Asveren
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages


Tolga,

Tolga Asveren wrote:
(Sun, 05 Jan 2003 04:10:25)
> [TOLGA] I feel I really fail to explain
> what I mean.  The real point is, if
> somebody can do it without
> interoperability problems, let them do
> it.

Let them do it outside of the standard
unless they can (at least logically)
demonstrate interoperability.

> And for some RK type even if it is
> really impossible, why us this related
> with M3UA itself? It is clear that for
> non-MTP3 RKs some management logic needs
> to be implemented and without violating
> the protocol. IMO, this is the only
> relevant thing from M3UA point of view.

Section 3.3.1:

  "The DATA message contains the SS7
  MTP3-User protocol data, which is an
  MTP-TRANSFER primitive, including the
  complete MTP3 Routing Label."

Split CGBs are not MTP-TRANSFER
primitives.

Section 3.3.1:

  "The Protocol Data parameter contains
  the original SS7 MTP3 message, including
  the Service Information Octet and
  Routing Label."

Split CGBs are not the "original SS7
MTP3 message".

Section 3.3.1:

  "The User Protocol Data field contains
  a byte string of MTP-User information
  from the original SS7 message starting
  with the first byte of the original SS7
  message following the Routing Label."

Split CGBs do not contain the original
SS7 byte for byte as indicated here.

Section 1.5.1

  "For internal SGP modeling purposes, at
  the NIF level, SS7 signalling messages
  that are destined to the MGC are
  received as MTP-TRANSFER indication
  primitives from the MTP Level 3 upper
  layer interface, translated to
  MTP-TRANSFER request primitives, and
  sent to the local M3UA-resident message
  distribution function for outgoing
  routing to the final IP destination.
  Messages received from the local M3UA
  network address translations and mapping
  function as MTP-TRANSFER indication
  primitives ar esent to the MTP Level 3
  upper layer interface as MTP-TRANSFER
  request primitives for outgoing MTP
  Level 3 routing to an SS7 SEP."

The message distribution function and
network address translations (routing) is
M3UA-resident (it is not in the NIF).

(Note that the above was also the only
ISUP example in the spec.)

Section 4.1.1:

  "The M3UA peer receiving the DATA
  message sends a MTP-TRANSFER indication
  primitive to the upper layer."

  "The M3UA message distribution function
  (see Section 1.4.2.1) determins the
  Application Server (AS) based on
  comparing the information in the
  MTP-TRANSFER request primitive with a
  provisioned Routing Key."

Comparison with Routing Keys occurs in the
M3UA, not the NIF.

Section 5.4.2.1:

  "When the M3UA layer at the SGP has
  received DATA messages from its peer
  destined to the SS7 network it will do
  the following:

  - Evaluate the optional fields of the
    DATA message, if present, to determine
    the Network Appearance;

  - Map the Protocol data field of the
    DATA message into an MTP-TRANSFER
    request primitive;

  - Pass the MTP-TRANSFER request
    primitive to the MTP3 of the concerned
    Network Appearance."

Aggregating CGBA responses would violate
this procedure.

> [TOLGA] For me the guideline is RFC/IG.
> As long as one does not violate it,
> she/he is free to do anyhting. I agree,
> the same applies to NIF, never violate
> the protocol. This is also my opinion
> for non-MTP3 RKs, if one can support
> them by not breaking the protocol, they
> are free to do it.

Who is "they?"

For CIC routing keys, the only current
propsal that does not violate the protocol
is to ensure than no circuit groups span
routing keys, ensuring that there is
always a default AS, and arranging
circuits and trunks such that a circuit
group message will never be generated that
spans the routing keys.

(Which is what I was telling Joseph when
you proposed your splitting algorithm
which violates all of the above.)

The fully interoperable way to acheive
what is being attempted with CIC routing
keys (but fails dismally) is by
_load-sharing_ on CIC ranges rather than
_routing_ on CIC ranges.

Why would anyone want to court a
proprietary solution (CIC routing) when an
interoperable solution (CIC load-sharing)
exists?

I don't see any problem saying that M3UA
MUST use CIC load-sharing, which is
demonstrably interoperable, and MUST NOT
use CIC routing keys which cannot (any
time soon) be demonstrated  to
interoperate.

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




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



From mailnull@www1.ietf.org  Mon Jan  6 07:04: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 HAA01753
	for <sigtran-archive@odin.ietf.org>; Mon, 6 Jan 2003 07:04:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h06CEGS12473
	for sigtran-archive@odin.ietf.org; Mon, 6 Jan 2003 07:14:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h06CDgJ12447;
	Mon, 6 Jan 2003 07:13:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h06CCVJ12399
	for <sigtran@optimus.ietf.org>; Mon, 6 Jan 2003 07:12:31 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01723
	for <sigtran@ietf.org>; Mon, 6 Jan 2003 07:01:46 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h06C4vBK014355;
	Mon, 6 Jan 2003 06:05:01 -0600 (CST)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h06C4dM17052;
	Mon, 6 Jan 2003 06:04:39 -0600 (CST)
Date: Mon, 6 Jan 2003 06:04:39 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: sigtran@ietf.org
In-Reply-To: <20030106005410.B7546@openss7.org>
Message-ID: <Pine.SOL.4.10.10301060533200.673-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sigtran] [M3UA] concerned ASPs
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,

According to section 3.4.1
(and in many SSNM messages)

The DUNA message is sent from an SGP in an SG to all concerned ASPs...

What is this concerned ASPs?

Are these the ASPs connected to the SGP?
or
Are these ASPs that have registered with the Affected Point
Codes(mentioned in OPC list of REG message) in SGP?

--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 mailnull@www1.ietf.org  Mon Jan  6 07:49: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 HAA02417
	for <sigtran-archive@odin.ietf.org>; Mon, 6 Jan 2003 07:49:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h06CxkW14705
	for sigtran-archive@odin.ietf.org; Mon, 6 Jan 2003 07:59:46 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h06CxLJ14687;
	Mon, 6 Jan 2003 07:59:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h06CwrJ14666
	for <sigtran@optimus.ietf.org>; Mon, 6 Jan 2003 07:58:53 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02412
	for <sigtran@ietf.org>; Mon, 6 Jan 2003 07:48:08 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:A3XQ4wx9ymZEyb8hdaRcY4i1lAGZqGWe@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h06CpND22291;
	Mon, 6 Jan 2003 05:51:23 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h06CpMh19288;
	Mon, 6 Jan 2003 05:51:22 -0700
Date: Mon, 6 Jan 2003 05:51:22 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: sigtran@ietf.org
Message-ID: <20030106055122.D7546@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030106005410.B7546@openss7.org> <Pine.SOL.4.10.10301060533200.673-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.10301060533200.673-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Mon, Jan 06, 2003 at 06:04:39AM -0600
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: [M3UA] concerned ASPs
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,

Concerned ASPs are ASPs which are ASP-ACTIVE for an AS which corresponds to an
MTP-User which needs to be delivered the MTP-PAUSE primitive in accordance
with SS7 MTP Level 3 specifications, or which need to be sent a DUNA message
in response to a valid DAUD message from that ASP.

--brian

Samuel Dur D. Jeyaseelan wrote:                       (Mon, 06 Jan 2003 06:04:39)
> 
> Brian,
> 
> According to section 3.4.1
> (and in many SSNM messages)
> 
> The DUNA message is sent from an SGP in an SG to all concerned ASPs...
> 
> What is this concerned ASPs?
> 
> Are these the ASPs connected to the SGP?
> or
> Are these ASPs that have registered with the Affected Point
> Codes(mentioned in OPC list of REG message) in SGP?
> 
> --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. *******
> 

-- 
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 Jan  6 09:32:50 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 JAA04156
	for <sigtran-archive@odin.ietf.org>; Mon, 6 Jan 2003 09:32:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h06Eh5t20916
	for sigtran-archive@odin.ietf.org; Mon, 6 Jan 2003 09:43:05 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h06EgSJ20870;
	Mon, 6 Jan 2003 09:42:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h06EfEJ20825
	for <sigtran@optimus.ietf.org>; Mon, 6 Jan 2003 09:41:14 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04113
	for <sigtran@ietf.org>; Mon, 6 Jan 2003 09:30:27 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:ZC+9hC5J1hEH/huZZJwr0vaQtKHBltaV@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h06EXfD25216;
	Mon, 6 Jan 2003 07:33:41 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h06EXef23598;
	Mon, 6 Jan 2003 07:33:40 -0700
Date: Mon, 6 Jan 2003 07:33:40 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Manjunath <manju@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M2PA two out of three
Message-ID: <20030106073340.E7546@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Manjunath <manju@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <3E153380.ACD487B0@axes-mach01.usa.alcatel.com> <20030103012425.A10860@openss7.org> <3E155467.7E0C192E@axes-mach01.usa.alcatel.com> <20030103022225.A11987@openss7.org> <007a01c2b30f$8eaa6c10$6501ff0a@axsppc51> <20030103151525.C30997@openss7.org> <012f01c2b555$801395d0$6501ff0a@axsppc51>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <012f01c2b555$801395d0$6501ff0a@axsppc51>; from manju@axes-mach01.usa.alcatel.com on Mon, Jan 06, 2003 at 01:00:16PM +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>

Manjunath,

Consider that in English `or' can mean:

	logical or
	logical exclusive or
	logical and

If you consider that the `or' means "logical exclusive or"
then:

  ~A (+) ~B => A (+) B

Which is correct.

`Or' means "logical exclusive or" more often in English than
it means "logical or".

--brian

Manjunath wrote:                                   (Mon, 06 Jan 2003 13:00:16)
> 
>   If I say i dont want coffee or tea doesnot it mean
>     that i dont want coffee and i dont want tea....
>   in another context
>    if i say 5 is not equal to 2 or 3 ,doesnot it mean
>    5 is not equal to 3 and 5 is not equal to 2 .
>   Is not that what even demorgan proved
>   _____      _    _
>   A + B  =  A . B,
>    If what you state is true the link has
>  to be treated as faulty if either of the two
> condition is true and the following becomes
> apparent
> 
>  If any two BSNs in three consecutively received User
>  Data messages are not the same as the previous one or if any two BSNs
>   in three consecutively received User  Data messages are not the same
> as any of the FSNs  of the User Data messages in the M2PA transmit buffer
> at the time they are received, then MTP3 should be informed that the link is
> faulty.
> 
> please clarify..
> 
> --manju/sibi
> 

-- 
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 Jan  6 13:41: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 NAA09930
	for <sigtran-archive@odin.ietf.org>; Mon, 6 Jan 2003 13:41:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h06IpNu04941
	for sigtran-archive@odin.ietf.org; Mon, 6 Jan 2003 13:51:23 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h06Ip4J04929;
	Mon, 6 Jan 2003 13:51:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h06InbJ04817
	for <sigtran@optimus.ietf.org>; Mon, 6 Jan 2003 13:49:37 -0500
Received: from revere.sonusnet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09847
	for <sigtran@ietf.org>; Mon, 6 Jan 2003 13:38:44 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3.sonusnet.com [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h06IfGS25458;
	Mon, 6 Jan 2003 13:41:16 -0500 (EST)
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19)
	id <Y68HRXSL>; Mon, 6 Jan 2003 13:41:47 -0500
Message-ID: <4CF48720B6E9D4118D040060CF2074E9072F6BA8@sonusdc3.sonusnet.com>
From: "Wung, Joseph" <JWung@sonusnet.com>
To: "'James Doss'" <JDoss@verisign.com>,
        "'bidulock@openss7.org'"
	 <bidulock@openss7.org>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
Date: Mon, 6 Jan 2003 13:41:15 -0500 
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>

Can someone tell me why as a user of MTP3, SCCP would need
SUA to backhaul SCCP services, but ISUP would not need
a UA function, e.g., ISUA to backhaul its services, and
rather uses M3UA to trasfer its services?

Joe

> -----Original Message-----
> From: James Doss [mailto:JDoss@verisign.com]
> Sent: Friday, January 03, 2003 6:06 PM
> To: 'bidulock@openss7.org'; Wung, Joseph
> Cc: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA distributing ISUP group messages
> 
> 
> Hi Joseph/Brian,
> I was thinking IETF has a separate RFC for ISUP.
> Is it not a good idea to start one. That will help to reduce the
> complexities in the M3UA.
> So that the ISUP and SCCP support can be seperated.
> 
> James Doss
> Verisign 
> 
> 
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Friday, January 03, 2003 5:06 PM
> To: Wung, Joseph
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] M3UA distributing ISUP group messages
> 
> 
> Joseph,
> 
> I offerred to write one several times.  Nobody took me up
> on my offer.
> 
> --brian
> 
> Wung, Joseph wrote:                      (Fri, 03 Jan 2003 11:35:13)
> > Brian,
> > 
> > Is there ISUA anywhere?
> > 
> > Joe
> > 
> > > You will need to describe all that M3UA lacks in support
> > > of CIC routing.  Once you are finished that exercise you
> > > will have ISUA.  (As mentioned on the original thread
> > > from July 2001.)
> > > 
> > > --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
> 
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Mon Jan  6 23:13: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 XAA22989
	for <sigtran-archive@odin.ietf.org>; Mon, 6 Jan 2003 23:13:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h074NZT09056
	for sigtran-archive@odin.ietf.org; Mon, 6 Jan 2003 23:23:35 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h074MrJ09040;
	Mon, 6 Jan 2003 23:22:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h074JiJ08900
	for <sigtran@optimus.ietf.org>; Mon, 6 Jan 2003 23:19:44 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22946
	for <sigtran@ietf.org>; Mon, 6 Jan 2003 23:08:41 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h074BqaN001964;
	Mon, 6 Jan 2003 22:11:53 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id IAA12055; Tue, 7 Jan 2003 08:40:32 -0500 (GMT)
Message-ID: <3E1A53B1.DEEA8876@axes-mach01.usa.alcatel.com>
Date: Tue, 07 Jan 2003 09:42:34 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
References: <20030102042412.A1077@openss7.org> <Pine.SOL.4.10.10301020550010.23295-100000@sun2594.ssd.usa.alcatel.com> <20030102045510.A2482@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

  >> Not necessarily.  They SHOULD return the same RC value.

   If SGP1 and SGP2 do not return the same RC values for RK1, does the RK:RC relation of 1:1 not voilated (Since
the scope of RK1 is global i.e., SG, the RC scope should aslo be for SG and return the same RC values).

--Srini

"Brian F. G. Bidulock" wrote:

> Samuel,
>
> Not necessarily.  They SHOULD return the same RC value.
>
> --brian
>
> Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 02 Jan 2003 05:51:29)
> >
> > Brian,
> >
> > For RK1 ,Will SGP1 and SGP2 return same RC?
> >
> > -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, 2 Jan 2003, Brian F. G. Bidulock wrote:
> >
> > > Samuel,
> > >
> > > Yes, all the SS7 UAs support this.  The ASP registers once each with SGP1
> > > and SGP2.
> > >
> > > --brian
> > >
> > > Samuel Dur D. Jeyaseelan wrote:                  (Thu, 02 Jan 2003 05:08:41)
> > > >
> > > > Hi,
> > > >
> > > >  Suppose an AS has single ASP and wants to connect to SGP1
> > > > and SGP2 for the same RK1.
> > > >
> > > >
> > > > +---------+                                 +-----+
> > > > |+------+ |          RK1      SCTP1         | ASP |
> > > > || SGP1 |-|---------------------------------+-----+
> > > > |+------+ |                                    |
> > > > |         |                                    |
> > > > |+------+ |          RK1      SCTP2            |
> > > > || SGP2 |-|------------------------------------+
> > > > |+------+ |
> > > > +---------+
> > > >
> > > > Does REG procedures at SGP allow this kind of scenario?
> > > >
> > > > This kind of scenario may be required in case SGP1 goes down
> > > > still ASP can deliver messages via SGP2.
> > > >
> > > > --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. *******
> > > >
> > >
> > > --
> > > 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

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



From mailnull@www1.ietf.org  Mon Jan  6 23:19: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 XAA23085
	for <sigtran-archive@odin.ietf.org>; Mon, 6 Jan 2003 23:19:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h074UV709298
	for sigtran-archive@odin.ietf.org; Mon, 6 Jan 2003 23:30:31 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h074TqJ09259;
	Mon, 6 Jan 2003 23:29:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h074RdJ09206
	for <sigtran@optimus.ietf.org>; Mon, 6 Jan 2003 23:27:39 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23039
	for <sigtran@ietf.org>; Mon, 6 Jan 2003 23:16:36 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:AeMnZpYXp4Db6AZW2IJkMx3P+WZDTxcE@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h074JoD05155;
	Mon, 6 Jan 2003 21:19:50 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h074Jo616728;
	Mon, 6 Jan 2003 21:19:50 -0700
Date: Mon, 6 Jan 2003 21:19:50 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
Message-ID: <20030106211950.F7546@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030102042412.A1077@openss7.org> <Pine.SOL.4.10.10301020550010.23295-100000@sun2594.ssd.usa.alcatel.com> <20030102045510.A2482@openss7.org> <3E1A53B1.DEEA8876@axes-mach01.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: <3E1A53B1.DEEA8876@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Tue, Jan 07, 2003 at 09:42:34AM +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>

Srini,

ksrinivas wrote:                                                                 (Tue, 07 Jan 2003 09:42:34)
> Brian,
> 
>   >> Not necessarily.  They SHOULD return the same RC value.
> 
>    If SGP1 and SGP2 do not return the same RC values for RK1, does the RK:RC
>    relation of 1:1 not voilated (Since the scope of RK1 is global i.e., SG,
>    the RC scope should aslo be for SG and return the same RC values).
> 
> --Srini
> 

Does it say somewhere in the RFC that the scope of the RK is the SG?

--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  Tue Jan  7 00:04: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 AAA23687
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 00:04:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h075Eip12015
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 00:14:44 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h075E8J12001;
	Tue, 7 Jan 2003 00:14:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h075BAJ11932
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 00:11:10 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23629
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 00:00:06 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0753HaN005348;
	Mon, 6 Jan 2003 23:03:18 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id JAA13506; Tue, 7 Jan 2003 09:31:16 -0500 (GMT)
Message-ID: <3E1A5F96.78E5EE12@axes-mach01.usa.alcatel.com>
Date: Tue, 07 Jan 2003 10:33:19 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
References: <20030102042412.A1077@openss7.org> <Pine.SOL.4.10.10301020550010.23295-100000@sun2594.ssd.usa.alcatel.com> <20030102045510.A2482@openss7.org> <3E1A53B1.DEEA8876@axes-mach01.usa.alcatel.com> <20030106211950.F7546@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

>> Does it say somewhere in the RFC that the scope of the RK is the SG?

I feel it is implied. This is because all the parameters of RK are global to a node(SG).

--Srini


"Brian F. G. Bidulock" wrote:

> Srini,
>
> ksrinivas wrote:                                                                 (Tue, 07 Jan 2003 09:42:34)
> > Brian,
> >
> >   >> Not necessarily.  They SHOULD return the same RC value.
> >
> >    If SGP1 and SGP2 do not return the same RC values for RK1, does the RK:RC
> >    relation of 1:1 not voilated (Since the scope of RK1 is global i.e., SG,
> >    the RC scope should aslo be for SG and return the same RC values).
> >
> > --Srini
> >
>
> Does it say somewhere in the RFC that the scope of the RK is the SG?
>
> --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  Tue Jan  7 01:05:15 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 BAA24426
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 01:05:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h076Foe15131
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 01:15:50 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h076FHJ15107;
	Tue, 7 Jan 2003 01:15:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h076ABJ14950
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 01:10:11 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24328
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 00:59:04 -0500 (EST)
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFA07B4C59.4A8BE5EA-ONC2256CA7.00200152@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Tue, 7 Jan 2003 07:58:57 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/07/2003
 07:59:01 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>


Srini,




>Brian,
>
>>> Does it say somewhere in the RFC that the scope of the RK is the SG?
>
>I feel it is implied. This is because all the parameters of RK are global
to a node(SG).
[TOLGA] Why do you get this impression? The peers in IP domain are SGPs and
ASPs and furthermore RK defines the traffic range served by ASP. If what
you mean is that because the range ASP serves is the same for all SGPs in a
SG, similarly one could argue, it will be also the same for all SGPs in the
network, even if they are not part of a SG. IMO, the key point is, who the
peers in the model are, and they are SGP and ASP.
>
>--Srini


"Brian F. G. Bidulock" wrote:

> Srini,
>
> ksrinivas wrote:
(Tue, 07 Jan 2003 09:42:34)
> > Brian,
> >
> >   >> Not necessarily.  They SHOULD return the same RC value.
> >
> >    If SGP1 and SGP2 do not return the same RC values for RK1, does the
RK:RC
> >    relation of 1:1 not voilated (Since the scope of RK1 is global i.e.,
SG,
> >    the RC scope should aslo be for SG and return the same RC values).
> >
> > --Srini
> >
>
> Does it say somewhere in the RFC that the scope of the RK is the SG?
>
> --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 mailnull@www1.ietf.org  Tue Jan  7 01:21: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 BAA24725
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 01:21:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h076VZ115586
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 01:31:35 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h076UnJ15555;
	Tue, 7 Jan 2003 01:30:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h076QuJ15461
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 01:26:56 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24682
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 01:15:49 -0500 (EST)
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFDB166B14.968F2540-ONC2256CA7.002176D2@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Tue, 7 Jan 2003 08:15:43 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/07/2003
 08:15:46 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>


Jo,

I would think, one of the reasons is, for separate ssn values, one might
have different applications whereas for different CIC values, it is still
the same call control. So, it seems to me loadsharing(instead of defining
separate RKs) for ISUP is a satisfactory solution.

          Tolga




Can someone tell me why as a user of MTP3, SCCP would need
SUA to backhaul SCCP services, but ISUP would not need
a UA function, e.g., ISUA to backhaul its services, and
rather uses M3UA to trasfer its services?

Joe

> -----Original Message-----
> From: James Doss [mailto:JDoss@verisign.com]
> Sent: Friday, January 03, 2003 6:06 PM
> To: 'bidulock@openss7.org'; Wung, Joseph
> Cc: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA distributing ISUP group messages
>
>
> Hi Joseph/Brian,
> I was thinking IETF has a separate RFC for ISUP.
> Is it not a good idea to start one. That will help to reduce the
> complexities in the M3UA.
> So that the ISUP and SCCP support can be seperated.
>
> James Doss
> Verisign
>
>
>
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Friday, January 03, 2003 5:06 PM
> To: Wung, Joseph
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] M3UA distributing ISUP group messages
>
>
> Joseph,
>
> I offerred to write one several times.  Nobody took me up
> on my offer.
>
> --brian
>
> Wung, Joseph wrote:                      (Fri, 03 Jan 2003 11:35:13)
> > Brian,
> >
> > Is there ISUA anywhere?
> >
> > Joe
> >
> > > You will need to describe all that M3UA lacks in support
> > > of CIC routing.  Once you are finished that exercise you
> > > will have ISUA.  (As mentioned on the original thread
> > > from July 2001.)
> > >
> > > --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
>
_______________________________________________
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  Tue Jan  7 02:34:52 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 CAA05949
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 02:34:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h077jQd31048
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 02:45:26 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h077irJ31014;
	Tue, 7 Jan 2003 02:44:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h077dMJ30764
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 02:39:22 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05847
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 02:28:13 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h077VDOZ005732;
	Tue, 7 Jan 2003 01:31:14 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id LAA17267; Tue, 7 Jan 2003 11:58:35 -0500 (GMT)
Message-ID: <3E1A821F.223CB53@axes-mach01.usa.alcatel.com>
Date: Tue, 07 Jan 2003 13:00:39 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
References: <20021223063159.A8878@openss7.org> <Pine.SOL.4.10.10301020445160.23295-100000@sun2594.ssd.usa.alcatel.com> <20030102042412.A1077@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

      Can you please tell me what could be the traffic handling mode of AS in
this scenario (for the figure below i.e., in the forwarded mail)?.

--Srini

"Brian F. G. Bidulock" wrote:

> Samuel,
>
> Yes, all the SS7 UAs support this.  The ASP registers once each with SGP1
> and SGP2.
>
> --brian
>
> Samuel Dur D. Jeyaseelan wrote:                  (Thu, 02 Jan 2003 05:08:41)
> >
> > Hi,
> >
> >  Suppose an AS has single ASP and wants to connect to SGP1
> > and SGP2 for the same RK1.
> >
> >
> > +---------+                                 +-----+
> > |+------+ |          RK1      SCTP1         | ASP |
> > || SGP1 |-|---------------------------------+-----+
> > |+------+ |                                    |
> > |         |                                    |
> > |+------+ |          RK1      SCTP2            |
> > || SGP2 |-|------------------------------------+
> > |+------+ |
> > +---------+
> >
> > Does REG procedures at SGP allow this kind of scenario?
> >
> > This kind of scenario may be required in case SGP1 goes down
> > still ASP can deliver messages via SGP2.
> >
> > --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. *******
> >
>
> --
> 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 mailnull@www1.ietf.org  Tue Jan  7 03:11: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 DAA06616
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 03:11:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h078Ldo00660
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 03:21:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h078L2J00640;
	Tue, 7 Jan 2003 03:21:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h078IBJ00486
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 03:18:11 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06574
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 03:07:03 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:alEjMBUGrBJAIpzR1Ck6hJm9dg0SCvK2@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h078AHD08189;
	Tue, 7 Jan 2003 01:10:17 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h078AHA21159;
	Tue, 7 Jan 2003 01:10:17 -0700
Date: Tue, 7 Jan 2003 01:10:16 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
Message-ID: <20030107011016.G7546@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	"Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20021223063159.A8878@openss7.org> <Pine.SOL.4.10.10301020445160.23295-100000@sun2594.ssd.usa.alcatel.com> <20030102042412.A1077@openss7.org> <3E1A821F.223CB53@axes-mach01.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: <3E1A821F.223CB53@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Tue, Jan 07, 2003 at 01:00:39PM +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>

Srini,

It doesn't matter what the traffic mode type is,
because there is only one ASP.  The TMT could be
Override, Load-share or Broadcast.

--brian


ksrinivas wrote:                                                                 (Tue, 07 Jan 2003 13:00:39)
> Brian,
> 
>       Can you please tell me what could be the traffic handling mode of AS in
> this scenario (for the figure below i.e., in the forwarded mail)?.
> 
> --Srini
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Samuel,
> >
> > Yes, all the SS7 UAs support this.  The ASP registers once each with SGP1
> > and SGP2.
> >
> > --brian
> >
> > Samuel Dur D. Jeyaseelan wrote:                  (Thu, 02 Jan 2003 05:08:41)
> > >
> > > Hi,
> > >
> > >  Suppose an AS has single ASP and wants to connect to SGP1
> > > and SGP2 for the same RK1.
> > >
> > >
> > > +---------+                                 +-----+
> > > |+------+ |          RK1      SCTP1         | ASP |
> > > || SGP1 |-|---------------------------------+-----+
> > > |+------+ |                                    |
> > > |         |                                    |
> > > |+------+ |          RK1      SCTP2            |
> > > || SGP2 |-|------------------------------------+
> > > |+------+ |
> > > +---------+
> > >
> > > Does REG procedures at SGP allow this kind of scenario?
> > >
> > > This kind of scenario may be required in case SGP1 goes down
> > > still ASP can deliver messages via SGP2.
> > >
> > > --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. *******
> > >
> >
> > --
> > 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 mailnull@www1.ietf.org  Tue Jan  7 03:52: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 DAA07358
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 03:52:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0793L803424
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 04:03:21 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0792ZJ03346;
	Tue, 7 Jan 2003 04:02:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h078xmJ02844
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 03:59:48 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07258
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 03:48:39 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h078pjBE016666;
	Tue, 7 Jan 2003 02:51:47 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id NAA18872; Tue, 7 Jan 2003 13:19:24 -0500 (GMT)
Message-ID: <3E1A94D4.2462E62F@axes-mach01.usa.alcatel.com>
Date: Tue, 07 Jan 2003 14:20:28 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
References: <20021223063159.A8878@openss7.org> <Pine.SOL.4.10.10301020445160.23295-100000@sun2594.ssd.usa.alcatel.com> <20030102042412.A1077@openss7.org> <3E1A821F.223CB53@axes-mach01.usa.alcatel.com> <20030107011016.G7546@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

    Further, Can you please clarify the following points:

1. Does ASP1 sends ASP UP message to both the SGPs?.
2. If point 1(above) is true, in that case, what would be the ASP ID?. Should they pass the same ASPID or
different ASPID?.
3. If point 2(above) is true for same ASPID, now suppose, if ASP1 is Active w.r.t SGP1 with TMT as Override and
ASP1 wishes to override the traffic through SGP2 by sending ASP Active to SGP2, What ASPID does the Notify
(alternate ASP Active) from SGP1 contain?.

--Srini


"Brian F. G. Bidulock" wrote:

> Srini,
>
> It doesn't matter what the traffic mode type is,
> because there is only one ASP.  The TMT could be
> Override, Load-share or Broadcast.
>
> --brian
>
> ksrinivas wrote:                                                                 (Tue, 07 Jan 2003 13:00:39)
> > Brian,
> >
> >       Can you please tell me what could be the traffic handling mode of AS in
> > this scenario (for the figure below i.e., in the forwarded mail)?.
> >
> > --Srini
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > Samuel,
> > >
> > > Yes, all the SS7 UAs support this.  The ASP registers once each with SGP1
> > > and SGP2.
> > >
> > > --brian
> > >
> > > Samuel Dur D. Jeyaseelan wrote:                  (Thu, 02 Jan 2003 05:08:41)
> > > >
> > > > Hi,
> > > >
> > > >  Suppose an AS has single ASP and wants to connect to SGP1
> > > > and SGP2 for the same RK1.
> > > >
> > > >
> > > > +---------+                                 +-----+
> > > > |+------+ |          RK1      SCTP1         | ASP |
> > > > || SGP1 |-|---------------------------------+-----+
> > > > |+------+ |                                    |
> > > > |         |                                    |
> > > > |+------+ |          RK1      SCTP2            |
> > > > || SGP2 |-|------------------------------------+
> > > > |+------+ |
> > > > +---------+
> > > >
> > > > Does REG procedures at SGP allow this kind of scenario?
> > > >
> > > > This kind of scenario may be required in case SGP1 goes down
> > > > still ASP can deliver messages via SGP2.
> > > >
> > > > --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. *******
> > > >
> > >
> > > --
> > > 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 mailnull@www1.ietf.org  Tue Jan  7 04:06:19 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 EAA07531
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 04:06:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h079GuU04560
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 04:16:56 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h079G6J04534;
	Tue, 7 Jan 2003 04:16:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h079D4J04454
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 04:13:04 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07513
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 04:01:55 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:7yrT53hYW6TNl4X4oy1RBvsVlLpxhw5+@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0795AD08906;
	Tue, 7 Jan 2003 02:05:10 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h07959Q22217;
	Tue, 7 Jan 2003 02:05:09 -0700
Date: Tue, 7 Jan 2003 02:05:09 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
Message-ID: <20030107020509.A21194@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	"Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20021223063159.A8878@openss7.org> <Pine.SOL.4.10.10301020445160.23295-100000@sun2594.ssd.usa.alcatel.com> <20030102042412.A1077@openss7.org> <3E1A821F.223CB53@axes-mach01.usa.alcatel.com> <20030107011016.G7546@openss7.org> <3E1A94D4.2462E62F@axes-mach01.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: <3E1A94D4.2462E62F@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Tue, Jan 07, 2003 at 02:20:28PM +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>

Srini,

ksrinivas wrote:                                   (Tue, 07 Jan 2003 14:20:28)
> Brian,
> 
>     Further, Can you please clarify the following points:
> 
> 1. Does ASP1 sends ASP UP message to both the SGPs?.

Yes, if the ASP wants to be viewed by each SGP as being in the ASP-UP
state it will have to send ASPUP to each SGP.

> 2. If point 1(above) is true, in that case, what would be the ASP ID?.
> Should they pass the same ASPID or different ASPID?.

If the ASP sends ASP Identifier in the ASPUP message, the identifier
must uniquely identify the ASP to the SGP.  This does not mean that it
has to be the same value, however, IMO it would be foolish not to send
the same ASP Identifier values to both SGPs (because then the ASP would
have to keep track of a separate ASP Id for each SGP even though it
accomplishes nothing).

Regardless of whether the ASP Id values are the same or different, the
SGP should store the value and use it in subsequent NTFY messages when
required.

> 3. If point 2(above) is true for same ASPID, now suppose, if ASP1 is Active
> w.r.t SGP1 with TMT as Override and ASP1 wishes to override the traffic
> through SGP2 by sending ASP Active to SGP2, What ASPID does the Notify
> (alternate ASP Active) from SGP1 contain?.

I think that you misunderstand traffic modes: an ASP cannot override
itself to an SGP for an Application Server.

--brian

> > > > >
> > > > > +---------+                                 +-----+
> > > > > |+------+ |          RK1      SCTP1         | ASP |
> > > > > || SGP1 |-|---------------------------------+-----+
> > > > > |+------+ |                                    |
> > > > > |         |                                    |
> > > > > |+------+ |          RK1      SCTP2            |
> > > > > || SGP2 |-|------------------------------------+
> > > > > |+------+ |
> > > > > +---------+
> > > > >

-- 
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 Jan  7 04:20: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 EAA07656
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 04:20:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h079UfX05054
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 04:30:41 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h079UBJ05029;
	Tue, 7 Jan 2003 04:30:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h079R5J04946
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 04:27:05 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07619
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 04:15:56 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h079J6aN022280;
	Tue, 7 Jan 2003 03:19:08 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id NAA19715; Tue, 7 Jan 2003 13:47:16 -0500 (GMT)
Message-ID: <3E1A9B5D.76FE1B94@axes-mach01.usa.alcatel.com>
Date: Tue, 07 Jan 2003 14:48:21 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
References: <20021223063159.A8878@openss7.org> <Pine.SOL.4.10.10301020445160.23295-100000@sun2594.ssd.usa.alcatel.com> <20030102042412.A1077@openss7.org> <3E1A821F.223CB53@axes-mach01.usa.alcatel.com> <20030107011016.G7546@openss7.org> <3E1A94D4.2462E62F@axes-mach01.usa.alcatel.com> <20030107020509.A21194@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

"Brian F. G. Bidulock" wrote:

> Srini,
>
> ksrinivas wrote:                                   (Tue, 07 Jan 2003 14:20:28)
> > Brian,
> >
> >     Further, Can you please clarify the following points:
> >
> > 1. Does ASP1 sends ASP UP message to both the SGPs?.
>
> Yes, if the ASP wants to be viewed by each SGP as being in the ASP-UP
> state it will have to send ASPUP to each SGP.
>
> > 2. If point 1(above) is true, in that case, what would be the ASP ID?.
> > Should they pass the same ASPID or different ASPID?.
>
> If the ASP sends ASP Identifier in the ASPUP message, the identifier
> must uniquely identify the ASP to the SGP.  This does not mean that it
> has to be the same value, however, IMO it would be foolish not to send
> the same ASP Identifier values to both SGPs (because then the ASP would
> have to keep track of a separate ASP Id for each SGP even though it
> accomplishes nothing).
>
> Regardless of whether the ASP Id values are the same or different, the
> SGP should store the value and use it in subsequent NTFY messages when
> required.
>
> > 3. If point 2(above) is true for same ASPID, now suppose, if ASP1 is Active
> > w.r.t SGP1 with TMT as Override and ASP1 wishes to override the traffic
> > through SGP2 by sending ASP Active to SGP2, What ASPID does the Notify
> > (alternate ASP Active) from SGP1 contain?.
>
> I think that you misunderstand traffic modes: an ASP cannot override
> itself to an SGP for an Application Server.
>

Due to some implementation dependent reason or problem, the LM would have
requested ASP1 to override. Because of this, ASP1 can still send ASP Active to
SGP2. So if the ASP1 has sent the same ASPID in both the ASP UP messages, should
the ASP1 be able to support this situation with the same ASPID in Notify message?.

--Srini

>
> --brian
>
> > > > > >
> > > > > > +---------+                                 +-----+
> > > > > > |+------+ |          RK1      SCTP1         | ASP |
> > > > > > || SGP1 |-|---------------------------------+-----+
> > > > > > |+------+ |                                    |
> > > > > > |         |                                    |
> > > > > > |+------+ |          RK1      SCTP2            |
> > > > > > || SGP2 |-|------------------------------------+
> > > > > > |+------+ |
> > > > > > +---------+
> > > > > >
>
> --
> 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 Jan  7 04:38: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 EAA07918
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 04:38:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h079n1b06405
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 04:49:01 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h079mHJ06363;
	Tue, 7 Jan 2003 04:48:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h079jMJ06276
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 04:45:22 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07863
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 04:34:12 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:aUEMYaBIeR5oJdTCpVTL7SWtXLaxf6J4@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h079bQD09331;
	Tue, 7 Jan 2003 02:37:26 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h079bPR22977;
	Tue, 7 Jan 2003 02:37:25 -0700
Date: Tue, 7 Jan 2003 02:37:25 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
Message-ID: <20030107023725.B21194@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	"Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20021223063159.A8878@openss7.org> <Pine.SOL.4.10.10301020445160.23295-100000@sun2594.ssd.usa.alcatel.com> <20030102042412.A1077@openss7.org> <3E1A821F.223CB53@axes-mach01.usa.alcatel.com> <20030107011016.G7546@openss7.org> <3E1A94D4.2462E62F@axes-mach01.usa.alcatel.com> <20030107020509.A21194@openss7.org> <3E1A9B5D.76FE1B94@axes-mach01.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: <3E1A9B5D.76FE1B94@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Tue, Jan 07, 2003 at 02:48:21PM +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>

ksrinivas,

ksrinivas wrote:                                                                 (Tue, 07 Jan 2003 14:48:21)
> Brian,
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Srini,
> >
> > ksrinivas wrote:                                   (Tue, 07 Jan 2003 14:20:28)
> > > Brian,
> > >
> > >     Further, Can you please clarify the following points:
> > >
> > > 1. Does ASP1 sends ASP UP message to both the SGPs?.
> >
> > Yes, if the ASP wants to be viewed by each SGP as being in the ASP-UP
> > state it will have to send ASPUP to each SGP.
> >
> > > 2. If point 1(above) is true, in that case, what would be the ASP ID?.
> > > Should they pass the same ASPID or different ASPID?.
> >
> > If the ASP sends ASP Identifier in the ASPUP message, the identifier
> > must uniquely identify the ASP to the SGP.  This does not mean that it
> > has to be the same value, however, IMO it would be foolish not to send
> > the same ASP Identifier values to both SGPs (because then the ASP would
> > have to keep track of a separate ASP Id for each SGP even though it
> > accomplishes nothing).
> >
> > Regardless of whether the ASP Id values are the same or different, the
> > SGP should store the value and use it in subsequent NTFY messages when
> > required.
> >
> > > 3. If point 2(above) is true for same ASPID, now suppose, if ASP1 is Active
> > > w.r.t SGP1 with TMT as Override and ASP1 wishes to override the traffic
> > > through SGP2 by sending ASP Active to SGP2, What ASPID does the Notify
> > > (alternate ASP Active) from SGP1 contain?.
> >
> > I think that you misunderstand traffic modes: an ASP cannot override
> > itself to an SGP for an Application Server.
> >
> 
> Due to some implementation dependent reason or problem, the LM would have
> requested ASP1 to override. Because of this, ASP1 can still send ASP Active to
> SGP2.

I still don't think you understand.  If ASP1 has send ASPAC to SGP2 before,
then SGP2 simply responds with ASPAC ACK.  If it has not, SGP2 still responds
with ASPAC ACK.  Nothing is overridden.

> So if the ASP1 has sent the same ASPID in both the ASP UP messages, should
> the ASP1 be able to support this situation with the same ASPID in Notify
> message?.

I'm afraid you will have to draw the message flow.  See the example
in section 5.2.2 of RFC 3332.  It takes a different ASP (ASP2 in the
example from section 5.2.2) to override an active ASP (ASP1 in the
example from section 5.2.2).

--brian

> > > > > > >
> > > > > > > +---------+                                 +-----+
> > > > > > > |+------+ |          RK1      SCTP1         | ASP |
> > > > > > > || SGP1 |-|---------------------------------+-----+
> > > > > > > |+------+ |                                    |
> > > > > > > |         |                                    |
> > > > > > > |+------+ |          RK1      SCTP2            |
> > > > > > > || SGP2 |-|------------------------------------+
> > > > > > > |+------+ |
> > > > > > > +---------+
> > > > > > >
> >
> > --
> > 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 mailnull@www1.ietf.org  Tue Jan  7 06: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 GAA10348
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 06:50:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h07C1Ij13974
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 07:01:18 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07C0SJ13889;
	Tue, 7 Jan 2003 07:00:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07BvLJ13773
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 06:57:21 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10187
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 06:46:08 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h07BnJOZ001145;
	Tue, 7 Jan 2003 05:49:21 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id QAA23317; Tue, 7 Jan 2003 16:17:42 -0500 (GMT)
Message-ID: <3E1ABEA0.57FA09F7@axes-mach01.usa.alcatel.com>
Date: Tue, 07 Jan 2003 17:18:48 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
References: <20021223063159.A8878@openss7.org> <Pine.SOL.4.10.10301020445160.23295-100000@sun2594.ssd.usa.alcatel.com> <20030102042412.A1077@openss7.org> <3E1A821F.223CB53@axes-mach01.usa.alcatel.com> <20030107011016.G7546@openss7.org> <3E1A94D4.2462E62F@axes-mach01.usa.alcatel.com> <20030107020509.A21194@openss7.org> <3E1A9B5D.76FE1B94@axes-mach01.usa.alcatel.com> <20030107023725.B21194@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

>>>I still don't think you understand.  If ASP1 has send ASPAC to SGP2 before,
>>>then SGP2 simply responds with ASPAC ACK.  If it has not, SGP2 still responds
>>>with ASPAC ACK.  Nothing is overridden.

For the Scenario under discussion, let us assume that ASP1 has sent the following messages to SGP1
ASPUP message with ASPID 1,
REG REQ message for RK1 and
ASP ACTIVE message with TMT as Override

and

that ASP1 has also sent the following messages to SGP2
ASPUP message with ASPID 1,
REG REQ message for RK1

Now, due to some implementation dependent reason or problem, the LM would request ASP1 to send ASP ACTIVE with
TMT as Override to SGP2.

As you mentioned, SGP2 shall also reply with ASP ACTIVE Ack to ASP1.

My question is, since the TMT is Override,  Does the SGP1 send a Notify message to ASP1 for alternate ASP
Active?.
If so, Does it send the same ASPID 1 in the Notify message?.

If ASPID 1 is sent in the Notify message to ASP1, Should the ASP1 be implemented(to take care such a situation)
to receive the same ASPID 1 without misbehaving.

--Srini



"Brian F. G. Bidulock" wrote:

> ksrinivas,
>
> ksrinivas wrote:                                                                 (Tue, 07 Jan 2003 14:48:21)
> > Brian,
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > Srini,
> > >
> > > ksrinivas wrote:                                   (Tue, 07 Jan 2003 14:20:28)
> > > > Brian,
> > > >
> > > >     Further, Can you please clarify the following points:
> > > >
> > > > 1. Does ASP1 sends ASP UP message to both the SGPs?.
> > >
> > > Yes, if the ASP wants to be viewed by each SGP as being in the ASP-UP
> > > state it will have to send ASPUP to each SGP.
> > >
> > > > 2. If point 1(above) is true, in that case, what would be the ASP ID?.
> > > > Should they pass the same ASPID or different ASPID?.
> > >
> > > If the ASP sends ASP Identifier in the ASPUP message, the identifier
> > > must uniquely identify the ASP to the SGP.  This does not mean that it
> > > has to be the same value, however, IMO it would be foolish not to send
> > > the same ASP Identifier values to both SGPs (because then the ASP would
> > > have to keep track of a separate ASP Id for each SGP even though it
> > > accomplishes nothing).
> > >
> > > Regardless of whether the ASP Id values are the same or different, the
> > > SGP should store the value and use it in subsequent NTFY messages when
> > > required.
> > >
> > > > 3. If point 2(above) is true for same ASPID, now suppose, if ASP1 is Active
> > > > w.r.t SGP1 with TMT as Override and ASP1 wishes to override the traffic
> > > > through SGP2 by sending ASP Active to SGP2, What ASPID does the Notify
> > > > (alternate ASP Active) from SGP1 contain?.
> > >
> > > I think that you misunderstand traffic modes: an ASP cannot override
> > > itself to an SGP for an Application Server.
> > >
> >
> > Due to some implementation dependent reason or problem, the LM would have
> > requested ASP1 to override. Because of this, ASP1 can still send ASP Active to
> > SGP2.
>
> I still don't think you understand.  If ASP1 has send ASPAC to SGP2 before,
> then SGP2 simply responds with ASPAC ACK.  If it has not, SGP2 still responds
> with ASPAC ACK.  Nothing is overridden.
>
> > So if the ASP1 has sent the same ASPID in both the ASP UP messages, should
> > the ASP1 be able to support this situation with the same ASPID in Notify
> > message?.
>
> I'm afraid you will have to draw the message flow.  See the example
> in section 5.2.2 of RFC 3332.  It takes a different ASP (ASP2 in the
> example from section 5.2.2) to override an active ASP (ASP1 in the
> example from section 5.2.2).
>
> --brian
>
> > > > > > > >
> > > > > > > > +---------+                                 +-----+
> > > > > > > > |+------+ |          RK1      SCTP1         | ASP |
> > > > > > > > || SGP1 |-|---------------------------------+-----+
> > > > > > > > |+------+ |                                    |
> > > > > > > > |         |                                    |
> > > > > > > > |+------+ |          RK1      SCTP2            |
> > > > > > > > || SGP2 |-|------------------------------------+
> > > > > > > > |+------+ |
> > > > > > > > +---------+
> > > > > > > >
> > >
> > > --
> > > 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

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



From mailnull@www1.ietf.org  Tue Jan  7 08:08:02 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 IAA11618
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 08:08:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h07DIk118649
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 08:18:46 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07DIOJ18620;
	Tue, 7 Jan 2003 08:18:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07DFoJ18522
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 08:15:50 -0500
Received: from bifrost.spider.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA11548
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 08:04:30 -0500 (EST)
Received: from no.name.available by bifrost.spider.com
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 7 Jan 2003 13:07:47 UT
Received: from heimdall-dmz.spider.com (batistuta.spider.com [212.240.99.13])
	by caly80.spider.com (Postfix) with SMTP id D53476F5C
	for <sigtran@ietf.org>; Tue,  7 Jan 2003 13:05:53 +0000 (GMT)
Received: from batistuta.spider.com by heimdall-dmz.spider.com
          via smtpd (for [172.16.254.22]) with SMTP; 7 Jan 2003 13:07:46 UT
Received: from spider.com (caleyipa.spider.com [212.240.99.103]) by batistuta.spider.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 4QSH1SPM; Tue, 7 Jan 2003 13:02:51 -0000
Message-ID: <3E1AD122.E796AAB1@spider.com>
Date: Tue, 07 Jan 2003 13:07:46 +0000
From: Stuart Alexander <stuarta@spider.com>
Organization: Spider Software Ltd.
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
References: <MAILTONEWS1030107075508.94679@rupert.spider.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

Tolga,

What happens when there is mixed traffic on a signalling link?
For example, an SSP (ASP) may generate database queries (SCCP) 
which need to be carried out before routing the call over ISUP.
I wouldn't have thought having both SUA and M3UA in the SG and
ASP made much sense.

//Stuart



TOLGA ASVEREN wrote:
> 
> Jo,
> 
> I would think, one of the reasons is, for separate ssn values, one might
> have different applications whereas for different CIC values, it is still
> the same call control. So, it seems to me loadsharing(instead of defining
> separate RKs) for ISUP is a satisfactory solution.
> 
>           Tolga
> 
> Can someone tell me why as a user of MTP3, SCCP would need
> SUA to backhaul SCCP services, but ISUP would not need
> a UA function, e.g., ISUA to backhaul its services, and
> rather uses M3UA to trasfer its services?
> 
> Joe
> 
> > -----Original Message-----
> > From: James Doss [mailto:JDoss@verisign.com]
> > Sent: Friday, January 03, 2003 6:06 PM
> > To: 'bidulock@openss7.org'; Wung, Joseph
> > Cc: sigtran@ietf.org
> > Subject: RE: [Sigtran] M3UA distributing ISUP group messages
> >
> >
> > Hi Joseph/Brian,
> > I was thinking IETF has a separate RFC for ISUP.
> > Is it not a good idea to start one. That will help to reduce the
> > complexities in the M3UA.
> > So that the ISUP and SCCP support can be seperated.
> >
> > James Doss
> > Verisign
> >
> >
> >
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Friday, January 03, 2003 5:06 PM
> > To: Wung, Joseph
> > Cc: sigtran@ietf.org
> > Subject: Re: [Sigtran] M3UA distributing ISUP group messages
> >
> >
> > Joseph,
> >
> > I offerred to write one several times.  Nobody took me up
> > on my offer.
> >
> > --brian
> >
> > Wung, Joseph wrote:                      (Fri, 03 Jan 2003 11:35:13)
> > > Brian,
> > >
> > > Is there ISUA anywhere?
> > >
> > > Joe
> > >
> > > > You will need to describe all that M3UA lacks in support
> > > > of CIC routing.  Once you are finished that exercise you
> > > > will have ISUA.  (As mentioned on the original thread
> > > > from July 2001.)
> > > >
> > > > --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
> >
> _______________________________________________
> 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

-- 
Stuart Alexander
Spider Software Ltd.             tel:    +44 (0)131 475 7036
8 John's Place, Leith,           email:  stuarta@spider.com
Edinburgh, EH6 7EL, UK           web:    www.spider.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Tue Jan  7 09:05: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 JAA14380
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 09:05:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h07EGYk22694
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 09:16:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07EG8J22663;
	Tue, 7 Jan 2003 09:16:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07EDGJ22515
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 09:13:16 -0500
Received: from web12801.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA14260
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 09:02:02 -0500 (EST)
Message-ID: <20030107140516.21866.qmail@web12801.mail.yahoo.com>
Received: from [217.31.225.14] by web12801.mail.yahoo.com via HTTP; Tue, 07 Jan 2003 06:05:16 PST
Date: Tue, 7 Jan 2003 06:05:16 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
In-Reply-To: <3E1AD122.E796AAB1@spider.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>

Stuart,
--- Stuart Alexander <stuarta@spider.com> wrote:
> Tolga,
> 
> What happens when there is mixed traffic on a
> signalling link?
> For example, an SSP (ASP) may generate database
> queries (SCCP) 
> which need to be carried out before routing the call
> over ISUP.
> I wouldn't have thought having both SUA and M3UA in
> the SG and
> ASP made much sense.
[TOLGA] For the scenario you mention I also would not
use both SUA and M3UA. That SUA is usefull for some
scenarios does not mean that it should be used
whenever possible. The point in my original messege
was that different applications are addressable by SSN
but not with CIC.
> 
> //Stuart
> 
> 
> 
> TOLGA ASVEREN wrote:
> > 
> > Jo,
> > 
> > I would think, one of the reasons is, for separate
> ssn values, one might
> > have different applications whereas for different
> CIC values, it is still
> > the same call control. So, it seems to me
> loadsharing(instead of defining
> > separate RKs) for ISUP is a satisfactory solution.
> > 
> >           Tolga
> > 
> > Can someone tell me why as a user of MTP3, SCCP
> would need
> > SUA to backhaul SCCP services, but ISUP would not
> need
> > a UA function, e.g., ISUA to backhaul its
> services, and
> > rather uses M3UA to trasfer its services?
> > 
> > Joe
> > 
> > > -----Original Message-----
> > > From: James Doss [mailto:JDoss@verisign.com]
> > > Sent: Friday, January 03, 2003 6:06 PM
> > > To: 'bidulock@openss7.org'; Wung, Joseph
> > > Cc: sigtran@ietf.org
> > > Subject: RE: [Sigtran] M3UA distributing ISUP
> group messages
> > >
> > >
> > > Hi Joseph/Brian,
> > > I was thinking IETF has a separate RFC for ISUP.
> > > Is it not a good idea to start one. That will
> help to reduce the
> > > complexities in the M3UA.
> > > So that the ISUP and SCCP support can be
> seperated.
> > >
> > > James Doss
> > > Verisign
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock
> [mailto:bidulock@openss7.org]
> > > Sent: Friday, January 03, 2003 5:06 PM
> > > To: Wung, Joseph
> > > Cc: sigtran@ietf.org
> > > Subject: Re: [Sigtran] M3UA distributing ISUP
> group messages
> > >
> > >
> > > Joseph,
> > >
> > > I offerred to write one several times.  Nobody
> took me up
> > > on my offer.
> > >
> > > --brian
> > >
> > > Wung, Joseph wrote:                      (Fri,
> 03 Jan 2003 11:35:13)
> > > > Brian,
> > > >
> > > > Is there ISUA anywhere?
> > > >
> > > > Joe
> > > >
> > > > > You will need to describe all that M3UA
> lacks in support
> > > > > of CIC routing.  Once you are finished that
> exercise you
> > > > > will have ISUA.  (As mentioned on the
> original thread
> > > > > from July 2001.)
> > > > >
> > > > > --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
> > >
> > _______________________________________________
> > 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
> 
> -- 
> Stuart Alexander
> Spider Software Ltd.             tel:    +44 (0)131
> 475 7036
> 8 John's Place, Leith,           email: 
> stuarta@spider.com
> Edinburgh, EH6 7EL, UK           web:   
> www.spider.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Tue Jan  7 09:49: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 JAA15308
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 09:49:13 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h07ExwB25641
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 09:59:58 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07ExOJ25619;
	Tue, 7 Jan 2003 09:59:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07EuqJ25530
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 09:56:52 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15237
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 09:45:36 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:IZ+XcjiVtYTAnLomt3TD4RSD6W7CVvrP@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h07EmoD13641;
	Tue, 7 Jan 2003 07:48:50 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h07Emnk30318;
	Tue, 7 Jan 2003 07:48:49 -0700
Date: Tue, 7 Jan 2003 07:48:49 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030107074849.C21194@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <3E1AD122.E796AAB1@spider.com> <20030107140516.21866.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: <20030107140516.21866.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Tue, Jan 07, 2003 at 06:05:16AM -0800
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, 07 Jan 2003 06:05:16)
> Stuart,
> --- Stuart Alexander <stuarta@spider.com> wrote:
> > Tolga,
> > 
> > What happens when there is mixed traffic on a signalling link?  For
> > example, an SSP (ASP) may generate database queries (SCCP) which need to
> > be carried out before routing the call over ISUP.  I wouldn't have thought
> > having both SUA and M3UA in the SG and ASP made much sense.
> [TOLGA] For the scenario you mention I also would not use both SUA and M3UA.
> That SUA is usefull for some scenarios does not mean that it should be used
> whenever possible. The point in my original messege was that different
> applications are addressable by SSN but not with CIC.

Different applications are addressable by CIC.  CICs are organized into trunk
groups.  Trunk groups may have different applications running against them.
Call Control is not necessarily one great glob of an application.

--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  Tue Jan  7 09:54:23 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 JAA15664
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 09:54:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h07F58B25910
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 10:05:08 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07F4qJ25864;
	Tue, 7 Jan 2003 10:04:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07F2GJ25777
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 10:02:16 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15349
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 09:51:00 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:+4qpTyQYcnNCpXQC8Q3wiU6cuwaPbFwr@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h07EsFD13716;
	Tue, 7 Jan 2003 07:54:15 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h07EsER30450;
	Tue, 7 Jan 2003 07:54:14 -0700
Date: Tue, 7 Jan 2003 07:54:14 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
Message-ID: <20030107075414.D21194@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	"Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20021223063159.A8878@openss7.org> <Pine.SOL.4.10.10301020445160.23295-100000@sun2594.ssd.usa.alcatel.com> <20030102042412.A1077@openss7.org> <3E1A821F.223CB53@axes-mach01.usa.alcatel.com> <20030107011016.G7546@openss7.org> <3E1A94D4.2462E62F@axes-mach01.usa.alcatel.com> <20030107020509.A21194@openss7.org> <3E1A9B5D.76FE1B94@axes-mach01.usa.alcatel.com> <20030107023725.B21194@openss7.org> <3E1ABEA0.57FA09F7@axes-mach01.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: <3E1ABEA0.57FA09F7@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Tue, Jan 07, 2003 at 05:18:48PM +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>

Srini,

ksrinivas wrote:                                                                 (Tue, 07 Jan 2003 17:18:48)
> Brian,
> 
> >>>I still don't think you understand.  If ASP1 has send ASPAC to SGP2 before,
> >>>then SGP2 simply responds with ASPAC ACK.  If it has not, SGP2 still responds
> >>>with ASPAC ACK.  Nothing is overridden.
> 
> For the Scenario under discussion, let us assume that ASP1 has sent the
> following messages to SGP1

> ASPUP message with ASPID 1,
> REG REQ message for RK1 and
> ASP ACTIVE message with TMT as Override
> 
> and
> 
> that ASP1 has also sent the following messages to SGP2
> ASPUP message with ASPID 1,
> REG REQ message for RK1
> 
> Now, due to some implementation dependent reason or problem, the LM would
> request ASP1 to send ASP ACTIVE with TMT as Override to SGP2.
> 
> As you mentioned, SGP2 shall also reply with ASP ACTIVE Ack to ASP1.
> 
> My question is, since the TMT is Override,  Does the SGP1 send a Notify
> message to ASP1 for alternate ASP Active?.

No, never.  This is the first ASP activating for the AS in SGP2.  It moves the
AS from the AS-INACTIVE state to the AS-ACTIVE state and sends ASPAC ACK and
NTFY("AS_Active") to ASP1.

Again, the traffic mode has nothing to do with it.  This is the first (and
only) ASP activating to SGP2.

--brian

> If so, Does it send the same ASPID 1 in the Notify message?.
> 
> If ASPID 1 is sent in the Notify message to ASP1, Should the ASP1 be
> implemented(to take care such a situation) to receive the same ASPID 1
> without misbehaving.
> 
> --Srini
> 

-- 
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 Jan  7 17:08: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 RAA00798
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 17:08:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h07MJis22620
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 17:19:44 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07MJ7J22596;
	Tue, 7 Jan 2003 17:19:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02DJYJ21455
	for <sigtran@optimus.ietf.org>; Thu, 2 Jan 2003 08:19:34 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04072
	for <sigtran@ietf.org>; Thu, 2 Jan 2003 08:10:46 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h02DDraN009691;
	Thu, 2 Jan 2003 07:13:56 -0600 (CST)
Received: from axsppc67 by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id RAA25968; Thu, 2 Jan 2003 17:42:51 -0500 (GMT)
Message-ID: <01f801c2b262$5cc79cc0$7501ff0a@axsppc67>
From: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
To: <bidulock@openss7.org>
Cc: <sigtran@ietf.org>
Subject: [Sigtran] [M3UA]1 AS and 1 ASP
Date: Thu, 2 Jan 2003 18:54:43 +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.50.4133.2400
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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

Brian,

In that case what is Routing Context from each SGP? Will it be same?
It has to be same because it is for the same AS and the scope of routing
context is per SG and not per SGP.
In that case SGP2 should return error for REG REQ of RK1 as RK1 for ASP is
already registered.

Thanks
Chak

----- Original Message -----
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: "Tolga Asveren" <tolga_asveren@yahoo.com>; <sigtran@ietf.org>
Sent: Thursday, January 02, 2003 4:54 PM
Subject: [Sigtran] Re: [M3UA]1 AS and 1 ASP


> Samuel,
>
> Yes, all the SS7 UAs support this.  The ASP registers once each with SGP1
> and SGP2.
>
> --brian
>
> Samuel Dur D. Jeyaseelan wrote:                  (Thu, 02 Jan 2003
05:08:41)
> >
> > Hi,
> >
> >  Suppose an AS has single ASP and wants to connect to SGP1
> > and SGP2 for the same RK1.
> >
> >
> > +---------+                                 +-----+
> > |+------+ |          RK1      SCTP1         | ASP |
> > || SGP1 |-|---------------------------------+-----+
> > |+------+ |                                    |
> > |         |                                    |
> > |+------+ |          RK1      SCTP2            |
> > || SGP2 |-|------------------------------------+
> > |+------+ |
> > +---------+
> >
> > Does REG procedures at SGP allow this kind of scenario?
> >
> > This kind of scenario may be required in case SGP1 goes down
> > still ASP can deliver messages via SGP2.
> >
> > --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.
*******
> >
>
> --
> 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 mailnull@www1.ietf.org  Tue Jan  7 17:12: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 RAA00868
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 17:12:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h07MNff22800
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 17:23:41 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07MN7J22766;
	Tue, 7 Jan 2003 17:23:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07AVDJ08478
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 05:31:13 -0500
Received: from bifrost.spider.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA08607
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 05:19:48 -0500 (EST)
Received: from no.name.available by bifrost.spider.com
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 7 Jan 2003 10:23:04 UT
Received: from heimdall-dmz.spider.com (batistuta.spider.com [212.240.99.13])
	by caly80.spider.com (Postfix) with SMTP id BF6F96F5C
	for <sigtran@ietf.org>; Tue,  7 Jan 2003 10:21:10 +0000 (GMT)
Received: from batistuta.spider.com by heimdall-dmz.spider.com
          via smtpd (for [172.16.254.22]) with SMTP; 7 Jan 2003 10:23:02 UT
Received: from spider.com (caleyipa.spider.com [212.240.99.103]) by batistuta.spider.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 4QSH1SK5; Tue, 7 Jan 2003 10:18:07 -0000
Message-ID: <3E1AAA86.6AE639E9@spider.com>
Date: Tue, 07 Jan 2003 10:23:02 +0000
From: Stuart Alexander <stuarta@spider.com>
Organization: Spider Software Ltd.
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
References: <MAILTONEWS1030107075508.94679@rupert.spider.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

Tolga,

What happens when there is mixed traffic on a signalling link?
For example, an SSP (ASP) may generate database queries (SCCP) 
which need to be carried out before routing the call over ISUP.
I wouldn't have thought having both SUA and M3UA in the SG and
ASP made much sense.

//Stuart


TOLGA ASVEREN wrote:
> 
> Jo,
> 
> I would think, one of the reasons is, for separate ssn values, one might
> have different applications whereas for different CIC values, it is still
> the same call control. So, it seems to me loadsharing(instead of defining
> separate RKs) for ISUP is a satisfactory solution.
> 
>           Tolga
> 
> Can someone tell me why as a user of MTP3, SCCP would need
> SUA to backhaul SCCP services, but ISUP would not need
> a UA function, e.g., ISUA to backhaul its services, and
> rather uses M3UA to trasfer its services?
> 
> Joe
> 
> > -----Original Message-----
> > From: James Doss [mailto:JDoss@verisign.com]
> > Sent: Friday, January 03, 2003 6:06 PM
> > To: 'bidulock@openss7.org'; Wung, Joseph
> > Cc: sigtran@ietf.org
> > Subject: RE: [Sigtran] M3UA distributing ISUP group messages
> >
> >
> > Hi Joseph/Brian,
> > I was thinking IETF has a separate RFC for ISUP.
> > Is it not a good idea to start one. That will help to reduce the
> > complexities in the M3UA.
> > So that the ISUP and SCCP support can be seperated.
> >
> > James Doss
> > Verisign
> >
> >
> >
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Friday, January 03, 2003 5:06 PM
> > To: Wung, Joseph
> > Cc: sigtran@ietf.org
> > Subject: Re: [Sigtran] M3UA distributing ISUP group messages
> >
> >
> > Joseph,
> >
> > I offerred to write one several times.  Nobody took me up
> > on my offer.
> >
> > --brian
> >
> > Wung, Joseph wrote:                      (Fri, 03 Jan 2003 11:35:13)
> > > Brian,
> > >
> > > Is there ISUA anywhere?
> > >
> > > Joe
> > >
> > > > You will need to describe all that M3UA lacks in support
> > > > of CIC routing.  Once you are finished that exercise you
> > > > will have ISUA.  (As mentioned on the original thread
> > > > from July 2001.)
> > > >
> > > > --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
> >
> _______________________________________________
> 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

-- 
Stuart Alexander
Spider Software Ltd.
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Tue Jan  7 17:35: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 RAA01591
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 17:35:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h07MkbY24440
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 17:46:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07MjrJ24375;
	Tue, 7 Jan 2003 17:45:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07MfDJ24226
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 17:41:13 -0500
Received: from zcamail05.zca.compaq.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01434
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 17:29:47 -0500 (EST)
Received: from cacexg11.americas.cpqcorp.net (cacexg11.americas.cpqcorp.net [16.105.250.94])
	by zcamail05.zca.compaq.com (Postfix) with ESMTP
	id 6AA181F05; Tue,  7 Jan 2003 14:33:02 -0800 (PST)
Received: from txpexc03.americas.cpqcorp.net ([16.73.2.18]) by cacexg11.americas.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 7 Jan 2003 14:33:02 -0800
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"
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
Date: Tue, 7 Jan 2003 16:33:01 -0600
Message-ID: <B9DFC898FD842647BF1143F23F8036B51375D8@e2k>
Thread-Topic: [Sigtran] M3UA distributing ISUP group messages
Thread-Index: AcK2mrwnxj7nK6WjRt+N6NMNzwiL8gAAPpCw
From: "Schantz, John" <john.schantz@hp.com>
To: "Stuart Alexander" <stuarta@spider.com>, <sigtran@ietf.org>
X-OriginalArrivalTime: 07 Jan 2003 22:33:02.0076 (UTC) FILETIME=[BCEF7BC0:01C2B69C]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h07MfDJ24227
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

Tolga,

Actually isn't that the reason to use M3UA because it can handle all of
the MTP3 users, especially SCCP and ISUP!

Isn't it an SG's job to span the gap.  If an SSP is using M3UA for SCCP
and an SCP is using SUA, then isn't the SG's job to interwork the two
UAs?  If not, the networks have become very complicated if you have to
make sure the end-points and the intermediate points all talk the same
UA.

John

-----Original Message-----
From: Stuart Alexander [mailto:stuarta@spider.com] 
Sent: Tuesday, January 07, 2003 4:23 AM
To: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages


Tolga,

What happens when there is mixed traffic on a signalling link? For
example, an SSP (ASP) may generate database queries (SCCP) 
which need to be carried out before routing the call over ISUP. I
wouldn't have thought having both SUA and M3UA in the SG and ASP made
much sense.

//Stuart


TOLGA ASVEREN wrote:
> 
> Jo,
> 
> I would think, one of the reasons is, for separate ssn values, one 
> might have different applications whereas for different CIC values, it

> is still the same call control. So, it seems to me loadsharing(instead

> of defining separate RKs) for ISUP is a satisfactory solution.
> 
>           Tolga
> 
> Can someone tell me why as a user of MTP3, SCCP would need SUA to 
> backhaul SCCP services, but ISUP would not need a UA function, e.g., 
> ISUA to backhaul its services, and rather uses M3UA to trasfer its 
> services?
> 
> Joe
> 
> > -----Original Message-----
> > From: James Doss [mailto:JDoss@verisign.com]
> > Sent: Friday, January 03, 2003 6:06 PM
> > To: 'bidulock@openss7.org'; Wung, Joseph
> > Cc: sigtran@ietf.org
> > Subject: RE: [Sigtran] M3UA distributing ISUP group messages
> >
> >
> > Hi Joseph/Brian,
> > I was thinking IETF has a separate RFC for ISUP.
> > Is it not a good idea to start one. That will help to reduce the 
> > complexities in the M3UA. So that the ISUP and SCCP support can be 
> > seperated.
> >
> > James Doss
> > Verisign
> >
> >
> >
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Friday, January 03, 2003 5:06 PM
> > To: Wung, Joseph
> > Cc: sigtran@ietf.org
> > Subject: Re: [Sigtran] M3UA distributing ISUP group messages
> >
> >
> > Joseph,
> >
> > I offerred to write one several times.  Nobody took me up on my 
> > offer.
> >
> > --brian
> >
> > Wung, Joseph wrote:                      (Fri, 03 Jan 2003 11:35:13)
> > > Brian,
> > >
> > > Is there ISUA anywhere?
> > >
> > > Joe
> > >
> > > > You will need to describe all that M3UA lacks in support of CIC 
> > > > routing.  Once you are finished that exercise you will have 
> > > > ISUA.  (As mentioned on the original thread from July 2001.)
> > > >
> > > > --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
> >
> _______________________________________________
> 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

-- 
Stuart Alexander
Spider Software Ltd. _______________________________________________
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  Tue Jan  7 17:57: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 RAA02075
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 17:57:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h07N8nm25931
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 18:08:49 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07N84J25901;
	Tue, 7 Jan 2003 18:08:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h07N2tJ24966
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 18:02:55 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01904
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 17:51:29 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:agLsNM1W+K4rMij/AIP+ZyKLjICuQEc3@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h07MsiD20798;
	Tue, 7 Jan 2003 15:54:44 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h07Mshq16701;
	Tue, 7 Jan 2003 15:54:43 -0700
Date: Tue, 7 Jan 2003 15:54:43 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Schantz, John" <john.schantz@hp.com>
Cc: Stuart Alexander <stuarta@spider.com>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030107155443.E21194@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Schantz, John" <john.schantz@hp.com>,
	Stuart Alexander <stuarta@spider.com>, sigtran@ietf.org
References: <B9DFC898FD842647BF1143F23F8036B51375D8@e2k>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <B9DFC898FD842647BF1143F23F8036B51375D8@e2k>; from john.schantz@hp.com on Tue, Jan 07, 2003 at 04:33:01PM -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>

John,

M2UA can handle all of the MTP3 users and MTP3 as well.  One certainly
doesn't need M3UA to carry ISUP and SCCP when you have M2UA.

--brian

Schantz, John wrote:                         (Tue, 07 Jan 2003 16:33:01)
> Tolga,
> 
> Actually isn't that the reason to use M3UA because it can handle all of
> the MTP3 users, especially SCCP and ISUP!
> 
> Isn't it an SG's job to span the gap.  If an SSP is using M3UA for SCCP
> and an SCP is using SUA, then isn't the SG's job to interwork the two
> UAs?  If not, the networks have become very complicated if you have to
> make sure the end-points and the intermediate points all talk the same
> UA.
> 
> John
> 

-- 
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 Jan  7 19:00: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 TAA04258
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 19:00:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h080BsL29948
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 19:11:54 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h080BEJ29884;
	Tue, 7 Jan 2003 19:11:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0803FJ28962
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 19:03:15 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03971
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 18:51:47 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h07Nt2aN008537;
	Tue, 7 Jan 2003 17:55:02 -0600 (CST)
Message-ID: <3E1B68D6.C6666197@alcatel.com>
Date: Tue, 07 Jan 2003 17:55:02 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M2PA two out of three
References: <3E153380.ACD487B0@axes-mach01.usa.alcatel.com> <20030103012425.A10860@openss7.org> <3E155467.7E0C192E@axes-mach01.usa.alcatel.com> <20030103022225.A11987@openss7.org> <007a01c2b30f$8eaa6c10$6501ff0a@axsppc51> <20030103151525.C30997@openss7.or <012f01c2b555$801395d0$6501ff0a@axsppc51>
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

Manju,

I think your coffee-and-tea example is correct. 

My interpretation of the statement is:

If any two BSNs in three consecutively received User
Data messages are not the same as ((the previous one) or (any of the
FSNs
of the User Data messages in the M2PA transmit buffer at the time they
are received)), then MTP3 should be informed that the link is faulty.

If A is not (B or C), then D.

This is equivalent to

If (A is not B) and (A is not C), then D.

Putting the words back in:

If (any two BSNs in three consecutively received User
Data messages are not the same as the previous one) and ([if any two
BSNs in three consecutively received User Data messages are not the same
as] any of the FSNs
of the User Data messages in the M2PA transmit buffer at the time they
are received), then MTP3 should be informed that the link is faulty.


If one wanted to replace "or" with "and" in the current text, it would
be a good idea to add some extra words, such as

If any two BSNs in three consecutively received User
Data messages are not the same as the previous one and *not the same as*
any of the FSNs
of the User Data messages in the M2PA transmit buffer at the time they
are received, then MTP3 should be informed that the link is faulty.

I prefer to leave the text as it is, since it is familiar to those who
have worked with Q.703. 

tomG.

The current text, for the sake of reference:
If any two BSNs in three consecutively received User
Data messages are not the same as the previous one or any of the FSNs
of the User Data messages in the M2PA transmit buffer at the time they
are received, then MTP3 should be informed that the link is faulty.

Manjunath wrote:
> 
>   If I say i dont want coffee or tea doesnot it mean
>     that i dont want coffee and i dont want tea....
>   in another context
>    if i say 5 is not equal to 2 or 3 ,doesnot it mean
>    5 is not equal to 3 and 5 is not equal to 2 .
>   Is not that what even demorgan proved
>   _____      _    _
>   A + B  =  A . B,
>    If what you state is true the link has
>  to be treated as faulty if either of the two
> condition is true and the following becomes
> apparent
> 
>  If any two BSNs in three consecutively received User
>  Data messages are not the same as the previous one or if any two BSNs
>   in three consecutively received User  Data messages are not the same
> as any of the FSNs  of the User Data messages in the M2PA transmit buffer
> at the time they are received, then MTP3 should be informed that the link is
> faulty.
> 
> please clarify..
> 
> --manju/sibi
> 
> ----- Original Message -----
> From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> To: "Manjunath" <manju@axes-mach01.usa.alcatel.com>
> Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>; <sigtran@ietf.org>
> Sent: Saturday, January 04, 2003 3:45 AM
> Subject: Re: [Sigtran] Re: M2PA two out of three
> 
> > Manjunath,
> >
> > You miss the efficiency in English of skipping qualifiers on the
> > second clause:
> >
> >    If A is not the same as B or C then D.
> > => If A is not the same as B or A is not the same as C then D.
> > => If ((A is not the same as B) or (A is not the same as C)) then D.
> >
> > --brian
> >
> > Manjunath wrote:                                    (Fri, 03 Jan 2003
> 15:34:30)
> > > Brain,
> > >   We  feel what srini observed holds valid,
> > >
> > >   M2PA should follow the criterion of [2] Q.703, section 5.3.1 for
> > > incorrect BSNs: If (( any two BSNs in three consecutively received User
> > > Data messages) are not the same ((as the previous one) or (any of the
> FSNs
> > > of the User Data messages in the M2PA transmit buffer at the time they
> > > are received))), then MTP3 should be informed that the link is faulty."
> > >   If A is not same as B or C then D, it means that A is not same as B
> and A
> > > is
> > > not same as C then D proving De Morgan's law
> > >            ____           _ _          _       _
> > >      A.( B+C) = A.(B.C) = A.B . A.C
> > >
> > > Is not what Srini stated valid??
> > >
> > > thanks
> > > manju/sibi
> > >
> > >
> > >
> > >
> > > ----- Original Message -----
> > > From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > To: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
> > > Cc: <sigtran@ietf.org>
> > > Sent: Friday, January 03, 2003 2:52 PM
> > > Subject: Re: [Sigtran] Re: M2PA two out of three
> > >
> > >
> > > > Srini,
> > > >
> > > > But there is the difference:
> > > >         _   _
> > > > I read  A + B.
> > > >
> > > > The "not" in this case only applies to the immediate subject and _not_
> the
> > > > entire sentence.
> > > >
> > > > --brian
> > > >
> > > > ksrinivas wrote:                                               (Fri,
> 03
> > > Jan 2003 14:44:16)
> > > > > Brian,
> > > > >
> > > > >       I understood the thing. But I still feel there is some
> relation
> > > between
> > > > > logic and English. This can be felt from the De-Morgans law below.
> > > > >
> > > > > ____    _ _
> > > > > A+B = A.B
> > > > >
> > > > > where, A = the same as the previous one(BSNs),
> > > > >            B = the same as any of the FSNs of the User Data messages
> in
> > > the M2PA
> > > > > transmit buffer at
> > > > >                   the time they are received.
> > > > >
> > > > > Thanks & Regards,
> > > > > Srini
> > > > >
> > > > > "Brian F. G. Bidulock" wrote:
> > > > >
> > > > > > Srini,
> > > > > >
> > > > > > "Or" and "and" (or "or" or "and") are not treated as logical or
> > > > > > and logical and when used in English. ;)
> > > > > >
> > > > > > Nevertheless in this case, "or" is correct in both senses.
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > > ksrinivas wrote:                                   (Fri, 03 Jan
> 2003
> > > 12:23:54)
> > > > > > >
> > > > > > >    Brian,
> > > > > > >
> > > > > > >         In  Section  4.2.1  of  M2PA  Draft  version  6, the
> > > following is
> > > > > > >    observed.
> > > > > > >
> > > > > > >    "M2PA should follow the criterion of [2] Q.703, section 5.3.1
> for
> > > > > > >    incorrect BSNs: If any two BSNs in three consecutively
> received
> > > User
> > > > > > >    Data messages are not the same as the previous one or any of
> the
> > > FSNs
> > > > > > >    of the User Data messages in the M2PA transmit buffer at the
> time
> > > they
> > > > > > >    are received, then MTP3 should be informed that the link is
> > > faulty."
> > > > > > >
> > > > > > >    The highlighted "or" should have been "and".
> > > > > > >
> > > > > > >    The same error "or" is carried from Q.703
> > > > > > >
> > > > > > >    --Srini
> > > > > >
> > > > > > --
> > > > > > 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

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan  7 19:22: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 TAA04984
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 19:22:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h080XgT31028
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 19:33:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h080X1J30980;
	Tue, 7 Jan 2003 19:33:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h080SKJ30853
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 19:28:20 -0500
Received: from w2ksjexg01.ciena.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04826
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 19:16:51 -0500 (EST)
Received: from wntcsdexg01.csd.ciena.com ([10.34.31.31]) by w2ksjexg01.ciena.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id C2BQJWAY; Tue, 7 Jan 2003 16:19:54 -0800
Received: by webdev-llnt.oni.com with Internet Mail Service (5.5.2653.19)
	id <Y5W9LV7K>; Tue, 7 Jan 2003 16:20:05 -0800
Message-ID: <2135200C183FD5119588009027DE572302836B84@webdev-owa.oni.com>
From: "Ong, Lyndon" <LyOng@ciena.com>
To: "'Wung, Joseph'" <JWung@sonusnet.com>,
        "'James Doss'"
	 <JDoss@verisign.com>,
        "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA distributing ISUP group messages
Date: Tue, 7 Jan 2003 16:20:00 -0800 
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>

Guys,

This discussion is a bit confusing to me - the UAs 
were intended to interwork transport functions,
hence SCCP - SUA, MTP3 - M3UA.  ISUP is an application,
not transport, unless you are talking about user-to-user
signaling.

We've ended up with a proliferation of UAs since there
has not been a single model of how to interwork SS7 
and IP that has been preeminent.  I'm not sure that
adding more will help...

Cheers,

Lyndon



-----Original Message-----
From: Wung, Joseph [mailto:JWung@sonusnet.com]
Sent: Monday, January 06, 2003 10:41 AM
To: 'James Doss'; 'bidulock@openss7.org'
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA distributing ISUP group messages


Can someone tell me why as a user of MTP3, SCCP would need
SUA to backhaul SCCP services, but ISUP would not need
a UA function, e.g., ISUA to backhaul its services, and
rather uses M3UA to trasfer its services?

Joe

> -----Original Message-----
> From: James Doss [mailto:JDoss@verisign.com]
> Sent: Friday, January 03, 2003 6:06 PM
> To: 'bidulock@openss7.org'; Wung, Joseph
> Cc: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA distributing ISUP group messages
> 
> 
> Hi Joseph/Brian,
> I was thinking IETF has a separate RFC for ISUP.
> Is it not a good idea to start one. That will help to reduce the
> complexities in the M3UA.
> So that the ISUP and SCCP support can be seperated.
> 
> James Doss
> Verisign 
> 
> 
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Friday, January 03, 2003 5:06 PM
> To: Wung, Joseph
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] M3UA distributing ISUP group messages
> 
> 
> Joseph,
> 
> I offerred to write one several times.  Nobody took me up
> on my offer.
> 
> --brian
> 
> Wung, Joseph wrote:                      (Fri, 03 Jan 2003 11:35:13)
> > Brian,
> > 
> > Is there ISUA anywhere?
> > 
> > Joe
> > 
> > > You will need to describe all that M3UA lacks in support
> > > of CIC routing.  Once you are finished that exercise you
> > > will have ISUA.  (As mentioned on the original thread
> > > from July 2001.)
> > > 
> > > --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
> 
_______________________________________________
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  Tue Jan  7 19:27: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 TAA05168
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 19:27:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h080cki31950
	for sigtran-archive@odin.ietf.org; Tue, 7 Jan 2003 19:38:46 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h080c0J31914;
	Tue, 7 Jan 2003 19:38:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h080XmJ31042
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 19:33:48 -0500
Received: from w2ksjexg01.ciena.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04969
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 19:22:20 -0500 (EST)
Received: from wntcsdexg01.csd.ciena.com ([10.34.31.31]) by w2ksjexg01.ciena.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id C2BQJWB0; Tue, 7 Jan 2003 16:25:24 -0800
Received: by webdev-llnt.oni.com with Internet Mail Service (5.5.2653.19)
	id <Y5W9LV7T>; Tue, 7 Jan 2003 16:25:35 -0800
Message-ID: <2135200C183FD5119588009027DE572302836B86@webdev-owa.oni.com>
From: "Ong, Lyndon" <LyOng@ciena.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Date: Tue, 7 Jan 2003 16:25:26 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] security framework
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,

Hope you all enjoyed the holidays and are ready to address the New Year
(also hopefully a better year for telecommunications than the last!)

Regarding the work on the security framework, based on the email
discussions it sounds like ipsec is the more accepted method of security
rather than tls, and Michael is preparing an updated security document
making ipsec support a requirement.  Once the work on the security document
is completed, this should open the path through IESG for some of the other
work that has been on hold.

Cheers,

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



From mailnull@www1.ietf.org  Tue Jan  7 23:49:50 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 XAA12585
	for <sigtran-archive@odin.ietf.org>; Tue, 7 Jan 2003 23:49:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0850qw13251
	for sigtran-archive@odin.ietf.org; Wed, 8 Jan 2003 00:00:52 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0850EJ13236;
	Wed, 8 Jan 2003 00:00:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h084tmJ13098
	for <sigtran@optimus.ietf.org>; Tue, 7 Jan 2003 23:55:48 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12429
	for <sigtran@ietf.org>; Tue, 7 Jan 2003 23:44:15 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h084lRaN000232;
	Tue, 7 Jan 2003 22:47:28 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id JAA08849; Wed, 8 Jan 2003 09:16:07 -0500 (GMT)
Message-ID: <3E1BAD5A.3BF7B647@axes-mach01.usa.alcatel.com>
Date: Wed, 08 Jan 2003 10:17:22 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: [M3UA]1 AS and 1 ASP
References: <20021223063159.A8878@openss7.org> <Pine.SOL.4.10.10301020445160.23295-100000@sun2594.ssd.usa.alcatel.com> <20030102042412.A1077@openss7.org> <3E1A821F.223CB53@axes-mach01.usa.alcatel.com> <20030107011016.G7546@openss7.org> <3E1A94D4.2462E62F@axes-mach01.usa.alcatel.com> <20030107020509.A21194@openss7.org> <3E1A9B5D.76FE1B94@axes-mach01.usa.alcatel.com> <20030107023725.B21194@openss7.org> <3E1ABEA0.57FA09F7@axes-mach01.usa.alcatel.com> <20030107075414.D21194@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

     Yes, I agree with you. Each SGP views the same AS (or RK) from different angle (as they have a separate RK
tables). Is it not difficult to implement, to return the same RC1 for RK1 from both SGP1 and SGP2?.

--Srini


"Brian F. G. Bidulock" wrote:

> Srini,
>
> ksrinivas wrote:                                                                 (Tue, 07 Jan 2003 17:18:48)
> > Brian,
> >
> > >>>I still don't think you understand.  If ASP1 has send ASPAC to SGP2 before,
> > >>>then SGP2 simply responds with ASPAC ACK.  If it has not, SGP2 still responds
> > >>>with ASPAC ACK.  Nothing is overridden.
> >
> > For the Scenario under discussion, let us assume that ASP1 has sent the
> > following messages to SGP1
>
> > ASPUP message with ASPID 1,
> > REG REQ message for RK1 and
> > ASP ACTIVE message with TMT as Override
> >
> > and
> >
> > that ASP1 has also sent the following messages to SGP2
> > ASPUP message with ASPID 1,
> > REG REQ message for RK1
> >
> > Now, due to some implementation dependent reason or problem, the LM would
> > request ASP1 to send ASP ACTIVE with TMT as Override to SGP2.
> >
> > As you mentioned, SGP2 shall also reply with ASP ACTIVE Ack to ASP1.
> >
> > My question is, since the TMT is Override,  Does the SGP1 send a Notify
> > message to ASP1 for alternate ASP Active?.
>
> No, never.  This is the first ASP activating for the AS in SGP2.  It moves the
> AS from the AS-INACTIVE state to the AS-ACTIVE state and sends ASPAC ACK and
> NTFY("AS_Active") to ASP1.
>
> Again, the traffic mode has nothing to do with it.  This is the first (and
> only) ASP activating to SGP2.
>
> --brian
>
> > If so, Does it send the same ASPID 1 in the Notify message?.
> >
> > If ASPID 1 is sent in the Notify message to ASP1, Should the ASP1 be
> > implemented(to take care such a situation) to receive the same ASPID 1
> > without misbehaving.
> >
> > --Srini
> >
>
> --
> 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 Jan  8 00:57: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 AAA15521
	for <sigtran-archive@odin.ietf.org>; Wed, 8 Jan 2003 00:57:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0868vl17441
	for sigtran-archive@odin.ietf.org; Wed, 8 Jan 2003 01:08:57 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0868UJ17427;
	Wed, 8 Jan 2003 01:08:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h08673J16808
	for <sigtran@optimus.ietf.org>; Wed, 8 Jan 2003 01:07:03 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15489
	for <sigtran@ietf.org>; Wed, 8 Jan 2003 00:55:28 -0500 (EST)
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFC520CB2B.4429B5D0-ONC2256CA8.00203A83@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Wed, 8 Jan 2003 07:55:20 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/08/2003
 07:55:24 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>


Brian,


     Tolga,

     Tolga Asveren wrote:
     (Tue, 07 Jan 2003 06:05:16)
     > Stuart,
     > --- Stuart Alexander <stuarta@spider.com> wrote:
     > > Tolga,
     > >
     > > What happens when there is mixed traffic on a signalling link?
     For
     > > example, an SSP (ASP) may generate database queries (SCCP) which
     need to
     > > be carried out before routing the call over ISUP.  I wouldn't have
     thought
     > > having both SUA and M3UA in the SG and ASP made much sense.
     > [TOLGA] For the scenario you mention I also would not use both SUA
     and M3UA.
     > That SUA is usefull for some scenarios does not mean that it should
     be used
     > whenever possible. The point in my original messege was that
     different
     > applications are addressable by SSN but not with CIC.

     Different applications are addressable by CIC.  CICs are organized
     into trunk
     groups.  Trunk groups may have different applications running against
     them.
     Call Control is not necessarily one great glob of an application.

[TOLGA] I assume this can be handled with the basic CIC based routing
-without a management functionality on SG-.






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



From mailnull@www1.ietf.org  Wed Jan  8 01:07: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 BAA15728
	for <sigtran-archive@odin.ietf.org>; Wed, 8 Jan 2003 01:07:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h086IGq17834
	for sigtran-archive@odin.ietf.org; Wed, 8 Jan 2003 01:18:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h086I6J17825;
	Wed, 8 Jan 2003 01:18:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h086HDJ17780
	for <sigtran@optimus.ietf.org>; Wed, 8 Jan 2003 01:17:13 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15699
	for <sigtran@ietf.org>; Wed, 8 Jan 2003 01:05:37 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:gV3VD0EEVAF4ygV7cI9rkYHDG6+BLnlG@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0868rD26885;
	Tue, 7 Jan 2003 23:08:53 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0868rY28606;
	Tue, 7 Jan 2003 23:08:53 -0700
Date: Tue, 7 Jan 2003 23:08:52 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030107230852.F21194@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OFC520CB2B.4429B5D0-ONC2256CA8.00203A83@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OFC520CB2B.4429B5D0-ONC2256CA8.00203A83@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Wed, Jan 08, 2003 at 07:55: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>

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Wed, 08 Jan 2003 07:55:20)
> 
> [TOLGA] I assume this can be handled with the basic CIC based routing
> -without a management functionality on SG-.

No, but it could be handled by CIC load sharing, just as SSN can be
handled by load sharing.

--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  Wed Jan  8 01:18: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 BAA16241
	for <sigtran-archive@odin.ietf.org>; Wed, 8 Jan 2003 01:18:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h086TYI18384
	for sigtran-archive@odin.ietf.org; Wed, 8 Jan 2003 01:29:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h086TJJ18369;
	Wed, 8 Jan 2003 01:29:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h086SxJ18349
	for <sigtran@optimus.ietf.org>; Wed, 8 Jan 2003 01:28:59 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16174
	for <sigtran@ietf.org>; Wed, 8 Jan 2003 01:17:23 -0500 (EST)
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFCB354CF7.7CBD3C3F-ONC2256CA8.00221885@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Wed, 8 Jan 2003 08:17:16 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/08/2003
 08:17:20 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>


Brian,



     TOLGA,

     TOLGA ASVEREN wrote:
     (Wed, 08 Jan 2003 07:55:20)
     >
     > [TOLGA] I assume this can be handled with the basic CIC based
     routing
     > -without a management functionality on SG-.

     No, but it could be handled by CIC load sharing, just as SSN can be
     handled by load sharing.
[TOLGA] So, for the case you mention, is it still possible to get ISUP
management messages spanning multiple trunk groups, served by different
applications?

For SSN case, will loadsharing be enough for SCCP congestion case?





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



From mailnull@www1.ietf.org  Wed Jan  8 02:20: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 CAA01527
	for <sigtran-archive@odin.ietf.org>; Wed, 8 Jan 2003 02:20:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h087Ut631784
	for sigtran-archive@odin.ietf.org; Wed, 8 Jan 2003 02:30:55 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h087UOJ31767;
	Wed, 8 Jan 2003 02:30:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h087OQJ31125
	for <sigtran@optimus.ietf.org>; Wed, 8 Jan 2003 02:24:26 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24525
	for <sigtran@ietf.org>; Wed, 8 Jan 2003 02:12:49 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:DCU1ZgA8JgoAQFM+N3UORAQufJQD1LPe@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h087G5D27676;
	Wed, 8 Jan 2003 00:16:05 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h087G4829705;
	Wed, 8 Jan 2003 00:16:04 -0700
Date: Wed, 8 Jan 2003 00:16:04 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030108001604.G21194@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OFCB354CF7.7CBD3C3F-ONC2256CA8.00221885@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OFCB354CF7.7CBD3C3F-ONC2256CA8.00221885@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Wed, Jan 08, 2003 at 08:17:16AM +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>

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Wed, 08 Jan 2003 08:17:16)
> 
> Brian,
> 
> 
> 
>      TOLGA,
> 
>      TOLGA ASVEREN wrote:
>      (Wed, 08 Jan 2003 07:55:20)
>      >
>      > [TOLGA] I assume this can be handled with the basic CIC based
>      routing
>      > -without a management functionality on SG-.
> 
>      No, but it could be handled by CIC load sharing, just as SSN can be
>      handled by load sharing.
> [TOLGA] So, for the case you mention, is it still possible to get ISUP
> management messages spanning multiple trunk groups, served by different
> applications?

It is possible to get Circuit Supervision group messages that span Call
Processing trunk groups.

> For SSN case, will loadsharing be enough for SCCP congestion case?

Does not MTP congestion work when loadsharing on, say, SLS?  Why should
SCCP congestion not work?

--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  Wed Jan  8 02:25: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 CAA05274
	for <sigtran-archive@odin.ietf.org>; Wed, 8 Jan 2003 02:25:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h087aHj32353
	for sigtran-archive@odin.ietf.org; Wed, 8 Jan 2003 02:36:17 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h087ZkJ32321;
	Wed, 8 Jan 2003 02:35:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h087TZJ31726
	for <sigtran@optimus.ietf.org>; Wed, 8 Jan 2003 02:29:35 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29195
	for <sigtran@ietf.org>; Wed, 8 Jan 2003 02:17:57 -0500 (EST)
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFE5F8C57B.24D5F71B-ONC2256CA8.00275049@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Wed, 8 Jan 2003 09:17:51 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/08/2003
 09:17:54 AM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h087TZJ31727
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


Brian,



     Brian,



          TOLGA,

          TOLGA ASVEREN wrote:
          (Wed, 08 Jan 2003 07:55:20)
          >
          > [TOLGA] I assume this can be handled with the basic CIC based
          routing
          > -without a management functionality on SG-.

          No, but it could be handled by CIC load sharing, just as SSN can
     be
          handled by load sharing.
     [TOLGA] So, for the case you mention, is it still possible to get ISUP
     management messages spanning multiple trunk groups, served by
     different
     applications?

     For SSN case, will loadsharing be enough for SCCP congestion case?
[TOLGA] Sorry, this won´t be a problem because SCCP will work as a single
entity in case of loadsharing. But this brings another question, if you
assume that user part(ISUP or SCCP) for one PC is going to work always as a
single entity, then what is the real benefit of loadsharing based on a user
part construct (CIC or SSN)? If the consensus is that entities, part of the
same user part and working independently are not necessary/easily
implementable then I also would agree with Brian that CIC range should be
taken out from RK in registration request.





_______________________________________________
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  Wed Jan  8 17:36: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 RAA10605
	for <sigtran-archive@odin.ietf.org>; Wed, 8 Jan 2003 17:36:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h08MlTq28841
	for sigtran-archive@odin.ietf.org; Wed, 8 Jan 2003 17:47:29 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h08Ml5J28800;
	Wed, 8 Jan 2003 17:47:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h08MfVJ28560
	for <sigtran@optimus.ietf.org>; Wed, 8 Jan 2003 17:41:31 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10104
	for <sigtran@ietf.org>; Wed, 8 Jan 2003 17:29:36 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:YaEvxmzZXMdCx3gPsATiuAhPCxkXJOL4@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h08MWqD09093
	for <sigtran@ietf.org>; Wed, 8 Jan 2003 15:32:52 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h08MWpi27914
	for sigtran@ietf.org; Wed, 8 Jan 2003 15:32:51 -0700
Date: Wed, 8 Jan 2003 15:32:51 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: sigtran@ietf.org
Message-ID: <20030108153251.A27265@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: sigtran@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Round-Robin Loadsharing
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>

All,

This use of the example of "round robin" is misleading.  Except for
completely unordered traffic flows (e.g.  simple query/response TCAP
transactions only, or extremely low traffic volumes), any round robin
based load sharing over available ASPs is guaranteed to result in
mis-sequencing at the AS.

Please include in the IG's for these documents the removal of the
reference to round robin as follows:

RFC 3331, Section 4.3.4.3, OLD TEXT:

           ... The algorithm could, for example be round-robin or based
   on information in the Data message (e.g., such as the SLS in the
   Routing Label).

RFC 3331, Section 4.3.4.3, NEW TEXT:

           ... The algorithm could, for example be based on information
   in the Data message (e.g., such as the SLS in the Routing Label).

RFC 3331, Section 4.1.1, OLD TEXT:

                                                          ... The
   selection algorithm is implementation dependent but could, for
   example, be round robin or based on the SLS or ISUP CIC.

RFC 3331, Section 4.1.1, NEW TEXT:

                                                          ... The
   selection algorithm is implementation dependent but could, for
   example, be based on the SLS or ISUP CIC.

RFC 3331, Section 4.3.4.3, OLD TEXT:

                          ... The algorithm could, for example, be
   round-robin or based on information in the Data message (e.g., the
   SLS, SCCP SSN, ISUP CIC value).

RFC 3331, Section 4.3.4.3, NEW TEXT:

                          ... The algorithm could, for example, be
   based on information in the Data message (e.g., the SLS, SCCP SSN,
   ISUP CIC value).

SUA-14,  Section 4.1.1, OLD TEXT:

                                                         ...  The 
   selection algorithm is implementation dependent but could, for 
   example, be round robin or based on the SLS.

SUA-14,  Section 4.1.1, NEW TEXT:

                                                         ...  The 
   selection algorithm is implementation dependent but could, for 
   example, be based on the SLS.

SUA-14 Section 4.3.4.3, OLD TEXT:

                         ...  The algorithm could, for example, be round
   robin or based on information in the Data message (e.g., the SLS or 
   SSN).   

SUA-14 Section 4.3.4.3, NEW TEXT:

                         ...  The algorithm could, for example, be
   based on information in the Data message (e.g., the SLS or SSN).   

SUA-14 Section A.3.1, OLD TEXT:

   The selection criterion can be based on a round robin mechanism, or 
   any other method that guarantees a balanced load sharing over the 
   active ASPs.

SUA-14 Section A.3.1, OLD TEXT:

   The selection criterion can be based on any method that guarantees
   a balanced load sharing, without mis-sequencing, over the active ASPs

--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  Thu Jan  9 03:17: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 DAA03402
	for <sigtran-archive@odin.ietf.org>; Thu, 9 Jan 2003 03:17:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h098TES04082
	for sigtran-archive@odin.ietf.org; Thu, 9 Jan 2003 03:29:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h098SqJ04073;
	Thu, 9 Jan 2003 03:28:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h098RBJ04009
	for <sigtran@optimus.ietf.org>; Thu, 9 Jan 2003 03:27:11 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03366
	for <sigtran@ietf.org>; Thu, 9 Jan 2003 03:15:04 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h098IIBE005016;
	Thu, 9 Jan 2003 02:18:19 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id MAA06400; Thu, 9 Jan 2003 12:46:46 -0500 (GMT)
Message-ID: <3E1D3046.27DA422A@axes-mach01.usa.alcatel.com>
Date: Thu, 09 Jan 2003 13:48:15 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: sigtran@ietf.org
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] [M3UA] Message distribution at the ASP
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

Brian,

    M3UA RFC 3332 does not tell much about message distribution at the
ASP (section 1.4.2.5). Is there any document to get the information?. or
Is it implementation dependent?.

--Srini

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



From mailnull@www1.ietf.org  Thu Jan  9 03:45:57 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 DAA04088
	for <sigtran-archive@odin.ietf.org>; Thu, 9 Jan 2003 03:45:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h098vYZ06195
	for sigtran-archive@odin.ietf.org; Thu, 9 Jan 2003 03:57:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h098vHJ06178;
	Thu, 9 Jan 2003 03:57:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h098uRJ06112
	for <sigtran@optimus.ietf.org>; Thu, 9 Jan 2003 03:56:27 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04051
	for <sigtran@ietf.org>; Thu, 9 Jan 2003 03:44:18 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:/U0ejIAPZzSXLCuHTEHVdNouux3eH7fV@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h098lZD17121;
	Thu, 9 Jan 2003 01:47:35 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h098lZs08758;
	Thu, 9 Jan 2003 01:47:35 -0700
Date: Thu, 9 Jan 2003 01:47:35 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Message-ID: <20030109014735.H21194@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <3E1D3046.27DA422A@axes-mach01.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: <3E1D3046.27DA422A@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Thu, Jan 09, 2003 at 01:48:15PM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: [M3UA] Message distribution at the ASP
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>

Srini,

See section A.2.2.

--brian

ksrinivas wrote:                                 (Thu, 09 Jan 2003 13:48:15)
> Brian,
> 
>     M3UA RFC 3332 does not tell much about message distribution at the
> ASP (section 1.4.2.5). Is there any document to get the information?. or
> Is it implementation dependent?.
> 
> --Srini

-- 
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 Jan  9 10:13:23 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 KAA14007
	for <sigtran-archive@odin.ietf.org>; Thu, 9 Jan 2003 10:13:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h09FP7B30509
	for sigtran-archive@odin.ietf.org; Thu, 9 Jan 2003 10:25:07 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h09FObJ30414;
	Thu, 9 Jan 2003 10:24:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h09FNKJ30306
	for <sigtran@optimus.ietf.org>; Thu, 9 Jan 2003 10:23:20 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13887
	for <sigtran@ietf.org>; Thu, 9 Jan 2003 10:11:04 -0500 (EST)
Received: from esealnt611.al.sw.ericsson.se (esealnt611.al.sw.ericsson.se [153.88.254.68])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id h09FEKKW008294;
	Thu, 9 Jan 2003 16:14:20 +0100 (MET)
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 ZGNLT6QH; Thu, 9 Jan 2003 16:14:20 +0100
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <Y826MCPM>; Thu, 9 Jan 2003 16:14:20 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C4759FE@EESTQNT105.es.eu.ericsson.se>
X-Sybari-Trust: 1984f92b 1864f774 d5511081 00000138
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'Tolga Asveren'" <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: RE: [Sigtran] m3ua IGv02: typo in 3.7.2
Date: Thu, 9 Jan 2003 16:03:29 +0100 
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 Tolga, 

We'll fix it.

Cheers // Javier.

> -----Original Message-----
> From: Tolga Asveren [mailto:tolga_asveren@yahoo.com]
> Sent: Sunday, January 05, 2003 4:48 PM
> To: sigtran@ietf.org
> Subject: [Sigtran] m3ua IGv02: typo in 3.7.2
> 
> 
> Hi Javier/Ken,
> 
> m3uaIGv02 3.7.2:
> "If the SG determines that the received RK was already
> registered, the
>     SGP returns a Registration Response message to the
> ASP, containing a
>     Registration Result "Error - Cannot Support Unique
> Routing"."
> 
> I think SG in the first sentence should be SGP.
> 
>    Regards,
>    Tolga
> 
> 
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.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 Jan  9 19:02: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 TAA00992
	for <sigtran-archive@odin.ietf.org>; Thu, 9 Jan 2003 19:02:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A0EAq04852
	for sigtran-archive@odin.ietf.org; Thu, 9 Jan 2003 19:14:10 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A0DkJ04820;
	Thu, 9 Jan 2003 19:13:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A0C1J04766
	for <sigtran@optimus.ietf.org>; Thu, 9 Jan 2003 19:12:01 -0500
Received: from revere.sonusnet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00904
	for <sigtran@ietf.org>; Thu, 9 Jan 2003 18:59:35 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3.sonusnet.com [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h0A02JS14860
	for <sigtran@ietf.org>; Thu, 9 Jan 2003 19:02:19 -0500 (EST)
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19)
	id <Y68HSK61>; Thu, 9 Jan 2003 19:02:50 -0500
Message-ID: <4CF48720B6E9D4118D040060CF2074E9072F6BC6@sonusdc3.sonusnet.com>
From: "Wung, Joseph" <JWung@sonusnet.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Date: Thu, 9 Jan 2003 19:02:49 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] M3UA default AS
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>

M3UA section 1.4.2.4 says

	"When there is no matching Routing Key entry for an
	incoming SS7 message, a default treatment MAY be
	specified.  Possible solutions are to provide a default
	AS at the SGP that directs all unallocated traffic to a
	(set of) default ASP(s), or to drop the message and
	provide a notification to layer management."

I have, say, 3 ASPs:
	ASP-1 for OPC/DPC/CIC=1-24
	ASP-2 for OPC/DPC/CIC=25-48
	ASP-3 for OPC/DPC/CIC=49-72,
	where OPC/DPC are the same.

How would the SGP route an incoming message with OPC/DPC/CIC=100.
My question is since the default AS is not registered, thus no
associated traffic mode, how does the SGP know the received 
message should be broadcast to all 3 of the ASPs or select one 
of them to send to?

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



From mailnull@www1.ietf.org  Thu Jan  9 20:54: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 UAA03543
	for <sigtran-archive@odin.ietf.org>; Thu, 9 Jan 2003 20:54:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A26pC10917
	for sigtran-archive@odin.ietf.org; Thu, 9 Jan 2003 21:06:51 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A26aJ10899;
	Thu, 9 Jan 2003 21:06:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A25AJ10858
	for <sigtran@optimus.ietf.org>; Thu, 9 Jan 2003 21:05:10 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03498
	for <sigtran@ietf.org>; Thu, 9 Jan 2003 20:52:41 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:cB6EzW4J5ZzPO4zkFq5t0YpgfwBrgWOa@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0A1twD32567;
	Thu, 9 Jan 2003 18:55:58 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0A1twc05495;
	Thu, 9 Jan 2003 18:55:58 -0700
Date: Thu, 9 Jan 2003 18:55:58 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Wung, Joseph" <JWung@sonusnet.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA default AS
Message-ID: <20030109185558.A8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Wung, Joseph" <JWung@sonusnet.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <4CF48720B6E9D4118D040060CF2074E9072F6BC6@sonusdc3.sonusnet.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: <4CF48720B6E9D4118D040060CF2074E9072F6BC6@sonusdc3.sonusnet.com>; from JWung@sonusnet.com on Thu, Jan 09, 2003 at 07:02:49PM -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>

Joseph,

Don't try to use CIC routing for this: use CIC load-sharing.
Then the SG knows that it can send CIC=100 to any of the ASPs in
the load-share AS.  If you need to have controlled load-sharing
consider:

	draft-bidulock-sigtran-loadsel-01.txt and
	draft-bidulock-sigtran-loadgrp-01.txt

that I have just submitted to the I-D drafts editor.

Until they are available on the I-D server, you will find a copy
here:

	http://www.openss7.org/sigtran01.html

--brian

Wung, Joseph wrote:                                                                  (Thu, 09 Jan 2003 19:02:49)
> M3UA section 1.4.2.4 says
> 
> 	"When there is no matching Routing Key entry for an
> 	incoming SS7 message, a default treatment MAY be
> 	specified.  Possible solutions are to provide a default
> 	AS at the SGP that directs all unallocated traffic to a
> 	(set of) default ASP(s), or to drop the message and
> 	provide a notification to layer management."
> 
> I have, say, 3 ASPs:
> 	ASP-1 for OPC/DPC/CIC=1-24
> 	ASP-2 for OPC/DPC/CIC=25-48
> 	ASP-3 for OPC/DPC/CIC=49-72,
> 	where OPC/DPC are the same.
> 
> How would the SGP route an incoming message with OPC/DPC/CIC=100.
> My question is since the default AS is not registered, thus no
> associated traffic mode, how does the SGP know the received 
> message should be broadcast to all 3 of the ASPs or select one 
> of them to send to?
> 
> Joe
> _______________________________________________
> 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 Jan 10 00:23: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 AAA07776
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 00:23:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A5ZpA22283
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 00:35:51 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A5ZYJ22266;
	Fri, 10 Jan 2003 00:35:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A5YdJ22237
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 00:34:39 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07756
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 00:22:07 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0A5P8Or012095;
	Thu, 9 Jan 2003 23:25:21 -0600 (CST)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0A5OvM23130;
	Thu, 9 Jan 2003 23:24:57 -0600 (CST)
Date: Thu, 9 Jan 2003 23:24:57 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: javier.pastor-balbas@ece.ericsson.se
cc: sigtran@ietf.org
Message-ID: <Pine.SOL.4.10.10301092242440.10635-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sigtran] m3ua IGv02: typo in  1.4.2.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>


Javier,Ken,

section 1.4.2.1 Overview

...The Routing Context therefore can be viewed as an index into a sending
node's Message Distribution Table containing the Routing Key entries.

Please change this to [ in IG]

...The Routing Context therefore can be viewed as an index into a sending 
SGP's or Signaling Peer process's Message Distribution Table containing
the Routing Key entries.

--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 Sun, 5 Jan 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> Yes, change node to SGP.  I don't have control over the document
> or I would do it for you.  Ask Javier or Ken to include it in the IG.
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                           (Sun, 05 Jan 2003 22:48:14)
> > 
> > Brian,
> >  Good explanation.As a reader of RFC i agree with you but as an
> > implementor i dont.Because it leads me to think that RC is within
> > the scope of SG but which is false as we discussed already.
> > 
> > --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, 3 Jan 2003, Brian F. G. Bidulock wrote:
> > 
> > > Samuel,
> > > 
> > > It's only an example of how to look at it: not a requirement-- node, SGP,
> > > what's the difference?
> > > 
> > > --brian
> > > 
> > > Samuel Dur D. Jeyaseelan wrote:                        (Fri, 03 Jan 2003 02:53:14)
> > > > 
> > > > Brian,
> > > > Why dont u change section 1.4.2.1 Overview
> > > > 
> > > > ...The Routing Context therefore can be viewed as an index into a sending
> > > > node's Message Distribution Table containing the Routing Key entries.
> > > > 
> > > > to
> > > > 
> > > > ...The Routing Context therefore can be viewed as an index into a sending
> > > > SGP's Message Distribution Table containing the Routing Key entries.
> > > > 
> > > > --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. *******
> > > > 
> 
> -- 
> 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 Jan 10 00:37: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 AAA08180
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 00:37:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A5nUd23311
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 00:49:30 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A5n6J23280;
	Fri, 10 Jan 2003 00:49:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A5mTJ23263
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 00:48:29 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08162
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 00:35:57 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0A5d8Oj013351
	for <sigtran@ietf.org>; Thu, 9 Jan 2003 23:39:13 -0600 (CST)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0A5cBM00357
	for <sigtran@ietf.org>; Thu, 9 Jan 2003 23:38:11 -0600 (CST)
Date: Thu, 9 Jan 2003 23:38:11 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: sigtran@ietf.org
In-Reply-To: <20030109185558.A8782@openss7.org>
Message-ID: <Pine.SOL.4.10.10301092326240.10635-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sigtran] m3ua- IG
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 think it would be good if we remove all SSN(sub system number)
references from RFC or make a global statement in IG as "SSN will not be
supported by RFC 3332 and wherever it is being referred it should be
ignored"

--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 mailnull@www1.ietf.org  Fri Jan 10 01:13: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 BAA08678
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 01:13:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A6Pci25271
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 01:25:38 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A6PJJ25256;
	Fri, 10 Jan 2003 01:25:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A6OVJ25207
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 01:24:31 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08669
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 01:11:57 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF7353F3BC.DE05D048-ONC2256CAA.0021A50E@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 08:11:49 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 08:11:54 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>


Samuel,

What does it mean exactly that M3UA supports this or that RK? One can argue
about how suitable it is to use a certain RK type with M3UA but this IMO is
a different thing. I think the best is to leave RK types flexible and maybe
with one sentence to warn people about non-MTP3 RK types, that those might
need some management functionalitiy on SG.

        Tolga



     I think it would be good if we remove all SSN(sub system number)
     references from RFC or make a global statement in IG as "SSN will not
     be
     supported by RFC 3332 and wherever it is being referred it should be
     ignored"

     --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 mailnull@www1.ietf.org  Fri Jan 10 01:38: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 BAA08916
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 01:38:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A6oj426924
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 01:50:45 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A6oSJ26900;
	Fri, 10 Jan 2003 01:50:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A6lYJ26774
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 01:47:34 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08878
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 01:35:01 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:AIC28srdUEGiWm7t/pnvB6L3v7eJ3EuC@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0A6cHD04279;
	Thu, 9 Jan 2003 23:38:17 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0A6cFv09999;
	Thu, 9 Jan 2003 23:38:15 -0700
Date: Thu, 9 Jan 2003 23:38:15 -0700
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] m3ua- IG
Message-ID: <20030109233815.B8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030109185558.A8782@openss7.org> <Pine.SOL.4.10.10301092326240.10635-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.10301092326240.10635-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Thu, Jan 09, 2003 at 11:38:11PM -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 agree and it was the concensus of the thread at LC that references
to SSN as routing key be removed from the spec and not mentioned.
Thus leaving it open for someone to implement if they can find a way
(which is not hopeful).

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 09 Jan 2003 23:38:11)
> 
> I think it would be good if we remove all SSN(sub system number)
> references from RFC or make a global statement in IG as "SSN will not be
> supported by RFC 3332 and wherever it is being referred it should be
> ignored"
> 
> --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 mailnull@www1.ietf.org  Fri Jan 10 01:39:19 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 BAA08937
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 01:39:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A6pL626975
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 01:51:21 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A6p9J26964;
	Fri, 10 Jan 2003 01:51:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A6mlJ26840
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 01:48:47 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08895
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 01:36:13 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Sk+d5VAJB9nIqTrqIjsAuHyc0jeDdAtY@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0A6dUD04292;
	Thu, 9 Jan 2003 23:39:30 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0A6dUH10007;
	Thu, 9 Jan 2003 23:39:30 -0700
Date: Thu, 9 Jan 2003 23:39:30 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030109233930.C8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF7353F3BC.DE05D048-ONC2256CAA.0021A50E@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF7353F3BC.DE05D048-ONC2256CAA.0021A50E@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 08:11:49AM +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>

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 08:11:49)
> 
> Samuel,
> 
> What does it mean exactly that M3UA supports this or that RK? One can argue
> about how suitable it is to use a certain RK type with M3UA but this IMO is
> a different thing. I think the best is to leave RK types flexible and maybe
> with one sentence to warn people about non-MTP3 RK types, that those might
> need some management functionalitiy on SG.

Yes, some non-standard, non-iteroperable mangement functionality on the SG.
Which IMO is the same as saying that M3UA does not support 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  Fri Jan 10 01:52: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 BAA09086
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 01:52:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A74dN28074
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 02:04:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A748J27764;
	Fri, 10 Jan 2003 02:04:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A73RJ27721
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 02:03:28 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09078
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 01:50:53 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0A6sAOZ018091;
	Fri, 10 Jan 2003 00:54:10 -0600 (CST)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0A6rEM29507;
	Fri, 10 Jan 2003 00:53:15 -0600 (CST)
Date: Fri, 10 Jan 2003 00:53:14 -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] m3ua- IG
In-Reply-To: <OF7353F3BC.DE05D048-ONC2256CAA.0021A50E@LocalDomain>
Message-ID: <Pine.SOL.4.10.10301100049160.21736-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>


Tolga,

It means peer M3UA can not recognize whether SSN is available or congested
or unavailable... 

what do you mean by saying "... RK types flexible..."

--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, 10 Jan 2003, TOLGA ASVEREN wrote:

> 
> Samuel,
> 
> What does it mean exactly that M3UA supports this or that RK? One can argue
> about how suitable it is to use a certain RK type with M3UA but this IMO is
> a different thing. I think the best is to leave RK types flexible and maybe
> with one sentence to warn people about non-MTP3 RK types, that those might
> need some management functionalitiy on SG.
> 
>         Tolga
> 
> 
> 
>      I think it would be good if we remove all SSN(sub system number)
>      references from RFC or make a global statement in IG as "SSN will not
>      be
>      supported by RFC 3332 and wherever it is being referred it should be
>      ignored"
> 
>      --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
> 

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



From mailnull@www1.ietf.org  Fri Jan 10 02:08: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 CAA19212
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 02:08:13 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A7KG604326
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 02:20:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A7JtJ04255;
	Fri, 10 Jan 2003 02:19:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A7IsJ04193
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 02:18:54 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17480
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 02:06:17 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:vk8tAREKIWVsiSzcHHCtgZerIFQ6/2PI@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0A79YD04754;
	Fri, 10 Jan 2003 00:09:34 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0A79Y010886;
	Fri, 10 Jan 2003 00:09:34 -0700
Date: Fri, 10 Jan 2003 00:09:34 -0700
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] m3ua- IG
Message-ID: <20030110000934.D8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030109185558.A8782@openss7.org> <Pine.SOL.4.10.10301092326240.10635-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.10301092326240.10635-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Thu, Jan 09, 2003 at 11:38:11PM -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,

The following IG entry would remove references to SSN and CIC from
the document.  It this what you had in mind?

--brian

Samuel Dur D. Jeyaseelan wrote:                   (Thu, 09 Jan 2003 23:38:11)
> 
> I think it would be good if we remove all SSN(sub system number)
> references from RFC or make a global statement in IG as "SSN will not be
> supported by RFC 3332 and wherever it is being referred it should be
> ignored"
> 
> --Samuel

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

 3.16 SSN and CIC Routing Keys

 3.16.1 Description of the problem

    Use of SSN and CIC Routing Keys is inadequate in the specification
    leading to non-interoperable solutions.

 3.16.2 Text changes to the document

    ---------
    Old text: (Section 1.4.2.1)
    ---------

    Possible SS7 address/routing information that comprise a Routing Key
    entry includes, for example, the OPC, DPC, SIO found in the MTP3
    routing label, or MTP3-User specific fields (such as the ISUP CIC,
    SCCP subsystem number).  Some example Routing Keys are: the DPC
    alone, the DPC/OPC combination, the DPC/OPC/CIC combination, or the
    DPC/SSN combination.  The particular information used to define an
    M3UA Routing Key is application and network dependent, and none of
    the above examples are mandated.

    ---------
    New text: (Section 1.4.2.1)
    ---------

    Possible SS7 address/routing information that comprise a Routing Key
    entry includes, for example, the OPC, DPC, SIO found in the MTP3
    routing label.  Some example Routing Keys are: the DPC alone, the
    DPC/OPC combination, or the DPC/OPC/SI combination.  The particular
    information used to define an M3UA Routing Key is application and
    network dependent, and none of the above examples are mandated.


    ---------
    Old text: (Section 1.4.2.2)
    ---------

    Routing Keys SHOULD be unique in the sense that each received SS7
    signalling message SHOULD have a full or partial match to a single
    routing result. It is not necessary for the parameter range values
    within a particular Routing Key to be contiguous.  For example, an AS
    could be configured to support call processing for multiple ranges of
    PSTN trunks that are not represented by contiguous CIC values.

    ---------
    New text: (Section 1.4.2.2)
    ---------

    Routing Keys SHOULD be unique in the sense that each received SS7
    signalling message SHOULD have a full or partial match to a single
    routing result. It is not necessary for the parameter range values
    within a particular Routing Key to be contiguous.



    ---------
    Old text: (Section 1.4.7)
    ---------

    The M3UA layer at both the SGP and ASP also supports the assignment
    of signalling traffic into streams within an SCTP association.
    Traffic that requires sequencing SHOULD be assigned to the same
    stream.  To accomplish this, MTP3-User traffic may be assigned to
    individual streams based on, for example, the SLS value in the MTP3
    Routing Label or the ISUP CIC assignment, subject of course to the
    maximum number of streams supported by the underlying SCTP
    association.

    ---------
    New text: (Section 1.4.7)
    ---------

    The M3UA layer at both the SGP and ASP also supports the assignment
    of signalling traffic into streams within an SCTP association.
    Traffic that requires sequencing SHOULD be assigned to the same
    stream.  To accomplish this, MTP3-User traffic may be assigned to
    individual streams based on, for example, the SLS value in the MTP3
    Routing Label, subject of course to the maximum number of streams
    supported by the underlying SCTP association.



    ---------
    Old text: (Section 1.5.3)
    ---------

    In this example, the SGP contains an instance of the SS7 SCCP
    protocol layer that may, for example, perform the SCCP Global Title
    Translation (GTT) function for messages logically addressed to the SG
    SCCP.  If the result of a GTT for an SCCP message yields an SS7 DPC
    or DPC/SSN address of an SCCP peer located in the IP domain, the
    resulting MTP-TRANSFER request primitive is sent to the local M3UA-
    resident network address translation and mapping function for ongoing
    routing to the final IP destination.

    ---------
    New text: (Section 1.5.3)
    ---------

    In this example, the SGP contains an instance of the SS7 SCCP
    protocol layer that may, for example, perform the SCCP Global Title
    Translation (GTT) function for messages logically addressed to the SG
    SCCP.  If the result of a GTT for an SCCP message yields an SS7 DPC
    or DPC/SI address of an SCCP peer located in the IP domain, the
    resulting MTP-TRANSFER request primitive is sent to the local M3UA-
    resident network address translation and mapping function for ongoing
    routing to the final IP destination.

    ---------
    Old text: (Section 1.5.3)
    ---------

    For internal SGP modeling purposes, this may be accomplished with the
    use of an implementation-dependent nodal interworking function within
    the SGP that effectively sits below the SCCP and routes MTP-TRANSFER
    request/indication messages to/from both the MTP3 and the M3UA layer,
    based on the SS7 DPC or DPC/SSN address information.  This nodal
    interworking function has no visible peer protocol with either the
    ASP or SEP.

    ---------
    New text: (Section 1.5.3)
    ---------

    For internal SGP modeling purposes, this may be accomplished with the
    use of an implementation-dependent nodal interworking function within
    the SGP that effectively sits below the SCCP and routes MTP-TRANSFER
    request/indication messages to/from both the MTP3 and the M3UA layer,
    based on the SS7 DPC or DPC/SI address information.  This nodal
    interworking function has no visible peer protocol with either the
    ASP or SEP.



    ---------
    Old text: (Section 3.2)
    ---------

         Congestion Indications                0x0205
         Concerned Destination                 0x0206
         Routing Key                           0x0207
         Registration Result                   0x0208
         Deregistration Result                 0x0209
         Local_Routing Key Identifier          0x020a
         Destination Point Code                0x020b
         Service Indicators                    0x020c
         Reserved                              0x020d
         Originating Point Code List           0x020e
         Circuit Range                         0x020f
         Protocol Data                         0x0210
         Reserved                              0x0211
         Registration Status                   0x0212
         Deregistration Status                 0x0213

    ---------
    New text: (Section 3.2)
    ---------

         Congestion Indications                0x0205
         Concerned Destination                 0x0206
         Routing Key                           0x0207
         Registration Result                   0x0208
         Deregistration Result                 0x0209
         Local_Routing Key Identifier          0x020a
         Destination Point Code                0x020b
         Service Indicators                    0x020c
         Reserved                              0x020d
         Originating Point Code List           0x020e
         Protocol Data                         0x0210
         Reserved                              0x0211
         Registration Status                   0x0212
         Deregistration Status                 0x0213



    ---------
    Old text: (Section 3.6.1)
    ---------

       |                  Traffic Mode Type (optional)                 |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                     Destination Point Code                    |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                  Network Appearance (optional)                |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                  Service Indicators (optional)                |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |              Originating Point Code List (optional)           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                   Circuit Range List (optional)               |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       \                                                               \
       /                              ...                              /
       \                                                               \
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                     Destination Point Code                    |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                  Service Indicators (optional)                |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |              Originating Point Code List (optional)           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                   Circuit Range List (optional)               |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 
       Note: The Destination Point Code, Service Indicators, Originating
       Point Code List and Circuit Range List parameters MAY be repeated
       as a grouping within the Routing Key parameter, in the structure
       shown above.

    ---------
    New text: (Section 3.6.1)
    ---------

       |                  Traffic Mode Type (optional)                 |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                     Destination Point Code                    |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                  Network Appearance (optional)                |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                  Service Indicators (optional)                |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |              Originating Point Code List (optional)           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       \                                                               \
       /                              ...                              /
       \                                                               \
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                     Destination Point Code                    |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                  Service Indicators (optional)                |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |              Originating Point Code List (optional)           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 
       Note: The Destination Point Code, Service Indicators, and
       Originating Point Code List parameters MAY be repeated as a
       grouping within the Routing Key parameter, in the structure shown
       above.

    ---------
    Old text: (Section 3.6.1)
    ---------

    Circuit Range:
 
       An ISUP controlled circuit is uniquely identified by the SS7 OPC,
       DPC and CIC value.  For the purposes of identifying Circuit Ranges
       in an M3UA Routing Key, the optional Circuit Range parameter
       includes one or more circuit ranges, each identified by an OPC and
       Upper/Lower CIC value.  The DPC is implicit as it is mandatory and
       already included in the DPC parameter of the Routing Key.  The
       absence of the Circuit Range parameter in the Routing Key
       indicates the use of any Circuit Range values, in the case of
       ISUP/TUP traffic.  The Origination Point Code is encoded the same
       as the Destination Point Code parameter, while the CIC values are
       16-bit integers.

    ---------
    New text: (Section 3.6.1)
    ---------

    (none)
 
    ---------
    Old text: (Section 3.6.1)
    ---------

    The Circuit Range format is as follows:
 
        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 = 0x020f        |              Length           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |    Mask = 0   |          Origination Point Code #1            |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |       Lower CIC Value #1      |      Upper CIC Value #1       |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |    Mask = 0   |          Origination Point Code #2            |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |       Lower CIC Value #2      |      Upper CIC Value #2       |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       /                              ...                              /
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |    Mask = 0   |          Origination Point Code #n            |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |       Lower CIC Value #n      |      Upper CIC Value #n       |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    ---------
    New text: (Section 3.6.1)
    ---------

    (none)
 


    ---------
    Old text: (Section 3.7.1)
    ---------

       An Application Server Process may be configured to process traffic
       for more than one logical Application Server.  From the
       perspective of an ASP, a Routing Context defines a range of
       signalling traffic that the ASP is currently configured to receive
       from the SGP.  For example, an ASP could be configured to support
       call processing for multiple ranges of PSTN trunks and therefore
       receive related signalling traffic, identified by separate SS7
       DPC/OPC/CIC ranges.

    ---------
    New text: (Section 3.7.1)
    ---------

       An Application Server Process may be configured to process traffic
       for more than one logical Application Server.  From the
       perspective of an ASP, a Routing Context defines a range of
       signalling traffic that the ASP is currently configured to receive
       from the SGP.  For example, an ASP could be configured to support
       call processing for multiple ranges of PSTN trunks and therefore
       receive related signalling traffic, identified by separate SS7
       DPC/OPC/SI ranges.



    ---------
    Old text: (Section 4.4.1)
    ---------

    If an SGP determines that one or more of the Routing Key parameters
    are not supported for the purpose of creating new Routing Key
    entries, the SGP returns a Registration Response message to the ASP,
    containing a Registration Result "Error - Unsupported RK parameter
    field".  This result MAY be used if, for example, the SGP does not
    support RK Circuit Range Lists in a Routing Key because the SGP does
    not support ISUP traffic, or does not provide CIC range granularity.

    ---------
    New text: (Section 4.4.1)
    ---------

    If an SGP determines that one or more of the Routing Key parameters
    are not supported for the purpose of creating new Routing Key
    entries, the SGP returns a Registration Response message to the ASP,
    containing a Registration Result "Error - Unsupported RK parameter
    field".



    ---------
    Old text: (Section A.2.1)
    ---------

    For example, where Application Servers are defined using ranges of
    ISUP CIC values, the Operator is implicitly splitting up control of
    the related circuit groups.  Some CIC value range assignments may
    interfere with ISUP circuit group management procedures.

    ---------
    New text: (Section A.2.1)
    ---------

    (none)
 
 3.16.3 Solution description

    The removal of reference to SSN and CIC used in Routing Keys as well
    as removal of Circuit Range from the Routing Key parameter removes
    the unclear text from the specification.

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

-- 
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 Jan 10 02:36: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 CAA19662
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 02:36:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A7mYs06769
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 02:48:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A7mFJ06749;
	Fri, 10 Jan 2003 02:48:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A7lTJ06729
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 02:47:30 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19631
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 02:34:54 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF9082A54F.15EAA27D-ONC2256CAA.002905F5@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 09:34:46 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 09:34:52 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>


Samuel,

An implementation dependent management functionality, which is implemented
without bringing any interoperability problems can decide for the status of
subsystems. How this funtionality can be implemented is beyond the scope of
M3UA IMO.

RK types are flexible means, type of RKs is not limited by M3UA RFC.

      Tolga





             Tolga,

             It means peer M3UA can not recognize whether SSN is available
             or congested
             or unavailable...

             what do you mean by saying "... RK types flexible..."




        --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, 10 Jan 2003, TOLGA ASVEREN wrote:

        >
        > Samuel,
        >
        > What does it mean exactly that M3UA supports this or that RK? One
        can argue
        > about how suitable it is to use a certain RK type with M3UA but
        this IMO is
        > a different thing. I think the best is to leave RK types flexible
        and maybe
        > with one sentence to warn people about non-MTP3 RK types, that
        those might
        > need some management functionalitiy on SG.
        >
        >         Tolga
        >
        >
        >
        >      I think it would be good if we remove all SSN(sub system
        number)
        >      references from RFC or make a global statement in IG as "SSN
        will not
        >      be
        >      supported by RFC 3332 and wherever it is being referred it
        should be
        >      ignored"
        >
        >      --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
        >





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



From mailnull@www1.ietf.org  Fri Jan 10 02: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 CAA19792
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 02:38:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A7oZi06978
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 02:50:35 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A7oPJ06943;
	Fri, 10 Jan 2003 02:50:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A7ndJ06878
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 02:49:39 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19756
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 02:37:03 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFE50C6E1C.1B24BAFA-ONC2256CAA.0029AD0F@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 09:36:57 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 09:37:02 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>


Brian,

It is true such a management functionality will be implementation
dependent, but it MUST be compliant with M3UA RFC/IG, so that it does not
bring interoperability problems.

     Tolga



TOLGA,

TOLGA ASVEREN wrote:
(Fri, 10 Jan 2003 08:11:49)
>
> Samuel,
>
> What does it mean exactly that M3UA supports this or that RK? One can
argue
> about how suitable it is to use a certain RK type with M3UA but this IMO
is
> a different thing. I think the best is to leave RK types flexible and
maybe
> with one sentence to warn people about non-MTP3 RK types, that those
might
> need some management functionalitiy on SG.

Yes, some non-standard, non-iteroperable mangement functionality on the SG.
Which IMO is the same as saying that M3UA does not support 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  Fri Jan 10 02:45: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 CAA19917
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 02:45:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A7voI07229
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 02:57:50 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A7vEJ07207;
	Fri, 10 Jan 2003 02:57:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A7uWJ07182
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 02:56:32 -0500
Received: from telesoft.indts.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19879
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 02:43:54 -0500 (EST)
Received: from indts_fs.indts.com (indts_fs.indts.com [201.64.64.29])
	by telesoft.indts.com (8.11.6/8.11.6) with ESMTP id h0A7e3b02776
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 13:10:07 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <Y3BMLRYD>; Fri, 10 Jan 2003 13:17:36 +0530
Message-ID: <F73B646FCC01D5118F530002B32C3372DB3021@INDTS_FS>
From: Latha <latha@indts.com>
To: sigtran@ietf.org
Date: Fri, 10 Jan 2003 13:17:33 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] IUA -  ASP Active and ACTIVE ACK
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,
we have a doubt regarding the IIDs exchanged in the ASP Active and
ASP ACTIVE ACK 
If ASP Active is sent with a specific IId/IIds, is it mandatory for the SGF
to send ASP Active Ack with the specified IId/IIds. 
 
Or can it send the Ack without any IId. If that is the case then ASP has to
maintain the list of IIds on which the Active is sent. 
Also what should the action on MGC side if it receives ASP Active Ack
without any IId as a response for ASP Active sent with a specific IId/IIds.
thanks
latha
 

> -----Original Message-----
> From: TOLGA ASVEREN [mailto:TOLGA.ASVEREN@o2.com.tr]
> Sent: Friday, January 10, 2003 1:05 PM
> To: sigtran@ietf.org
> Subject: Re: [Sigtran] m3ua- IG
> 
> 
> 
> Samuel,
> 
> An implementation dependent management functionality, which 
> is implemented
> without bringing any interoperability problems can decide for 
> the status of
> subsystems. How this funtionality can be implemented is 
> beyond the scope of
> M3UA IMO.
> 
> RK types are flexible means, type of RKs is not limited by M3UA RFC.
> 
>       Tolga
> 
> 
> 
> 
> 
>              Tolga,
> 
>              It means peer M3UA can not recognize whether SSN 
> is available
>              or congested
>              or unavailable...
> 
>              what do you mean by saying "... RK types flexible..."
> 
> 
> 
> 
>         --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, 10 Jan 2003, TOLGA ASVEREN wrote:
> 
>         >
>         > Samuel,
>         >
>         > What does it mean exactly that M3UA supports this 
> or that RK? One
>         can argue
>         > about how suitable it is to use a certain RK type 
> with M3UA but
>         this IMO is
>         > a different thing. I think the best is to leave RK 
> types flexible
>         and maybe
>         > with one sentence to warn people about non-MTP3 RK 
> types, that
>         those might
>         > need some management functionalitiy on SG.
>         >
>         >         Tolga
>         >
>         >
>         >
>         >      I think it would be good if we remove all 
> SSN(sub system
>         number)
>         >      references from RFC or make a global statement 
> in IG as "SSN
>         will not
>         >      be
>         >      supported by RFC 3332 and wherever it is being 
> referred it
>         should be
>         >      ignored"
>         >
>         >      --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
>         >
> 
> 
> 
> 
> 
> _______________________________________________
> 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 Jan 10 03:04: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 DAA20201
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 03:04:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A8GaF08553
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 03:16:36 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A8GDJ08539;
	Fri, 10 Jan 2003 03:16:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A8FaJ08520
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 03:15:36 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20173
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 03:02:59 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:VTBGLz1o15M4oomfJr1LJCPgzkJZ3N75@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0A86HD05729;
	Fri, 10 Jan 2003 01:06:17 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0A86GM12407;
	Fri, 10 Jan 2003 01:06:16 -0700
Date: Fri, 10 Jan 2003 01:06:16 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110010616.E8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OFE50C6E1C.1B24BAFA-ONC2256CAA.0029AD0F@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OFE50C6E1C.1B24BAFA-ONC2256CAA.0029AD0F@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 09:36:57AM +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>

Tolga,

In the case of both SSN and CIC it is logically impossible to assure that such
a function can be compliant in that regard.

For CIC, this is because Circuit Supervision groups can always span Call
Processing groups.  (It is not possible to assign Call Processing CIC ranges
in such a fashion that Circuit Supervision groups are not broken, resulting in
the problems mentioned in the appendix).

For SSN, this is because SCCP management (SSN=0) functions span SSN
assignments.

If it were possible to do what you say (design a management functionality
which was implementation dependent without causing interoperability problems)
then I would say fine.  But as it is logically impossible to do so, M3UA
cannot be said to suport either.

--brian

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 09:36:57)
> 
> Brian,
> 
> It is true such a management functionality will be implementation
> dependent, but it MUST be compliant with M3UA RFC/IG, so that it does not
> bring interoperability problems.
> 
>      Tolga
> 
> 
> 
> TOLGA,
> 
> TOLGA ASVEREN wrote:
> (Fri, 10 Jan 2003 08:11:49)
> >
> > Samuel,
> >
> > What does it mean exactly that M3UA supports this or that RK? One can
> argue
> > about how suitable it is to use a certain RK type with M3UA but this IMO
> is
> > a different thing. I think the best is to leave RK types flexible and
> maybe
> > with one sentence to warn people about non-MTP3 RK types, that those
> might
> > need some management functionalitiy on SG.
> 
> Yes, some non-standard, non-iteroperable mangement functionality on the SG.
> Which IMO is the same as saying that M3UA does not support 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

-- 
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 Jan 10 03:07: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 DAA20238
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 03:07:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A8JFY08668
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 03:19:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A8J5J08649;
	Fri, 10 Jan 2003 03:19:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A8IAJ08605
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 03:18:10 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20219
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 03:05:33 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:XKIIQMvhleV058B5pv2FaehBj7q8SN/C@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0A88oD05757;
	Fri, 10 Jan 2003 01:08:50 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0A88o812451;
	Fri, 10 Jan 2003 01:08:50 -0700
Date: Fri, 10 Jan 2003 01:08:50 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Latha <latha@indts.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030110010850.F8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Latha <latha@indts.com>, sigtran@ietf.org
References: <F73B646FCC01D5118F530002B32C3372DB3021@INDTS_FS>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <F73B646FCC01D5118F530002B32C3372DB3021@INDTS_FS>; from latha@indts.com on Fri, Jan 10, 2003 at 01:17:33PM +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>

Latha,

Latha wrote:                                                                         (Fri, 10 Jan 2003 13:17:33)
> Hi,
> we have a doubt regarding the IIDs exchanged in the ASP Active and
> ASP ACTIVE ACK 
> If ASP Active is sent with a specific IId/IIds, is it mandatory for the SGF
> to send ASP Active Ack with the specified IId/IIds. 
>  
> Or can it send the Ack without any IId. If that is the case then ASP has to
> maintain the list of IIds on which the Active is sent. 
> Also what should the action on MGC side if it receives ASP Active Ack
> without any IId as a response for ASP Active sent with a specific IId/IIds.
> thanks
> latha
>  
Then the ASP could hardly be expected to correlate multiple ASPAC ACK
responses to multiple ASPAC requests.  If IID is placed in ASPAC, then
the SG MUST respond with IID in ASPAC ACK to be sure that the ASP can
correlate the response with the request.

--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  Fri Jan 10 03:20: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 DAA20558
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 03:20:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A8Wmi09372
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 03:32:48 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A8WPJ09356;
	Fri, 10 Jan 2003 03:32:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A8V7J09304
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 03:31:07 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20515
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 03:18:30 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF1A45EEA0.D6BC4333-ONC2256CAA.002C83B0@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 10:18:25 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 10:18:28 AM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0A8V7J09305
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


Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> Tolga,
>
> In the case of both SSN and CIC it is logically
> impossible to assure that such
> a function can be compliant in that regard.
>
> For CIC, this is because Circuit Supervision groups
> can always span Call
> Processing groups.  (It is not possible to assign
> Call Processing CIC ranges
> in such a fashion that Circuit Supervision groups
> are not broken, resulting in
> the problems mentioned in the appendix).
>
> For SSN, this is because SCCP management (SSN=0)
> functions span SSN
> assignments.
>
> If it were possible to do what you say (design a
> management functionality
> which was implementation dependent without causing
> interoperability problems)
> then I would say fine.  But as it is logically
> impossible to do so, M3UA
> cannot be said to suport either.
[TOLGA] For class0/class1 SCCP SSN based RKs seems to me doable. SSN state
can be kept on SG based on AS status, and also routing of management
messages probably won´t be very difficult for the ones destined for a
specific subsystem. A MSU containing SCCP congestion message needs to be
mapped to multiple DATA messages. One can argue that this violates some of
the paragraphs in RFC (the ones you pointed out, that one MSU should be
mapped to one DATA), but in fact this really does not bring a real
interoperability problem, because it does not require any special behaviour
from the peer. But still I would think a clarification sentence saying that
it might be necessary to map one MSU to multiple DATA to support non-MTP3
RKs, could be helpfull.

BTW, I agree for most of the changes you propose. IMO it is not a problem
to delete SSN examples but I prefer that RK types are kept flexible.
>
> --brian
>
> TOLGA ASVEREN wrote:
>                                 (Fri, 10 Jan 2003
> 09:36:57)
> >
> > Brian,
> >
> > It is true such a management functionality will be
> implementation
> > dependent, but it MUST be compliant with M3UA
> RFC/IG, so that it does not
> > bring interoperability problems.
> >
> >      Tolga
> >
> >
> >
> > TOLGA,
> >
> > TOLGA ASVEREN wrote:
> > (Fri, 10 Jan 2003 08:11:49)
> > >
> > > Samuel,
> > >
> > > What does it mean exactly that M3UA supports
> this or that RK? One can
> > argue
> > > about how suitable it is to use a certain RK
> type with M3UA but this IMO
> > is
> > > a different thing. I think the best is to leave
> RK types flexible and
> > maybe
> > > with one sentence to warn people about non-MTP3
> RK types, that those
> > might
> > > need some management functionalitiy on SG.
> >
> > Yes, some non-standard, non-iteroperable mangement
> functionality on the SG.
> > Which IMO is the same as saying that M3UA does not
> support 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
>
> --
> 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 mailnull@www1.ietf.org  Fri Jan 10 03:21: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 DAA20576
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 03:21:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A8XGm09412
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 03:33:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A8X3J09403;
	Fri, 10 Jan 2003 03:33:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A8WVJ09366
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 03:32:31 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20542
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 03:19:53 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0A8N9Ob000475;
	Fri, 10 Jan 2003 02:23:09 -0600 (CST)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0A8MRM27897;
	Fri, 10 Jan 2003 02:22:27 -0600 (CST)
Date: Fri, 10 Jan 2003 02:22:27 -0600 (CST)
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] m3ua- IG
In-Reply-To: <20030110000934.D8782@openss7.org>
Message-ID: <Pine.SOL.4.10.10301100134120.21736-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,

Ok, new changes hold good.

section 1.5.3

SCCP layer(an instance of the SS7 SCCP protocol layer) is placed above
M3UA layer and even performs GTT.
Once GTT is performed , nobody can restrict that result should be only
DPC, but result can be DPC/SSN also.

When you use M3UA , it conveys that your user-part services are
(including GTT) are offered remotely. So it causes little inconvenience
to view SCCP layer above M3UA.

--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, 10 Jan 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> The following IG entry would remove references to SSN and CIC from
> the document.  It this what you had in mind?
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                   (Thu, 09 Jan 2003 23:38:11)
> > 
> > I think it would be good if we remove all SSN(sub system number)
> > references from RFC or make a global statement in IG as "SSN will not be
> > supported by RFC 3332 and wherever it is being referred it should be
> > ignored"
> > 
> > --Samuel
> 
>  ------------------------------------------------------------------------
> 
>  3.16 SSN and CIC Routing Keys
> 
>  3.16.1 Description of the problem
> 
>     Use of SSN and CIC Routing Keys is inadequate in the specification
>     leading to non-interoperable solutions.
> 
>  3.16.2 Text changes to the document
> 
>     ---------
>     Old text: (Section 1.4.2.1)
>     ---------
> 
>     Possible SS7 address/routing information that comprise a Routing Key
>     entry includes, for example, the OPC, DPC, SIO found in the MTP3
>     routing label, or MTP3-User specific fields (such as the ISUP CIC,
>     SCCP subsystem number).  Some example Routing Keys are: the DPC
>     alone, the DPC/OPC combination, the DPC/OPC/CIC combination, or the
>     DPC/SSN combination.  The particular information used to define an
>     M3UA Routing Key is application and network dependent, and none of
>     the above examples are mandated.
> 
>     ---------
>     New text: (Section 1.4.2.1)
>     ---------
> 
>     Possible SS7 address/routing information that comprise a Routing Key
>     entry includes, for example, the OPC, DPC, SIO found in the MTP3
>     routing label.  Some example Routing Keys are: the DPC alone, the
>     DPC/OPC combination, or the DPC/OPC/SI combination.  The particular
>     information used to define an M3UA Routing Key is application and
>     network dependent, and none of the above examples are mandated.
> 
> 
>     ---------
>     Old text: (Section 1.4.2.2)
>     ---------
> 
>     Routing Keys SHOULD be unique in the sense that each received SS7
>     signalling message SHOULD have a full or partial match to a single
>     routing result. It is not necessary for the parameter range values
>     within a particular Routing Key to be contiguous.  For example, an AS
>     could be configured to support call processing for multiple ranges of
>     PSTN trunks that are not represented by contiguous CIC values.
> 
>     ---------
>     New text: (Section 1.4.2.2)
>     ---------
> 
>     Routing Keys SHOULD be unique in the sense that each received SS7
>     signalling message SHOULD have a full or partial match to a single
>     routing result. It is not necessary for the parameter range values
>     within a particular Routing Key to be contiguous.
> 
> 
> 
>     ---------
>     Old text: (Section 1.4.7)
>     ---------
> 
>     The M3UA layer at both the SGP and ASP also supports the assignment
>     of signalling traffic into streams within an SCTP association.
>     Traffic that requires sequencing SHOULD be assigned to the same
>     stream.  To accomplish this, MTP3-User traffic may be assigned to
>     individual streams based on, for example, the SLS value in the MTP3
>     Routing Label or the ISUP CIC assignment, subject of course to the
>     maximum number of streams supported by the underlying SCTP
>     association.
> 
>     ---------
>     New text: (Section 1.4.7)
>     ---------
> 
>     The M3UA layer at both the SGP and ASP also supports the assignment
>     of signalling traffic into streams within an SCTP association.
>     Traffic that requires sequencing SHOULD be assigned to the same
>     stream.  To accomplish this, MTP3-User traffic may be assigned to
>     individual streams based on, for example, the SLS value in the MTP3
>     Routing Label, subject of course to the maximum number of streams
>     supported by the underlying SCTP association.
> 
> 
> 
>     ---------
>     Old text: (Section 1.5.3)
>     ---------
> 
>     In this example, the SGP contains an instance of the SS7 SCCP
>     protocol layer that may, for example, perform the SCCP Global Title
>     Translation (GTT) function for messages logically addressed to the SG
>     SCCP.  If the result of a GTT for an SCCP message yields an SS7 DPC
>     or DPC/SSN address of an SCCP peer located in the IP domain, the
>     resulting MTP-TRANSFER request primitive is sent to the local M3UA-
>     resident network address translation and mapping function for ongoing
>     routing to the final IP destination.
> 
>     ---------
>     New text: (Section 1.5.3)
>     ---------
> 
>     In this example, the SGP contains an instance of the SS7 SCCP
>     protocol layer that may, for example, perform the SCCP Global Title
>     Translation (GTT) function for messages logically addressed to the SG
>     SCCP.  If the result of a GTT for an SCCP message yields an SS7 DPC
>     or DPC/SI address of an SCCP peer located in the IP domain, the
>     resulting MTP-TRANSFER request primitive is sent to the local M3UA-
>     resident network address translation and mapping function for ongoing
>     routing to the final IP destination.
> 
>     ---------
>     Old text: (Section 1.5.3)
>     ---------
> 
>     For internal SGP modeling purposes, this may be accomplished with the
>     use of an implementation-dependent nodal interworking function within
>     the SGP that effectively sits below the SCCP and routes MTP-TRANSFER
>     request/indication messages to/from both the MTP3 and the M3UA layer,
>     based on the SS7 DPC or DPC/SSN address information.  This nodal
>     interworking function has no visible peer protocol with either the
>     ASP or SEP.
> 
>     ---------
>     New text: (Section 1.5.3)
>     ---------
> 
>     For internal SGP modeling purposes, this may be accomplished with the
>     use of an implementation-dependent nodal interworking function within
>     the SGP that effectively sits below the SCCP and routes MTP-TRANSFER
>     request/indication messages to/from both the MTP3 and the M3UA layer,
>     based on the SS7 DPC or DPC/SI address information.  This nodal
>     interworking function has no visible peer protocol with either the
>     ASP or SEP.
> 
> 
> 
>     ---------
>     Old text: (Section 3.2)
>     ---------
> 
>          Congestion Indications                0x0205
>          Concerned Destination                 0x0206
>          Routing Key                           0x0207
>          Registration Result                   0x0208
>          Deregistration Result                 0x0209
>          Local_Routing Key Identifier          0x020a
>          Destination Point Code                0x020b
>          Service Indicators                    0x020c
>          Reserved                              0x020d
>          Originating Point Code List           0x020e
>          Circuit Range                         0x020f
>          Protocol Data                         0x0210
>          Reserved                              0x0211
>          Registration Status                   0x0212
>          Deregistration Status                 0x0213
> 
>     ---------
>     New text: (Section 3.2)
>     ---------
> 
>          Congestion Indications                0x0205
>          Concerned Destination                 0x0206
>          Routing Key                           0x0207
>          Registration Result                   0x0208
>          Deregistration Result                 0x0209
>          Local_Routing Key Identifier          0x020a
>          Destination Point Code                0x020b
>          Service Indicators                    0x020c
>          Reserved                              0x020d
>          Originating Point Code List           0x020e
>          Protocol Data                         0x0210
>          Reserved                              0x0211
>          Registration Status                   0x0212
>          Deregistration Status                 0x0213
> 
> 
> 
>     ---------
>     Old text: (Section 3.6.1)
>     ---------
> 
>        |                  Traffic Mode Type (optional)                 |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                     Destination Point Code                    |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                  Network Appearance (optional)                |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                  Service Indicators (optional)                |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |              Originating Point Code List (optional)           |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                   Circuit Range List (optional)               |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        \                                                               \
>        /                              ...                              /
>        \                                                               \
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                     Destination Point Code                    |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                  Service Indicators (optional)                |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |              Originating Point Code List (optional)           |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                   Circuit Range List (optional)               |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>  
>        Note: The Destination Point Code, Service Indicators, Originating
>        Point Code List and Circuit Range List parameters MAY be repeated
>        as a grouping within the Routing Key parameter, in the structure
>        shown above.
> 
>     ---------
>     New text: (Section 3.6.1)
>     ---------
> 
>        |                  Traffic Mode Type (optional)                 |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                     Destination Point Code                    |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                  Network Appearance (optional)                |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                  Service Indicators (optional)                |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |              Originating Point Code List (optional)           |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        \                                                               \
>        /                              ...                              /
>        \                                                               \
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                     Destination Point Code                    |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                  Service Indicators (optional)                |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |              Originating Point Code List (optional)           |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>  
>        Note: The Destination Point Code, Service Indicators, and
>        Originating Point Code List parameters MAY be repeated as a
>        grouping within the Routing Key parameter, in the structure shown
>        above.
> 
>     ---------
>     Old text: (Section 3.6.1)
>     ---------
> 
>     Circuit Range:
>  
>        An ISUP controlled circuit is uniquely identified by the SS7 OPC,
>        DPC and CIC value.  For the purposes of identifying Circuit Ranges
>        in an M3UA Routing Key, the optional Circuit Range parameter
>        includes one or more circuit ranges, each identified by an OPC and
>        Upper/Lower CIC value.  The DPC is implicit as it is mandatory and
>        already included in the DPC parameter of the Routing Key.  The
>        absence of the Circuit Range parameter in the Routing Key
>        indicates the use of any Circuit Range values, in the case of
>        ISUP/TUP traffic.  The Origination Point Code is encoded the same
>        as the Destination Point Code parameter, while the CIC values are
>        16-bit integers.
> 
>     ---------
>     New text: (Section 3.6.1)
>     ---------
> 
>     (none)
>  
>     ---------
>     Old text: (Section 3.6.1)
>     ---------
> 
>     The Circuit Range format is as follows:
>  
>         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 = 0x020f        |              Length           |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |    Mask = 0   |          Origination Point Code #1            |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |       Lower CIC Value #1      |      Upper CIC Value #1       |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |    Mask = 0   |          Origination Point Code #2            |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |       Lower CIC Value #2      |      Upper CIC Value #2       |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        /                              ...                              /
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |    Mask = 0   |          Origination Point Code #n            |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |       Lower CIC Value #n      |      Upper CIC Value #n       |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>     ---------
>     New text: (Section 3.6.1)
>     ---------
> 
>     (none)
>  
> 
> 
>     ---------
>     Old text: (Section 3.7.1)
>     ---------
> 
>        An Application Server Process may be configured to process traffic
>        for more than one logical Application Server.  From the
>        perspective of an ASP, a Routing Context defines a range of
>        signalling traffic that the ASP is currently configured to receive
>        from the SGP.  For example, an ASP could be configured to support
>        call processing for multiple ranges of PSTN trunks and therefore
>        receive related signalling traffic, identified by separate SS7
>        DPC/OPC/CIC ranges.
> 
>     ---------
>     New text: (Section 3.7.1)
>     ---------
> 
>        An Application Server Process may be configured to process traffic
>        for more than one logical Application Server.  From the
>        perspective of an ASP, a Routing Context defines a range of
>        signalling traffic that the ASP is currently configured to receive
>        from the SGP.  For example, an ASP could be configured to support
>        call processing for multiple ranges of PSTN trunks and therefore
>        receive related signalling traffic, identified by separate SS7
>        DPC/OPC/SI ranges.
> 
> 
> 
>     ---------
>     Old text: (Section 4.4.1)
>     ---------
> 
>     If an SGP determines that one or more of the Routing Key parameters
>     are not supported for the purpose of creating new Routing Key
>     entries, the SGP returns a Registration Response message to the ASP,
>     containing a Registration Result "Error - Unsupported RK parameter
>     field".  This result MAY be used if, for example, the SGP does not
>     support RK Circuit Range Lists in a Routing Key because the SGP does
>     not support ISUP traffic, or does not provide CIC range granularity.
> 
>     ---------
>     New text: (Section 4.4.1)
>     ---------
> 
>     If an SGP determines that one or more of the Routing Key parameters
>     are not supported for the purpose of creating new Routing Key
>     entries, the SGP returns a Registration Response message to the ASP,
>     containing a Registration Result "Error - Unsupported RK parameter
>     field".
> 
> 
> 
>     ---------
>     Old text: (Section A.2.1)
>     ---------
> 
>     For example, where Application Servers are defined using ranges of
>     ISUP CIC values, the Operator is implicitly splitting up control of
>     the related circuit groups.  Some CIC value range assignments may
>     interfere with ISUP circuit group management procedures.
> 
>     ---------
>     New text: (Section A.2.1)
>     ---------
> 
>     (none)
>  
>  3.16.3 Solution description
> 
>     The removal of reference to SSN and CIC used in Routing Keys as well
>     as removal of Circuit Range from the Routing Key parameter removes
>     the unclear text from the specification.
> 
>  ------------------------------------------------------------------------
> 
> -- 
> 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 mailnull@www1.ietf.org  Fri Jan 10 03:33: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 DAA20772
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 03:33:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A8jVC10568
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 03:45:31 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A8jDJ10555;
	Fri, 10 Jan 2003 03:45:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A8iTJ10519
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 03:44:29 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20759
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 03:31:52 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0A8Z9OZ001536;
	Fri, 10 Jan 2003 02:35:09 -0600 (CST)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0A8YGM01633;
	Fri, 10 Jan 2003 02:34:16 -0600 (CST)
Date: Fri, 10 Jan 2003 02:34:16 -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] m3ua- IG
In-Reply-To: <OF9082A54F.15EAA27D-ONC2256CAA.002905F5@LocalDomain>
Message-ID: <Pine.SOL.4.10.10301100229090.22103-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>


Tolga,
 
M3UA RFC must conflict with flexible RKs.If it allows flexible RKs
then somebody may develop M3UA stack with SSN and others may develop
M3UA stack with CIC...

So finally no standards are followed to define RK type which will
lead into confusion in interoperability.

--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, 10 Jan 2003, TOLGA ASVEREN wrote:

> 
> Samuel,
> 
> An implementation dependent management functionality, which is implemented
> without bringing any interoperability problems can decide for the status of
> subsystems. How this funtionality can be implemented is beyond the scope of
> M3UA IMO.
> 
> RK types are flexible means, type of RKs is not limited by M3UA RFC.
> 
>       Tolga
> 
> 
> 
> 
> 
>              Tolga,
> 
>              It means peer M3UA can not recognize whether SSN is available
>              or congested
>              or unavailable...
> 
>              what do you mean by saying "... RK types flexible..."
> 
> 
> 
> 
>         --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, 10 Jan 2003, TOLGA ASVEREN wrote:
> 
>         >
>         > Samuel,
>         >
>         > What does it mean exactly that M3UA supports this or that RK? One
>         can argue
>         > about how suitable it is to use a certain RK type with M3UA but
>         this IMO is
>         > a different thing. I think the best is to leave RK types flexible
>         and maybe
>         > with one sentence to warn people about non-MTP3 RK types, that
>         those might
>         > need some management functionalitiy on SG.
>         >
>         >         Tolga
>         >
>         >
>         >
>         >      I think it would be good if we remove all SSN(sub system
>         number)
>         >      references from RFC or make a global statement in IG as "SSN
>         will not
>         >      be
>         >      supported by RFC 3332 and wherever it is being referred it
>         should be
>         >      ignored"
>         >
>         >      --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
>         >
> 
> 
> 
> 
> 
> _______________________________________________
> 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 Jan 10 03:37:25 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 DAA20833
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 03:37:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A8nUC10743
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 03:49:30 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A8nCJ10726;
	Fri, 10 Jan 2003 03:49:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A8mEJ10694
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 03:48:15 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20813
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 03:35:37 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:7vVYibj5QJ/nUp3DN8zBfXH3BRxz7Y2c@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0A8csD06223;
	Fri, 10 Jan 2003 01:38:54 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0A8csh13071;
	Fri, 10 Jan 2003 01:38:54 -0700
Date: Fri, 10 Jan 2003 01:38:54 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110013854.G8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF1A45EEA0.D6BC4333-ONC2256CAA.002C83B0@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF1A45EEA0.D6BC4333-ONC2256CAA.002C83B0@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 10:18:25AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 10:18:25)
> 
> [TOLGA] For class0/class1 SCCP SSN based RKs seems to me doable. SSN state
> can be kept on SG based on AS status, and also routing of management
> messages probably won´t be very difficult for the ones destined for a
> specific subsystem.

Routing of management messages is impossible in an interoperable way.
Where they should go is niether specified nor obvious from the point
of view of using SSN for routing.  The ASP must know where and when it
will receive SCCP management messages to be interoperable.  M3UA does
not specify this, and so SSN routing keys are not supported.

> A MSU containing SCCP congestion message needs to be
> mapped to multiple DATA messages. One can argue that this violates some of
> the paragraphs in RFC (the ones you pointed out, that one MSU should be
> mapped to one DATA), but in fact this really does not bring a real
> interoperability problem, because it does not require any special behaviour
> from the peer. But still I would think a clarification sentence saying that
> it might be necessary to map one MSU to multiple DATA to support non-MTP3
> RKs, could be helpfull.
> 
> BTW, I agree for most of the changes you propose. IMO it is not a problem
> to delete SSN examples but I prefer that RK types are kept flexible.

Then the IG changes I proposed should meet with your approval.

--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  Fri Jan 10 03:39: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 DAA20892
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 03:39:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A8pgx10860
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 03:51:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A8pWJ10852;
	Fri, 10 Jan 2003 03:51:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A8okJ10811
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 03:50:46 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20857
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 03:38:09 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFE5FC33B7.6169D0F3-ONC2256CAA.002F26BD@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 10:38:04 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 10:38:07 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>


Samuel,

So, what is wrong with this? Those are features of each separate SG
products. Should we try to standardize the feature set supported by each
and every SG?

      Tolga





Tolga,

M3UA RFC must conflict with flexible RKs.If it allows flexible RKs
then somebody may develop M3UA stack with SSN and others may develop
M3UA stack with CIC...

So finally no standards are followed to define RK type which will
lead into confusion in interoperability.

--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, 10 Jan 2003, TOLGA ASVEREN wrote:

>
> Samuel,
>
> An implementation dependent management functionality, which is
implemented
> without bringing any interoperability problems can decide for the status
of
> subsystems. How this funtionality can be implemented is beyond the scope
of
> M3UA IMO.
>
> RK types are flexible means, type of RKs is not limited by M3UA RFC.
>
>       Tolga
>
>
>
>
>
>              Tolga,
>
>              It means peer M3UA can not recognize whether SSN is
available
>              or congested
>              or unavailable...
>
>              what do you mean by saying "... RK types flexible..."
>
>
>
>
>         --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, 10 Jan 2003, TOLGA ASVEREN wrote:
>
>         >
>         > Samuel,
>         >
>         > What does it mean exactly that M3UA supports this or that RK?
One
>         can argue
>         > about how suitable it is to use a certain RK type with M3UA but
>         this IMO is
>         > a different thing. I think the best is to leave RK types
flexible
>         and maybe
>         > with one sentence to warn people about non-MTP3 RK types, that
>         those might
>         > need some management functionalitiy on SG.
>         >
>         >         Tolga
>         >
>         >
>         >
>         >      I think it would be good if we remove all SSN(sub system
>         number)
>         >      references from RFC or make a global statement in IG as
"SSN
>         will not
>         >      be
>         >      supported by RFC 3332 and wherever it is being referred it
>         should be
>         >      ignored"
>         >
>         >      --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
>         >
>
>
>
>
>
> _______________________________________________
> 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 Jan 10 03:48: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 DAA21034
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 03:48:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A90Zu11204
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 04:00:35 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A90GJ11190;
	Fri, 10 Jan 2003 04:00:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A8xpJ11131
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 03:59:52 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20985
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 03:47:14 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF6AB53B3A.67031477-ONC2256CAA.002F980F@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 10:47:09 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 10:47:13 AM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0A8xqJ11132
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


Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> TOLGA,
>
> TOLGA ASVEREN wrote:
>                                 (Fri, 10 Jan 2003
> 10:18:25)
> >
> > [TOLGA] For class0/class1 SCCP SSN based RKs seems
> to me doable. SSN state
> > can be kept on SG based on AS status, and also
> routing of management
> > messages probably won´t be very difficult for the
> ones destined for a
> > specific subsystem.
>
> Routing of management messages is impossible in an
> interoperable way.
> Where they should go is niether specified nor
> obvious from the point
> of view of using SSN for routing.  The ASP must know
> where and when it
> will receive SCCP management messages to be
> interoperable.  M3UA does
> not specify this, and so SSN routing keys are not
> supported.
[TOLGA] Why should ASP know anything special not defined in RFC? It serves
an AS for a specific DPC+SSN and it is SGs responsibility to distribute
messages properly -including management messages-. One can look to SCCP
management message and decide for which SSN it is send.
>
> > A MSU containing SCCP congestion message needs to
> be
> > mapped to multiple DATA messages. One can argue
> that this violates some of
> > the paragraphs in RFC (the ones you pointed out,
> that one MSU should be
> > mapped to one DATA), but in fact this really does
> not bring a real
> > interoperability problem, because it does not
> require any special behaviour
> > from the peer. But still I would think a
> clarification sentence saying that
> > it might be necessary to map one MSU to multiple
> DATA to support non-MTP3
> > RKs, could be helpfull.
> >
> > BTW, I agree for most of the changes you propose.
> IMO it is not a problem
> > to delete SSN examples but I prefer that RK types
> are kept flexible.
>
> Then the IG changes I proposed should meet with your
> approval.
[TOLGA] I don´t think the changes require any approval from me :) But yes,
I don´t think, they bring any restriction.
>
> --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 mailnull@www1.ietf.org  Fri Jan 10 03:52: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 DAA21147
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 03:52:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A94hG11759
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 04:04:43 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A94CJ11719;
	Fri, 10 Jan 2003 04:04:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A91TJ11263
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 04:01:33 -0500
Received: from tank.fr.ulticom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21057
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 03:48:48 -0500 (EST)
Received: from PCGASTAUDL (pc-gastaud-l.fr.ulticom.com [172.26.32.87])
	by tank.fr.ulticom.com (8.8.8+Sun/8.8.8) with SMTP id JAA12768;
	Fri, 10 Jan 2003 09:51:53 +0100 (MET)
From: "Valerie Gastaud" <valerie.gastaud@ulticom.com>
To: <bidulock@openss7.org>, "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Cc: <sigtran@ietf.org>
Subject: RE: [Sigtran] m3ua- IG
Date: Fri, 10 Jan 2003 10:16:12 +0100
Message-ID: <NDBBIHAOCKGAMIKNLALOKEBCDKAA.valerie.gastaud@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
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.2600.0000
Importance: Normal
In-Reply-To: <20030110013854.G8782@openss7.org>
Content-Transfer-Encoding: 8bit
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

Brian,


TOLGA,

TOLGA ASVEREN wrote:
(Fri, 10 Jan 2003 10:18:25)
>
> [TOLGA] For class0/class1 SCCP SSN based RKs seems to me doable. SSN state
> can be kept on SG based on AS status, and also routing of management
> messages probably won´t be very difficult for the ones destined for a
> specific subsystem.

Routing of management messages is impossible in an interoperable way.
Where they should go is niether specified nor obvious from the point
of view of using SSN for routing.  The ASP must know where and when it
will receive SCCP management messages to be interoperable.  M3UA does
not specify this, and so SSN routing keys are not supported.

VG: If all the ASPs register for SSN=0 in broadcast mode, they will all
receive
SCCP management messages.


Valerie

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



From mailnull@www1.ietf.org  Fri Jan 10 03:59: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 DAA21287
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 03:59:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A9BmI12806
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 04:11:48 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9BDJ12763;
	Fri, 10 Jan 2003 04:11:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9AYJ12707
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 04:10:34 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21241
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 03:57:56 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0A91COZ003372;
	Fri, 10 Jan 2003 03:01:12 -0600 (CST)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0A90PM09977;
	Fri, 10 Jan 2003 03:00:25 -0600 (CST)
Date: Fri, 10 Jan 2003 03:00:25 -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] m3ua- IG
In-Reply-To: <OFE5FC33B7.6169D0F3-ONC2256CAA.002F26BD@LocalDomain>
Message-ID: <Pine.SOL.4.10.10301100248530.22103-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>


Tolga,

RK with SSN, RK with CIC - they are not features of SG.
Total RFC strength is on RK.If RK is flexible then why 
RFC would say RK's mandatory and optional parameter,
It could have reserved some space and could have said
'this space can be used for any purpose'.

--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, 10 Jan 2003, TOLGA ASVEREN wrote:

> 
> Samuel,
> 
> So, what is wrong with this? Those are features of each separate SG
> products. Should we try to standardize the feature set supported by each
> and every SG?
> 
>       Tolga
> 
> 
> 
> 
> 
> Tolga,
> 
> M3UA RFC must conflict with flexible RKs.If it allows flexible RKs
> then somebody may develop M3UA stack with SSN and others may develop
> M3UA stack with CIC...
> 
> So finally no standards are followed to define RK type which will
> lead into confusion in interoperability.
> 
> --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, 10 Jan 2003, TOLGA ASVEREN wrote:
> 
> >
> > Samuel,
> >
> > An implementation dependent management functionality, which is
> implemented
> > without bringing any interoperability problems can decide for the status
> of
> > subsystems. How this funtionality can be implemented is beyond the scope
> of
> > M3UA IMO.
> >
> > RK types are flexible means, type of RKs is not limited by M3UA RFC.
> >
> >       Tolga
> >
> >
> >
> >
> >
> >              Tolga,
> >
> >              It means peer M3UA can not recognize whether SSN is
> available
> >              or congested
> >              or unavailable...
> >
> >              what do you mean by saying "... RK types flexible..."
> >
> >
> >
> >
> >         --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, 10 Jan 2003, TOLGA ASVEREN wrote:
> >
> >         >
> >         > Samuel,
> >         >
> >         > What does it mean exactly that M3UA supports this or that RK?
> One
> >         can argue
> >         > about how suitable it is to use a certain RK type with M3UA but
> >         this IMO is
> >         > a different thing. I think the best is to leave RK types
> flexible
> >         and maybe
> >         > with one sentence to warn people about non-MTP3 RK types, that
> >         those might
> >         > need some management functionalitiy on SG.
> >         >
> >         >         Tolga
> >         >
> >         >
> >         >
> >         >      I think it would be good if we remove all SSN(sub system
> >         number)
> >         >      references from RFC or make a global statement in IG as
> "SSN
> >         will not
> >         >      be
> >         >      supported by RFC 3332 and wherever it is being referred it
> >         should be
> >         >      ignored"
> >         >
> >         >      --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
> >         >
> >
> >
> >
> >
> >
> > _______________________________________________
> > 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 Jan 10 04:06: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 EAA21473
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 04:06:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A9IeW13065
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 04:18:40 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9IAJ13043;
	Fri, 10 Jan 2003 04:18:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9HNJ13015
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 04:17:23 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21441
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 04:04:45 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:8ofgHMD910I2k06W0a6JOwKL37N7ILKK@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0A981D06708;
	Fri, 10 Jan 2003 02:08:01 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0A981T13812;
	Fri, 10 Jan 2003 02:08:01 -0700
Date: Fri, 10 Jan 2003 02:08:01 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Valerie Gastaud <valerie.gastaud@ulticom.com>
Cc: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110020801.I8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Valerie Gastaud <valerie.gastaud@ulticom.com>,
	TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <20030110013854.G8782@openss7.org> <NDBBIHAOCKGAMIKNLALOKEBCDKAA.valerie.gastaud@ulticom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <NDBBIHAOCKGAMIKNLALOKEBCDKAA.valerie.gastaud@ulticom.com>; from valerie.gastaud@ulticom.com on Fri, Jan 10, 2003 at 10:16:12AM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

Valerie,

Valerie Gastaud wrote:                                                             (Fri, 10 Jan 2003 10:16:12)
> Brian,
> 
> 
> TOLGA,
> 
> TOLGA ASVEREN wrote:
> (Fri, 10 Jan 2003 10:18:25)
> >
> > [TOLGA] For class0/class1 SCCP SSN based RKs seems to me doable. SSN state
> > can be kept on SG based on AS status, and also routing of management
> > messages probably won´t be very difficult for the ones destined for a
> > specific subsystem.
> 
> Routing of management messages is impossible in an interoperable way.
> Where they should go is niether specified nor obvious from the point
> of view of using SSN for routing.  The ASP must know where and when it
> will receive SCCP management messages to be interoperable.  M3UA does
> not specify this, and so SSN routing keys are not supported.
> 
> VG: If all the ASPs register for SSN=0 in broadcast mode, they will all
> receive SCCP management messages.

Then somewhere that would have to be specified, which it is not.  My point was
that the SG cannot do this without the ASP also having to know something of
the implementation.  Therefore, for interoperability it must be specified.

Tolga was trying to say that this could be implemented on the SG only without
the ASP even knowing about it, and without any procedures needing to be
specified for interoperability.  Your suggestion does not alter the case that
specification would be necessary for interoperability.

Also, if what you want to do is send particular SSNs to particular ASPs,
routing on SI and loadsharing on SSN is most appropriate.  Routing keys
are worthless in this regard do to underspecification in the 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 mailnull@www1.ietf.org  Fri Jan 10 04:08: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 EAA21514
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 04:08:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A9KRV13158
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 04:20:27 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9KAJ13141;
	Fri, 10 Jan 2003 04:20:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9JnJ13090
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 04:19:49 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21488
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 04:07:10 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFABD9E7CE.932B9405-ONC2256CAA.00316087@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 11:07:06 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 11:07:09 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>


Samuel,

First of all I consider whether a SG supports this or that type of RK as a
feature of that SG, not as a property of M3UA protocol. M3UA does not work
assuming some special RK type.
IMO, the only place where RK type comes into play is dynamic registration.
And this is natural, because there one tells about the type of the RK. One
has to define some types for registration otherwise how can you tell your
peer what you want? Also please note, RK type not supported case is
handled, so it is not a problem if an ASP asks to register for a SSN based
RK to a SG, which does not support it.

     Tolga



Tolga,

RK with SSN, RK with CIC - they are not features of SG.
Total RFC strength is on RK.If RK is flexible then why
RFC would say RK's mandatory and optional parameter,
It could have reserved some space and could have said
'this space can be used for any purpose'.

--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, 10 Jan 2003, TOLGA ASVEREN wrote:

>
> Samuel,
>
> So, what is wrong with this? Those are features of each separate SG
> products. Should we try to standardize the feature set supported by each
> and every SG?
>
>       Tolga
>
>
>
>
>
> Tolga,
>
> M3UA RFC must conflict with flexible RKs.If it allows flexible RKs
> then somebody may develop M3UA stack with SSN and others may develop
> M3UA stack with CIC...
>
> So finally no standards are followed to define RK type which will
> lead into confusion in interoperability.
>
> --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, 10 Jan 2003, TOLGA ASVEREN wrote:
>
> >
> > Samuel,
> >
> > An implementation dependent management functionality, which is
> implemented
> > without bringing any interoperability problems can decide for the
status
> of
> > subsystems. How this funtionality can be implemented is beyond the
scope
> of
> > M3UA IMO.
> >
> > RK types are flexible means, type of RKs is not limited by M3UA RFC.
> >
> >       Tolga
> >
> >
> >
> >
> >
> >              Tolga,
> >
> >              It means peer M3UA can not recognize whether SSN is
> available
> >              or congested
> >              or unavailable...
> >
> >              what do you mean by saying "... RK types flexible..."
> >
> >
> >
> >
> >         --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, 10 Jan 2003, TOLGA ASVEREN wrote:
> >
> >         >
> >         > Samuel,
> >         >
> >         > What does it mean exactly that M3UA supports this or that RK?
> One
> >         can argue
> >         > about how suitable it is to use a certain RK type with M3UA
but
> >         this IMO is
> >         > a different thing. I think the best is to leave RK types
> flexible
> >         and maybe
> >         > with one sentence to warn people about non-MTP3 RK types,
that
> >         those might
> >         > need some management functionalitiy on SG.
> >         >
> >         >         Tolga
> >         >
> >         >
> >         >
> >         >      I think it would be good if we remove all SSN(sub system
> >         number)
> >         >      references from RFC or make a global statement in IG as
> "SSN
> >         will not
> >         >      be
> >         >      supported by RFC 3332 and wherever it is being referred
it
> >         should be
> >         >      ignored"
> >         >
> >         >      --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
> >         >
> >
> >
> >
> >
> >
> > _______________________________________________
> > 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 Jan 10 04:11: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 EAA21577
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 04:11:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A9NX213303
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 04:23:33 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9N9J13283;
	Fri, 10 Jan 2003 04:23:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9MFJ13249
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 04:22:15 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21542
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 04:09:37 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Mz0HclGfUHb24v3iAeHakTq7bEUfoXzz@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0A9CsD06764;
	Fri, 10 Jan 2003 02:12:54 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0A9Csh13973;
	Fri, 10 Jan 2003 02:12:54 -0700
Date: Fri, 10 Jan 2003 02:12:53 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110021253.J8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF6AB53B3A.67031477-ONC2256CAA.002F980F@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF6AB53B3A.67031477-ONC2256CAA.002F980F@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 10:47:09AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 10:47:09)
> 
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > TOLGA,
> >
> > TOLGA ASVEREN wrote:
> >                                 (Fri, 10 Jan 2003
> > 10:18:25)
> > >
> > > [TOLGA] For class0/class1 SCCP SSN based RKs seems
> > to me doable. SSN state
> > > can be kept on SG based on AS status, and also
> > routing of management
> > > messages probably won´t be very difficult for the
> > ones destined for a
> > > specific subsystem.
> >
> > Routing of management messages is impossible in an
> > interoperable way.
> > Where they should go is niether specified nor
> > obvious from the point
> > of view of using SSN for routing.  The ASP must know
> > where and when it
> > will receive SCCP management messages to be
> > interoperable.  M3UA does
> > not specify this, and so SSN routing keys are not
> > supported.
> [TOLGA] Why should ASP know anything special not defined in RFC? It serves
> an AS for a specific DPC+SSN and it is SGs responsibility to distribute
> messages properly -including management messages-. One can look to SCCP
> management message and decide for which SSN it is send.

That would not be using the SSN in the messaage (which is SSN=0), that
would be using the ASSN.  Also, you would need to use the APC rather than
the DPC in the message.  These things are not even mentioned for M3UA.

Also, where does it say that the ASP registered with SSN=5 is the "rignt"
place to send SCCP management messages?

--brian


> >
> > > A MSU containing SCCP congestion message needs to
> > be
> > > mapped to multiple DATA messages. One can argue
> > that this violates some of
> > > the paragraphs in RFC (the ones you pointed out,
> > that one MSU should be
> > > mapped to one DATA), but in fact this really does
> > not bring a real
> > > interoperability problem, because it does not
> > require any special behaviour
> > > from the peer. But still I would think a
> > clarification sentence saying that
> > > it might be necessary to map one MSU to multiple
> > DATA to support non-MTP3
> > > RKs, could be helpfull.
> > >
> > > BTW, I agree for most of the changes you propose.
> > IMO it is not a problem
> > > to delete SSN examples but I prefer that RK types
> > are kept flexible.
> >
> > Then the IG changes I proposed should meet with your
> > approval.
> [TOLGA] I don´t think the changes require any approval from me :) But yes,
> I don´t think, they bring any restriction.

Then do you support them?

--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  Fri Jan 10 04:16:52 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 EAA21718
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 04:16:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A9Swh13564
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 04:28:58 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9S6J13520;
	Fri, 10 Jan 2003 04:28:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9RVJ13484
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 04:27:31 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21652
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 04:14:53 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0A9I9aN015815;
	Fri, 10 Jan 2003 03:18:10 -0600 (CST)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0A9HBM15471;
	Fri, 10 Jan 2003 03:17:11 -0600 (CST)
Date: Fri, 10 Jan 2003 03:17:11 -0600 (CST)
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] m3ua- IG
In-Reply-To: <20030110014155.H8782@openss7.org>
Message-ID: <Pine.SOL.4.10.10301100304590.22103-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id h0A9RVJ13485
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


Brian,

Will this full-blown SCCP perform GTT?.Of course, it performs.
But what will happen if the result is DPC+SSN?


To avoid this problem a node should support SUA or we should
perform GTT at remote peer.

--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, 10 Jan 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> In section 1.5.3, this is a full-blown SCCP above M3UA.  I don't
> think this section needs any modification.
> 
> --brian
> 
> On Fri, 10 Jan 2003, Samuel Dur D. Jeyaseelan wrote:
> 
> > 
> > Brian,
> > 
> > Ok, new changes hold good.
> > 
> > section 1.5.3
> > 
> > SCCP layer(an instance of the SS7 SCCP protocol layer) is placed above
> > M3UA layer and even performs GTT.
> > Once GTT is performed , nobody can restrict that result should be only
> > DPC, but result can be DPC/SSN also.
> > 
> > When you use M3UA , it conveys that your user-part services are
> > (including GTT) are offered remotely. So it causes little inconvenience
> > to view SCCP layer above M3UA.
> > 
> > --Samuel
> > 
> 
> -- 
> 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  Fri Jan 10 04:30: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 EAA22024
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 04:30:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A9gfD15233
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 04:42:41 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9gJJ15202;
	Fri, 10 Jan 2003 04:42:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9fKJ15121
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 04:41:20 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21989
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 04:28:41 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:XFhd9HdoVisfskMuBTgYzMyGwdBiIwJK@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0A9VwD07095;
	Fri, 10 Jan 2003 02:31:58 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0A9VwR14595;
	Fri, 10 Jan 2003 02:31:58 -0700
Date: Fri, 10 Jan 2003 02:31:58 -0700
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] m3ua- IG
Message-ID: <20030110023158.K8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030110014155.H8782@openss7.org> <Pine.SOL.4.10.10301100304590.22103-100000@sun2594.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10301100304590.22103-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Jan 10, 2003 at 03:17:11AM -0600
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

Samuel,

Huh?  This is a normal MTP-User.  When the result is DPC/SSN it
formulates a message and sends it to the DPC using a MTP-TRANSFER
primitive to the M3UA acting as MTP Level 3.  There is no need
to support SSN RKs to acheive this.  SCCP is just a normal MTP
User in this case.  M3UA already supports MTP Users.

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 03:17:11)
> 
> Brian,
> 
> Will this full-blown SCCP perform GTT?.Of course, it performs.
> But what will happen if the result is DPC+SSN?
> 
> 
> To avoid this problem a node should support SUA or we should
> perform GTT at remote peer.
> 
> --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > In section 1.5.3, this is a full-blown SCCP above M3UA.  I don't
> > think this section needs any modification.
> > 
> > --brian
> > 
> > On Fri, 10 Jan 2003, Samuel Dur D. Jeyaseelan wrote:
> > 
> > > 
> > > Brian,
> > > 
> > > Ok, new changes hold good.
> > > 
> > > section 1.5.3
> > > 
> > > SCCP layer(an instance of the SS7 SCCP protocol layer) is placed above
> > > M3UA layer and even performs GTT.
> > > Once GTT is performed , nobody can restrict that result should be only
> > > DPC, but result can be DPC/SSN also.
> > > 
> > > When you use M3UA , it conveys that your user-part services are
> > > (including GTT) are offered remotely. So it causes little inconvenience
> > > to view SCCP layer above M3UA.
> > > 
> > > --Samuel
> > > 
> > 
> > -- 
> > 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 ¦
> > 

-- 
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 Jan 10 04:30: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 EAA22026
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 04:30:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A9gkO15246
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 04:42:46 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9gUJ15225;
	Fri, 10 Jan 2003 04:42:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9fxJ15140
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 04:41:59 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22001
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 04:29:19 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF89451CE4.D364520F-ONC2256CAA.00339110@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 11:29:14 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 11:29:18 AM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0A9fxJ15141
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


Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> TOLGA,
>
> TOLGA ASVEREN wrote:
>                                 (Fri, 10 Jan 2003
> 10:47:09)
> >
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > > TOLGA,
> > >
> > > TOLGA ASVEREN wrote:
> > >                                 (Fri, 10 Jan
> 2003
> > > 10:18:25)
> > > >
> > > > [TOLGA] For class0/class1 SCCP SSN based RKs
> seems
> > > to me doable. SSN state
> > > > can be kept on SG based on AS status, and also
> > > routing of management
> > > > messages probably won´t be very difficult for
> the
> > > ones destined for a
> > > > specific subsystem.
> > >
> > > Routing of management messages is impossible in
> an
> > > interoperable way.
> > > Where they should go is niether specified nor
> > > obvious from the point
> > > of view of using SSN for routing.  The ASP must
> know
> > > where and when it
> > > will receive SCCP management messages to be
> > > interoperable.  M3UA does
> > > not specify this, and so SSN routing keys are
> not
> > > supported.
> > [TOLGA] Why should ASP know anything special not
> defined in RFC? It serves
> > an AS for a specific DPC+SSN and it is SGs
> responsibility to distribute
> > messages properly -including management messages-.
> One can look to SCCP
> > management message and decide for which SSN it is
> send.
>
> That would not be using the SSN in the messaage
> (which is SSN=0), that
> would be using the ASSN.  Also, you would need to
> use the APC rather than
> the DPC in the message.  These things are not even
> mentioned for M3UA.
[TOLGA] This is precisely what I mean with implementation dependent: how RK
analysis is done.
>
> Also, where does it say that the ASP registered with
> SSN=5 is the "rignt"
> place to send SCCP management messages?
[TOLGA] Each AS should receive management messages sent for the SSN it
serves. Only management messages sent for the whole SCCP need to be
replicated.
>
> --brian
>
>
> > >
> > > > A MSU containing SCCP congestion message needs
> to
> > > be
> > > > mapped to multiple DATA messages. One can
> argue
> > > that this violates some of
> > > > the paragraphs in RFC (the ones you pointed
> out,
> > > that one MSU should be
> > > > mapped to one DATA), but in fact this really
> does
> > > not bring a real
> > > > interoperability problem, because it does not
> > > require any special behaviour
> > > > from the peer. But still I would think a
> > > clarification sentence saying that
> > > > it might be necessary to map one MSU to
> multiple
> > > DATA to support non-MTP3
> > > > RKs, could be helpfull.
> > > >
> > > > BTW, I agree for most of the changes you
> propose.
> > > IMO it is not a problem
> > > > to delete SSN examples but I prefer that RK
> types
> > > are kept flexible.
> > >
> > > Then the IG changes I proposed should meet with
> your
> > > approval.
> > [TOLGA] I don´t think the changes require any
> approval from me :) But yes,
> > I don´t think, they bring any restriction.
>
> Then do you support them?
[TOLGA] Yes, to prevent a possible confusion for newcomers and to not
repeat this discussion again. I also believe, a sentence about the
necessity for a management funtionality for non-MTP3 RK types migth be
usefull.

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



From mailnull@www1.ietf.org  Fri Jan 10 04:34: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 EAA22127
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 04:34:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A9kXc15414
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 04:46:33 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9k4J15398;
	Fri, 10 Jan 2003 04:46:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9jXJ15367
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 04:45:33 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22089
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 04:32:54 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0A9a9aR017180;
	Fri, 10 Jan 2003 03:36:10 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0A9ZfM21379;
	Fri, 10 Jan 2003 03:35:41 -0600 (CST)
Date: Fri, 10 Jan 2003 03:35:40 -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] m3ua- IG
In-Reply-To: <OFABD9E7CE.932B9405-ONC2256CAA.00316087@LocalDomain>
Message-ID: <Pine.SOL.4.10.10301100329530.10518-100000@sun3271.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>


Tolga,

Agreed.Using flexible RK we support SSN.But How do you handle SSN
congested, SSN unavailable and SSN available ? 
What M3UA message carries these information from ASP to SG?
If you say 'DATA' then what is the need of SUA?

--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, 10 Jan 2003, TOLGA ASVEREN wrote:

> 
> Samuel,
> 
> First of all I consider whether a SG supports this or that type of RK as a
> feature of that SG, not as a property of M3UA protocol. M3UA does not work
> assuming some special RK type.
> IMO, the only place where RK type comes into play is dynamic registration.
> And this is natural, because there one tells about the type of the RK. One
> has to define some types for registration otherwise how can you tell your
> peer what you want? Also please note, RK type not supported case is
> handled, so it is not a problem if an ASP asks to register for a SSN based
> RK to a SG, which does not support it.
> 
>      Tolga
> 
> 
> 
> Tolga,
> 
> RK with SSN, RK with CIC - they are not features of SG.
> Total RFC strength is on RK.If RK is flexible then why
> RFC would say RK's mandatory and optional parameter,
> It could have reserved some space and could have said
> 'this space can be used for any purpose'.
> 
> --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, 10 Jan 2003, TOLGA ASVEREN wrote:
> 
> >
> > Samuel,
> >
> > So, what is wrong with this? Those are features of each separate SG
> > products. Should we try to standardize the feature set supported by each
> > and every SG?
> >
> >       Tolga
> >
> >
> >
> >
> >
> > Tolga,
> >
> > M3UA RFC must conflict with flexible RKs.If it allows flexible RKs
> > then somebody may develop M3UA stack with SSN and others may develop
> > M3UA stack with CIC...
> >
> > So finally no standards are followed to define RK type which will
> > lead into confusion in interoperability.
> >
> > --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, 10 Jan 2003, TOLGA ASVEREN wrote:
> >
> > >
> > > Samuel,
> > >
> > > An implementation dependent management functionality, which is
> > implemented
> > > without bringing any interoperability problems can decide for the
> status
> > of
> > > subsystems. How this funtionality can be implemented is beyond the
> scope
> > of
> > > M3UA IMO.
> > >
> > > RK types are flexible means, type of RKs is not limited by M3UA RFC.
> > >
> > >       Tolga
> > >
> > >
> > >
> > >
> > >
> > >              Tolga,
> > >
> > >              It means peer M3UA can not recognize whether SSN is
> > available
> > >              or congested
> > >              or unavailable...
> > >
> > >              what do you mean by saying "... RK types flexible..."
> > >
> > >
> > >
> > >
> > >         --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, 10 Jan 2003, TOLGA ASVEREN wrote:
> > >
> > >         >
> > >         > Samuel,
> > >         >
> > >         > What does it mean exactly that M3UA supports this or that RK?
> > One
> > >         can argue
> > >         > about how suitable it is to use a certain RK type with M3UA
> but
> > >         this IMO is
> > >         > a different thing. I think the best is to leave RK types
> > flexible
> > >         and maybe
> > >         > with one sentence to warn people about non-MTP3 RK types,
> that
> > >         those might
> > >         > need some management functionalitiy on SG.
> > >         >
> > >         >         Tolga
> > >         >
> > >         >
> > >         >
> > >         >      I think it would be good if we remove all SSN(sub system
> > >         number)
> > >         >      references from RFC or make a global statement in IG as
> > "SSN
> > >         will not
> > >         >      be
> > >         >      supported by RFC 3332 and wherever it is being referred
> it
> > >         should be
> > >         >      ignored"
> > >         >
> > >         >      --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
> > >         >
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > 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
> 

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



From mailnull@www1.ietf.org  Fri Jan 10 04:40:19 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 EAA22319
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 04:40:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0A9qQx15668
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 04:52:26 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9piJ15637;
	Fri, 10 Jan 2003 04:51:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0A9oYJ15558
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 04:50:34 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22195
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 04:37:55 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:8H43ZNZCUkgnTyo2wfFnnrRLEz83kB+n@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0A9fCD07213;
	Fri, 10 Jan 2003 02:41:12 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0A9fCU14852;
	Fri, 10 Jan 2003 02:41:12 -0700
Date: Fri, 10 Jan 2003 02:41:12 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110024112.L8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF89451CE4.D364520F-ONC2256CAA.00339110@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF89451CE4.D364520F-ONC2256CAA.00339110@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 11:29:14AM +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>

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 11:29:14)
> >
> > That would not be using the SSN in the messaage
> > (which is SSN=0), that
> > would be using the ASSN.  Also, you would need to
> > use the APC rather than
> > the DPC in the message.  These things are not even
> > mentioned for M3UA.
> [TOLGA] This is precisely what I mean with implementation dependent: how RK
> analysis is done.
> >
> > Also, where does it say that the ASP registered with
> > SSN=5 is the "rignt"
> > place to send SCCP management messages?
> [TOLGA] Each AS should receive management messages sent for the SSN it
> serves. Only management messages sent for the whole SCCP need to be
> replicated.

Where does it say that?  Valerie thinks that SSN=0 should be
registered for as a separate broadcast AS.  Your diverging
view are an excellent example of why interoperability will not
result.

--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  Fri Jan 10 04:53: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 EAA22565
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 04:53:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AA5uj16214
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 05:05:56 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AA5VJ16183;
	Fri, 10 Jan 2003 05:05:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AA4kJ16136
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 05:04:46 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22548
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 04:52:07 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF8393330D.A1832A3D-ONC2256CAA.003531CE@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 11:52:00 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 11:52:07 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>


Samuel,
--- "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com> wrote:
>
> Tolga,
>
> Agreed.Using flexible RK we support SSN.But How do
> you handle SSN
> congested, SSN unavailable and SSN available ?
> What M3UA message carries these information from ASP
> to SG?
> If you say 'DATA' then what is the need of SUA?
[TOLGA] Management logic in SG can decide for SSN status based on received
DATA and on AS status. In fact also for MTP3 based RK types, it is not a
special management message but the AS state, which helps SG to build the
combined SPMC state. But becase SSN is not a MTP3 based RK, also SCCP
management messages in DATA should be handled properly.

For your final question I guess:
SUA handles SSN based RKs more elegantly and I believe people had in mind
to use it between mobile network nodes in a peer to peer fashion (but last
time I checked 3GPP core network was still preferring M3UA), with one layer
less and possibly by addressing nodes with IP addresses.
>
> --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, 10 Jan 2003, TOLGA ASVEREN wrote:
>
> >
> > Samuel,
> >
> > First of all I consider whether a SG supports this
> or that type of RK as a
> > feature of that SG, not as a property of M3UA
> protocol. M3UA does not work
> > assuming some special RK type.
> > IMO, the only place where RK type comes into play
> is dynamic registration.
> > And this is natural, because there one tells about
> the type of the RK. One
> > has to define some types for registration
> otherwise how can you tell your
> > peer what you want? Also please note, RK type not
> supported case is
> > handled, so it is not a problem if an ASP asks to
> register for a SSN based
> > RK to a SG, which does not support it.

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



From mailnull@www1.ietf.org  Fri Jan 10 04:58: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 EAA22667
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 04:58:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AAAYk17045
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 05:10:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AAA5J17014;
	Fri, 10 Jan 2003 05:10:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AA9XJ16965
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 05:09:33 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22643
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 04:56:54 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0AA09Ob007719;
	Fri, 10 Jan 2003 04:00:10 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0A9xjM29074;
	Fri, 10 Jan 2003 03:59:45 -0600 (CST)
Date: Fri, 10 Jan 2003 03:59:45 -0600 (CST)
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] m3ua- IG
In-Reply-To: <20030110023158.K8782@openss7.org>
Message-ID: <Pine.SOL.4.10.10301100348050.10518-100000@sun3271.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id h0AA9XJ16966
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


Brian,

See the mail below you said 'full-blown SCCP' which means matured sccp.
But now you are saying normal MTP-user.

Ok.Suppose GTT results in DPC+HLR.
Say under one SPMC we have Subsystetems HLR,ALR and LNP.

Now How does SGP know to route the message(DATA) to the particular(HLR)
SSN?

--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, 10 Jan 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> Huh?  This is a normal MTP-User.  When the result is DPC/SSN it
> formulates a message and sends it to the DPC using a MTP-TRANSFER
> primitive to the M3UA acting as MTP Level 3.  There is no need
> to support SSN RKs to acheive this.  SCCP is just a normal MTP
> User in this case.  M3UA already supports MTP Users.
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 03:17:11)
> > 
> > Brian,
> > 
> > Will this full-blown SCCP perform GTT?.Of course, it performs.
> > But what will happen if the result is DPC+SSN?
> > 
> > 
> > To avoid this problem a node should support SUA or we should
> > perform GTT at remote peer.
> > 
> > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > 
> > > Samuel,
> > > 
> > > In section 1.5.3, this is a full-blown SCCP above M3UA.  I don't
> > > think this section needs any modification.
> > > 
> > > --brian
> > > 
> > > On Fri, 10 Jan 2003, Samuel Dur D. Jeyaseelan wrote:
> > > 
> > > > 
> > > > Brian,
> > > > 
> > > > Ok, new changes hold good.
> > > > 
> > > > section 1.5.3
> > > > 
> > > > SCCP layer(an instance of the SS7 SCCP protocol layer) is placed above
> > > > M3UA layer and even performs GTT.
> > > > Once GTT is performed , nobody can restrict that result should be only
> > > > DPC, but result can be DPC/SSN also.
> > > > 
> > > > When you use M3UA , it conveys that your user-part services are
> > > > (including GTT) are offered remotely. So it causes little inconvenience
> > > > to view SCCP layer above M3UA.
> > > > 
> > > > --Samuel
> > > > 
> > > 
> > > -- 
> > > 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 ¦
> > > 
> 
> -- 
> 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 mailnull@www1.ietf.org  Fri Jan 10 05:01: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 FAA22781
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 05:01:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AADQn17258
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 05:13:26 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AAD9J17192;
	Fri, 10 Jan 2003 05:13:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AACfJ17149
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 05:12:41 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22725
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 05:00:01 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFBCAC16AA.29600A48-ONC2256CAA.00365440@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 11:59:56 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 12:00:00 PM
MIME-Version: 1.0
Content-type: text/plain; charset=Windows-1254
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0AACfJ17150
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


Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> TOLGA,
>
> TOLGA ASVEREN wrote:
>                                 (Fri, 10 Jan 2003
> 11:29:14)
> > >
> > > That would not be using the SSN in the messaage
> > > (which is SSN=0), that
> > > would be using the ASSN.  Also, you would need
> to
> > > use the APC rather than
> > > the DPC in the message.  These things are not
> even
> > > mentioned for M3UA.
> > [TOLGA] This is precisely what I mean with
> implementation dependent: how RK
> > analysis is done.
> > >
> > > Also, where does it say that the ASP registered
> with
> > > SSN=5 is the "rignt"
> > > place to send SCCP management messages?
> > [TOLGA] Each AS should receive management messages
> sent for the SSN it
> > serves. Only management messages sent for the
> whole SCCP need to be
> > replicated.
>
> Where does it say that?  Valerie thinks that SSN=0
> should be
> registered for as a separate broadcast AS.  Your
> diverging
> view are an excellent example of why
> interoperability will not
> result.
[TOLGA]All of the things I mentioned, how SSN based routing might be done
is based on the SCCP protocol itself. IMO, this is how it should work, if
one wants to support a RK type, one takes the relevant specification and
thinks whether/how the management functionality needs to be implemented.
The benchmark to decide whether a solution brings interoperability problems
or not is IMO, to see whether the solution requires any change on the peer.
One can even support the same RK type with different ýmplementation
dependent on SG, I think the key point is not to require any change on the
peer. For example as long as a SG supporting SSN based RKs works with yours
and Valeries ASPs (assuming they are M3UA complinat :-) ) there is no
problem IMO.

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



From mailnull@www1.ietf.org  Fri Jan 10 05:47: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 FAA23977
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 05:47:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AAxdJ20210
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 05:59:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AAxBJ20184;
	Fri, 10 Jan 2003 05:59:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AAvlJ20092
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 05:57:47 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23913
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 05:45:06 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:38oYQ/JaVdcOQf1cHZQW+DArz38/0YgD@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0AAmND08253;
	Fri, 10 Jan 2003 03:48:23 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0AAmNg16200;
	Fri, 10 Jan 2003 03:48:23 -0700
Date: Fri, 10 Jan 2003 03:48:23 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110034823.M8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF8393330D.A1832A3D-ONC2256CAA.003531CE@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF8393330D.A1832A3D-ONC2256CAA.003531CE@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 11:52:00AM +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>

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 11:52:00)
> 
> Samuel,
> --- "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com> wrote:
> >
> > Tolga,
> >
> > Agreed.Using flexible RK we support SSN.But How do
> > you handle SSN
> > congested, SSN unavailable and SSN available ?
> > What M3UA message carries these information from ASP
> > to SG?
> > If you say 'DATA' then what is the need of SUA?
> [TOLGA] Management logic in SG can decide for SSN status based on received
> DATA and on AS status. In fact also for MTP3 based RK types, it is not a
> special management message but the AS state, which helps SG to build the
> combined SPMC state. But becase SSN is not a MTP3 based RK, also SCCP
> management messages in DATA should be handled properly.
> 
> For your final question I guess:
> SUA handles SSN based RKs more elegantly and I believe people had in mind
> to use it between mobile network nodes in a peer to peer fashion (but last
> time I checked 3GPP core network was still preferring M3UA), with one layer
> less and possibly by addressing nodes with IP addresses.

SSN based RKs would not help 3GPP as the SCCP used is connection-oriented.
Most connection-oriented messages do not have SSN at all, just the local
reference number.

Fortunately even though M3UA is used between nodes, SUA can still be used
within a node.

--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  Fri Jan 10 05:48: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 FAA24002
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 05:48:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AB0NM20353
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 06:00:23 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AB08J20327;
	Fri, 10 Jan 2003 06:00:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AAwgJ20164
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 05:58:42 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23952
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 05:46:02 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:s9O8O6CwIV2PiOXuBnufMiRHlFzQotLj@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0AAnJD08266;
	Fri, 10 Jan 2003 03:49:19 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0AAnJN16213;
	Fri, 10 Jan 2003 03:49:19 -0700
Date: Fri, 10 Jan 2003 03:49:19 -0700
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] m3ua- IG
Message-ID: <20030110034919.N8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030110023158.K8782@openss7.org> <Pine.SOL.4.10.10301100348050.10518-100000@sun3271.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.10301100348050.10518-100000@sun3271.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Jan 10, 2003 at 03:59:45AM -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,

Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 03:59:45)
> 
> Brian,
> 
> See the mail below you said 'full-blown SCCP' which means matured sccp.
> But now you are saying normal MTP-user.
> 
> Ok.Suppose GTT results in DPC+HLR.
> Say under one SPMC we have Subsystetems HLR,ALR and LNP.
> 
> Now How does SGP know to route the message(DATA) to the particular(HLR)
> SSN?

It routes on DPC.

--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  Fri Jan 10 05:56:52 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 FAA24186
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 05:56:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AB90l21443
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 06:09:00 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AB8TJ21413;
	Fri, 10 Jan 2003 06:08:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AB7JJ21071
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 06:07:19 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24142
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 05:54:38 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:0jnT2jUO4ZiFjMi9T3Qc/dbg2op/XDwR@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0AAvuD08365;
	Fri, 10 Jan 2003 03:57:56 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0AAvuh16455;
	Fri, 10 Jan 2003 03:57:56 -0700
Date: Fri, 10 Jan 2003 03:57:55 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110035755.O8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OFBCAC16AA.29600A48-ONC2256CAA.00365440@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OFBCAC16AA.29600A48-ONC2256CAA.00365440@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 11:59:56AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 11:59:56)
> 
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > TOLGA,
> >
> > TOLGA ASVEREN wrote:
> >                                 (Fri, 10 Jan 2003
> > 11:29:14)
> > > >
> > > > That would not be using the SSN in the messaage
> > > > (which is SSN=0), that
> > > > would be using the ASSN.  Also, you would need
> > to
> > > > use the APC rather than
> > > > the DPC in the message.  These things are not
> > even
> > > > mentioned for M3UA.
> > > [TOLGA] This is precisely what I mean with
> > implementation dependent: how RK
> > > analysis is done.
> > > >
> > > > Also, where does it say that the ASP registered
> > with
> > > > SSN=5 is the "rignt"
> > > > place to send SCCP management messages?
> > > [TOLGA] Each AS should receive management messages
> > sent for the SSN it
> > > serves. Only management messages sent for the
> > whole SCCP need to be
> > > replicated.
> >
> > Where does it say that?  Valerie thinks that SSN=0
> > should be
> > registered for as a separate broadcast AS.  Your
> > diverging
> > view are an excellent example of why
> > interoperability will not
> > result.
> [TOLGA]All of the things I mentioned, how SSN based routing might be done
> is based on the SCCP protocol itself. IMO, this is how it should work, if
> one wants to support a RK type, one takes the relevant specification and
> thinks whether/how the management functionality needs to be implemented.
> The benchmark to decide whether a solution brings interoperability problems
> or not is IMO, to see whether the solution requires any change on the peer.
> One can even support the same RK type with different ýmplementation
> dependent on SG, I think the key point is not to require any change on the
> peer. For example as long as a SG supporting SSN based RKs works with yours
> and Valeries ASPs (assuming they are M3UA complinat :-) ) there is no
> problem IMO.

In a short period of time we have two approaches: yours and Valerie's.  How
many more approaches must both the SG and ASP support to be interoperable?
That is what is missing from the M3UA spec: a basis for interoperability.  As
an IETF document, M3UA RFC as it stands does not support SSN, because there is
no basis for this interoperability (because it is completely unspecified).

So, tommorrow, Joe comes up with a new approach for SCCP management.  He reads
the M3UA spec and it says that any messages that do not match a routing key
are sent to a default ASP.  So he builds his ASP to receive these messages
only when it is configured in the SG as the default ASP.  His ASP does not
work with your or Valerie's SGs, but he has not violated any requirement in
the M3UA RFC.

So all that results is a bunch of non-interoperable solutions.  That is not
the objective of an IETF RFC.  In fact, an RFC should remove the possibility
of interoperability through specification.  Therefore, the M3UA RFC should go
so far as to say that SSN Routing Keys MUST NOT be supported, because
non-interoperable solutions will result.

--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  Fri Jan 10 05:57: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 FAA24192
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 05:57:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AB9K921491
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 06:09:20 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AB96J21469;
	Fri, 10 Jan 2003 06:09:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AB8YJ21419
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 06:08:34 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24163
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 05:55:53 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0AAxABE011469;
	Fri, 10 Jan 2003 04:59:10 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0AAwYM24367;
	Fri, 10 Jan 2003 04:58:34 -0600 (CST)
Date: Fri, 10 Jan 2003 04:58:34 -0600 (CST)
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] m3ua- IG
In-Reply-To: <20030110034919.N8782@openss7.org>
Message-ID: <Pine.SOL.4.10.10301100455160.10518-100000@sun3271.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,

DPC is not consisting of only HLR but it also has LNP(Locan Number
Portability),ALR(Application Location Register).. under one SPMC.

--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, 10 Jan 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 03:59:45)
> > 
> > Brian,
> > 
> > See the mail below you said 'full-blown SCCP' which means matured sccp.
> > But now you are saying normal MTP-user.
> > 
> > Ok.Suppose GTT results in DPC+HLR.
> > Say under one SPMC we have Subsystetems HLR,ALR and LNP.
> > 
> > Now How does SGP know to route the message(DATA) to the particular(HLR)
> > SSN?
> 
> It routes on DPC.
> 
> --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  Fri Jan 10 06:12:19 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 GAA24548
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 06:12:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ABOQt22209
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 06:24:26 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ABO8J22192;
	Fri, 10 Jan 2003 06:24:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ABN2J22140
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 06:23:02 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24516
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 06:10:22 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF04D2C119.3A451EE0-ONC2256CAA.003CDE7C@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 13:10:15 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 01:10:19 PM
MIME-Version: 1.0
Content-type: text/plain; charset=Windows-1254
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0ABN2J22141
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


Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> TOLGA,
>
> TOLGA ASVEREN wrote:
>                                 (Fri, 10 Jan 2003
> 11:59:56)
> >
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > > TOLGA,
> > >
> > > TOLGA ASVEREN wrote:
> > >                                 (Fri, 10 Jan
> 2003
> > > 11:29:14)
> > > > >
> > > > > That would not be using the SSN in the
> messaage
> > > > > (which is SSN=0), that
> > > > > would be using the ASSN.  Also, you would
> need
> > > to
> > > > > use the APC rather than
> > > > > the DPC in the message.  These things are
> not
> > > even
> > > > > mentioned for M3UA.
> > > > [TOLGA] This is precisely what I mean with
> > > implementation dependent: how RK
> > > > analysis is done.
> > > > >
> > > > > Also, where does it say that the ASP
> registered
> > > with
> > > > > SSN=5 is the "rignt"
> > > > > place to send SCCP management messages?
> > > > [TOLGA] Each AS should receive management
> messages
> > > sent for the SSN it
> > > > serves. Only management messages sent for the
> > > whole SCCP need to be
> > > > replicated.
> > >
> > > Where does it say that?  Valerie thinks that
> SSN=0
> > > should be
> > > registered for as a separate broadcast AS.  Your
> > > diverging
> > > view are an excellent example of why
> > > interoperability will not
> > > result.
> > [TOLGA]All of the things I mentioned, how SSN
> based routing might be done
> > is based on the SCCP protocol itself. IMO, this is
> how it should work, if
> > one wants to support a RK type, one takes the
> relevant specification and
> > thinks whether/how the management functionality
> needs to be implemented.
> > The benchmark to decide whether a solution brings
> interoperability problems
> > or not is IMO, to see whether the solution
> requires any change on the peer.
> > One can even support the same RK type with
> different ýmplementation
> > dependent on SG, I think the key point is not to
> require any change on the
> > peer. For example as long as a SG supporting SSN
> based RKs works with yours
> > and Valeries ASPs (assuming they are M3UA
> complinat :-) ) there is no
> > problem IMO.
>
> In a short period of time we have two approaches:
> yours and Valerie's.  How
> many more approaches must both the SG and ASP
> support to be interoperable?
> That is what is missing from the M3UA spec: a basis
> for interoperability.  As
> an IETF document, M3UA RFC as it stands does not
> support SSN, because there is
> no basis for this interoperability (because it is
> completely unspecified).
>
> So, tommorrow, Joe comes up with a new approach for
> SCCP management.  He reads
> the M3UA spec and it says that any messages that do
> not match a routing key
> are sent to a default ASP.  So he builds his ASP to
> receive these messages
> only when it is configured in the SG as the default
> ASP.  His ASP does not
> work with your or Valerie's SGs, but he has not
> violated any requirement in
> the M3UA RFC.
>
> So all that results is a bunch of non-interoperable
> solutions.  That is not
> the objective of an IETF RFC.  In fact, an RFC
> should remove the possibility
> of interoperability through specification.
> Therefore, the M3UA RFC should go
> so far as to say that SSN Routing Keys MUST NOT be
> supported, because
> non-interoperable solutions will result.
[TOLGA] I totally disagree. You present some solutions, which bring some
interoperability problems, and use this as an evidence of inappropriateness
of a solution, which does not have interoperability problems. As I said
several times, as long as a SG supporting SSN based routing works with a
standard M3UA based ASP, I don´t see any problem.

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



From mailnull@www1.ietf.org  Fri Jan 10 06:14: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 GAA24592
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 06:14:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ABQFl22316
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 06:26:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ABQ3J22305;
	Fri, 10 Jan 2003 06:26:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ABPHJ22250
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 06:25:17 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24565
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 06:12:38 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:8Zx+9geyDx0P9iwQ5NMA5Eh506P1Cvjr@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0ABFtD09130;
	Fri, 10 Jan 2003 04:15:55 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0ABFsW17609;
	Fri, 10 Jan 2003 04:15:54 -0700
Date: Fri, 10 Jan 2003 04:15:54 -0700
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] m3ua- IG
Message-ID: <20030110041554.P8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030110034919.N8782@openss7.org> <Pine.SOL.4.10.10301100455160.10518-100000@sun3271.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.10301100455160.10518-100000@sun3271.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Jan 10, 2003 at 04:58:34AM -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,

When SCCP sends these messages to MTP, they get routed through the
SS7 network on DPC only.  SCCP does not need any more service than
is provided by MTP.  So, things will work fine if M3UA routes on
DPC only.  M3UA no more needs to look at SSN than MTP does (and
MTP does not need to look at SSN, it uses DPC only).  Look at Q.714
routing rules to see how MTP transfers all messages on DPC only.
Only once the message gets to the DPC is SSN or GT examined by
SCCP to determine the proper SCCP-User.

So, in the example in 1.5.3, SCCP is acting as a normal MTP-User.
It sends messages to MTP with MTP-TRANSFER primitive and expects
them to be routed by MTP on the DPC, without reference to the SSN.
To provide correct service to SCCP, M3UA must do the same.

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 04:58:34)
> 
> Brian,
> 
> DPC is not consisting of only HLR but it also has LNP(Locan Number
> Portability),ALR(Application Location Register).. under one SPMC.
> 
> --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 03:59:45)
> > > 
> > > Brian,
> > > 
> > > See the mail below you said 'full-blown SCCP' which means matured sccp.
> > > But now you are saying normal MTP-user.
> > > 
> > > Ok.Suppose GTT results in DPC+HLR.
> > > Say under one SPMC we have Subsystetems HLR,ALR and LNP.
> > > 
> > > Now How does SGP know to route the message(DATA) to the particular(HLR)
> > > SSN?
> > 
> > It routes on DPC.
> > 
> > --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 mailnull@www1.ietf.org  Fri Jan 10 06:17:15 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 GAA24653
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 06:17:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ABTNf22449
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 06:29:23 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ABT3J22437;
	Fri, 10 Jan 2003 06:29:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ABSeJ22413
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 06:28:40 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24632
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 06:16:01 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:qOedFC1aoifh3bBIfamEGKkhFETJkTBj@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0ABJHD09170;
	Fri, 10 Jan 2003 04:19:17 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0ABJH117655;
	Fri, 10 Jan 2003 04:19:17 -0700
Date: Fri, 10 Jan 2003 04:19:16 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110041916.Q8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF04D2C119.3A451EE0-ONC2256CAA.003CDE7C@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF04D2C119.3A451EE0-ONC2256CAA.003CDE7C@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 01:10:15PM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 13:10:15)
> > In a short period of time we have two
> > approaches: yours and Valerie's.  How
> > many more approaches must both the SG
> > and ASP support to be interoperable?
> > That is what is missing from the M3UA
> > spec: a basis for interoperability.
> > As an IETF document, M3UA RFC as it
> > stands does not support SSN, because
> > there is no basis for this
> > interoperability (because it is
> > completely unspecified).
> >
> > So, tommorrow, Joe comes up with a new
> > approach for SCCP management.  He
> > reads the M3UA spec and it says that
> > any messages that do not match a
> > routing key are sent to a default ASP.
> > So he builds his ASP to receive these
> > messages only when it is configured in
> > the SG as the default ASP.  His ASP
> > does not work with your or Valerie's
> > SGs, but he has not violated any
> > requirement in the M3UA RFC.
> >
> > So all that results is a bunch of
> > non-interoperable solutions.  That is
> > not the objective of an IETF RFC.  In
> > fact, an RFC should remove the
> > possibility of interoperability
> > through specification.  Therefore, the
> > M3UA RFC should go so far as to say
> > that SSN Routing Keys MUST NOT be
> > supported, because non-interoperable
> > solutions will result.
> [TOLGA] I totally disagree. You present
> some solutions, which bring some
> interoperability problems, and use this
> as an evidence of inappropriateness of a
> solution, which does not have
> interoperability problems. As I said
> several times, as long as a SG
> supporting SSN based routing works with
> a standard M3UA based ASP, I don´t see
> any problem.

Which standard M3UA ASP?  Yours?
Valeries?  Joes?  Several? All?

You cannot acheive interoperability in
this regard without both the SG and the
ASP knowing which procedures are used.

Therefore, you cannot (as you said
previously) just implement SSN RK on the
SG without the ASP knowing how it is done.

Is there anyone else on the list that
thinks this is basis for interoperability?

--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  Fri Jan 10 06:22:23 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 GAA24769
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 06:22:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ABYVc22771
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 06:34:31 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ABY6J22749;
	Fri, 10 Jan 2003 06:34:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ABXAJ22705
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 06:33:10 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24708
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 06:20:30 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF2F05E98E.072778EA-ONC2256CAA.003DDF2C@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 13:20:23 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 01:20:28 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>


Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> TOLGA,
>
> TOLGA ASVEREN wrote:
>                                 (Fri, 10 Jan 2003
> 11:52:00)
> >
> > Samuel,
> > --- "Samuel Dur D. Jeyaseelan"
> <sjeyasee@ssd.usa.alcatel.com> wrote:
> > >
> > > Tolga,
> > >
> > > Agreed.Using flexible RK we support SSN.But How
> do
> > > you handle SSN
> > > congested, SSN unavailable and SSN available ?
> > > What M3UA message carries these information from
> ASP
> > > to SG?
> > > If you say 'DATA' then what is the need of SUA?
> > [TOLGA] Management logic in SG can decide for SSN
> status based on received
> > DATA and on AS status. In fact also for MTP3 based
> RK types, it is not a
> > special management message but the AS state, which
> helps SG to build the
> > combined SPMC state. But becase SSN is not a MTP3
> based RK, also SCCP
> > management messages in DATA should be handled
> properly.
> >
> > For your final question I guess:
> > SUA handles SSN based RKs more elegantly and I
> believe people had in mind
> > to use it between mobile network nodes in a peer
> to peer fashion (but last
> > time I checked 3GPP core network was still
> preferring M3UA), with one layer
> > less and possibly by addressing nodes with IP
> addresses.
>
> SSN based RKs would not help 3GPP as the SCCP used
> is connection-oriented.
[TOLGA] I think connectionless mode is also still there in 3GPP.
> Most connection-oriented messages do not have SSN at
> all, just the local
> reference number.
>
> Fortunately even though M3UA is used between nodes,
> SUA can still be used
> within a node.

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



From mailnull@www1.ietf.org  Fri Jan 10 06:29: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 GAA24933
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 06:29:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ABfS323752
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 06:41:28 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ABf5J23722;
	Fri, 10 Jan 2003 06:41:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ABe5J23656
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 06:40:05 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24824
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 06:27:25 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF61139FA4.D3F36462-ONC2256CAA.003E6EBB@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 13:27:19 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 01:27:23 PM
MIME-Version: 1.0
Content-type: text/plain; charset=Windows-1254
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0ABe5J23665
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


Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> TOLGA,
>
> TOLGA ASVEREN wrote:
>                                 (Fri, 10 Jan 2003
> 13:10:15)
> > > In a short period of time we have two
> > > approaches: yours and Valerie's.  How
> > > many more approaches must both the SG
> > > and ASP support to be interoperable?
> > > That is what is missing from the M3UA
> > > spec: a basis for interoperability.
> > > As an IETF document, M3UA RFC as it
> > > stands does not support SSN, because
> > > there is no basis for this
> > > interoperability (because it is
> > > completely unspecified).
> > >
> > > So, tommorrow, Joe comes up with a new
> > > approach for SCCP management.  He
> > > reads the M3UA spec and it says that
> > > any messages that do not match a
> > > routing key are sent to a default ASP.
> > > So he builds his ASP to receive these
> > > messages only when it is configured in
> > > the SG as the default ASP.  His ASP
> > > does not work with your or Valerie's
> > > SGs, but he has not violated any
> > > requirement in the M3UA RFC.
> > >
> > > So all that results is a bunch of
> > > non-interoperable solutions.  That is
> > > not the objective of an IETF RFC.  In
> > > fact, an RFC should remove the
> > > possibility of interoperability
> > > through specification.  Therefore, the
> > > M3UA RFC should go so far as to say
> > > that SSN Routing Keys MUST NOT be
> > > supported, because non-interoperable
> > > solutions will result.
> > [TOLGA] I totally disagree. You present
> > some solutions, which bring some
> > interoperability problems, and use this
> > as an evidence of inappropriateness of a
> > solution, which does not have
> > interoperability problems. As I said
> > several times, as long as a SG
> > supporting SSN based routing works with
> > a standard M3UA based ASP, I don´t see
> > any problem.
>
> Which standard M3UA ASP?  Yours?
> Valeries?  Joes?  Several? All?
[TOLGA] Any ASP compliant with M3UA RFC.
>
> You cannot acheive interoperability in
> this regard without both the SG and the
> ASP knowing which procedures are used.
[TOLGA] I don´t propose this. What I propose is, an implementation
dependent management funtionality on SG, which does not require any change
on the peer, i.e. which won´t prevent SG to work with a M3UA compliant ASP.
>
> Therefore, you cannot (as you said
> previously) just implement SSN RK on the
> SG without the ASP knowing how it is done.
[TOLGA]Why? What requirement will it put to ASP or to the M3UA protocol?
>
> Is there anyone else on the list that
> thinks this is basis for interoperability?
[TOLGA} Or which thinks that ýmplementing a functionality on SG which does
not put any requirement to M3UA protocol or to the peer, is a violation of
the protocol?

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



From mailnull@www1.ietf.org  Fri Jan 10 06:45: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 GAA25461
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 06:45:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ABvXY24457
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 06:57:33 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ABvAJ24422;
	Fri, 10 Jan 2003 06:57:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ABuZJ24378
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 06:56:35 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25423
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 06:43:55 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0ABl9Ob015567;
	Fri, 10 Jan 2003 05:47:11 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0ABkMM10222;
	Fri, 10 Jan 2003 05:46:22 -0600 (CST)
Date: Fri, 10 Jan 2003 05:46:22 -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] m3ua- IG
In-Reply-To: <OF61139FA4.D3F36462-ONC2256CAA.003E6EBB@LocalDomain>
Message-ID: <Pine.SOL.4.10.10301100538420.10518-100000@sun3271.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id h0ABuZJ24379
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


Tolga,

If X has implemented SG with SSN RK (eventhough it is not told in rfc),
How does X expect Y to implement the same 'management logic' at ASP?

Everyone will try to follow RFC strictly to go for interop.

Blindly speaking SSN is not a field(whereas SSN in one of the fields in
SUA messages) of any M3UA message so nobody will implement SSN RK with
M3UA stack.

--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, 10 Jan 2003, TOLGA ASVEREN wrote:

> 
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > TOLGA,
> >
> > TOLGA ASVEREN wrote:
> >                                 (Fri, 10 Jan 2003
> > 13:10:15)
> > > > In a short period of time we have two
> > > > approaches: yours and Valerie's.  How
> > > > many more approaches must both the SG
> > > > and ASP support to be interoperable?
> > > > That is what is missing from the M3UA
> > > > spec: a basis for interoperability.
> > > > As an IETF document, M3UA RFC as it
> > > > stands does not support SSN, because
> > > > there is no basis for this
> > > > interoperability (because it is
> > > > completely unspecified).
> > > >
> > > > So, tommorrow, Joe comes up with a new
> > > > approach for SCCP management.  He
> > > > reads the M3UA spec and it says that
> > > > any messages that do not match a
> > > > routing key are sent to a default ASP.
> > > > So he builds his ASP to receive these
> > > > messages only when it is configured in
> > > > the SG as the default ASP.  His ASP
> > > > does not work with your or Valerie's
> > > > SGs, but he has not violated any
> > > > requirement in the M3UA RFC.
> > > >
> > > > So all that results is a bunch of
> > > > non-interoperable solutions.  That is
> > > > not the objective of an IETF RFC.  In
> > > > fact, an RFC should remove the
> > > > possibility of interoperability
> > > > through specification.  Therefore, the
> > > > M3UA RFC should go so far as to say
> > > > that SSN Routing Keys MUST NOT be
> > > > supported, because non-interoperable
> > > > solutions will result.
> > > [TOLGA] I totally disagree. You present
> > > some solutions, which bring some
> > > interoperability problems, and use this
> > > as an evidence of inappropriateness of a
> > > solution, which does not have
> > > interoperability problems. As I said
> > > several times, as long as a SG
> > > supporting SSN based routing works with
> > > a standard M3UA based ASP, I don´t see
> > > any problem.
> >
> > Which standard M3UA ASP?  Yours?
> > Valeries?  Joes?  Several? All?
> [TOLGA] Any ASP compliant with M3UA RFC.
> >
> > You cannot acheive interoperability in
> > this regard without both the SG and the
> > ASP knowing which procedures are used.
> [TOLGA] I don´t propose this. What I propose is, an implementation
> dependent management funtionality on SG, which does not require any change
> on the peer, i.e. which won´t prevent SG to work with a M3UA compliant ASP.
> >
> > Therefore, you cannot (as you said
> > previously) just implement SSN RK on the
> > SG without the ASP knowing how it is done.
> [TOLGA]Why? What requirement will it put to ASP or to the M3UA protocol?
> >
> > Is there anyone else on the list that
> > thinks this is basis for interoperability?
> [TOLGA} Or which thinks that ýmplementing a functionality on SG which does
> not put any requirement to M3UA protocol or to the peer, is a violation of
> the protocol?
> 
> _______________________________________________
> 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 Jan 10 06:55: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 GAA25628
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 06:55:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AC7Fe25193
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 07:07:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AC5eJ24738;
	Fri, 10 Jan 2003 07:05:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AC42J24711
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 07:04:02 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25584
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 06:51:21 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF99CAD5F0.72432D40-ONC2256CAA.0040889B@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 13:51:14 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 01:51:18 PM
MIME-Version: 1.0
Content-type: text/plain; charset=Windows-1254
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0AC42J24712
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


Samuel,

The point is, no special management logic should be necessary on ASP. The
ASP is just any M3UA compliant ASP, nothing special there. BTW, does M3UA
RFC tell to support any specific RK type? For example if a SG supports only
DPC based RKs, will it be compliant or not with RFC?
I think it is totally dependent on the implementor, which types of RKs
her/his SG is going to support.

    Tolga





Tolga,

If X has implemented SG with SSN RK (eventhough it is not told in rfc),
How does X expect Y to implement the same 'management logic' at ASP?

Everyone will try to follow RFC strictly to go for interop.

Blindly speaking SSN is not a field(whereas SSN in one of the fields in
SUA messages) of any M3UA message so nobody will implement SSN RK with
M3UA stack.

--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, 10 Jan 2003, TOLGA ASVEREN wrote:

>
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > TOLGA,
> >
> > TOLGA ASVEREN wrote:
> >                                 (Fri, 10 Jan 2003
> > 13:10:15)
> > > > In a short period of time we have two
> > > > approaches: yours and Valerie's.  How
> > > > many more approaches must both the SG
> > > > and ASP support to be interoperable?
> > > > That is what is missing from the M3UA
> > > > spec: a basis for interoperability.
> > > > As an IETF document, M3UA RFC as it
> > > > stands does not support SSN, because
> > > > there is no basis for this
> > > > interoperability (because it is
> > > > completely unspecified).
> > > >
> > > > So, tommorrow, Joe comes up with a new
> > > > approach for SCCP management.  He
> > > > reads the M3UA spec and it says that
> > > > any messages that do not match a
> > > > routing key are sent to a default ASP.
> > > > So he builds his ASP to receive these
> > > > messages only when it is configured in
> > > > the SG as the default ASP.  His ASP
> > > > does not work with your or Valerie's
> > > > SGs, but he has not violated any
> > > > requirement in the M3UA RFC.
> > > >
> > > > So all that results is a bunch of
> > > > non-interoperable solutions.  That is
> > > > not the objective of an IETF RFC.  In
> > > > fact, an RFC should remove the
> > > > possibility of interoperability
> > > > through specification.  Therefore, the
> > > > M3UA RFC should go so far as to say
> > > > that SSN Routing Keys MUST NOT be
> > > > supported, because non-interoperable
> > > > solutions will result.
> > > [TOLGA] I totally disagree. You present
> > > some solutions, which bring some
> > > interoperability problems, and use this
> > > as an evidence of inappropriateness of a
> > > solution, which does not have
> > > interoperability problems. As I said
> > > several times, as long as a SG
> > > supporting SSN based routing works with
> > > a standard M3UA based ASP, I don´t see
> > > any problem.
> >
> > Which standard M3UA ASP?  Yours?
> > Valeries?  Joes?  Several? All?
> [TOLGA] Any ASP compliant with M3UA RFC.
> >
> > You cannot acheive interoperability in
> > this regard without both the SG and the
> > ASP knowing which procedures are used.
> [TOLGA] I don´t propose this. What I propose is, an implementation
> dependent management funtionality on SG, which does not require any
change
> on the peer, i.e. which won´t prevent SG to work with a M3UA compliant
ASP.
> >
> > Therefore, you cannot (as you said
> > previously) just implement SSN RK on the
> > SG without the ASP knowing how it is done.
> [TOLGA]Why? What requirement will it put to ASP or to the M3UA protocol?
> >
> > Is there anyone else on the list that
> > thinks this is basis for interoperability?
> [TOLGA} Or which thinks that ýmplementing a functionality on SG which
does
> not put any requirement to M3UA protocol or to the peer, is a violation
of
> the protocol?
>
> _______________________________________________
> 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 Jan 10 06:57: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 GAA25706
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 06:57:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AC9jt25547
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 07:09:45 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AC9VJ25536;
	Fri, 10 Jan 2003 07:09:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AC88J25484
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 07:08:08 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25650
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 06:55:28 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:xJG2/j3HUkq47KyVbfM07IW72wgWyiEg@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0ABwjD09784;
	Fri, 10 Jan 2003 04:58:45 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0ABwj118476;
	Fri, 10 Jan 2003 04:58:45 -0700
Date: Fri, 10 Jan 2003 04:58:44 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110045844.R8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF2F05E98E.072778EA-ONC2256CAA.003DDF2C@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF2F05E98E.072778EA-ONC2256CAA.003DDF2C@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 01:20:23PM +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>

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 13:20:23)
> 
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > TOLGA,
> >
> > TOLGA ASVEREN wrote:
> >                                 (Fri, 10 Jan 2003
> > 11:52:00)
> > >
> > > Samuel,
> > > --- "Samuel Dur D. Jeyaseelan"
> > <sjeyasee@ssd.usa.alcatel.com> wrote:
> > > >
> > > > Tolga,
> > > >
> > > > Agreed.Using flexible RK we
> > > > support SSN.But How do you
> > > > handle SSN congested, SSN
> > > > unavailable and SSN available ?
> > > > What M3UA message carries these
> > > > information from ASP to SG?  If
> > > > you say 'DATA' then what is the
> > > > need of SUA?
> > > [TOLGA] Management logic in SG can
> > > decide for SSN status based on
> > > received DATA and on AS status. In
> > > fact also for MTP3 based RK types,
> > > it is not a special management
> > > message but the AS state, which
> > > helps SG to build the combined
> > > SPMC state. But becase SSN is not
> > > a MTP3 based RK, also SCCP
> > > management messages in DATA should
> > > be handled properly.
> > >
> > > For your final question I guess:
> > > SUA handles SSN based RKs more
> > > elegantly and I believe people had
> > > in mind to use it between mobile
> > > network nodes in a peer to peer
> > > fashion (but last time I checked
> > > 3GPP core network was still
> > > preferring M3UA), with one layer
> > > less and possibly by addressing
> > > nodes with IP addresses.
> >
> > SSN based RKs would not help 3GPP as
> > the SCCP used is
> > connection-oriented.
> [TOLGA] I think connectionless mode is
> also still there in 3GPP.
I uses both... and together serving the
same user.

--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  Fri Jan 10 07:01: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 HAA25818
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 07:01:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ACDbJ25726
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 07:13:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ACD5J25689;
	Fri, 10 Jan 2003 07:13:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ACCSJ25660
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 07:12:28 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25745
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 06:59:48 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:JO7nkPiUXa4zMNUxswOz2+xEGGPYTmLU@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0AC34D10002;
	Fri, 10 Jan 2003 05:03:04 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0AC34N18737;
	Fri, 10 Jan 2003 05:03:04 -0700
Date: Fri, 10 Jan 2003 05:03:04 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110050304.S8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF61139FA4.D3F36462-ONC2256CAA.003E6EBB@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF61139FA4.D3F36462-ONC2256CAA.003E6EBB@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 01:27:19PM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 13:27:19)
> 
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > TOLGA,
> >
> > TOLGA ASVEREN wrote:
> >                                 (Fri, 10 Jan 2003
> > 13:10:15)
> > > > In a short period of time we have two
> > > > approaches: yours and Valerie's.  How
> > > > many more approaches must both the SG
> > > > and ASP support to be interoperable?
> > > > That is what is missing from the M3UA
> > > > spec: a basis for interoperability.
> > > > As an IETF document, M3UA RFC as it
> > > > stands does not support SSN, because
> > > > there is no basis for this
> > > > interoperability (because it is
> > > > completely unspecified).
> > > >
> > > > So, tommorrow, Joe comes up with a new
> > > > approach for SCCP management.  He
> > > > reads the M3UA spec and it says that
> > > > any messages that do not match a
> > > > routing key are sent to a default ASP.
> > > > So he builds his ASP to receive these
> > > > messages only when it is configured in
> > > > the SG as the default ASP.  His ASP
> > > > does not work with your or Valerie's
> > > > SGs, but he has not violated any
> > > > requirement in the M3UA RFC.
> > > >
> > > > So all that results is a bunch of
> > > > non-interoperable solutions.  That is
> > > > not the objective of an IETF RFC.  In
> > > > fact, an RFC should remove the
> > > > possibility of interoperability
> > > > through specification.  Therefore, the
> > > > M3UA RFC should go so far as to say
> > > > that SSN Routing Keys MUST NOT be
> > > > supported, because non-interoperable
> > > > solutions will result.
> > > [TOLGA] I totally disagree. You present
> > > some solutions, which bring some
> > > interoperability problems, and use this
> > > as an evidence of inappropriateness of a
> > > solution, which does not have
> > > interoperability problems. As I said
> > > several times, as long as a SG
> > > supporting SSN based routing works with
> > > a standard M3UA based ASP, I don´t see
> > > any problem.
> >
> > Which standard M3UA ASP?  Yours?
> > Valeries?  Joes?  Several? All?
> [TOLGA] Any ASP compliant with M3UA RFC.
Any and all?  How do you ensure that
your SG works with Jim's ASP? (Jim hasn't
told the world his method yet.)

> >
> > You cannot acheive interoperability in
> > this regard without both the SG and the
> > ASP knowing which procedures are used.
> [TOLGA] I don´t propose this. What I
> propose is, an implementation
> dependent management funtionality on
> SG, which does not require any change
> on the peer, i.e. which won´t prevent
> SG to work with a M3UA compliant ASP.
But ASP needs to know what SG is doing.
This requires some kind of change on the
ASP.  Otherwise, and OBVIOUSLY,
interoperability will not result.

> >
> > Therefore, you cannot (as you said
> > previously) just implement SSN RK on the
> > SG without the ASP knowing how it is done.
> [TOLGA]Why? What requirement will it
> put to ASP or to the M3UA protocol?

It puts requirements on the ASP as to
where (which AS) and in what manner (when
configured how) it can expect to recieve
SCCP management messages.

> > Is there anyone else on the list that
> > thinks this is basis for interoperability?
> [TOLGA} Or which thinks that
> ýmplementing a functionality on SG
> which does not put any requirement to
> M3UA protocol or to the peer, is a
> violation of the protocol?
All three methods mentioned put
requirements on the peer.  That's
why they don't interoperate.

--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  Fri Jan 10 07:06: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 HAA25886
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 07:06:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ACIVX25897
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 07:18:31 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ACI6J25882;
	Fri, 10 Jan 2003 07:18:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ACHcJ25861
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 07:17:38 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25862
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 07:04:57 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:IxxmuH5q9Nq/lVnSkhMGl1fH3K+KQPYn@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0AC8DD10061;
	Fri, 10 Jan 2003 05:08:13 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0AC8DI18800;
	Fri, 10 Jan 2003 05:08:13 -0700
Date: Fri, 10 Jan 2003 05:08:13 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110050813.T8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF99CAD5F0.72432D40-ONC2256CAA.0040889B@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF99CAD5F0.72432D40-ONC2256CAA.0040889B@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 01:51:14PM +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>

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 13:51:14)
> 
> Samuel,
> 
> The point is, no special management logic should be necessary on ASP.

The point is special management logic is required on the ASP so that
it can know where and when it is receiving SCCP management messages.

> The ASP is just any M3UA compliant ASP, nothing special there.

It is a VERY special ASP.  It's M3UA knows about SCCP mangement messages
and knows where the particular SG is going to place them, whether it needs
to register for an AS with SSN=0, whether it needs to only act as a default
ASP, whether it can expect management messages on each AS corresponding to
a subsystem, in fact it needs to know that the SG is performing SSN routing
at all (which is not supported by dynamic registration).

> BTW, does M3UA RFC tell to support any specific RK type? For example if a SG
> supports only DPC based RKs, will it be compliant or not with RFC?  I think
> it is totally dependent on the implementor, which types of RKs her/his SG is
> going to support.

Of the proper M3UA routing keys (OPC/DPC/SI) routing on DPC must be supported
at a minimum, otherwise, the implementation will not be useful.

--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  Fri Jan 10 07:17: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 HAA26069
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 07:17:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ACTUh26475
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 07:29:30 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ACT7J26436;
	Fri, 10 Jan 2003 07:29:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ACSoJ26406
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 07:28:50 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26042
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 07:16:09 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF40737600.B9550294-ONC2256CAA.0042B2A6@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 14:16:02 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 02:16:07 PM
MIME-Version: 1.0
Content-type: text/plain; charset=Windows-1254
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0ACSoJ26407
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


Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> TOLGA,
>
> TOLGA ASVEREN wrote:
>                                 (Fri, 10 Jan 2003
> 13:27:19)
> >
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > > TOLGA,
> > >
> > > TOLGA ASVEREN wrote:
> > >                                 (Fri, 10 Jan
> 2003
> > > 13:10:15)
> > > > > In a short period of time we have two
> > > > > approaches: yours and Valerie's.  How
> > > > > many more approaches must both the SG
> > > > > and ASP support to be interoperable?
> > > > > That is what is missing from the M3UA
> > > > > spec: a basis for interoperability.
> > > > > As an IETF document, M3UA RFC as it
> > > > > stands does not support SSN, because
> > > > > there is no basis for this
> > > > > interoperability (because it is
> > > > > completely unspecified).
> > > > >
> > > > > So, tommorrow, Joe comes up with a new
> > > > > approach for SCCP management.  He
> > > > > reads the M3UA spec and it says that
> > > > > any messages that do not match a
> > > > > routing key are sent to a default ASP.
> > > > > So he builds his ASP to receive these
> > > > > messages only when it is configured in
> > > > > the SG as the default ASP.  His ASP
> > > > > does not work with your or Valerie's
> > > > > SGs, but he has not violated any
> > > > > requirement in the M3UA RFC.
> > > > >
> > > > > So all that results is a bunch of
> > > > > non-interoperable solutions.  That is
> > > > > not the objective of an IETF RFC.  In
> > > > > fact, an RFC should remove the
> > > > > possibility of interoperability
> > > > > through specification.  Therefore, the
> > > > > M3UA RFC should go so far as to say
> > > > > that SSN Routing Keys MUST NOT be
> > > > > supported, because non-interoperable
> > > > > solutions will result.
> > > > [TOLGA] I totally disagree. You present
> > > > some solutions, which bring some
> > > > interoperability problems, and use this
> > > > as an evidence of inappropriateness of a
> > > > solution, which does not have
> > > > interoperability problems. As I said
> > > > several times, as long as a SG
> > > > supporting SSN based routing works with
> > > > a standard M3UA based ASP, I don´t see
> > > > any problem.
> > >
> > > Which standard M3UA ASP?  Yours?
> > > Valeries?  Joes?  Several? All?
> > [TOLGA] Any ASP compliant with M3UA RFC.
> Any and all?  How do you ensure that
> your SG works with Jim's ASP? (Jim hasn't
> told the world his method yet.)
[TOLGA]If Jim´s ASP is M3UA compliant, there is no problem. But if his
method requires some changes on the ASP -and if he had implemented them
there- and if those changes require any change to the protocol, then I
don´t think it is a problem that SG can´t interwork with it. So, pleae
don´t blame me, if Jim does not want to copmly with M3UA.
>
> > >
> > > You cannot acheive interoperability in
> > > this regard without both the SG and the
> > > ASP knowing which procedures are used.
> > [TOLGA] I don´t propose this. What I
> > propose is, an implementation
> > dependent management funtionality on
> > SG, which does not require any change
> > on the peer, i.e. which won´t prevent
> > SG to work with a M3UA compliant ASP.
> But ASP needs to know what SG is doing.
> This requires some kind of change on the
> ASP.  Otherwise, and OBVIOUSLY,
> interoperability will not result.
[TOLGA] ASP does not need to know anything special.
>
> > >
> > > Therefore, you cannot (as you said
> > > previously) just implement SSN RK on the
> > > SG without the ASP knowing how it is done.
> > [TOLGA]Why? What requirement will it
> > put to ASP or to the M3UA protocol?
>
> It puts requirements on the ASP as to
> where (which AS) and in what manner (when
> configured how) it can expect to recieve
> SCCP management messages.
[TOLGA] Each AS serving a SSN will receive each message, which needs to be
routed to this SSN. The answer to the question, which ones those messages
is in the relevant SCCP specification and will be decided on SG. No
interaction is necessary from ASP.
>
> > > Is there anyone else on the list that
> > > thinks this is basis for interoperability?
> > [TOLGA} Or which thinks that
> > ýmplementing a functionality on SG
> > which does not put any requirement to
> > M3UA protocol or to the peer, is a
> > violation of the protocol?
> All three methods mentioned put
> requirements on the peer.  That's
> why they don't interoperate.
[TOLGA] It is no suprise that a non-interoperable solution does not
interoperate with a interoprable solution.

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



From mailnull@www1.ietf.org  Fri Jan 10 07:28: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 HAA26241
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 07:28:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ACepD27654
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 07:40:51 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ACe8J27611;
	Fri, 10 Jan 2003 07:40:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ACdZJ27554
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 07:39:35 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26213
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 07:26:53 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFFD539BAC.4CB6544A-ONC2256CAA.004387A7@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 14:26:46 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 02:26:50 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>


Brian,

Again the last message from me on this thread, because I think I already
started repeating the same things.

Please find the comments are below.

   Tolga
--- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> TOLGA,
>
> TOLGA ASVEREN wrote:
>                                 (Fri, 10 Jan 2003
> 13:51:14)
> >
> > Samuel,
> >
> > The point is, no special management logic should
> be necessary on ASP.
>
> The point is special management logic is required on
> the ASP so that
> it can know where and when it is receiving SCCP
> management messages.
[TOLGA] No, this is not necesary.
>
> > The ASP is just any M3UA compliant ASP, nothing
> special there.
>
> It is a VERY special ASP.  It's M3UA knows about
> SCCP mangement messages
> and knows where the particular SG is going to place
> them, whether it needs
> to register for an AS with SSN=0, whether it needs
> to only act as a default
> ASP, whether it can expect management messages on
> each AS corresponding to
> a subsystem, in fact it needs to know that the SG is
> performing SSN routing
> at all (which is not supported by dynamic
> registration).
[TOLGA] I think soon you will ask for an ASP, which can work with any SG
with no configuration at all. Of course it needs to know, which SG it needs
to connect for a specific RK in case of static configurations. Afterall,
RKs need to be agreed by both sides through configuration. I think, it is
the normal operation that each AS gets the messages, it needs to get
-including management messages-. But if you think it as necessary, then
just a few sentences might be added to IG.
>
> > BTW, does M3UA RFC tell to support any specific RK
> type? For example if a SG
> > supports only DPC based RKs, will it be compliant
> or not with RFC?  I think
> > it is totally dependent on the implementor, which
> types of RKs her/his SG is
> > going to support.
>
> Of the proper M3UA routing keys (OPC/DPC/SI) routing
> on DPC must be supported
> at a minimum, otherwise, the implementation will not
> be useful.
[TOLGA] This is what most people would expect, but is a SG, which supports
only DPC+SI RKs -anf not DPC RKs- not compliant with M3UA RFC?

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



From mailnull@www1.ietf.org  Fri Jan 10 07:30: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 HAA26266
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 07:30:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ACgKI27734
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 07:42:20 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ACg4J27708;
	Fri, 10 Jan 2003 07:42:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ACfeJ27685
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 07:41:40 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26245
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 07:28:59 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:xI7SzciFq3lpPx8V9kTb9myJ5SVDOWF8@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0ACWGD10423;
	Fri, 10 Jan 2003 05:32:16 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0ACWG219458;
	Fri, 10 Jan 2003 05:32:16 -0700
Date: Fri, 10 Jan 2003 05:32:16 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110053216.U8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF40737600.B9550294-ONC2256CAA.0042B2A6@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF40737600.B9550294-ONC2256CAA.0042B2A6@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 02:16:02PM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 14:16:02)
> 
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > TOLGA,
> >
> > TOLGA ASVEREN wrote:
> >                                 (Fri, 10 Jan 2003
> > 13:27:19)
> > >
> > > Brian,
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > > TOLGA,
> > > >
> > > > TOLGA ASVEREN wrote:
> > > >                                 (Fri, 10 Jan
> > 2003
> > > > 13:10:15)
> > > > > > In a short period of time we have two
> > > > > > approaches: yours and Valerie's.  How
> > > > > > many more approaches must both the SG
> > > > > > and ASP support to be interoperable?
> > > > > > That is what is missing from the M3UA
> > > > > > spec: a basis for interoperability.
> > > > > > As an IETF document, M3UA RFC as it
> > > > > > stands does not support SSN, because
> > > > > > there is no basis for this
> > > > > > interoperability (because it is
> > > > > > completely unspecified).
> > > > > >
> > > > > > So, tommorrow, Joe comes up with a new
> > > > > > approach for SCCP management.  He
> > > > > > reads the M3UA spec and it says that
> > > > > > any messages that do not match a
> > > > > > routing key are sent to a default ASP.
> > > > > > So he builds his ASP to receive these
> > > > > > messages only when it is configured in
> > > > > > the SG as the default ASP.  His ASP
> > > > > > does not work with your or Valerie's
> > > > > > SGs, but he has not violated any
> > > > > > requirement in the M3UA RFC.
> > > > > >
> > > > > > So all that results is a bunch of
> > > > > > non-interoperable solutions.  That is
> > > > > > not the objective of an IETF RFC.  In
> > > > > > fact, an RFC should remove the
> > > > > > possibility of interoperability
> > > > > > through specification.  Therefore, the
> > > > > > M3UA RFC should go so far as to say
> > > > > > that SSN Routing Keys MUST NOT be
> > > > > > supported, because non-interoperable
> > > > > > solutions will result.
> > > > > [TOLGA] I totally disagree. You present
> > > > > some solutions, which bring some
> > > > > interoperability problems, and use this
> > > > > as an evidence of inappropriateness of a
> > > > > solution, which does not have
> > > > > interoperability problems. As I said
> > > > > several times, as long as a SG
> > > > > supporting SSN based routing works with
> > > > > a standard M3UA based ASP, I don´t see
> > > > > any problem.
> > > >
> > > > Which standard M3UA ASP?  Yours?
> > > > Valeries?  Joes?  Several? All?
> > > [TOLGA] Any ASP compliant with M3UA RFC.
> > Any and all?  How do you ensure that
> > your SG works with Jim's ASP? (Jim hasn't
> > told the world his method yet.)
> [TOLGA]If Jim´s ASP is M3UA compliant, there is no problem. But if his
> method requires some changes on the ASP -and if he had implemented them
> there- and if those changes require any change to the protocol, then I
> don´t think it is a problem that SG can´t interwork with it. So, pleae
> don´t blame me, if Jim does not want to copmly with M3UA.

Jim's is as compliant as yours, Valerie's and Joe's.  But
it still doesn't interwork because the SG designer could
not anticipate his solution.

> >
> > > >
> > > > You cannot acheive interoperability in
> > > > this regard without both the SG and the
> > > > ASP knowing which procedures are used.
> > > [TOLGA] I don´t propose this. What I
> > > propose is, an implementation
> > > dependent management funtionality on
> > > SG, which does not require any change
> > > on the peer, i.e. which won´t prevent
> > > SG to work with a M3UA compliant ASP.
> > But ASP needs to know what SG is doing.
> > This requires some kind of change on the
> > ASP.  Otherwise, and OBVIOUSLY,
> > interoperability will not result.
> [TOLGA] ASP does not need to know anything special.

It needs to know where it will receive SCCP management
messages.  This is special.

> >
> > > >
> > > > Therefore, you cannot (as you said
> > > > previously) just implement SSN RK on the
> > > > SG without the ASP knowing how it is done.
> > > [TOLGA]Why? What requirement will it
> > > put to ASP or to the M3UA protocol?
> >
> > It puts requirements on the ASP as to
> > where (which AS) and in what manner (when
> > configured how) it can expect to recieve
> > SCCP management messages.
> [TOLGA] Each AS serving a SSN will receive each message, which needs to be
> routed to this SSN. The answer to the question, which ones those messages
> is in the relevant SCCP specification and will be decided on SG. No
> interaction is necessary from ASP.

SCCP specifications say nothing about ASPs, or to which
AS SCCP management messages need to be routed.

> >
> > > > Is there anyone else on the list that
> > > > thinks this is basis for interoperability?
> > > [TOLGA} Or which thinks that
> > > ýmplementing a functionality on SG
> > > which does not put any requirement to
> > > M3UA protocol or to the peer, is a
> > > violation of the protocol?
> > All three methods mentioned put
> > requirements on the peer.  That's
> > why they don't interoperate.
> [TOLGA] It is no suprise that a non-interoperable solution does not
> interoperate with a interoprable solution.

None of these solutions are interoperable.

--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  Fri Jan 10 07:34:17 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 HAA26315
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 07:34:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ACkRN27860
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 07:46:27 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ACk5J27839;
	Fri, 10 Jan 2003 07:46:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ACjlJ27818
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 07:45:47 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26297
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 07:33:05 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:9byOFi3xuo7oOh2usRXHey5womeYNPnw@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0ACaMD10475;
	Fri, 10 Jan 2003 05:36:22 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0ACaMM19532;
	Fri, 10 Jan 2003 05:36:22 -0700
Date: Fri, 10 Jan 2003 05:36:22 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110053622.V8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OFFD539BAC.4CB6544A-ONC2256CAA.004387A7@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OFFD539BAC.4CB6544A-ONC2256CAA.004387A7@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 02:26:46PM +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>

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 14:26:46)
> 
> Brian,
> 
> Again the last message from me on this thread, because I think I already
> started repeating the same things.
> 
> Please find the comments are below.
> 
>    Tolga
> --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > TOLGA,
> >
> > TOLGA ASVEREN wrote:
> >                                 (Fri, 10 Jan 2003
> > 13:51:14)
> > >
> > > Samuel,
> > >
> > > The point is, no special management logic should
> > be necessary on ASP.
> >
> > The point is special management logic is required on
> > the ASP so that
> > it can know where and when it is receiving SCCP
> > management messages.
> [TOLGA] No, this is not necesary.

It is necessary so that the ASP can route the SCCP management
messages to the correct SCCP user.

> >
> > > The ASP is just any M3UA compliant ASP, nothing
> > special there.
> >
> > It is a VERY special ASP.  It's M3UA knows about
> > SCCP mangement messages
> > and knows where the particular SG is going to place
> > them, whether it needs
> > to register for an AS with SSN=0, whether it needs
> > to only act as a default
> > ASP, whether it can expect management messages on
> > each AS corresponding to
> > a subsystem, in fact it needs to know that the SG is
> > performing SSN routing
> > at all (which is not supported by dynamic
> > registration).
> [TOLGA] I think soon you will ask for an ASP, which can work with any SG
> with no configuration at all. Of course it needs to know, which SG it needs
> to connect for a specific RK in case of static configurations. Afterall,
> RKs need to be agreed by both sides through configuration. I think, it is
> the normal operation that each AS gets the messages, it needs to get
> -including management messages-. But if you think it as necessary, then
> just a few sentences might be added to IG.

M3UA RFC covers SSNM.  It does not cover SCCP management messages.

If you want to add text to M3UA to allow it to support SSN routing,
do so.  My point has always been that it does not support SSN routing
as it stands.  What is your proposed text?

> >
> > > BTW, does M3UA RFC tell to support any specific RK
> > type? For example if a SG
> > > supports only DPC based RKs, will it be compliant
> > or not with RFC?  I think
> > > it is totally dependent on the implementor, which
> > types of RKs her/his SG is
> > > going to support.
> >
> > Of the proper M3UA routing keys (OPC/DPC/SI) routing
> > on DPC must be supported
> > at a minimum, otherwise, the implementation will not
> > be useful.
> [TOLGA] This is what most people would expect, but is a SG, which supports
> only DPC+SI RKs -anf not DPC RKs- not compliant with M3UA RFC?

No. But if it does not support any routing keys, the implementation will
not be useful.  If it supports only SSN routing keys, it will be useless.

--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  Fri Jan 10 07:47: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 HAA26604
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 07:47:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ACxdY28460
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 07:59:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ACx7J28430;
	Fri, 10 Jan 2003 07:59:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ACwZJ28404
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 07:58:35 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26540
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 07:45:54 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0ACn9aN000585;
	Fri, 10 Jan 2003 06:49:09 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0ACn1M00299;
	Fri, 10 Jan 2003 06:49:01 -0600 (CST)
Date: Fri, 10 Jan 2003 06:49:01 -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] m3ua- IG
In-Reply-To: <OF99CAD5F0.72432D40-ONC2256CAA.0040889B@LocalDomain>
Message-ID: <Pine.SOL.4.10.10301100639580.10518-100000@sun3271.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id h0ACwZJ28405
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


Tolga,
  
Say i have implemented M3UA with SSN RK.means my node has a
database which contains Subsystem backup type(such as Load
shared,replicate...) and Subsystem status(such as available,congested and
unavailable).

Subsystem at ASP is congested or unavailable ,How does ASP indicate this
to SG? Do you have any M3UA message which will say so and so subsytem is
congested...like this lot issues are there.


--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, 10 Jan 2003, TOLGA ASVEREN wrote:

> 
> Samuel,
> 
> The point is, no special management logic should be necessary on ASP. The
> ASP is just any M3UA compliant ASP, nothing special there. BTW, does M3UA
> RFC tell to support any specific RK type? For example if a SG supports only
> DPC based RKs, will it be compliant or not with RFC?
> I think it is totally dependent on the implementor, which types of RKs
> her/his SG is going to support.
> 
>     Tolga
> 
> 
> 
> 
> 
> Tolga,
> 
> If X has implemented SG with SSN RK (eventhough it is not told in rfc),
> How does X expect Y to implement the same 'management logic' at ASP?
> 
> Everyone will try to follow RFC strictly to go for interop.
> 
> Blindly speaking SSN is not a field(whereas SSN in one of the fields in
> SUA messages) of any M3UA message so nobody will implement SSN RK with
> M3UA stack.
> 
> --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, 10 Jan 2003, TOLGA ASVEREN wrote:
> 
> >
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > > TOLGA,
> > >
> > > TOLGA ASVEREN wrote:
> > >                                 (Fri, 10 Jan 2003
> > > 13:10:15)
> > > > > In a short period of time we have two
> > > > > approaches: yours and Valerie's.  How
> > > > > many more approaches must both the SG
> > > > > and ASP support to be interoperable?
> > > > > That is what is missing from the M3UA
> > > > > spec: a basis for interoperability.
> > > > > As an IETF document, M3UA RFC as it
> > > > > stands does not support SSN, because
> > > > > there is no basis for this
> > > > > interoperability (because it is
> > > > > completely unspecified).
> > > > >
> > > > > So, tommorrow, Joe comes up with a new
> > > > > approach for SCCP management.  He
> > > > > reads the M3UA spec and it says that
> > > > > any messages that do not match a
> > > > > routing key are sent to a default ASP.
> > > > > So he builds his ASP to receive these
> > > > > messages only when it is configured in
> > > > > the SG as the default ASP.  His ASP
> > > > > does not work with your or Valerie's
> > > > > SGs, but he has not violated any
> > > > > requirement in the M3UA RFC.
> > > > >
> > > > > So all that results is a bunch of
> > > > > non-interoperable solutions.  That is
> > > > > not the objective of an IETF RFC.  In
> > > > > fact, an RFC should remove the
> > > > > possibility of interoperability
> > > > > through specification.  Therefore, the
> > > > > M3UA RFC should go so far as to say
> > > > > that SSN Routing Keys MUST NOT be
> > > > > supported, because non-interoperable
> > > > > solutions will result.
> > > > [TOLGA] I totally disagree. You present
> > > > some solutions, which bring some
> > > > interoperability problems, and use this
> > > > as an evidence of inappropriateness of a
> > > > solution, which does not have
> > > > interoperability problems. As I said
> > > > several times, as long as a SG
> > > > supporting SSN based routing works with
> > > > a standard M3UA based ASP, I don´t see
> > > > any problem.
> > >
> > > Which standard M3UA ASP?  Yours?
> > > Valeries?  Joes?  Several? All?
> > [TOLGA] Any ASP compliant with M3UA RFC.
> > >
> > > You cannot acheive interoperability in
> > > this regard without both the SG and the
> > > ASP knowing which procedures are used.
> > [TOLGA] I don´t propose this. What I propose is, an implementation
> > dependent management funtionality on SG, which does not require any
> change
> > on the peer, i.e. which won´t prevent SG to work with a M3UA compliant
> ASP.
> > >
> > > Therefore, you cannot (as you said
> > > previously) just implement SSN RK on the
> > > SG without the ASP knowing how it is done.
> > [TOLGA]Why? What requirement will it put to ASP or to the M3UA protocol?
> > >
> > > Is there anyone else on the list that
> > > thinks this is basis for interoperability?
> > [TOLGA} Or which thinks that ýmplementing a functionality on SG which
> does
> > not put any requirement to M3UA protocol or to the peer, is a violation
> of
> > the protocol?
> >
> > _______________________________________________
> > 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 Jan 10 07:56: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 HAA26758
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 07:56:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AD8rE29497
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:08:53 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AD8VJ29477;
	Fri, 10 Jan 2003 08:08:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AD77J28969
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:07:07 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26727
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 07:54:24 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF8041D52A.9F9F6CB2-ONC2256CAA.0046B2BE@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 14:54:18 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 02:54:22 PM
MIME-Version: 1.0
Content-type: text/plain; charset=Windows-1254
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0AD77J28971
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


Samuel,

As you have also pointed out in one of your messages, this will be sent as
a SCCP management message in DATA. Then it is up to management logic in SG
to decide whether the global SSN state should be updated or not (similar to
what happens with SPMC availability/unavailability)

      Tolga





Tolga,

Say i have implemented M3UA with SSN RK.means my node has a
database which contains Subsystem backup type(such as Load
shared,replicate...) and Subsystem status(such as available,congested and
unavailable).

Subsystem at ASP is congested or unavailable ,How does ASP indicate this
to SG? Do you have any M3UA message which will say so and so subsytem is
congested...like this lot issues are there.


--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, 10 Jan 2003, TOLGA ASVEREN wrote:

>
> Samuel,
>
> The point is, no special management logic should be necessary on ASP. The
> ASP is just any M3UA compliant ASP, nothing special there. BTW, does M3UA
> RFC tell to support any specific RK type? For example if a SG supports
only
> DPC based RKs, will it be compliant or not with RFC?
> I think it is totally dependent on the implementor, which types of RKs
> her/his SG is going to support.
>
>     Tolga
>
>
>
>
>
> Tolga,
>
> If X has implemented SG with SSN RK (eventhough it is not told in rfc),
> How does X expect Y to implement the same 'management logic' at ASP?
>
> Everyone will try to follow RFC strictly to go for interop.
>
> Blindly speaking SSN is not a field(whereas SSN in one of the fields in
> SUA messages) of any M3UA message so nobody will implement SSN RK with
> M3UA stack.
>
> --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, 10 Jan 2003, TOLGA ASVEREN wrote:
>
> >
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > > TOLGA,
> > >
> > > TOLGA ASVEREN wrote:
> > >                                 (Fri, 10 Jan 2003
> > > 13:10:15)
> > > > > In a short period of time we have two
> > > > > approaches: yours and Valerie's.  How
> > > > > many more approaches must both the SG
> > > > > and ASP support to be interoperable?
> > > > > That is what is missing from the M3UA
> > > > > spec: a basis for interoperability.
> > > > > As an IETF document, M3UA RFC as it
> > > > > stands does not support SSN, because
> > > > > there is no basis for this
> > > > > interoperability (because it is
> > > > > completely unspecified).
> > > > >
> > > > > So, tommorrow, Joe comes up with a new
> > > > > approach for SCCP management.  He
> > > > > reads the M3UA spec and it says that
> > > > > any messages that do not match a
> > > > > routing key are sent to a default ASP.
> > > > > So he builds his ASP to receive these
> > > > > messages only when it is configured in
> > > > > the SG as the default ASP.  His ASP
> > > > > does not work with your or Valerie's
> > > > > SGs, but he has not violated any
> > > > > requirement in the M3UA RFC.
> > > > >
> > > > > So all that results is a bunch of
> > > > > non-interoperable solutions.  That is
> > > > > not the objective of an IETF RFC.  In
> > > > > fact, an RFC should remove the
> > > > > possibility of interoperability
> > > > > through specification.  Therefore, the
> > > > > M3UA RFC should go so far as to say
> > > > > that SSN Routing Keys MUST NOT be
> > > > > supported, because non-interoperable
> > > > > solutions will result.
> > > > [TOLGA] I totally disagree. You present
> > > > some solutions, which bring some
> > > > interoperability problems, and use this
> > > > as an evidence of inappropriateness of a
> > > > solution, which does not have
> > > > interoperability problems. As I said
> > > > several times, as long as a SG
> > > > supporting SSN based routing works with
> > > > a standard M3UA based ASP, I don´t see
> > > > any problem.
> > >
> > > Which standard M3UA ASP?  Yours?
> > > Valeries?  Joes?  Several? All?
> > [TOLGA] Any ASP compliant with M3UA RFC.
> > >
> > > You cannot acheive interoperability in
> > > this regard without both the SG and the
> > > ASP knowing which procedures are used.
> > [TOLGA] I don´t propose this. What I propose is, an implementation
> > dependent management funtionality on SG, which does not require any
> change
> > on the peer, i.e. which won´t prevent SG to work with a M3UA compliant
> ASP.
> > >
> > > Therefore, you cannot (as you said
> > > previously) just implement SSN RK on the
> > > SG without the ASP knowing how it is done.
> > [TOLGA]Why? What requirement will it put to ASP or to the M3UA
protocol?
> > >
> > > Is there anyone else on the list that
> > > thinks this is basis for interoperability?
> > [TOLGA} Or which thinks that ýmplementing a functionality on SG which
> does
> > not put any requirement to M3UA protocol or to the peer, is a violation
> of
> > the protocol?
> >
> > _______________________________________________
> > 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




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



From mailnull@www1.ietf.org  Fri Jan 10 08:03: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 IAA26920
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:03:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADFHv29724
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:15:17 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADEnJ29691;
	Fri, 10 Jan 2003 08:14:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADDeJ29647
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:13:40 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26870
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:00:58 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:2lDRcyTYH5ObUKgmlKn8n0uB2jZzdd5Y@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0AD4FD10963;
	Fri, 10 Jan 2003 06:04:15 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0AD4FG20562;
	Fri, 10 Jan 2003 06:04:15 -0700
Date: Fri, 10 Jan 2003 06:04:14 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110060414.W8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF8041D52A.9F9F6CB2-ONC2256CAA.0046B2BE@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF8041D52A.9F9F6CB2-ONC2256CAA.0046B2BE@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 02:54:18PM +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>

TOLGA,

Then you would have the SG intercepting and altering DATA sent to it by the AS?
This was the same as the problem for CIC.  The ASP has an expectation (stated
in the RFC) that DATA messages are transferred unaltered.

--brian

TOLGA ASVEREN wrote:                              (Fri, 10 Jan 2003 14:54:18)
> 
> Samuel,
> 
> As you have also pointed out in one of your messages, this will be sent as
> a SCCP management message in DATA. Then it is up to management logic in SG
> to decide whether the global SSN state should be updated or not (similar to
> what happens with SPMC availability/unavailability)
> 
>       Tolga
> 

-- 
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 Jan 10 08:08: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 IAA26991
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:08:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADKsF29960
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:20:54 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADI4J29823;
	Fri, 10 Jan 2003 08:18:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADHwJ29795
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:17:58 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26953
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:05:16 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFEDCE8E22.ACC36D2C-ONC2256CAA.0046F313@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 15:05:08 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 03:05:13 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>


Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> TOLGA,
>
> TOLGA ASVEREN wrote:
>                                 (Fri, 10 Jan 2003
> 14:26:46)
> >
> > Brian,
> >
> > Again the last message from me on this thread,
> because I think I already
> > started repeating the same things.
> >
> > Please find the comments are below.
> >
> >    Tolga
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > > TOLGA,
> > >
> > > TOLGA ASVEREN wrote:
> > >                                 (Fri, 10 Jan
> 2003
> > > 13:51:14)
> > > >
> > > > Samuel,
> > > >
> > > > The point is, no special management logic
> should
> > > be necessary on ASP.
> > >
> > > The point is special management logic is
> required on
> > > the ASP so that
> > > it can know where and when it is receiving SCCP
> > > management messages.
> > [TOLGA] No, this is not necesary.
>
> It is necessary so that the ASP can route the SCCP
> management
> messages to the correct SCCP user.
[TOLGA] M3UA-ASP routes the messages based on RC. So, each message will be
sent to the entity serving the AS corresponding to RC in the message.
M3UA-ASP does not need to know -and it does not know- that inside DATA
there is a SCCP management message. SG takes care of everything.
>
> > >
> > > > The ASP is just any M3UA compliant ASP,
> nothing
> > > special there.
> > >
> > > It is a VERY special ASP.  It's M3UA knows about
> > > SCCP mangement messages
> > > and knows where the particular SG is going to
> place
> > > them, whether it needs
> > > to register for an AS with SSN=0, whether it
> needs
> > > to only act as a default
> > > ASP, whether it can expect management messages
> on
> > > each AS corresponding to
> > > a subsystem, in fact it needs to know that the
> SG is
> > > performing SSN routing
> > > at all (which is not supported by dynamic
> > > registration).
> > [TOLGA] I think soon you will ask for an ASP,
> which can work with any SG
> > with no configuration at all. Of course it needs
> to know, which SG it needs
> > to connect for a specific RK in case of static
> configurations. Afterall,
> > RKs need to be agreed by both sides through
> configuration. I think, it is
> > the normal operation that each AS gets the
> messages, it needs to get
> > -including management messages-. But if you think
> it as necessary, then
> > just a few sentences might be added to IG.
>
> M3UA RFC covers SSNM.  It does not cover SCCP
> management messages.
[TOLGA] It covers SSNM because it is a MTP3/MTP3 User interface. SCCP
management message are encapsulated in DATA.
>
> If you want to add text to M3UA to allow it to
> support SSN routing,
> do so.  My point has always been that it does not
> support SSN routing
> as it stands.  What is your proposed text?
[TOLGA] 1.4.2.2
"For RK types, which are not based on MTP3/MTP3-User Interface
constructs(DPC, SI) some management functionality might be necessary. This
functionality should be implemented on SG and is implementation dependent.
It should be taken care of, that no special behavior from the peer is
expected.
>
> > >
> > > > BTW, does M3UA RFC tell to support any
> specific RK
> > > type? For example if a SG
> > > > supports only DPC based RKs, will it be
> compliant
> > > or not with RFC?  I think
> > > > it is totally dependent on the implementor,
> which
> > > types of RKs her/his SG is
> > > > going to support.
> > >
> > > Of the proper M3UA routing keys (OPC/DPC/SI)
> routing
> > > on DPC must be supported
> > > at a minimum, otherwise, the implementation will
> not
> > > be useful.
> > [TOLGA] This is what most people would expect, but
> is a SG, which supports
> > only DPC+SI RKs -anf not DPC RKs- not compliant
> with M3UA RFC?
>
> No. But if it does not support any routing keys, the
> implementation will
> not be useful.  If it supports only SSN routing
> keys, it will be useless.

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



From mailnull@www1.ietf.org  Fri Jan 10 08:11: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 IAA27085
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:11:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADNd530127
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:23:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADN9J30095;
	Fri, 10 Jan 2003 08:23:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADMdJ30056
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:22:39 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27047
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:09:56 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0ADDAOd022129;
	Fri, 10 Jan 2003 07:13:12 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0ADCMM07559;
	Fri, 10 Jan 2003 07:12:22 -0600 (CST)
Date: Fri, 10 Jan 2003 07:12:22 -0600 (CST)
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] m3ua- IG
In-Reply-To: <20030110041554.P8782@openss7.org>
Message-ID: <Pine.SOL.4.10.10301100652420.10518-100000@sun3271.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,

So, this normal MTP-User will not perform GTT?

if it performs see the following case
 
SCCP finds SSN (say GTT resulted DPC+SSN)as prohibited, MTP can not route
this message successfully with DPC alone.This case WHEN will this SSN will
become unprohibited, until you get a message from ASP saying 'now SSN is
not prohibited' Is it not so?

if it so Which M3UA message carries this information from ASP to SG?

--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, 10 Jan 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> When SCCP sends these messages to MTP, they get routed through the
> SS7 network on DPC only.  SCCP does not need any more service than
> is provided by MTP.  So, things will work fine if M3UA routes on
> DPC only.  M3UA no more needs to look at SSN than MTP does (and
> MTP does not need to look at SSN, it uses DPC only).  Look at Q.714
> routing rules to see how MTP transfers all messages on DPC only.
> Only once the message gets to the DPC is SSN or GT examined by
> SCCP to determine the proper SCCP-User.
> 
> So, in the example in 1.5.3, SCCP is acting as a normal MTP-User.
> It sends messages to MTP with MTP-TRANSFER primitive and expects
> them to be routed by MTP on the DPC, without reference to the SSN.
> To provide correct service to SCCP, M3UA must do the same.
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 04:58:34)
> > 
> > Brian,
> > 
> > DPC is not consisting of only HLR but it also has LNP(Locan Number
> > Portability),ALR(Application Location Register).. under one SPMC.
> > 
> > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > 
> > > Samuel,
> > > 
> > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 03:59:45)
> > > > 
> > > > Brian,
> > > > 
> > > > See the mail below you said 'full-blown SCCP' which means matured sccp.
> > > > But now you are saying normal MTP-user.
> > > > 
> > > > Ok.Suppose GTT results in DPC+HLR.
> > > > Say under one SPMC we have Subsystetems HLR,ALR and LNP.
> > > > 
> > > > Now How does SGP know to route the message(DATA) to the particular(HLR)
> > > > SSN?
> > > 
> > > It routes on DPC.
> > > 
> > > --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 mailnull@www1.ietf.org  Fri Jan 10 08:12: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 IAA27114
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:12:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADOF530167
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:24:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADO4J30160;
	Fri, 10 Jan 2003 08:24:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADNgJ30139
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:23:42 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27072
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:11:00 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFAFEE2463.0CB73303-ONC2256CAA.0047FBE0@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 15:10:53 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 03:10:57 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>


Brian,



TOLGA,

Then you would have the SG intercepting and altering DATA sent to it by the
AS?
This was the same as the problem for CIC.  The ASP has an expectation
(stated
in the RFC) that DATA messages are transferred unaltered.
[TOLGA] (In addition to the changes I initially proposed)
"This management functionality might require that some messages are
filtered/generated by SG."

--brian

TOLGA ASVEREN wrote:                              (Fri, 10 Jan 2003
14:54:18)
>
> Samuel,
>
> As you have also pointed out in one of your messages, this will be sent
as
> a SCCP management message in DATA. Then it is up to management logic in
SG
> to decide whether the global SSN state should be updated or not (similar
to
> what happens with SPMC availability/unavailability)
>
>       Tolga
>

--
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 Jan 10 08:15:19 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 IAA27157
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:15:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADRTl30290
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:27:29 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADR4J30266;
	Fri, 10 Jan 2003 08:27:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADQkJ30245
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:26:46 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27146
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:14:04 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:7CDPZReYKNLABjldIvlEH3WK/ZbLNWIf@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0ADHLD11121;
	Fri, 10 Jan 2003 06:17:21 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0ADHLS20881;
	Fri, 10 Jan 2003 06:17:21 -0700
Date: Fri, 10 Jan 2003 06:17:21 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110061721.X8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OFEDCE8E22.ACC36D2C-ONC2256CAA.0046F313@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OFEDCE8E22.ACC36D2C-ONC2256CAA.0046F313@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 03:05:08PM +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>

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 15:05:08)
> 
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > TOLGA,
> >
> > TOLGA ASVEREN wrote:
> >                                 (Fri, 10 Jan 2003
> > 14:26:46)
> > >
> > > Brian,
> > >
> > > Again the last message from me on this thread,
> > because I think I already
> > > started repeating the same things.
> > >
> > > Please find the comments are below.
> > >
> > >    Tolga
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > > TOLGA,
> > > >
> > > > TOLGA ASVEREN wrote:
> > > >                                 (Fri, 10 Jan
> > 2003
> > > > 13:51:14)
> > > > >
> > > > > Samuel,
> > > > >
> > > > > The point is, no special management logic
> > should
> > > > be necessary on ASP.
> > > >
> > > > The point is special management logic is
> > required on
> > > > the ASP so that
> > > > it can know where and when it is receiving SCCP
> > > > management messages.
> > > [TOLGA] No, this is not necesary.
> >
> > It is necessary so that the ASP can route the SCCP
> > management
> > messages to the correct SCCP user.
> [TOLGA] M3UA-ASP routes the messages based on RC. So, each message will be
> sent to the entity serving the AS corresponding to RC in the message.
> M3UA-ASP does not need to know -and it does not know- that inside DATA
> there is a SCCP management message. SG takes care of everything.

The SG does not send messages to SCCP users.  How will the ASP get the
management messages get to the SCCP user?

> >
> > > >
> > > > > The ASP is just any M3UA compliant ASP,
> > nothing
> > > > special there.
> > > >
> > > > It is a VERY special ASP.  It's M3UA knows about
> > > > SCCP mangement messages
> > > > and knows where the particular SG is going to
> > place
> > > > them, whether it needs
> > > > to register for an AS with SSN=0, whether it
> > needs
> > > > to only act as a default
> > > > ASP, whether it can expect management messages
> > on
> > > > each AS corresponding to
> > > > a subsystem, in fact it needs to know that the
> > SG is
> > > > performing SSN routing
> > > > at all (which is not supported by dynamic
> > > > registration).
> > > [TOLGA] I think soon you will ask for an ASP,
> > which can work with any SG
> > > with no configuration at all. Of course it needs
> > to know, which SG it needs
> > > to connect for a specific RK in case of static
> > configurations. Afterall,
> > > RKs need to be agreed by both sides through
> > configuration. I think, it is
> > > the normal operation that each AS gets the
> > messages, it needs to get
> > > -including management messages-. But if you think
> > it as necessary, then
> > > just a few sentences might be added to IG.
> >
> > M3UA RFC covers SSNM.  It does not cover SCCP
> > management messages.
> [TOLGA] It covers SSNM because it is a MTP3/MTP3 User interface. SCCP
> management message are encapsulated in DATA.

M3UA RFC also covers the treatment of DATA.  DATA is never sent
to more than one ASP except in a broadcast mode AS.  It looks like
your suggestion (sending SCCP management messages to multiple ASPs
in DATA) is not compliant with the M3UA RFC.  Valerie's and Joe's
are compliant.

> >
> > If you want to add text to M3UA to allow it to
> > support SSN routing,
> > do so.  My point has always been that it does not
> > support SSN routing
> > as it stands.  What is your proposed text?
> [TOLGA] 1.4.2.2
> "For RK types, which are not based on MTP3/MTP3-User Interface
> constructs(DPC, SI) some management functionality might be necessary. This
> functionality should be implemented on SG and is implementation dependent.
> It should be taken care of, that no special behavior from the peer is
> expected.

This does not tell ASP how to expect SCCP management (or messages
not containing SSN) to be kouted differently than SCCP messages.
You proposed text is not a basis for interoperability at all.

> >
> > > >
> > > > > BTW, does M3UA RFC tell to support any
> > specific RK
> > > > type? For example if a SG
> > > > > supports only DPC based RKs, will it be
> > compliant
> > > > or not with RFC?  I think
> > > > > it is totally dependent on the implementor,
> > which
> > > > types of RKs her/his SG is
> > > > > going to support.
> > > >
> > > > Of the proper M3UA routing keys (OPC/DPC/SI)
> > routing
> > > > on DPC must be supported
> > > > at a minimum, otherwise, the implementation will
> > not
> > > > be useful.
> > > [TOLGA] This is what most people would expect, but
> > is a SG, which supports
> > > only DPC+SI RKs -anf not DPC RKs- not compliant
> > with M3UA RFC?
> >
> > No. But if it does not support any routing keys, the
> > implementation will
> > not be useful.  If it supports only SSN routing
> > keys, it will be useless.
> 
> _______________________________________________
> 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 Jan 10 08:20: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 IAA27364
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:20:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADWW830579
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:32:32 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADW8J30543;
	Fri, 10 Jan 2003 08:32:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADVqJ30512
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:31:52 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27338
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:19:09 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Vkm8S76WNjlBExztAiMdLIsLDiJPqlNQ@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0ADMQD11185;
	Fri, 10 Jan 2003 06:22:26 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0ADMQb21085;
	Fri, 10 Jan 2003 06:22:26 -0700
Date: Fri, 10 Jan 2003 06:22:26 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110062226.Y8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OFAFEE2463.0CB73303-ONC2256CAA.0047FBE0@LocalDomain>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="n8g4imXOkfNTN/H1"
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OFAFEE2463.0CB73303-ONC2256CAA.0047FBE0@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 03:10:53PM +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>


--n8g4imXOkfNTN/H1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 15:10:53)
> 
> Brian,
> 
> 
> 
> TOLGA,
> 
> Then you would have the SG intercepting and altering DATA sent to it by the
> AS?
> This was the same as the problem for CIC.  The ASP has an expectation
> (stated
> in the RFC) that DATA messages are transferred unaltered.
> [TOLGA] (In addition to the changes I initially proposed)
> "This management functionality might require that some messages are
> filtered/generated by SG."

Which messages?  The ASP has an expectation that DATA messages that it sends
are not altered.  Are you saying that ANY DATA message can be altered,
filtered, generated?  That is in conflict with statements in the RFC requiring
non-encapsulation of MTP management messages and normal DATA message flows.
Please redescribe the discrimination and distribution functions of M3UA with
the additions of these new filtering and generation procedures.  I provided on
the CIC thread a number of statements in the RFC that present that no
alteration be made to DATA messages (see attached).  Please provide proposed
text changes for each of those sections.

--brian

> 
> --brian
> 
> TOLGA ASVEREN wrote:                              (Fri, 10 Jan 2003
> 14:54:18)
> >
> > Samuel,
> >
> > As you have also pointed out in one of your messages, this will be sent
> as
> > a SCCP management message in DATA. Then it is up to management logic in
> SG
> > to decide whether the global SSN state should be updated or not (similar
> to
> > what happens with SPMC availability/unavailability)
> >
> >       Tolga
> >
> 
> --
> 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/

--n8g4imXOkfNTN/H1
Content-Type: message/rfc822
Content-Disposition: inline

Return-Path: <sigtran-admin@ietf.org>
Received: from gw.openss7.com (IDENT:GlrBFmtZrj8wLAspP11Ic7pA6ImEStya@ns2.evil.openss7.net [192.168.9.2])
	by ns.pigworks.openss7.net (8.11.6/8.11.6) with ESMTP id h05DEiW24544
	for <bidulock@ns1.evil.openss7.net>; Sun, 5 Jan 2003 06:14:44 -0700
Received: from www1.ietf.org (ietf.org [132.151.1.19])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h05DEhD02126
	for <bidulock@openss7.org>; Sun, 5 Jan 2003 06:14:43 -0700
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05DLOJ32033;
	Sun, 5 Jan 2003 08:21:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h05DIvJ31969
	for <sigtran@optimus.ietf.org>; Sun, 5 Jan 2003 08:18:57 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05025
	for <sigtran@ietf.org>; Sun, 5 Jan 2003 08:08:41 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:QNnoMIQ3nsU62MVr5ycSUBBOG08rWUyZ@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h05DBsD02100;
	Sun, 5 Jan 2003 06:11:54 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h05DBs024531;
	Sun, 5 Jan 2003 06:11:54 -0700
Date: Sun, 5 Jan 2003 06:11:54 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA distributing ISUP group messages
Message-ID: <20030105061154.S23879@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030104180446.Q23879@openss7.org> <20030105121025.10418.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: <20030105121025.10418.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sun, Jan 05, 2003 at 04:10:25AM -0800
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>
X-Loop: brian@ns.pigworks.openss7.org
X-Mozilla-Status: 0000
X-Mozilla-Status2: 00000000

Tolga,

Tolga Asveren wrote:                                                                 (Sun, 05 Jan 2003 04:10:25)
> [TOLGA] I feel I really fail to explain
> what I mean.  The real point is, if
> somebody can do it without
> interoperability problems, let them do
> it.

Let them do it outside of the standard
unless they can (at least logically)
demonstrate interoperability.

> And for some RK type even if it is
> really impossible, why us this related
> with M3UA itself? It is clear that for
> non-MTP3 RKs some management logic needs
> to be implemented and without violating
> the protocol. IMO, this is the only
> relevant thing from M3UA point of view.

Section 3.3.1:

  "The DATA message contains the SS7
  MTP3-User protocol data, which is an
  MTP-TRANSFER primitive, including the
  complete MTP3 Routing Label."

Split CGBs are not MTP-TRANSFER
primitives.

Section 3.3.1:

  "The Protocol Data parameter contains
  the original SS7 MTP3 message, including
  the Service Information Octet and
  Routing Label."

Split CGBs are not the "original SS7
MTP3 message".

Section 3.3.1:

  "The User Protocol Data field contains
  a byte string of MTP-User information
  from the original SS7 message starting
  with the first byte of the original SS7
  message following the Routing Label."

Split CGBs do not contain the original
SS7 byte for byte as indicated here.

Section 1.5.1

  "For internal SGP modeling purposes, at
  the NIF level, SS7 signalling messages
  that are destined to the MGC are
  received as MTP-TRANSFER indication
  primitives from the MTP Level 3 upper
  layer interface, translated to
  MTP-TRANSFER request primitives, and
  sent to the local M3UA-resident message
  distribution function for outgoing
  routing to the final IP destination.
  Messages received from the local M3UA
  network address translations and mapping
  function as MTP-TRANSFER indication
  primitives ar esent to the MTP Level 3
  upper layer interface as MTP-TRANSFER
  request primitives for outgoing MTP
  Level 3 routing to an SS7 SEP."

The message distribution function and
network address translations (routing) is
M3UA-resident (it is not in the NIF).

(Note that the above was also the only
ISUP example in the spec.)

Section 4.1.1:

  "The M3UA peer receiving the DATA
  message sends a MTP-TRANSFER indication
  primitive to the upper layer."

  "The M3UA message distribution function
  (see Section 1.4.2.1) determins the
  Application Server (AS) based on
  comparing the information in the
  MTP-TRANSFER request primitive with a
  provisioned Routing Key."

Comparison with Routing Keys occurs in the
M3UA, not the NIF.

Section 5.4.2.1:

  "When the M3UA layer at the SGP has
  received DATA messages from its peer
  destined to the SS7 network it will do
  the following:

  - Evaluate the optional fields of the
    DATA message, if present, to determine
    the Network Appearance;

  - Map the Protocol data field of the
    DATA message into an MTP-TRANSFER
    request primitive;

  - Pass the MTP-TRANSFER request
    primitive to the MTP3 of the concerned
    Network Appearance."

Aggregating CGBA responses would violate
this procedure.

> [TOLGA] For me the guideline is RFC/IG.
> As long as one does not violate it,
> she/he is free to do anyhting. I agree,
> the same applies to NIF, never violate
> the protocol. This is also my opinion
> for non-MTP3 RKs, if one can support
> them by not breaking the protocol, they
> are free to do it.

Who is "they?"

For CIC routing keys, the only current
propsal that does not violate the protocol
is to ensure than no circuit groups span
routing keys, ensuring that there is
always a default AS, and arranging
circuits and trunks such that a circuit
group message will never be generated that
spans the routing keys.

(Which is what I was telling Joseph when
you proposed your splitting algorithm
which violates all of the above.)

The fully interoperable way to acheive
what is being attempted with CIC routing
keys (but fails dismally) is by
_load-sharing_ on CIC ranges rather than
_routing_ on CIC ranges.

Why would anyone want to court a
proprietary solution (CIC routing) when an
interoperable solution (CIC load-sharing)
exists? 

I don't see any problem saying that M3UA
MUST use CIC load-sharing, which is
demonstrably interoperable, and MUST NOT
use CIC routing keys which cannot (any
time soon) be demonstrated  to
interoperate.

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

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



From mailnull@www1.ietf.org  Fri Jan 10 08:22: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 IAA27400
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:22:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADYGg30682
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:34:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADY5J30674;
	Fri, 10 Jan 2003 08:34:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADXpJ30658
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:33:51 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27380
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:21:09 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:M+Pcdsy8+3Y4s7H/G1nVWfiiGAP/anMX@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0ADOQD11206;
	Fri, 10 Jan 2003 06:24:26 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0ADOPa21110;
	Fri, 10 Jan 2003 06:24:25 -0700
Date: Fri, 10 Jan 2003 06:24:25 -0700
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] m3ua- IG
Message-ID: <20030110062425.Z8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030110041554.P8782@openss7.org> <Pine.SOL.4.10.10301100652420.10518-100000@sun3271.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.10301100652420.10518-100000@sun3271.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Jan 10, 2003 at 07:12:22AM -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,

You are confused:

 - MTP routes messages on DPC.
 - SCCP runs over MTP (today in SS7 network).
 - SCCP does not need M3UA to route on SSN to support it.

Read Q.714.

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 07:12:22)
> 
> Brian,
> 
> So, this normal MTP-User will not perform GTT?
> 
> if it performs see the following case
>  
> SCCP finds SSN (say GTT resulted DPC+SSN)as prohibited, MTP can not route
> this message successfully with DPC alone.This case WHEN will this SSN will
> become unprohibited, until you get a message from ASP saying 'now SSN is
> not prohibited' Is it not so?
> 
> if it so Which M3UA message carries this information from ASP to SG?
> 
> --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > When SCCP sends these messages to MTP, they get routed through the
> > SS7 network on DPC only.  SCCP does not need any more service than
> > is provided by MTP.  So, things will work fine if M3UA routes on
> > DPC only.  M3UA no more needs to look at SSN than MTP does (and
> > MTP does not need to look at SSN, it uses DPC only).  Look at Q.714
> > routing rules to see how MTP transfers all messages on DPC only.
> > Only once the message gets to the DPC is SSN or GT examined by
> > SCCP to determine the proper SCCP-User.
> > 
> > So, in the example in 1.5.3, SCCP is acting as a normal MTP-User.
> > It sends messages to MTP with MTP-TRANSFER primitive and expects
> > them to be routed by MTP on the DPC, without reference to the SSN.
> > To provide correct service to SCCP, M3UA must do the same.
> > 
> > --brian
> > 
> > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 04:58:34)
> > > 
> > > Brian,
> > > 
> > > DPC is not consisting of only HLR but it also has LNP(Locan Number
> > > Portability),ALR(Application Location Register).. under one SPMC.
> > > 
> > > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > > 
> > > > Samuel,
> > > > 
> > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 03:59:45)
> > > > > 
> > > > > Brian,
> > > > > 
> > > > > See the mail below you said 'full-blown SCCP' which means matured sccp.
> > > > > But now you are saying normal MTP-user.
> > > > > 
> > > > > Ok.Suppose GTT results in DPC+HLR.
> > > > > Say under one SPMC we have Subsystetems HLR,ALR and LNP.
> > > > > 
> > > > > Now How does SGP know to route the message(DATA) to the particular(HLR)
> > > > > SSN?
> > > > 
> > > > It routes on DPC.
> > > > 
> > > > --brian
> > > > 
> > > > -- 
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > > 
> > 
> > -- 
> > 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 mailnull@www1.ietf.org  Fri Jan 10 08: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 IAA27448
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:25:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADbfM31540
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:37:41 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADbQJ31430;
	Fri, 10 Jan 2003 08:37:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADadJ30784
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:36:39 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27431
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:23:56 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0ADR9Ob023595;
	Fri, 10 Jan 2003 07:27:13 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0ADQbM11821;
	Fri, 10 Jan 2003 07:26:37 -0600 (CST)
Date: Fri, 10 Jan 2003 07:26:37 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
In-Reply-To: <20030110060414.W8782@openss7.org>
Message-ID: <Pine.SOL.4.10.10301100719130.10518-100000@sun3271.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>


Tolga,

To the point if we want to support SSN RK with M3UA stack then RFC 3332
should have been writen with much details of SSN, but it was not writen
so.and its too late to update M3UA with SSN RKs.

But on the other hand i have SUA to handle all SSN related issues.
So One will always select SUA to implement SSN RKs.
Nobody will select M3UA to implement SSN RK because i have much better
stack SUA to support SSN RK.

--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, 10 Jan 2003, Brian F. G. Bidulock wrote:

> TOLGA,
> 
> Then you would have the SG intercepting and altering DATA sent to it by the AS?
> This was the same as the problem for CIC.  The ASP has an expectation (stated
> in the RFC) that DATA messages are transferred unaltered.
> 
> --brian
> 
> TOLGA ASVEREN wrote:                              (Fri, 10 Jan 2003 14:54:18)
> > 
> > Samuel,
> > 
> > As you have also pointed out in one of your messages, this will be sent as
> > a SCCP management message in DATA. Then it is up to management logic in SG
> > to decide whether the global SSN state should be updated or not (similar to
> > what happens with SPMC availability/unavailability)
> > 
> >       Tolga
> > 
> 
> -- 
> 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 mailnull@www1.ietf.org  Fri Jan 10 08:26: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 IAA27462
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:26:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADcGi31587
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:38:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADc4J31575;
	Fri, 10 Jan 2003 08:38:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADbGJ31235
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:37:16 -0500
Received: from tank.fr.ulticom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27438
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:24:34 -0500 (EST)
Received: from PCGASTAUDL (pc-gastaud-l.fr.ulticom.com [172.26.32.87])
	by tank.fr.ulticom.com (8.8.8+Sun/8.8.8) with SMTP id OAA25558;
	Fri, 10 Jan 2003 14:27:40 +0100 (MET)
From: "Valerie Gastaud" <valerie.gastaud@ulticom.com>
To: <bidulock@openss7.org>, "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Cc: <sigtran@ietf.org>
Subject: RE: [Sigtran] m3ua- IG
Date: Fri, 10 Jan 2003 14:52:00 +0100
Message-ID: <NDBBIHAOCKGAMIKNLALOAEBJDKAA.valerie.gastaud@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <20030110021253.J8782@openss7.org>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 8bit
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

Brian,

I feel I don't answer as quickly as you all on the list....

> > >
> > > [TOLGA] For class0/class1 SCCP SSN based RKs seems
> > to me doable. SSN state
> > > can be kept on SG based on AS status, and also
> > routing of management
> > > messages probably won´t be very difficult for the
> > ones destined for a
> > > specific subsystem.
> >
> > Routing of management messages is impossible in an
> > interoperable way.
> > Where they should go is niether specified nor
> > obvious from the point
> > of view of using SSN for routing.  The ASP must know
> > where and when it
> > will receive SCCP management messages to be
> > interoperable.  M3UA does
> > not specify this, and so SSN routing keys are not
> > supported.
> [TOLGA] Why should ASP know anything special not defined in RFC? It serves
> an AS for a specific DPC+SSN and it is SGs responsibility to distribute
> messages properly -including management messages-. One can look to SCCP
> management message and decide for which SSN it is send.

That would not be using the SSN in the messaage (which is SSN=0), that
would be using the ASSN.  Also, you would need to use the APC rather than
the DPC in the message.  These things are not even mentioned for M3UA.

Also, where does it say that the ASP registered with SSN=5 is the "rignt"
place to send SCCP management messages?

>>>VG: I don't think that using the ASSN helps since this it does not
contain the same SSN as the SSN registered in the RK.

SS7 node                        SG                         ASP          ASP
SSN=8                           RK=called SSN=9            SSN=9
SSN=10
        SSP ASSN=8              RK=called SSN=10
------------------------------>  ??

Valerie


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



From mailnull@www1.ietf.org  Fri Jan 10 08:33: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 IAA27663
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:33:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADjWi31942
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:45:32 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADjKJ31929;
	Fri, 10 Jan 2003 08:45:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADiwJ31878
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:44:58 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27647
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:32:15 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF4A5EF3A5.F0FB23F1-ONC2256CAA.0049973F@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 15:32:07 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 03:32:12 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 h0ADixJ31879
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


Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> TOLGA,
>
> TOLGA ASVEREN wrote:
>                                 (Fri, 10 Jan 2003
> 15:05:08)
> >
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > > TOLGA,
> > >
> > > TOLGA ASVEREN wrote:
> > >                                 (Fri, 10 Jan
> 2003
> > > 14:26:46)
> > > >
> > > > Brian,
> > > >
> > > > Again the last message from me on this thread,
> > > because I think I already
> > > > started repeating the same things.
> > > >
> > > > Please find the comments are below.
> > > >
> > > >    Tolga
> > > > --- "Brian F. G. Bidulock"
> <bidulock@openss7.org>
> > > wrote:
> > > > > TOLGA,
> > > > >
> > > > > TOLGA ASVEREN wrote:
> > > > >                                 (Fri, 10 Jan
> > > 2003
> > > > > 13:51:14)
> > > > > >
> > > > > > Samuel,
> > > > > >
> > > > > > The point is, no special management logic
> > > should
> > > > > be necessary on ASP.
> > > > >
> > > > > The point is special management logic is
> > > required on
> > > > > the ASP so that
> > > > > it can know where and when it is receiving
> SCCP
> > > > > management messages.
> > > > [TOLGA] No, this is not necesary.
> > >
> > > It is necessary so that the ASP can route the
> SCCP
> > > management
> > > messages to the correct SCCP user.
> > [TOLGA] M3UA-ASP routes the messages based on RC.
> So, each message will be
> > sent to the entity serving the AS corresponding to
> RC in the message.
> > M3UA-ASP does not need to know -and it does not
> know- that inside DATA
> > there is a SCCP management message. SG takes care
> of everything.
>
> The SG does not send messages to SCCP users.  How
> will the ASP get the
> management messages get to the SCCP user?
[TOLGA] This is responsibility of SCCP. M3UA-ASP will just delºver the
messages to the corresponding entity, taking care of traffic for the AS,
corresponding to RC in the message.
>
> > >
> > > > >
> > > > > > The ASP is just any M3UA compliant ASP,
> > > nothing
> > > > > special there.
> > > > >
> > > > > It is a VERY special ASP.  It's M3UA knows
> about
> > > > > SCCP mangement messages
> > > > > and knows where the particular SG is going
> to
> > > place
> > > > > them, whether it needs
> > > > > to register for an AS with SSN=0, whether it
> > > needs
> > > > > to only act as a default
> > > > > ASP, whether it can expect management
> messages
> > > on
> > > > > each AS corresponding to
> > > > > a subsystem, in fact it needs to know that
> the
> > > SG is
> > > > > performing SSN routing
> > > > > at all (which is not supported by dynamic
> > > > > registration).
> > > > [TOLGA] I think soon you will ask for an ASP,
> > > which can work with any SG
> > > > with no configuration at all. Of course it
> needs
> > > to know, which SG it needs
> > > > to connect for a specific RK in case of static
> > > configurations. Afterall,
> > > > RKs need to be agreed by both sides through
> > > configuration. I think, it is
> > > > the normal operation that each AS gets the
> > > messages, it needs to get
> > > > -including management messages-. But if you
> think
> > > it as necessary, then
> > > > just a few sentences might be added to IG.
> > >
> > > M3UA RFC covers SSNM.  It does not cover SCCP
> > > management messages.
> > [TOLGA] It covers SSNM because it is a MTP3/MTP3
> User interface. SCCP
> > management message are encapsulated in DATA.
>
> M3UA RFC also covers the treatment of DATA.  DATA is
> never sent
> to more than one ASP except in a broadcast mode AS.
> It looks like
> your suggestion (sending SCCP management messages to
> multiple ASPs
> in DATA) is not compliant with the M3UA RFC.
> Valerie's and Joe's
> are compliant.
[TOLGA] I consider it ot as the same DATA replicated to multiple
destinations but as a SCCP management message replicated by the management
functionality on SG. But still I proposed in my former message a new
sentence to clarify this. I think it should be enough to address your this
concern.
>
> > >
> > > If you want to add text to M3UA to allow it to
> > > support SSN routing,
> > > do so.  My point has always been that it does
> not
> > > support SSN routing
> > > as it stands.  What is your proposed text?
> > [TOLGA] 1.4.2.2
> > "For RK types, which are not based on
> MTP3/MTP3-User Interface
> > constructs(DPC, SI) some management functionality
> might be necessary. This
> > functionality should be implemented on SG and is
> implementation dependent.
> > It should be taken care of, that no special
> behavior from the peer is
> > expected.
>
> This does not tell ASP how to expect SCCP management
> (or messages
> not containing SSN) to be kouted differently than
> SCCP messages.
> You proposed text is not a basis for
> interoperability at all.
[TOLGA] ASP does not need to know/care what is going on with SCCP. It just
cares about RC in the message and delivers it to the corresponding user
based on that.
>
> > >
> > > > >
> > > > > > BTW, does M3UA RFC tell to support any
> > > specific RK
> > > > > type? For example if a SG
> > > > > > supports only DPC based RKs, will it be
> > > compliant
> > > > > or not with RFC?  I think
> > > > > > it is totally dependent on the
> implementor,
> > > which
> > > > > types of RKs her/his SG is
> > > > > > going to support.
> > > > >

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



From mailnull@www1.ietf.org  Fri Jan 10 08:33: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 IAA27665
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:33:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADjcV31960
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:45:38 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADjBJ31913;
	Fri, 10 Jan 2003 08:45:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADiZJ31871
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:44:35 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27644
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:31:53 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0ADZ9OZ024573;
	Fri, 10 Jan 2003 07:35:10 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0ADYfM14355;
	Fri, 10 Jan 2003 07:34:41 -0600 (CST)
Date: Fri, 10 Jan 2003 07:34:41 -0600 (CST)
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] m3ua- IG
In-Reply-To: <20030110062425.Z8782@openss7.org>
Message-ID: <Pine.SOL.4.10.10301100731420.10518-100000@sun3271.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,

You misinterpreted my mail.

--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, 10 Jan 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> You are confused:
> 
>  - MTP routes messages on DPC.
>  - SCCP runs over MTP (today in SS7 network).
>  - SCCP does not need M3UA to route on SSN to support it.
> 
> Read Q.714.
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 07:12:22)
> > 
> > Brian,
> > 
> > So, this normal MTP-User will not perform GTT?
> > 
> > if it performs see the following case
> >  
> > SCCP finds SSN (say GTT resulted DPC+SSN)as prohibited, MTP can not route
> > this message successfully with DPC alone.This case WHEN will this SSN will
> > become unprohibited, until you get a message from ASP saying 'now SSN is
> > not prohibited' Is it not so?
> > 
> > if it so Which M3UA message carries this information from ASP to SG?
> > 
> > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > 
> > > Samuel,
> > > 
> > > When SCCP sends these messages to MTP, they get routed through the
> > > SS7 network on DPC only.  SCCP does not need any more service than
> > > is provided by MTP.  So, things will work fine if M3UA routes on
> > > DPC only.  M3UA no more needs to look at SSN than MTP does (and
> > > MTP does not need to look at SSN, it uses DPC only).  Look at Q.714
> > > routing rules to see how MTP transfers all messages on DPC only.
> > > Only once the message gets to the DPC is SSN or GT examined by
> > > SCCP to determine the proper SCCP-User.
> > > 
> > > So, in the example in 1.5.3, SCCP is acting as a normal MTP-User.
> > > It sends messages to MTP with MTP-TRANSFER primitive and expects
> > > them to be routed by MTP on the DPC, without reference to the SSN.
> > > To provide correct service to SCCP, M3UA must do the same.
> > > 
> > > --brian
> > > 
> > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 04:58:34)
> > > > 
> > > > Brian,
> > > > 
> > > > DPC is not consisting of only HLR but it also has LNP(Locan Number
> > > > Portability),ALR(Application Location Register).. under one SPMC.
> > > > 
> > > > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > > > 
> > > > > Samuel,
> > > > > 
> > > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 03:59:45)
> > > > > > 
> > > > > > Brian,
> > > > > > 
> > > > > > See the mail below you said 'full-blown SCCP' which means matured sccp.
> > > > > > But now you are saying normal MTP-user.
> > > > > > 
> > > > > > Ok.Suppose GTT results in DPC+HLR.
> > > > > > Say under one SPMC we have Subsystetems HLR,ALR and LNP.
> > > > > > 
> > > > > > Now How does SGP know to route the message(DATA) to the particular(HLR)
> > > > > > SSN?
> > > > > 
> > > > > It routes on DPC.
> > > > > 
> > > > > --brian
> > > > > 
> > > > > -- 
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > > > > 
> > > 
> > > -- 
> > > 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
> 

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



From mailnull@www1.ietf.org  Fri Jan 10 08:37: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 IAA27770
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:37:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADnVU32087
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:49:31 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADn4J32065;
	Fri, 10 Jan 2003 08:49:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADmrJ32051
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:48:53 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27739
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:36:10 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Wcg0ZKGahjRcV1o6K4DHY4+by4vJFS0F@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0ADdRD11480;
	Fri, 10 Jan 2003 06:39:27 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0ADdRa21508;
	Fri, 10 Jan 2003 06:39:27 -0700
Date: Fri, 10 Jan 2003 06:39:27 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110063927.A8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF4A5EF3A5.F0FB23F1-ONC2256CAA.0049973F@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF4A5EF3A5.F0FB23F1-ONC2256CAA.0049973F@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 03:32:07PM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 15:32:07)
> 
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > TOLGA,
> >
> > TOLGA ASVEREN wrote:
> >                                 (Fri, 10 Jan 2003
> > 15:05:08)
> > >
> > > Brian,
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > > TOLGA,
> > > >
> > > > TOLGA ASVEREN wrote:
> > > >                                 (Fri, 10 Jan
> > 2003
> > > > 14:26:46)
> > > > >
> > > > > Brian,
> > > > >
> > > > > Again the last message from me on this thread,
> > > > because I think I already
> > > > > started repeating the same things.
> > > > >
> > > > > Please find the comments are below.
> > > > >
> > > > >    Tolga
> > > > > --- "Brian F. G. Bidulock"
> > <bidulock@openss7.org>
> > > > wrote:
> > > > > > TOLGA,
> > > > > >
> > > > > > TOLGA ASVEREN wrote:
> > > > > >                                 (Fri, 10 Jan
> > > > 2003
> > > > > > 13:51:14)
> > > > > > >
> > > > > > > Samuel,
> > > > > > >
> > > > > > > The point is, no special management logic
> > > > should
> > > > > > be necessary on ASP.
> > > > > >
> > > > > > The point is special management logic is
> > > > required on
> > > > > > the ASP so that
> > > > > > it can know where and when it is receiving
> > SCCP
> > > > > > management messages.
> > > > > [TOLGA] No, this is not necesary.
> > > >
> > > > It is necessary so that the ASP can route the
> > SCCP
> > > > management
> > > > messages to the correct SCCP user.
> > > [TOLGA] M3UA-ASP routes the messages based on RC.
> > So, each message will be
> > > sent to the entity serving the AS corresponding to
> > RC in the message.
> > > M3UA-ASP does not need to know -and it does not
> > know- that inside DATA
> > > there is a SCCP management message. SG takes care
> > of everything.
> >
> > The SG does not send messages to SCCP users.  How
> > will the ASP get the
> > management messages get to the SCCP user?
> [TOLGA] This is responsibility of SCCP. M3UA-ASP will just delºver the
> messages to the corresponding entity, taking care of traffic for the AS,
> corresponding to RC in the message.

But the only reason for using SSN RK is because SCCP is partitioned
over multiple ASPs.  How can ASP get SCCP management messagess to
the correct SCCP user without knowing where they appear?

> >
> > > >
> > > > > >
> > > > > > > The ASP is just any M3UA compliant ASP,
> > > > nothing
> > > > > > special there.
> > > > > >
> > > > > > It is a VERY special ASP.  It's M3UA knows
> > about
> > > > > > SCCP mangement messages
> > > > > > and knows where the particular SG is going
> > to
> > > > place
> > > > > > them, whether it needs
> > > > > > to register for an AS with SSN=0, whether it
> > > > needs
> > > > > > to only act as a default
> > > > > > ASP, whether it can expect management
> > messages
> > > > on
> > > > > > each AS corresponding to
> > > > > > a subsystem, in fact it needs to know that
> > the
> > > > SG is
> > > > > > performing SSN routing
> > > > > > at all (which is not supported by dynamic
> > > > > > registration).
> > > > > [TOLGA] I think soon you will ask for an ASP,
> > > > which can work with any SG
> > > > > with no configuration at all. Of course it
> > needs
> > > > to know, which SG it needs
> > > > > to connect for a specific RK in case of static
> > > > configurations. Afterall,
> > > > > RKs need to be agreed by both sides through
> > > > configuration. I think, it is
> > > > > the normal operation that each AS gets the
> > > > messages, it needs to get
> > > > > -including management messages-. But if you
> > think
> > > > it as necessary, then
> > > > > just a few sentences might be added to IG.
> > > >
> > > > M3UA RFC covers SSNM.  It does not cover SCCP
> > > > management messages.
> > > [TOLGA] It covers SSNM because it is a MTP3/MTP3
> > User interface. SCCP
> > > management message are encapsulated in DATA.
> >
> > M3UA RFC also covers the treatment of DATA.  DATA is
> > never sent
> > to more than one ASP except in a broadcast mode AS.
> > It looks like
> > your suggestion (sending SCCP management messages to
> > multiple ASPs
> > in DATA) is not compliant with the M3UA RFC.
> > Valerie's and Joe's
> > are compliant.
> [TOLGA] I consider it ot as the same DATA replicated to multiple
> destinations but as a SCCP management message replicated by the management
> functionality on SG. But still I proposed in my former message a new
> sentence to clarify this. I think it should be enough to address your this
> concern.

No it is not.  You must say which messages are to be duplicated,
how, and to which ASPs in which AS.

> >
> > > >
> > > > If you want to add text to M3UA to allow it to
> > > > support SSN routing,
> > > > do so.  My point has always been that it does
> > not
> > > > support SSN routing
> > > > as it stands.  What is your proposed text?
> > > [TOLGA] 1.4.2.2
> > > "For RK types, which are not based on
> > MTP3/MTP3-User Interface
> > > constructs(DPC, SI) some management functionality
> > might be necessary. This
> > > functionality should be implemented on SG and is
> > implementation dependent.
> > > It should be taken care of, that no special
> > behavior from the peer is
> > > expected.
> >
> > This does not tell ASP how to expect SCCP management
> > (or messages
> > not containing SSN) to be kouted differently than
> > SCCP messages.
> > You proposed text is not a basis for
> > interoperability at all.
> [TOLGA] ASP does not need to know/care what is going on with SCCP. It just
> cares about RC in the message and delivers it to the corresponding user
> based on that.

If that were the case, there would be no need for RK on SSN in the first
place.  It is only by nature of the fact that SCCP users could be split
over ASPs that the RK would be necessary at all.  So, the ASP needs to
know/care what is going on with SCCP.

--brian

> >
> > > >
> > > > > >
> > > > > > > BTW, does M3UA RFC tell to support any
> > > > specific RK
> > > > > > type? For example if a SG
> > > > > > > supports only DPC based RKs, will it be
> > > > compliant
> > > > > > or not with RFC?  I think
> > > > > > > it is totally dependent on the
> > implementor,
> > > > which
> > > > > > types of RKs her/his SG is
> > > > > > > going to support.
> > > > > >
> 
> _______________________________________________
> 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 Jan 10 08:38: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 IAA27797
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:38:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADoMW32182
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:50:22 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADo4J32154;
	Fri, 10 Jan 2003 08:50:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADnkJ32112
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:49:46 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27766
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:37:03 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF637FF49E.FB3B842F-ONC2256CAA.004A851F@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 15:36:56 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 03: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>


Samuel,

Did I say that you or anybody else MUST use M3UA with SSN based RKs?

IMO M3UA does not need much changes to be able to handle this case(just the
concerns Brian has pointed out about handling of DATA must be addressed in
the corresponding sections with a few sentences. The rest is implementation
dependent management functionality on SG).

     Tolga





Tolga,

To the point if we want to support SSN RK with M3UA stack then RFC 3332
should have been writen with much details of SSN, but it was not writen
so.and its too late to update M3UA with SSN RKs.

But on the other hand i have SUA to handle all SSN related issues.
So One will always select SUA to implement SSN RKs.
Nobody will select M3UA to implement SSN RK because i have much better
stack SUA to support SSN RK.

--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, 10 Jan 2003, Brian F. G. Bidulock wrote:

> TOLGA,
>
> Then you would have the SG intercepting and altering DATA sent to it by
the AS?
> This was the same as the problem for CIC.  The ASP has an expectation
(stated
> in the RFC) that DATA messages are transferred unaltered.
>
> --brian
>
> TOLGA ASVEREN wrote:                              (Fri, 10 Jan 2003
14:54:18)
> >
> > Samuel,
> >
> > As you have also pointed out in one of your messages, this will be sent
as
> > a SCCP management message in DATA. Then it is up to management logic in
SG
> > to decide whether the global SSN state should be updated or not
(similar to
> > what happens with SPMC availability/unavailability)
> >
> >       Tolga
> >
>
> --
> 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 mailnull@www1.ietf.org  Fri Jan 10 08:39: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 IAA27838
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:39:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADpKE32271
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:51:20 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADp8J32264;
	Fri, 10 Jan 2003 08:51:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADodJ32205
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:50:39 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27787
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:37:56 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:LmwP0dN2K6KmFgjZK2rDpl/sX0byiHOP@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0ADfCD11513;
	Fri, 10 Jan 2003 06:41:12 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0ADfCD21631;
	Fri, 10 Jan 2003 06:41:12 -0700
Date: Fri, 10 Jan 2003 06:41:12 -0700
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] m3ua- IG
Message-ID: <20030110064112.B8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030110062425.Z8782@openss7.org> <Pine.SOL.4.10.10301100731420.10518-100000@sun3271.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.10301100731420.10518-100000@sun3271.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Jan 10, 2003 at 07:34:41AM -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 don't think so.  What did you mean by:

> > > SCCP finds SSN (say GTT resulted DPC+SSN)as prohibited, MTP can not route
                                                              ^^^^^^^^^^^^^^^^^
> > > this message successfully with DPC alone.This case WHEN will this SSN will
      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

MTP routes all messages by DPC alone.

Read Q.704.

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 07:34:41)
> 
> Brian,
> 
> You misinterpreted my mail.
> 
> --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > You are confused:
> > 
> >  - MTP routes messages on DPC.
> >  - SCCP runs over MTP (today in SS7 network).
> >  - SCCP does not need M3UA to route on SSN to support it.
> > 
> > Read Q.714.
> > 
> > --brian
> > 
> > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 07:12:22)
> > > 
> > > Brian,
> > > 
> > > So, this normal MTP-User will not perform GTT?
> > > 
> > > if it performs see the following case
> > >  
> > > SCCP finds SSN (say GTT resulted DPC+SSN)as prohibited, MTP can not route
> > > this message successfully with DPC alone.This case WHEN will this SSN will
> > > become unprohibited, until you get a message from ASP saying 'now SSN is
> > > not prohibited' Is it not so?
> > > 
> > > if it so Which M3UA message carries this information from ASP to SG?
> > > 
> > > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > > 
> > > > Samuel,
> > > > 
> > > > When SCCP sends these messages to MTP, they get routed through the
> > > > SS7 network on DPC only.  SCCP does not need any more service than
> > > > is provided by MTP.  So, things will work fine if M3UA routes on
> > > > DPC only.  M3UA no more needs to look at SSN than MTP does (and
> > > > MTP does not need to look at SSN, it uses DPC only).  Look at Q.714
> > > > routing rules to see how MTP transfers all messages on DPC only.
> > > > Only once the message gets to the DPC is SSN or GT examined by
> > > > SCCP to determine the proper SCCP-User.
> > > > 
> > > > So, in the example in 1.5.3, SCCP is acting as a normal MTP-User.
> > > > It sends messages to MTP with MTP-TRANSFER primitive and expects
> > > > them to be routed by MTP on the DPC, without reference to the SSN.
> > > > To provide correct service to SCCP, M3UA must do the same.
> > > > 
> > > > --brian
> > > > 
> > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 04:58:34)
> > > > > 
> > > > > Brian,
> > > > > 
> > > > > DPC is not consisting of only HLR but it also has LNP(Locan Number
> > > > > Portability),ALR(Application Location Register).. under one SPMC.
> > > > > 
> > > > > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > > > > 
> > > > > > Samuel,
> > > > > > 
> > > > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 03:59:45)
> > > > > > > 
> > > > > > > Brian,
> > > > > > > 
> > > > > > > See the mail below you said 'full-blown SCCP' which means matured sccp.
> > > > > > > But now you are saying normal MTP-user.
> > > > > > > 
> > > > > > > Ok.Suppose GTT results in DPC+HLR.
> > > > > > > Say under one SPMC we have Subsystetems HLR,ALR and LNP.
> > > > > > > 
> > > > > > > Now How does SGP know to route the message(DATA) to the particular(HLR)
> > > > > > > SSN?
> > > > > > 
> > > > > > It routes on DPC.
> > > > > > 
> > > > > > --brian
> > > > > > 
> > > > > > -- 
> > > > > > Brian F. G. Bidulock
> > > > > > bidulock@openss7.org
> > > > > > http://www.openss7.org/
> > > > > > 
> > > > 
> > > > -- 
> > > > 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
> > 

-- 
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 Jan 10 08:44: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 IAA27966
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:44:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADuXv32516
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:56:33 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADu6J32490;
	Fri, 10 Jan 2003 08:56:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADtJJ32451
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:55:19 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27933
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:42:36 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:0edds2dqmD6VmRPQGlbkQDDFjhRsdzCo@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0ADjqD11577;
	Fri, 10 Jan 2003 06:45:52 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0ADjqX21762;
	Fri, 10 Jan 2003 06:45:52 -0700
Date: Fri, 10 Jan 2003 06:45:52 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110064552.C8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF637FF49E.FB3B842F-ONC2256CAA.004A851F@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF637FF49E.FB3B842F-ONC2256CAA.004A851F@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 03:36:56PM +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>

TOLGA,

I think you also need to say which SCCP classes, and what SCCP routing
cannot be handled by such an M3UA.  Obviously, M3UA cannot support
SCCP classes 2 or 3, and cannot support messages which are marked
"Route on GT".

--brian

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 15:36:56)
> 
> Samuel,
> 
> Did I say that you or anybody else MUST use M3UA with SSN based RKs?
> 
> IMO M3UA does not need much changes to be able to handle this case(just the
> concerns Brian has pointed out about handling of DATA must be addressed in
> the corresponding sections with a few sentences. The rest is implementation
> dependent management functionality on SG).
> 
>      Tolga

-- 
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 Jan 10 08:47: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 IAA28046
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:47:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ADxJ232677
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 08:59:19 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADx7J32661;
	Fri, 10 Jan 2003 08:59:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ADwaJ32637
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 08:58:36 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28027
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:45:53 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0ADnAOZ026567;
	Fri, 10 Jan 2003 07:49:10 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0ADmgM18647;
	Fri, 10 Jan 2003 07:48:42 -0600 (CST)
Date: Fri, 10 Jan 2003 07:48:42 -0600 (CST)
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] m3ua- IG
In-Reply-To: <20030110064112.B8782@openss7.org>
Message-ID: <Pine.SOL.4.10.10301100744070.10518-100000@sun3271.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,

Meant to say that SCCP finds SSN as prohibited and this message is being 
given to MTP3. But MTP cannot route this message successfully even though
dpc is perfect to the point of MTP3.

--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, 10 Jan 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> I don't think so.  What did you mean by:
> 
> > > > SCCP finds SSN (say GTT resulted DPC+SSN)as prohibited, MTP can not route
>                                                               ^^^^^^^^^^^^^^^^^
> > > > this message successfully with DPC alone.This case WHEN will this SSN will
>       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> MTP routes all messages by DPC alone.
> 
> Read Q.704.
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 07:34:41)
> > 
> > Brian,
> > 
> > You misinterpreted my mail.
> > 
> > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > 
> > > Samuel,
> > > 
> > > You are confused:
> > > 
> > >  - MTP routes messages on DPC.
> > >  - SCCP runs over MTP (today in SS7 network).
> > >  - SCCP does not need M3UA to route on SSN to support it.
> > > 
> > > Read Q.714.
> > > 
> > > --brian
> > > 
> > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 07:12:22)
> > > > 
> > > > Brian,
> > > > 
> > > > So, this normal MTP-User will not perform GTT?
> > > > 
> > > > if it performs see the following case
> > > >  
> > > > SCCP finds SSN (say GTT resulted DPC+SSN)as prohibited, MTP can not route
> > > > this message successfully with DPC alone.This case WHEN will this SSN will
> > > > become unprohibited, until you get a message from ASP saying 'now SSN is
> > > > not prohibited' Is it not so?
> > > > 
> > > > if it so Which M3UA message carries this information from ASP to SG?
> > > > 
> > > > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > > > 
> > > > > Samuel,
> > > > > 
> > > > > When SCCP sends these messages to MTP, they get routed through the
> > > > > SS7 network on DPC only.  SCCP does not need any more service than
> > > > > is provided by MTP.  So, things will work fine if M3UA routes on
> > > > > DPC only.  M3UA no more needs to look at SSN than MTP does (and
> > > > > MTP does not need to look at SSN, it uses DPC only).  Look at Q.714
> > > > > routing rules to see how MTP transfers all messages on DPC only.
> > > > > Only once the message gets to the DPC is SSN or GT examined by
> > > > > SCCP to determine the proper SCCP-User.
> > > > > 
> > > > > So, in the example in 1.5.3, SCCP is acting as a normal MTP-User.
> > > > > It sends messages to MTP with MTP-TRANSFER primitive and expects
> > > > > them to be routed by MTP on the DPC, without reference to the SSN.
> > > > > To provide correct service to SCCP, M3UA must do the same.
> > > > > 
> > > > > --brian
> > > > > 
> > > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 04:58:34)
> > > > > > 
> > > > > > Brian,
> > > > > > 
> > > > > > DPC is not consisting of only HLR but it also has LNP(Locan Number
> > > > > > Portability),ALR(Application Location Register).. under one SPMC.
> > > > > > 
> > > > > > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > > > > > 
> > > > > > > Samuel,
> > > > > > > 
> > > > > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 03:59:45)
> > > > > > > > 
> > > > > > > > Brian,
> > > > > > > > 
> > > > > > > > See the mail below you said 'full-blown SCCP' which means matured sccp.
> > > > > > > > But now you are saying normal MTP-user.
> > > > > > > > 
> > > > > > > > Ok.Suppose GTT results in DPC+HLR.
> > > > > > > > Say under one SPMC we have Subsystetems HLR,ALR and LNP.
> > > > > > > > 
> > > > > > > > Now How does SGP know to route the message(DATA) to the particular(HLR)
> > > > > > > > SSN?
> > > > > > > 
> > > > > > > It routes on DPC.
> > > > > > > 
> > > > > > > --brian
> > > > > > > 
> > > > > > > -- 
> > > > > > > Brian F. G. Bidulock
> > > > > > > bidulock@openss7.org
> > > > > > > http://www.openss7.org/
> > > > > > > 
> > > > > 
> > > > > -- 
> > > > > 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
> > > 
> 
> -- 
> 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 Jan 10 08:49: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 IAA28111
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:49:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AE1WU00364
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 09:01:32 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AE15J00341;
	Fri, 10 Jan 2003 09:01:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AE0oJ00306
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 09:00:50 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28085
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:48:06 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:sBdcdmJDtT+MQGxKxYvj7g7UmYYuF03J@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0ADpND11654;
	Fri, 10 Jan 2003 06:51:23 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0ADpNQ21993;
	Fri, 10 Jan 2003 06:51:23 -0700
Date: Fri, 10 Jan 2003 06:51:23 -0700
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] m3ua- IG
Message-ID: <20030110065123.D8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030110064112.B8782@openss7.org> <Pine.SOL.4.10.10301100744070.10518-100000@sun3271.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.10301100744070.10518-100000@sun3271.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Jan 10, 2003 at 07:48:42AM -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,

Read Q.714.  SCCP does not send messages to MTP for prohibited SSNs.

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 07:48:42)
> 
> Brian,
> 
> Meant to say that SCCP finds SSN as prohibited and this message is being 
> given to MTP3. But MTP cannot route this message successfully even though
> dpc is perfect to the point of MTP3.
> 
> --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > I don't think so.  What did you mean by:
> > 
> > > > > SCCP finds SSN (say GTT resulted DPC+SSN)as prohibited, MTP can not route
> >                                                               ^^^^^^^^^^^^^^^^^
> > > > > this message successfully with DPC alone.This case WHEN will this SSN will
> >       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > 
> > MTP routes all messages by DPC alone.
> > 
> > Read Q.704.
> > 
> > --brian
> > 
> > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 07:34:41)
> > > 
> > > Brian,
> > > 
> > > You misinterpreted my mail.
> > > 
> > > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > > 
> > > > Samuel,
> > > > 
> > > > You are confused:
> > > > 
> > > >  - MTP routes messages on DPC.
> > > >  - SCCP runs over MTP (today in SS7 network).
> > > >  - SCCP does not need M3UA to route on SSN to support it.
> > > > 
> > > > Read Q.714.
> > > > 
> > > > --brian
> > > > 
> > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 07:12:22)
> > > > > 
> > > > > Brian,
> > > > > 
> > > > > So, this normal MTP-User will not perform GTT?
> > > > > 
> > > > > if it performs see the following case
> > > > >  
> > > > > SCCP finds SSN (say GTT resulted DPC+SSN)as prohibited, MTP can not route
> > > > > this message successfully with DPC alone.This case WHEN will this SSN will
> > > > > become unprohibited, until you get a message from ASP saying 'now SSN is
> > > > > not prohibited' Is it not so?
> > > > > 
> > > > > if it so Which M3UA message carries this information from ASP to SG?
> > > > > 
> > > > > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > > > > 
> > > > > > Samuel,
> > > > > > 
> > > > > > When SCCP sends these messages to MTP, they get routed through the
> > > > > > SS7 network on DPC only.  SCCP does not need any more service than
> > > > > > is provided by MTP.  So, things will work fine if M3UA routes on
> > > > > > DPC only.  M3UA no more needs to look at SSN than MTP does (and
> > > > > > MTP does not need to look at SSN, it uses DPC only).  Look at Q.714
> > > > > > routing rules to see how MTP transfers all messages on DPC only.
> > > > > > Only once the message gets to the DPC is SSN or GT examined by
> > > > > > SCCP to determine the proper SCCP-User.
> > > > > > 
> > > > > > So, in the example in 1.5.3, SCCP is acting as a normal MTP-User.
> > > > > > It sends messages to MTP with MTP-TRANSFER primitive and expects
> > > > > > them to be routed by MTP on the DPC, without reference to the SSN.
> > > > > > To provide correct service to SCCP, M3UA must do the same.
> > > > > > 
> > > > > > --brian
> > > > > > 
> > > > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 04:58:34)
> > > > > > > 
> > > > > > > Brian,
> > > > > > > 
> > > > > > > DPC is not consisting of only HLR but it also has LNP(Locan Number
> > > > > > > Portability),ALR(Application Location Register).. under one SPMC.
> > > > > > > 
> > > > > > > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > > > > > > 
> > > > > > > > Samuel,
> > > > > > > > 
> > > > > > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 03:59:45)
> > > > > > > > > 
> > > > > > > > > Brian,
> > > > > > > > > 
> > > > > > > > > See the mail below you said 'full-blown SCCP' which means matured sccp.
> > > > > > > > > But now you are saying normal MTP-user.
> > > > > > > > > 
> > > > > > > > > Ok.Suppose GTT results in DPC+HLR.
> > > > > > > > > Say under one SPMC we have Subsystetems HLR,ALR and LNP.
> > > > > > > > > 
> > > > > > > > > Now How does SGP know to route the message(DATA) to the particular(HLR)
> > > > > > > > > SSN?
> > > > > > > > 
> > > > > > > > It routes on DPC.
> > > > > > > > 
> > > > > > > > --brian
> > > > > > > > 
> > > > > > > > -- 
> > > > > > > > Brian F. G. Bidulock
> > > > > > > > bidulock@openss7.org
> > > > > > > > http://www.openss7.org/
> > > > > > > > 
> > > > > > 
> > > > > > -- 
> > > > > > 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
> > > > 
> > 
> > -- 
> > 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 mailnull@www1.ietf.org  Fri Jan 10 08:51:02 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 IAA28192
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 08:51:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AE3EV00456
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 09:03:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AE33J00444;
	Fri, 10 Jan 2003 09:03:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AE2ZJ00426
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 09:02:35 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28127
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 08:49:52 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:gENxNlgHQm/grmykHMlj3w9w9+9qTXvJ@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0ADr9D11675;
	Fri, 10 Jan 2003 06:53:09 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0ADr9r22018;
	Fri, 10 Jan 2003 06:53:09 -0700
Date: Fri, 10 Jan 2003 06:53:09 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110065309.E8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF637FF49E.FB3B842F-ONC2256CAA.004A851F@LocalDomain> <20030110064552.C8782@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: <20030110064552.C8782@openss7.org>; from bidulock@openss7.org on Fri, Jan 10, 2003 at 06:45:52AM -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,

While your at it, I think you should say which SCCP management
messages are intercepted by the SG in performing its SPMC-like
management of SSNs and which are transparently passed to the ASP.
Otherwise, how is the ASP to know when it is responsibile for
SCCP management and when the SG is?

(You have SUA re-specified before your done... ;)

--brian

Brian F. G. Bidulock wrote:                                                          (Fri, 10 Jan 2003 06:45:52)
> TOLGA,
> 
> I think you also need to say which SCCP classes, and what SCCP routing
> cannot be handled by such an M3UA.  Obviously, M3UA cannot support
> SCCP classes 2 or 3, and cannot support messages which are marked
> "Route on GT".
> 
> --brian
> 
> TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 15:36:56)
> > 
> > Samuel,
> > 
> > Did I say that you or anybody else MUST use M3UA with SSN based RKs?
> > 
> > IMO M3UA does not need much changes to be able to handle this case(just the
> > concerns Brian has pointed out about handling of DATA must be addressed in
> > the corresponding sections with a few sentences. The rest is implementation
> > dependent management functionality on SG).
> > 
> >      Tolga
> 
> -- 
> 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 mailnull@www1.ietf.org  Fri Jan 10 09:09: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 JAA28439
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 09:09:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AELXj01809
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 09:21:33 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AELBJ01794;
	Fri, 10 Jan 2003 09:21:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AEJaJ01676
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 09:19:36 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28412
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 09:06:53 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0AEAAOZ029653;
	Fri, 10 Jan 2003 08:10:10 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0AE9DM24975;
	Fri, 10 Jan 2003 08:09:14 -0600 (CST)
Date: Fri, 10 Jan 2003 08:09:13 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
In-Reply-To: <20030110064552.C8782@openss7.org>
Message-ID: <Pine.SOL.4.10.10301100808150.10518-100000@sun3271.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,

Can M3UA support messages which are marked "Route on PC/SSN"

--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, 10 Jan 2003, Brian F. G. Bidulock wrote:

> TOLGA,
> 
> I think you also need to say which SCCP classes, and what SCCP routing
> cannot be handled by such an M3UA.  Obviously, M3UA cannot support
> SCCP classes 2 or 3, and cannot support messages which are marked
> "Route on GT".
> 
> --brian
> 
> TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 15:36:56)
> > 
> > Samuel,
> > 
> > Did I say that you or anybody else MUST use M3UA with SSN based RKs?
> > 
> > IMO M3UA does not need much changes to be able to handle this case(just the
> > concerns Brian has pointed out about handling of DATA must be addressed in
> > the corresponding sections with a few sentences. The rest is implementation
> > dependent management functionality on SG).
> > 
> >      Tolga
> 
> -- 
> 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 mailnull@www1.ietf.org  Fri Jan 10 09:10:57 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 JAA28497
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 09:10:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AENAJ01938
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 09:23:10 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AEMwJ01910;
	Fri, 10 Jan 2003 09:22:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AEKiJ01781
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 09:20:44 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28426
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 09:08:01 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:XxQT9dCifddbNbOy01c0FiV1KdAvs9O+@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0AEBID12025;
	Fri, 10 Jan 2003 07:11:18 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0AEBIw22485;
	Fri, 10 Jan 2003 07:11:18 -0700
Date: Fri, 10 Jan 2003 07:11:17 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110071117.G8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <20030110064552.C8782@openss7.org> <Pine.SOL.4.10.10301100808150.10518-100000@sun3271.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.10301100808150.10518-100000@sun3271.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Jan 10, 2003 at 08:09:13AM -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 believe that is what Tolga is proposing.

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 08:09:13)
> 
> Brian,
> 
> Can M3UA support messages which are marked "Route on PC/SSN"
> 
> --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> 
> > TOLGA,
> > 
> > I think you also need to say which SCCP classes, and what SCCP routing
> > cannot be handled by such an M3UA.  Obviously, M3UA cannot support
> > SCCP classes 2 or 3, and cannot support messages which are marked
> > "Route on GT".
> > 
> > --brian
> > 
> > TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 15:36:56)
> > > 
> > > Samuel,
> > > 
> > > Did I say that you or anybody else MUST use M3UA with SSN based RKs?
> > > 
> > > IMO M3UA does not need much changes to be able to handle this case(just the
> > > concerns Brian has pointed out about handling of DATA must be addressed in
> > > the corresponding sections with a few sentences. The rest is implementation
> > > dependent management functionality on SG).
> > > 
> > >      Tolga
> > 
> > -- 
> > 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 mailnull@www1.ietf.org  Fri Jan 10 09:10: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 JAA28500
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 09:10:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AENCP01950
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 09:23:12 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AEMuJ01894;
	Fri, 10 Jan 2003 09:22:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AEKeJ01777
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 09:20:40 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28422
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 09:07:56 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0AEB9Of029805;
	Fri, 10 Jan 2003 08:11:13 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0AEATM25330;
	Fri, 10 Jan 2003 08:10:29 -0600 (CST)
Date: Fri, 10 Jan 2003 08:10:29 -0600 (CST)
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] m3ua- IG
In-Reply-To: <20030110065123.D8782@openss7.org>
Message-ID: <Pine.SOL.4.10.10301100809500.10518-100000@sun3271.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,
Thanks, let me go through it.

--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, 10 Jan 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> Read Q.714.  SCCP does not send messages to MTP for prohibited SSNs.
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 07:48:42)
> > 
> > Brian,
> > 
> > Meant to say that SCCP finds SSN as prohibited and this message is being 
> > given to MTP3. But MTP cannot route this message successfully even though
> > dpc is perfect to the point of MTP3.
> > 
> > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > 
> > > Samuel,
> > > 
> > > I don't think so.  What did you mean by:
> > > 
> > > > > > SCCP finds SSN (say GTT resulted DPC+SSN)as prohibited, MTP can not route
> > >                                                               ^^^^^^^^^^^^^^^^^
> > > > > > this message successfully with DPC alone.This case WHEN will this SSN will
> > >       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > 
> > > MTP routes all messages by DPC alone.
> > > 
> > > Read Q.704.
> > > 
> > > --brian
> > > 
> > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 07:34:41)
> > > > 
> > > > Brian,
> > > > 
> > > > You misinterpreted my mail.
> > > > 
> > > > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > > > 
> > > > > Samuel,
> > > > > 
> > > > > You are confused:
> > > > > 
> > > > >  - MTP routes messages on DPC.
> > > > >  - SCCP runs over MTP (today in SS7 network).
> > > > >  - SCCP does not need M3UA to route on SSN to support it.
> > > > > 
> > > > > Read Q.714.
> > > > > 
> > > > > --brian
> > > > > 
> > > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 07:12:22)
> > > > > > 
> > > > > > Brian,
> > > > > > 
> > > > > > So, this normal MTP-User will not perform GTT?
> > > > > > 
> > > > > > if it performs see the following case
> > > > > >  
> > > > > > SCCP finds SSN (say GTT resulted DPC+SSN)as prohibited, MTP can not route
> > > > > > this message successfully with DPC alone.This case WHEN will this SSN will
> > > > > > become unprohibited, until you get a message from ASP saying 'now SSN is
> > > > > > not prohibited' Is it not so?
> > > > > > 
> > > > > > if it so Which M3UA message carries this information from ASP to SG?
> > > > > > 
> > > > > > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > > > > > 
> > > > > > > Samuel,
> > > > > > > 
> > > > > > > When SCCP sends these messages to MTP, they get routed through the
> > > > > > > SS7 network on DPC only.  SCCP does not need any more service than
> > > > > > > is provided by MTP.  So, things will work fine if M3UA routes on
> > > > > > > DPC only.  M3UA no more needs to look at SSN than MTP does (and
> > > > > > > MTP does not need to look at SSN, it uses DPC only).  Look at Q.714
> > > > > > > routing rules to see how MTP transfers all messages on DPC only.
> > > > > > > Only once the message gets to the DPC is SSN or GT examined by
> > > > > > > SCCP to determine the proper SCCP-User.
> > > > > > > 
> > > > > > > So, in the example in 1.5.3, SCCP is acting as a normal MTP-User.
> > > > > > > It sends messages to MTP with MTP-TRANSFER primitive and expects
> > > > > > > them to be routed by MTP on the DPC, without reference to the SSN.
> > > > > > > To provide correct service to SCCP, M3UA must do the same.
> > > > > > > 
> > > > > > > --brian
> > > > > > > 
> > > > > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 04:58:34)
> > > > > > > > 
> > > > > > > > Brian,
> > > > > > > > 
> > > > > > > > DPC is not consisting of only HLR but it also has LNP(Locan Number
> > > > > > > > Portability),ALR(Application Location Register).. under one SPMC.
> > > > > > > > 
> > > > > > > > --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, 10 Jan 2003, Brian F. G. Bidulock wrote:
> > > > > > > > 
> > > > > > > > > Samuel,
> > > > > > > > > 
> > > > > > > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 10 Jan 2003 03:59:45)
> > > > > > > > > > 
> > > > > > > > > > Brian,
> > > > > > > > > > 
> > > > > > > > > > See the mail below you said 'full-blown SCCP' which means matured sccp.
> > > > > > > > > > But now you are saying normal MTP-user.
> > > > > > > > > > 
> > > > > > > > > > Ok.Suppose GTT results in DPC+HLR.
> > > > > > > > > > Say under one SPMC we have Subsystetems HLR,ALR and LNP.
> > > > > > > > > > 
> > > > > > > > > > Now How does SGP know to route the message(DATA) to the particular(HLR)
> > > > > > > > > > SSN?
> > > > > > > > > 
> > > > > > > > > It routes on DPC.
> > > > > > > > > 
> > > > > > > > > --brian
> > > > > > > > > 
> > > > > > > > > -- 
> > > > > > > > > Brian F. G. Bidulock
> > > > > > > > > bidulock@openss7.org
> > > > > > > > > http://www.openss7.org/
> > > > > > > > > 
> > > > > > > 
> > > > > > > -- 
> > > > > > > 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
> > > > > 
> > > 
> > > -- 
> > > 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
> 

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



From mailnull@www1.ietf.org  Fri Jan 10 09:14: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 JAA28569
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 09:14:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AEQOm02080
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 09:26:24 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AEP5J02044;
	Fri, 10 Jan 2003 09:25:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AEOTJ02007
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 09:24:29 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28522
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 09:11:45 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFB3B4A2BE.4D6C0964-ONC2256CAA.004D47F2@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 16:11:37 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 04:11:43 PM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0AEOTJ02008
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


Brian,



[...snip...]
> [TOLGA] This is responsibility of SCCP. M3UA-ASP will just delºver the
> messages to the corresponding entity, taking care of traffic for the AS,
> corresponding to RC in the message.

But the only reason for using SSN RK is because SCCP is partitioned
over multiple ASPs.  How can ASP get SCCP management messagess to
the correct SCCP user without knowing where they appear?
[TOLGA] It is not M3UA-ASPs responsibility to toute messaegs to SCCP-Users.
M3UA-ASP will deliver the message to the correct SCCP entity based on RC.
The rest belongs to SCCP itself.



[..snip...]
> [TOLGA] I consider it ot as the same DATA replicated to multiple
> destinations but as a SCCP management message replicated by the
management
> functionality on SG. But still I proposed in my former message a new
> sentence to clarify this. I think it should be enough to address your
this
> concern.

No it is not.  You must say which messages are to be duplicated,
how, and to which ASPs in which AS.
[TOLGA]Maybe just one more sentence:
"The filtering/generation of managament messages happens on the protocol
layer, the RK type is construct of. This filtering/generation must be based
on the information in the relevant protocol specification to build a global
view of the corresponding protocol entity."



[...snip..]
> [TOLGA] ASP does not need to know/care what is going on with SCCP. It
just
> cares about RC in the message and delivers it to the corresponding user
> based on that.

If that were the case, there would be no need for RK on SSN in the first
place.  It is only by nature of the fact that SCCP users could be split
over ASPs that the RK would be necessary at all.  So, the ASP needs to
know/care what is going on with SCCP.
[TOLGA]M3UA-ASP will route just based on RC. Why should it do more?






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



From mailnull@www1.ietf.org  Fri Jan 10 09:17: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 JAA28656
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 09:17:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AETIm02199
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 09:29:18 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AET6J02189;
	Fri, 10 Jan 2003 09:29:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AESiJ02170
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 09:28:44 -0500
Received: from ihemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28641
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 09:16:01 -0500 (EST)
Received: from ih2mail.ih.lucent.com (h135-1-241-39.lucent.com [135.1.241.39])
	by ihemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0AEJHG02505
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 09:19:17 -0500 (EST)
Received: from SLBRYSON1 by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id IAA28489; Fri, 10 Jan 2003 08:19:16 -0600 (CST)
Reply-To: <slbryson@lucent.com>
From: "Sidney L. Bryson" <slbryson@lucent.com>
To: <sigtran@ietf.org>
Subject: RE: [Sigtran] m3ua- IG
Date: Fri, 10 Jan 2003 08:19:11 -0600
Message-ID: <003201c2b8b3$3f040500$930db987@SLBRYSON1>
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 CWS, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <20030110064552.C8782@openss7.org>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
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

Is this to say there limitations when using GTT with M3UA?

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
Brian F. G. Bidulock
Sent: Friday, January 10, 2003 7:46 AM
To: TOLGA ASVEREN
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG


TOLGA,

I think you also need to say which SCCP classes, and what SCCP routing
cannot be handled by such an M3UA.  Obviously, M3UA cannot support
SCCP classes 2 or 3, and cannot support messages which are marked
"Route on GT".

--brian

TOLGA ASVEREN wrote:
(Fri, 10 Jan 2003 15:36:56)
>
> Samuel,
>
> Did I say that you or anybody else MUST use M3UA with SSN based RKs?
>
> IMO M3UA does not need much changes to be able to handle this case(just
the
> concerns Brian has pointed out about handling of DATA must be addressed in
> the corresponding sections with a few sentences. The rest is
implementation
> dependent management functionality on SG).
>
>      Tolga

--
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 mailnull@www1.ietf.org  Fri Jan 10 09: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 JAA28778
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 09:20:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AEWPF02344
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 09:32:25 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AEW5J02329;
	Fri, 10 Jan 2003 09:32:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AEVRJ02294
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 09:31:27 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28740
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 09:18:43 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF5237673E.57207AFC-ONC2256CAA.004E2899@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 10 Jan 2003 16:18:36 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/10/2003
 04:18:40 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>


Brian,




TOLGA,

While your at it, I think you should say which SCCP management
messages are intercepted by the SG in performing its SPMC-like
management of SSNs and which are transparently passed to the ASP.
Otherwise, how is the ASP to know when it is responsibile for
SCCP management and when the SG is?
(You have SUA re-specified before your done... ;)
[TOLGA]What I am trying is not to define, how management logic in SG can be
implemented for SSN based RKs. I think this is out of the scope of M3UA
RFC(otherwise one could argue that each and every possible RK type should
be explained). What I try is to make it possible/clear using non-MTP3 RK
types with M3UA.

--brian

Brian F. G. Bidulock wrote:
(Fri, 10 Jan 2003 06:45:52)
> TOLGA,
>
> I think you also need to say which SCCP classes, and what SCCP routing
> cannot be handled by such an M3UA.  Obviously, M3UA cannot support
> SCCP classes 2 or 3, and cannot support messages which are marked
> "Route on GT".
>
> --brian
>
> TOLGA ASVEREN wrote:
(Fri, 10 Jan 2003 15:36:56)
> >
> > Samuel,
> >
> > Did I say that you or anybody else MUST use M3UA with SSN based RKs?
> >
> > IMO M3UA does not need much changes to be able to handle this case(just
the
> > concerns Brian has pointed out about handling of DATA must be addressed
in
> > the corresponding sections with a few sentences. The rest is
implementation
> > dependent management functionality on SG).
> >
> >      Tolga





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



From mailnull@www1.ietf.org  Fri Jan 10 10:15: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 KAA00252
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 10:15:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AFRct06255
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 10:27:38 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AFQgJ06175;
	Fri, 10 Jan 2003 10:26:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AFKhJ05816
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 10:20:43 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29974
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 10:07:57 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:hwkZCKGEzsqm5WsoJZe1uPgrx42mI0DW@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0AFBFD13189;
	Fri, 10 Jan 2003 08:11:15 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0AFBFE24778;
	Fri, 10 Jan 2003 08:11:15 -0700
Date: Fri, 10 Jan 2003 08:11:15 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Sidney L. Bryson" <slbryson@lucent.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110081115.H8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Sidney L. Bryson" <slbryson@lucent.com>,
	sigtran@ietf.org
References: <20030110064552.C8782@openss7.org> <003201c2b8b3$3f040500$930db987@SLBRYSON1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <003201c2b8b3$3f040500$930db987@SLBRYSON1>; from slbryson@lucent.com on Fri, Jan 10, 2003 at 08:19:11AM -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>

Sidney,

Just when attempting to use SSN routing keys.

--brian

Sidney L. Bryson wrote:                                                             (Fri, 10 Jan 2003 08:19:11)
> Is this to say there limitations when using GTT with M3UA?
> 
> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> Brian F. G. Bidulock
> Sent: Friday, January 10, 2003 7:46 AM
> To: TOLGA ASVEREN
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] m3ua- IG
> 
> 
> TOLGA,
> 
> I think you also need to say which SCCP classes, and what SCCP routing
> cannot be handled by such an M3UA.  Obviously, M3UA cannot support
> SCCP classes 2 or 3, and cannot support messages which are marked
> "Route on GT".
> 
> --brian
> 
> TOLGA ASVEREN wrote:
> (Fri, 10 Jan 2003 15:36:56)
> >
> > Samuel,
> >
> > Did I say that you or anybody else MUST use M3UA with SSN based RKs?
> >
> > IMO M3UA does not need much changes to be able to handle this case(just
> the
> > concerns Brian has pointed out about handling of DATA must be addressed in
> > the corresponding sections with a few sentences. The rest is
> implementation
> > dependent management functionality on SG).
> >
> >      Tolga
> 
> --
> 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 mailnull@www1.ietf.org  Fri Jan 10 10:15: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 KAA00268
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 10:15:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AFReZ06268
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 10:27:40 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AFRQJ06224;
	Fri, 10 Jan 2003 10:27:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AFNDJ05920
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 10:23:13 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00054
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 10:10:28 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:ytfmw85qk031PEVxh9FwDS0If58LcwRJ@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0AFDkD13207;
	Fri, 10 Jan 2003 08:13:46 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0AFDkC24789;
	Fri, 10 Jan 2003 08:13:46 -0700
Date: Fri, 10 Jan 2003 08:13:46 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110081346.I8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OFB3B4A2BE.4D6C0964-ONC2256CAA.004D47F2@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OFB3B4A2BE.4D6C0964-ONC2256CAA.004D47F2@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 04:11:37PM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 16:11:37)
> 
> Brian,
> 
> 
> 
> [...snip...]
> > [TOLGA] This is responsibility of SCCP. M3UA-ASP will just delºver the
> > messages to the corresponding entity, taking care of traffic for the AS,
> > corresponding to RC in the message.
> 
> But the only reason for using SSN RK is because SCCP is partitioned
> over multiple ASPs.  How can ASP get SCCP management messagess to
> the correct SCCP user without knowing where they appear?
> [TOLGA] It is not M3UA-ASPs responsibility to toute messaegs to SCCP-Users.
> M3UA-ASP will deliver the message to the correct SCCP entity based on RC.
> The rest belongs to SCCP itself.

But which SCCP management messages are arriving on which RC?

> 
> 
> 
> [..snip...]
> > [TOLGA] I consider it ot as the same DATA replicated to multiple
> > destinations but as a SCCP management message replicated by the
> management
> > functionality on SG. But still I proposed in my former message a new
> > sentence to clarify this. I think it should be enough to address your
> this
> > concern.
> 
> No it is not.  You must say which messages are to be duplicated,
> how, and to which ASPs in which AS.
> [TOLGA]Maybe just one more sentence:
> "The filtering/generation of managament messages happens on the protocol
> layer, the RK type is construct of. This filtering/generation must be based
> on the information in the relevant protocol specification to build a global
> view of the corresponding protocol entity."

Which messages are to be generated by SG and which by AS?  Which messages
will be intercepted and handled by SG and which are to be passed transparently
to AS?

> 
> 
> 
> [...snip..]
> > [TOLGA] ASP does not need to know/care what is going on with SCCP. It just
> > cares about RC in the message and delivers it to the corresponding user
> > based on that.
> 
> If that were the case, there would be no need for RK on SSN in the first
> place.  It is only by nature of the fact that SCCP users could be split
> over ASPs that the RK would be necessary at all.  So, the ASP needs to
> know/care what is going on with SCCP.
> [TOLGA]M3UA-ASP will route just based on RC. Why should it do more?

Which RC are the messages arriving?  It seems to be different for your
solution (which is broken) and Valerie's and Joe's.

--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  Fri Jan 10 10:15: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 KAA00281
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 10:15:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AFRgE06288
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 10:27:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AFRSJ06239;
	Fri, 10 Jan 2003 10:27:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AFO9J05972
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 10:24:09 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00072
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 10:11:24 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:v2piYP2Fs27HWWUEZzL7/8U5756ruJus@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0AFEgD13217;
	Fri, 10 Jan 2003 08:14:42 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0AFEgT24797;
	Fri, 10 Jan 2003 08:14:42 -0700
Date: Fri, 10 Jan 2003 08:14:42 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110081442.J8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF5237673E.57207AFC-ONC2256CAA.004E2899@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF5237673E.57207AFC-ONC2256CAA.004E2899@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 10, 2003 at 04:18:36PM +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>

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 10 Jan 2003 16:18:36)
> 
> Brian,
> 
> 
> 
> 
> TOLGA,
> 
> While your at it, I think you should say which SCCP management
> messages are intercepted by the SG in performing its SPMC-like
> management of SSNs and which are transparently passed to the ASP.
> Otherwise, how is the ASP to know when it is responsibile for
> SCCP management and when the SG is?
> (You have SUA re-specified before your done... ;)
> [TOLGA]What I am trying is not to define, how management logic in SG can be
> implemented for SSN based RKs. I think this is out of the scope of M3UA
> RFC(otherwise one could argue that each and every possible RK type should
> be explained). What I try is to make it possible/clear using non-MTP3 RK
> types with M3UA.

But you have to say which SCCP management functions are performed where.
You have some at the SG and some at the AS.  Which ones are where?

--brian


> 
> --brian
> 
> Brian F. G. Bidulock wrote:
> (Fri, 10 Jan 2003 06:45:52)
> > TOLGA,
> >
> > I think you also need to say which SCCP classes, and what SCCP routing
> > cannot be handled by such an M3UA.  Obviously, M3UA cannot support
> > SCCP classes 2 or 3, and cannot support messages which are marked
> > "Route on GT".
> >
> > --brian
> >
> > TOLGA ASVEREN wrote:
> (Fri, 10 Jan 2003 15:36:56)
> > >
> > > Samuel,
> > >
> > > Did I say that you or anybody else MUST use M3UA with SSN based RKs?
> > >
> > > IMO M3UA does not need much changes to be able to handle this case(just
> the
> > > concerns Brian has pointed out about handling of DATA must be addressed
> in
> > > the corresponding sections with a few sentences. The rest is
> implementation
> > > dependent management functionality on SG).
> > >
> > >      Tolga
> 
> 
> 
> 
> 
> _______________________________________________
> 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 Jan 10 13:11:56 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 NAA08198
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 13:11:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AIOCX19001
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 13:24:12 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AINnJ18984;
	Fri, 10 Jan 2003 13:23:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AIMHJ18941
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 13:22:17 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08136
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 13:09:29 -0500 (EST)
Received: from esealnt611.al.sw.ericsson.se (esealnt611.al.sw.ericsson.se [153.88.254.68])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id h0AICiKV028744;
	Fri, 10 Jan 2003 19:12:44 +0100 (MET)
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 ZGNL7Q0J; Fri, 10 Jan 2003 19:12:44 +0100
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <Y8J2TY8V>; Fri, 10 Jan 2003 19:12:44 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C475A02@EESTQNT105.es.eu.ericsson.se>
X-Sybari-Trust: 355ba314 1864f774 21c82a8a 00000138
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: sigtran@ietf.org
Cc: "'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>,
        "'TOLGA ASVEREN'" <TOLGA.ASVEREN@o2.com.tr>,
        "'Brian F. G. Bidulock'"
	 <bidulock@openss7.org>
Subject: RE: [Sigtran] m3ua- IG
Date: Fri, 10 Jan 2003 19:12:12 +0100
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, 

It was decided to remove SSN from the RK some time ago. But Samuel is right saying that there are still some "SSNs" throughout the text. I would agree to remove them.

The inclusion of the SCCP management procedures in M3UA is not that easy. I would suggest to people interested in that, to write a separate document with a clear proposal. 


Thanks // Javier.



> -----Original Message-----
> From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> Sent: Friday, January 10, 2003 6:38 AM
> To: sigtran@ietf.org
> Subject: [Sigtran] m3ua- IG
> 
> 
> 
> I think it would be good if we remove all SSN(sub system number)
> references from RFC or make a global statement in IG as "SSN 
> will not be
> supported by RFC 3332 and wherever it is being referred it should be
> ignored"
> 
> --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 mailnull@www1.ietf.org  Fri Jan 10 13:15: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 NAA08314
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 13:15:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AIRPS19184
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 13:27:25 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AIR3J19165;
	Fri, 10 Jan 2003 13:27:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AIQWJ19135
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 13:26:32 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08245
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 13:13:44 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (esealnt612.al.sw.ericsson.se [153.88.254.71])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id h0AIH0KV029368;
	Fri, 10 Jan 2003 19:17:00 +0100 (MET)
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 ZGNC1T6C; Fri, 10 Jan 2003 19:17:00 +0100
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <Y826MQ1H>; Fri, 10 Jan 2003 19:17:00 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C475A03@EESTQNT105.es.eu.ericsson.se>
X-Sybari-Trust: 6119ee5e 1864f774 21c82a8a 00000138
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>
Cc: sigtran@ietf.org
Date: Fri, 10 Jan 2003 19:16:59 +0100
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 IGv02: typo in  1.4.2.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 Samuel. 

Cheers // Javier.

> -----Original Message-----
> From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> Sent: Friday, January 10, 2003 6:25 AM
> To: javier.pastor-balbas@ece.ericsson.se
> Cc: sigtran@ietf.org
> Subject: m3ua IGv02: typo in 1.4.2.1
> 
> 
> 
> Javier,Ken,
> 
> section 1.4.2.1 Overview
> 
> ...The Routing Context therefore can be viewed as an index 
> into a sending
> node's Message Distribution Table containing the Routing Key entries.
> 
> Please change this to [ in IG]
> 
> ...The Routing Context therefore can be viewed as an index 
> into a sending 
> SGP's or Signaling Peer process's Message Distribution Table 
> containing
> the Routing Key entries.
> 
> --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 Sun, 5 Jan 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > Yes, change node to SGP.  I don't have control over the document
> > or I would do it for you.  Ask Javier or Ken to include it 
> in the IG.
> > 
> > --brian
> > 
> > Samuel Dur D. Jeyaseelan wrote:                           
> (Sun, 05 Jan 2003 22:48:14)
> > > 
> > > Brian,
> > >  Good explanation.As a reader of RFC i agree with you but as an
> > > implementor i dont.Because it leads me to think that RC is within
> > > the scope of SG but which is false as we discussed already.
> > > 
> > > --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, 3 Jan 2003, Brian F. G. Bidulock wrote:
> > > 
> > > > Samuel,
> > > > 
> > > > It's only an example of how to look at it: not a 
> requirement-- node, SGP,
> > > > what's the difference?
> > > > 
> > > > --brian
> > > > 
> > > > Samuel Dur D. Jeyaseelan wrote:                        
> (Fri, 03 Jan 2003 02:53:14)
> > > > > 
> > > > > Brian,
> > > > > Why dont u change section 1.4.2.1 Overview
> > > > > 
> > > > > ...The Routing Context therefore can be viewed as an 
> index into a sending
> > > > > node's Message Distribution Table containing the 
> Routing Key entries.
> > > > > 
> > > > > to
> > > > > 
> > > > > ...The Routing Context therefore can be viewed as an 
> index into a sending
> > > > > SGP's Message Distribution Table containing the 
> Routing Key entries.
> > > > > 
> > > > > --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. *******
> > > > > 
> > 
> > -- 
> > 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 Jan 10 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 OAA12908
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 14:15:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AJS6P23204
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 14:28:06 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AJRdJ23172;
	Fri, 10 Jan 2003 14:27:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AJQFJ23132
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 14:26:15 -0500
Received: from revere.sonusnet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12852
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 14:13:26 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3.sonusnet.com [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h0AJG2S15693;
	Fri, 10 Jan 2003 14:16:02 -0500 (EST)
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19)
	id <Y68HS3D1>; Fri, 10 Jan 2003 14:16:33 -0500
Message-ID: <4CF48720B6E9D4118D040060CF2074E9072F6BCC@sonusdc3.sonusnet.com>
From: "Wung, Joseph" <JWung@sonusnet.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>,
        TOLGA ASVEREN
	 <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] m3ua- IG
Date: Fri, 10 Jan 2003 14:16:32 -0500
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,
Tolga,

I agree that interoperability is not just the 
syntax of messages being exchanged between peers.
It is also about the procedures being executed
by the peers.  If it is implementation dependent,
vendor SG-A can implement in the method A, and
vendor SG-B in method B, the question is that can 
the ASP switch vendor from A to B without 
any changes on ASP?  If changes are needed when 
switching vendors occurs, then there is no 
interoperability.

Joe

> 
> Which standard M3UA ASP?  Yours?
> Valeries?  Joes?  Several? All?
> 
> You cannot acheive interoperability in
> this regard without both the SG and the
> ASP knowing which procedures are used.
> 
> Therefore, you cannot (as you said
> previously) just implement SSN RK on the
> SG without the ASP knowing how it is done.
> 
> Is there anyone else on the list that
> thinks this is basis for interoperability?
> 
> --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 mailnull@www1.ietf.org  Fri Jan 10 17:39:17 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 RAA18690
	for <sigtran-archive@odin.ietf.org>; Fri, 10 Jan 2003 17:39:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0AMpeT03589
	for sigtran-archive@odin.ietf.org; Fri, 10 Jan 2003 17:51:40 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AMpAJ03565;
	Fri, 10 Jan 2003 17:51:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AMnHJ03510
	for <sigtran@optimus.ietf.org>; Fri, 10 Jan 2003 17:49:17 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18605
	for <sigtran@ietf.org>; Fri, 10 Jan 2003 17:36:21 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:mvBtDaKPmOGpVq6I5yMaWhOt48IeJIqg@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0AMdZD20744;
	Fri, 10 Jan 2003 15:39:35 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0AMdYk09404;
	Fri, 10 Jan 2003 15:39:34 -0700
Date: Fri, 10 Jan 2003 15:39:34 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: sigtran@ietf.org,
        "'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>,
        "'TOLGA ASVEREN'" <TOLGA.ASVEREN@o2.com.tr>
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030110153934.K8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
	sigtran@ietf.org,
	"'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>,
	'TOLGA ASVEREN' <TOLGA.ASVEREN@o2.com.tr>
References: <1AB3D30B989BF141BBD5C70057B2EF7C475A02@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: <1AB3D30B989BF141BBD5C70057B2EF7C475A02@EESTQNT105.es.eu.ericsson.se>; from javier.pastor-balbas@ece.ericsson.se on Fri, Jan 10, 2003 at 07:12:12PM +0100
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,

Here's the proposed text: (again)

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

 3.16 SSN and CIC Routing Keys

 3.16.1 Description of the problem

    Use of SSN and CIC Routing Keys is inadequate in the specification
    leading to non-interoperable solutions.

 3.16.2 Text changes to the document

    ---------
    Old text: (Section 1.4.2.1)
    ---------

    Possible SS7 address/routing information that comprise a Routing Key
    entry includes, for example, the OPC, DPC, SIO found in the MTP3
    routing label, or MTP3-User specific fields (such as the ISUP CIC,
    SCCP subsystem number).  Some example Routing Keys are: the DPC
    alone, the DPC/OPC combination, the DPC/OPC/CIC combination, or the
    DPC/SSN combination.  The particular information used to define an
    M3UA Routing Key is application and network dependent, and none of
    the above examples are mandated.

    ---------
    New text: (Section 1.4.2.1)
    ---------

    Possible SS7 address/routing information that comprise a Routing Key
    entry includes, for example, the OPC, DPC, SIO found in the MTP3
    routing label.  Some example Routing Keys are: the DPC alone, the
    DPC/OPC combination, or the DPC/OPC/SI combination.  The particular
    information used to define an M3UA Routing Key is application and
    network dependent, and none of the above examples are mandated.


    ---------
    Old text: (Section 1.4.2.2)
    ---------

    Routing Keys SHOULD be unique in the sense that each received SS7
    signalling message SHOULD have a full or partial match to a single
    routing result. It is not necessary for the parameter range values
    within a particular Routing Key to be contiguous.  For example, an AS
    could be configured to support call processing for multiple ranges of
    PSTN trunks that are not represented by contiguous CIC values.

    ---------
    New text: (Section 1.4.2.2)
    ---------

    Routing Keys SHOULD be unique in the sense that each received SS7
    signalling message SHOULD have a full or partial match to a single
    routing result. It is not necessary for the parameter range values
    within a particular Routing Key to be contiguous.


    ---------
    Old text: (Section 1.4.7)
    ---------

    The M3UA layer at both the SGP and ASP also supports the assignment
    of signalling traffic into streams within an SCTP association.
    Traffic that requires sequencing SHOULD be assigned to the same
    stream.  To accomplish this, MTP3-User traffic may be assigned to
    individual streams based on, for example, the SLS value in the MTP3
    Routing Label or the ISUP CIC assignment, subject of course to the
    maximum number of streams supported by the underlying SCTP
    association.

    ---------
    New text: (Section 1.4.7)
    ---------

    The M3UA layer at both the SGP and ASP also supports the assignment
    of signalling traffic into streams within an SCTP association.
    Traffic that requires sequencing SHOULD be assigned to the same
    stream.  To accomplish this, MTP3-User traffic may be assigned to
    individual streams based on, for example, the SLS value in the MTP3
    Routing Label, subject of course to the maximum number of streams
    supported by the underlying SCTP association.


    ---------
    Old text: (Section 1.5.3)
    ---------

    In this example, the SGP contains an instance of the SS7 SCCP
    protocol layer that may, for example, perform the SCCP Global Title
    Translation (GTT) function for messages logically addressed to the SG
    SCCP.  If the result of a GTT for an SCCP message yields an SS7 DPC
    or DPC/SSN address of an SCCP peer located in the IP domain, the
    resulting MTP-TRANSFER request primitive is sent to the local M3UA-
    resident network address translation and mapping function for ongoing
    routing to the final IP destination.

    ---------
    New text: (Section 1.5.3)
    ---------

    In this example, the SGP contains an instance of the SS7 SCCP
    protocol layer that may, for example, perform the SCCP Global Title
    Translation (GTT) function for messages logically addressed to the SG
    SCCP.  If the result of a GTT for an SCCP message yields an SS7 DPC
    or DPC/SI address of an SCCP peer located in the IP domain, the
    resulting MTP-TRANSFER request primitive is sent to the local M3UA-
    resident network address translation and mapping function for ongoing
    routing to the final IP destination.


    ---------
    Old text: (Section 1.5.3)
    ---------

    For internal SGP modeling purposes, this may be accomplished with the
    use of an implementation-dependent nodal interworking function within
    the SGP that effectively sits below the SCCP and routes MTP-TRANSFER
    request/indication messages to/from both the MTP3 and the M3UA layer,
    based on the SS7 DPC or DPC/SSN address information.  This nodal
    interworking function has no visible peer protocol with either the
    ASP or SEP.

    ---------
    New text: (Section 1.5.3)
    ---------

    For internal SGP modeling purposes, this may be accomplished with the
    use of an implementation-dependent nodal interworking function within
    the SGP that effectively sits below the SCCP and routes MTP-TRANSFER
    request/indication messages to/from both the MTP3 and the M3UA layer,
    based on the SS7 DPC or DPC/SI address information.  This nodal
    interworking function has no visible peer protocol with either the
    ASP or SEP.



    ---------
    Old text: (Section 3.2)
    ---------

         Congestion Indications                0x0205
         Concerned Destination                 0x0206
         Routing Key                           0x0207
         Registration Result                   0x0208
         Deregistration Result                 0x0209
         Local_Routing Key Identifier          0x020a
         Destination Point Code                0x020b
         Service Indicators                    0x020c
         Reserved                              0x020d
         Originating Point Code List           0x020e
         Circuit Range                         0x020f
         Protocol Data                         0x0210
         Reserved                              0x0211
         Registration Status                   0x0212
         Deregistration Status                 0x0213

    ---------
    New text: (Section 3.2)
    ---------

         Congestion Indications                0x0205
         Concerned Destination                 0x0206
         Routing Key                           0x0207
         Registration Result                   0x0208
         Deregistration Result                 0x0209
         Local_Routing Key Identifier          0x020a
         Destination Point Code                0x020b
         Service Indicators                    0x020c
         Reserved                              0x020d
         Originating Point Code List           0x020e
         Protocol Data                         0x0210
         Reserved                              0x0211
         Registration Status                   0x0212
         Deregistration Status                 0x0213



    ---------
    Old text: (Section 3.6.1)
    ---------

       |                  Traffic Mode Type (optional)                 |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                     Destination Point Code                    |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                  Network Appearance (optional)                |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                  Service Indicators (optional)                |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |              Originating Point Code List (optional)           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                   Circuit Range List (optional)               |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       \                                                               \
       /                              ...                              /
       \                                                               \
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                     Destination Point Code                    |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                  Service Indicators (optional)                |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |              Originating Point Code List (optional)           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                   Circuit Range List (optional)               |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 
       Note: The Destination Point Code, Service Indicators, Originating
       Point Code List and Circuit Range List parameters MAY be repeated
       as a grouping within the Routing Key parameter, in the structure
       shown above.

    ---------
    New text: (Section 3.6.1)
    ---------

       |                  Traffic Mode Type (optional)                 |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                     Destination Point Code                    |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                  Network Appearance (optional)                |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                  Service Indicators (optional)                |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |              Originating Point Code List (optional)           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       \                                                               \
       /                              ...                              /
       \                                                               \
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                     Destination Point Code                    |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                  Service Indicators (optional)                |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |              Originating Point Code List (optional)           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 
       Note: The Destination Point Code, Service Indicators, and
       Originating Point Code List parameters MAY be repeated as a
       grouping within the Routing Key parameter, in the structure shown
       above.

    ---------
    Old text: (Section 3.6.1)
    ---------

    Circuit Range:
 
       An ISUP controlled circuit is uniquely identified by the SS7 OPC,
       DPC and CIC value.  For the purposes of identifying Circuit Ranges
       in an M3UA Routing Key, the optional Circuit Range parameter
       includes one or more circuit ranges, each identified by an OPC and
       Upper/Lower CIC value.  The DPC is implicit as it is mandatory and
       already included in the DPC parameter of the Routing Key.  The
       absence of the Circuit Range parameter in the Routing Key
       indicates the use of any Circuit Range values, in the case of
       ISUP/TUP traffic.  The Origination Point Code is encoded the same
       as the Destination Point Code parameter, while the CIC values are
       16-bit integers.

    ---------
    New text: (Section 3.6.1)
    ---------

    (none)
 

    ---------
    Old text: (Section 3.6.1)
    ---------

    The Circuit Range format is as follows:
 
        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 = 0x020f        |              Length           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |    Mask = 0   |          Origination Point Code #1            |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |       Lower CIC Value #1      |      Upper CIC Value #1       |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |    Mask = 0   |          Origination Point Code #2            |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |       Lower CIC Value #2      |      Upper CIC Value #2       |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       /                              ...                              /
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |    Mask = 0   |          Origination Point Code #n            |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |       Lower CIC Value #n      |      Upper CIC Value #n       |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    ---------
    New text: (Section 3.6.1)
    ---------

    (none)
 


    ---------
    Old text: (Section 3.7.1)
    ---------

       An Application Server Process may be configured to process traffic
       for more than one logical Application Server.  From the
       perspective of an ASP, a Routing Context defines a range of
       signalling traffic that the ASP is currently configured to receive
       from the SGP.  For example, an ASP could be configured to support
       call processing for multiple ranges of PSTN trunks and therefore
       receive related signalling traffic, identified by separate SS7
       DPC/OPC/CIC ranges.

    ---------
    New text: (Section 3.7.1)
    ---------

       An Application Server Process may be configured to process traffic
       for more than one logical Application Server.  From the
       perspective of an ASP, a Routing Context defines a range of
       signalling traffic that the ASP is currently configured to receive
       from the SGP.  For example, an ASP could be configured to support
       call processing for multiple ranges of PSTN trunks and therefore
       receive related signalling traffic, identified by separate SS7
       DPC/OPC/SI ranges.



    ---------
    Old text: (Section 4.4.1)
    ---------

    If an SGP determines that one or more of the Routing Key parameters
    are not supported for the purpose of creating new Routing Key
    entries, the SGP returns a Registration Response message to the ASP,
    containing a Registration Result "Error - Unsupported RK parameter
    field".  This result MAY be used if, for example, the SGP does not
    support RK Circuit Range Lists in a Routing Key because the SGP does
    not support ISUP traffic, or does not provide CIC range granularity.

    ---------
    New text: (Section 4.4.1)
    ---------

    If an SGP determines that one or more of the Routing Key parameters
    are not supported for the purpose of creating new Routing Key
    entries, the SGP returns a Registration Response message to the ASP,
    containing a Registration Result "Error - Unsupported RK parameter
    field".



    ---------
    Old text: (Section A.2.1)
    ---------

    For example, where Application Servers are defined using ranges of
    ISUP CIC values, the Operator is implicitly splitting up control of
    the related circuit groups.  Some CIC value range assignments may
    interfere with ISUP circuit group management procedures.

    ---------
    New text: (Section A.2.1)
    ---------

    (none)
 

 3.16.3 Solution description

    The removal of reference to SSN and CIC used in Routing Keys as well
    as removal of Circuit Range from the Routing Key parameter removes
    the unclear text from the specification.

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

--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  Sat Jan 11 08:07:52 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 IAA11052
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 08:07:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BDKV320737
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 08:20:31 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDJsJ20682;
	Sat, 11 Jan 2003 08:19:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDHkJ20643
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 08:17:46 -0500
Received: from web12801.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA11032
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 08:04:35 -0500 (EST)
Message-ID: <20030111130753.24467.qmail@web12801.mail.yahoo.com>
Received: from [62.29.76.4] by web12801.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 05:07:53 PST
Date: Sat, 11 Jan 2003 05:07:53 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <20030110081442.J8782@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, 10 Jan 2003
> 16:18:36)
> > 
> > Brian,
> > 
> > 
> > 
> > 
> > TOLGA,
> > 
> > While your at it, I think you should say which
> SCCP management
> > messages are intercepted by the SG in performing
> its SPMC-like
> > management of SSNs and which are transparently
> passed to the ASP.
> > Otherwise, how is the ASP to know when it is
> responsibile for
> > SCCP management and when the SG is?
> > (You have SUA re-specified before your done... ;)
> > [TOLGA]What I am trying is not to define, how
> management logic in SG can be
> > implemented for SSN based RKs. I think this is out
> of the scope of M3UA
> > RFC(otherwise one could argue that each and every
> possible RK type should
> > be explained). What I try is to make it
> possible/clear using non-MTP3 RK
> > types with M3UA.
> 
> But you have to say which SCCP management functions
> are performed where.
> You have some at the SG and some at the AS.  Which
> ones are where?
[TOLGA] Neither on M3UA-ASP nor on SCCP on ASP side
any special behavoir is expected. So, SCCP on ASP side
is a regular SCCP as defined by the relevant standard,
and it executes all of the procedures a regular SCCP
executes. That is the whole point I am trying to
explain. Nothing special is necessary there, only on
SG side. Like one has SPMC management on SG one can
implement a SCCP management there -to present a unique
and global view of the SCCP entity to the rest of the
network-, without any additional requirement. 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 08:08: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 IAA11074
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 08:08:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BDLF320767
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 08:21:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDL5J20759;
	Sat, 11 Jan 2003 08:21:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDJlJ20676
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 08:19:47 -0500
Received: from web12808.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA11042
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 08:06:36 -0500 (EST)
Message-ID: <20030111130954.52127.qmail@web12808.mail.yahoo.com>
Received: from [62.29.76.4] by web12808.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 05:09:54 PST
Date: Sat, 11 Jan 2003 05:09:54 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <4CF48720B6E9D4118D040060CF2074E9072F6BCC@sonusdc3.sonusnet.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>

Joe,
--- "Wung, Joseph" <JWung@sonusnet.com> wrote:
> Brian,
> Tolga,
> 
> I agree that interoperability is not just the 
> syntax of messages being exchanged between peers.
> It is also about the procedures being executed
> by the peers.  If it is implementation dependent,
> vendor SG-A can implement in the method A, and
> vendor SG-B in method B, the question is that can 
> the ASP switch vendor from A to B without 
> any changes on ASP?  If changes are needed when 
> switching vendors occurs, then there is no 
> interoperability.
[TOLGA] I also agree with your understanding of
interoperability but if one does not break
interoperability one should be free to do anything.
This is what I mean with a implementation dependent
management functionality, which does not break
interoperability.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 08:11: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 IAA11112
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 08:11:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BDOSO20855
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 08:24:28 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDO3J20839;
	Sat, 11 Jan 2003 08:24:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDNEJ20821
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 08:23:14 -0500
Received: from web12803.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA11092
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 08:10:03 -0500 (EST)
Message-ID: <20030111131320.82158.qmail@web12803.mail.yahoo.com>
Received: from [62.29.76.4] by web12803.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 05:13:20 PST
Date: Sat, 11 Jan 2003 05:13:20 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C475A02@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>

Javier,
--- "Javier Pastor-Balbas (ECE)"
<javier.pastor-balbas@ece.ericsson.se> wrote:
> Hi guys, 
> 
> It was decided to remove SSN from the RK some time
> ago. But Samuel is right saying that there are still
> some "SSNs" throughout the text. I would agree to
> remove them.
[TOLGA] Removing SSN from examples is not a problem,
but IMO RK type flexibility should be kept.
> 
> The inclusion of the SCCP management procedures in
> M3UA is not that easy. I would suggest to people
> interested in that, to write a separate document
> with a clear proposal. 
[TOLGA] I think nobody proposes to include SCCP
management functions into M3UA. My proposal is to add
a few sentences for the non-MTP3 based RK types -about
implementation dependent management functionality and
that it shouldn't break interoperability etc..-.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 08:12: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 IAA11143
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 08:12:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BDPHp20935
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 08:25:17 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDP7J20913;
	Sat, 11 Jan 2003 08:25:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDO4J20841
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 08:24:04 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11097
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 08:10:53 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:a/+BDCW6Xovp4wtrymV+dS0LTV21yojC@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BDEAD00854;
	Sat, 11 Jan 2003 06:14:10 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BDE9n03148;
	Sat, 11 Jan 2003 06:14:09 -0700
Date: Sat, 11 Jan 2003 06:14:09 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111061409.L8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030110081442.J8782@openss7.org> <20030111130753.24467.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: <20030111130753.24467.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 05:07:53AM -0800
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, 11 Jan 2003 05:07:53)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > TOLGA,
> > 
> > TOLGA ASVEREN wrote:                                
> >                                 (Fri, 10 Jan 2003
> > 16:18:36)
> > > 
> > > Brian,
> > > 
> > > 
> > > 
> > > 
> > > TOLGA,
> > > 
> > > While your at it, I think you should say which
> > SCCP management
> > > messages are intercepted by the SG in performing
> > its SPMC-like
> > > management of SSNs and which are transparently
> > passed to the ASP.
> > > Otherwise, how is the ASP to know when it is
> > responsibile for
> > > SCCP management and when the SG is?
> > > (You have SUA re-specified before your done... ;)
> > > [TOLGA]What I am trying is not to define, how
> > management logic in SG can be
> > > implemented for SSN based RKs. I think this is out
> > of the scope of M3UA
> > > RFC(otherwise one could argue that each and every
> > possible RK type should
> > > be explained). What I try is to make it
> > possible/clear using non-MTP3 RK
> > > types with M3UA.
> > 
> > But you have to say which SCCP management functions
> > are performed where.
> > You have some at the SG and some at the AS.  Which
> > ones are where?
> [TOLGA] Neither on M3UA-ASP nor on SCCP on ASP side
> any special behavoir is expected. So, SCCP on ASP side
> is a regular SCCP as defined by the relevant standard,
> and it executes all of the procedures a regular SCCP
> executes. That is the whole point I am trying to
> explain. Nothing special is necessary there, only on
> SG side. Like one has SPMC management on SG one can
> implement a SCCP management there -to present a unique
> and global view of the SCCP entity to the rest of the
> network-, without any additional requirement. 

No you can't.  SPMC management does not require the
involvement of the MTP-User.  SCCP management does.
So if you start performing any SCCP management on the
SG, it affects the ASP because it affects the SCCP
user at the AS.

--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  Sat Jan 11 08:12: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 IAA11169
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 08:12:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BDPJr20949
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 08:25:19 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDP9J20928;
	Sat, 11 Jan 2003 08:25:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDOrJ20873
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 08:24:53 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11110
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 08:11:42 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Qt+9S7fChQumaB2aZ4HCenZ7y71qsZxT@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BDExD00862;
	Sat, 11 Jan 2003 06:14:59 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BDExW03185;
	Sat, 11 Jan 2003 06:14:59 -0700
Date: Sat, 11 Jan 2003 06:14:59 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111061459.M8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <4CF48720B6E9D4118D040060CF2074E9072F6BCC@sonusdc3.sonusnet.com> <20030111130954.52127.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: <20030111130954.52127.qmail@web12808.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 05:09:54AM -0800
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, 11 Jan 2003 05:09:54)
> Joe,
> --- "Wung, Joseph" <JWung@sonusnet.com> wrote:
> > Brian,
> > Tolga,
> > 
> > I agree that interoperability is not just the 
> > syntax of messages being exchanged between peers.
> > It is also about the procedures being executed
> > by the peers.  If it is implementation dependent,
> > vendor SG-A can implement in the method A, and
> > vendor SG-B in method B, the question is that can 
> > the ASP switch vendor from A to B without 
> > any changes on ASP?  If changes are needed when 
> > switching vendors occurs, then there is no 
> > interoperability.
> [TOLGA] I also agree with your understanding of
> interoperability but if one does not break
> interoperability one should be free to do anything.
> This is what I mean with a implementation dependent
> management functionality, which does not break
> interoperability.

Such an implementation does not exist for either
SSN or CIC routing keys.

--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  Sat Jan 11 08:16: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 IAA11208
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 08:16:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BDSeV21073
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 08:28:40 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDS5J21059;
	Sat, 11 Jan 2003 08:28:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDRnJ21030
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 08:27:49 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11201
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 08:14:38 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:bW9YiGYEXaCcsvGQlCPgWRiw9UmVx6p9@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BDHuD00903;
	Sat, 11 Jan 2003 06:17:56 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BDHuo03259;
	Sat, 11 Jan 2003 06:17:56 -0700
Date: Sat, 11 Jan 2003 06:17:56 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111061756.N8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <1AB3D30B989BF141BBD5C70057B2EF7C475A02@EESTQNT105.es.eu.ericsson.se> <20030111131320.82158.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: <20030111131320.82158.qmail@web12803.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 05:13:20AM -0800
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, 11 Jan 2003 05:13:20)
> Javier,
> --- "Javier Pastor-Balbas (ECE)"
> <javier.pastor-balbas@ece.ericsson.se> wrote:
> > Hi guys, 
> > 
> > It was decided to remove SSN from the RK some time
> > ago. But Samuel is right saying that there are still
> > some "SSNs" throughout the text. I would agree to
> > remove them.
> [TOLGA] Removing SSN from examples is not a problem,
> but IMO RK type flexibility should be kept.

I disagree.  M3UA RKs SHOULD be restricted to MTP Level 3
information only (i.e. information from the MTP Routing
Label).

> > 
> > The inclusion of the SCCP management procedures in
> > M3UA is not that easy. I would suggest to people
> > interested in that, to write a separate document
> > with a clear proposal. 
> [TOLGA] I think nobody proposes to include SCCP
> management functions into M3UA. My proposal is to add
> a few sentences for the non-MTP3 based RK types -about
> implementation dependent management functionality and
> that it shouldn't break interoperability etc..-.

A single method that does not break interoperablity has
not yet been demonstrated.

--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  Sat Jan 11 08:22: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 IAA11269
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 08:22:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BDZXx21225
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 08:35:33 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDZ8J21214;
	Sat, 11 Jan 2003 08:35:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDYbJ21186
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 08:34:37 -0500
Received: from web12804.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA11257
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 08:21:25 -0500 (EST)
Message-ID: <20030111132442.89057.qmail@web12804.mail.yahoo.com>
Received: from [62.29.76.4] by web12804.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 05:24:42 PST
Date: Sat, 11 Jan 2003 05:24:42 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <20030110081346.I8782@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, 10 Jan 2003
> 16:11:37)
> > 
> > Brian,
> > 
> > 
> > 
> > [...snip...]
> > > [TOLGA] This is responsibility of SCCP. M3UA-ASP
> will just delºver the
> > > messages to the corresponding entity, taking
> care of traffic for the AS,
> > > corresponding to RC in the message.
> > 
> > But the only reason for using SSN RK is because
> SCCP is partitioned
> > over multiple ASPs.  How can ASP get SCCP
> management messagess to
> > the correct SCCP user without knowing where they
> appear?
> > [TOLGA] It is not M3UA-ASPs responsibility to
> toute messaegs to SCCP-Users.
> > M3UA-ASP will deliver the message to the correct
> SCCP entity based on RC.
> > The rest belongs to SCCP itself.
> 
> But which SCCP management messages are arriving on
> which RC?
[TOLGA] Each AS will receive the necessary management
messages. Now you might ask, which ones are
"necessary"? As I said, for this one has to look to
the relevant specification. There is no
interoprability problem, let me explain why for the
SSN case just as an example. The goal is to
interoperate with a M3UA compliant ASP which has a
SCCP stack compliant with relevant specification.So we
have a regular M3UA and SCCP on ASP and we don't want
to touch them and to assume any special behavior from
them. Now, for each AS(which is based on DPC+SSN), SG
will send management messages sent for this SSN and
also management messages sent for the whole
SCCP(requires duplication of SCCP message in this
case). This IMO is not something to be described in
M3UA RFC. Did we put any extra requirement to M3UA on
ASP, or on any M3UA procedure or on SCCP on ASP side?
And the decision how to implement the managemnt
functionality was based just on SCCP specification
itself. 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 08:26: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 IAA11327
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 08:26:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BDdNL21956
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 08:39:23 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDd3J21948;
	Sat, 11 Jan 2003 08:39:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDc5J21931
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 08:38:06 -0500
Received: from web12801.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA11293
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 08:24:54 -0500 (EST)
Message-ID: <20030111132812.26221.qmail@web12801.mail.yahoo.com>
Received: from [62.29.76.4] by web12801.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 05:28:12 PST
Date: Sat, 11 Jan 2003 05:28:12 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <20030111061409.L8782@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:                                
>                                 (Sat, 11 Jan 2003
> 05:07:53)
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > TOLGA,
> > > 
> > > TOLGA ASVEREN wrote:                            
>    
> > >                                 (Fri, 10 Jan
> 2003
> > > 16:18:36)
> > > > 
> > > > Brian,
> > > > 
> > > > 
> > > > 
> > > > 
> > > > TOLGA,
> > > > 
> > > > While your at it, I think you should say which
> > > SCCP management
> > > > messages are intercepted by the SG in
> performing
> > > its SPMC-like
> > > > management of SSNs and which are transparently
> > > passed to the ASP.
> > > > Otherwise, how is the ASP to know when it is
> > > responsibile for
> > > > SCCP management and when the SG is?
> > > > (You have SUA re-specified before your done...
> ;)
> > > > [TOLGA]What I am trying is not to define, how
> > > management logic in SG can be
> > > > implemented for SSN based RKs. I think this is
> out
> > > of the scope of M3UA
> > > > RFC(otherwise one could argue that each and
> every
> > > possible RK type should
> > > > be explained). What I try is to make it
> > > possible/clear using non-MTP3 RK
> > > > types with M3UA.
> > > 
> > > But you have to say which SCCP management
> functions
> > > are performed where.
> > > You have some at the SG and some at the AS. 
> Which
> > > ones are where?
> > [TOLGA] Neither on M3UA-ASP nor on SCCP on ASP
> side
> > any special behavoir is expected. So, SCCP on ASP
> side
> > is a regular SCCP as defined by the relevant
> standard,
> > and it executes all of the procedures a regular
> SCCP
> > executes. That is the whole point I am trying to
> > explain. Nothing special is necessary there, only
> on
> > SG side. Like one has SPMC management on SG one
> can
> > implement a SCCP management there -to present a
> unique
> > and global view of the SCCP entity to the rest of
> the
> > network-, without any additional requirement. 
> 
> No you can't.  SPMC management does not require the
> involvement of the MTP-User.  SCCP management does.
> So if you start performing any SCCP management on
> the
> SG, it affects the ASP because it affects the SCCP
> user at the AS.
[TOLGA] Can you give an example, how the method I
propose affects the SCCP user at the ASP side?

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 08:28: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 IAA11358
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 08:28:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BDfIN22050
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 08:41:18 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDf8J22037;
	Sat, 11 Jan 2003 08:41:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDeTJ22016
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 08:40:29 -0500
Received: from web12806.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA11343
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 08:27:18 -0500 (EST)
Message-ID: <20030111133036.90270.qmail@web12806.mail.yahoo.com>
Received: from [62.29.76.4] by web12806.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 05:30:36 PST
Date: Sat, 11 Jan 2003 05:30:36 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <20030111061459.M8782@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:                                
>                                 (Sat, 11 Jan 2003
> 05:09:54)
> > Joe,
> > --- "Wung, Joseph" <JWung@sonusnet.com> wrote:
> > > Brian,
> > > Tolga,
> > > 
> > > I agree that interoperability is not just the 
> > > syntax of messages being exchanged between
> peers.
> > > It is also about the procedures being executed
> > > by the peers.  If it is implementation
> dependent,
> > > vendor SG-A can implement in the method A, and
> > > vendor SG-B in method B, the question is that
> can 
> > > the ASP switch vendor from A to B without 
> > > any changes on ASP?  If changes are needed when 
> > > switching vendors occurs, then there is no 
> > > interoperability.
> > [TOLGA] I also agree with your understanding of
> > interoperability but if one does not break
> > interoperability one should be free to do
> anything.
> > This is what I mean with a implementation
> dependent
> > management functionality, which does not break
> > interoperability.
> 
> Such an implementation does not exist for either
> SSN or CIC routing keys.
[TOLGA] IMO, the SSN method discussed ont he list is O.K.

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 08:37: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 IAA11436
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 08:37:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BDneh22244
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 08:49:40 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDnEJ22206;
	Sat, 11 Jan 2003 08:49:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BDmsJ22169
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 08:48:54 -0500
Received: from web12808.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA11408
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 08:35:43 -0500 (EST)
Message-ID: <20030111133900.55283.qmail@web12808.mail.yahoo.com>
Received: from [62.29.76.4] by web12808.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 05:39:00 PST
Date: Sat, 11 Jan 2003 05:39:00 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <20030111061756.N8782@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:                                
>                                 (Sat, 11 Jan 2003
> 05:13:20)
> > Javier,
> > --- "Javier Pastor-Balbas (ECE)"
> > <javier.pastor-balbas@ece.ericsson.se> wrote:
> > > Hi guys, 
> > > 
> > > It was decided to remove SSN from the RK some
> time
> > > ago. But Samuel is right saying that there are
> still
> > > some "SSNs" throughout the text. I would agree
> to
> > > remove them.
> > [TOLGA] Removing SSN from examples is not a
> problem,
> > but IMO RK type flexibility should be kept.
> 
> I disagree.  M3UA RKs SHOULD be restricted to MTP
> Level 3
> information only (i.e. information from the MTP
> Routing
> Label).
[TOLGA] Why do you want to do this? Is there a pert of
the core M3UA protocol, which relies on a specific RK
type? IMO it is better to leave the people free for
this decision. As I pointed out several times, in fact
a solution, which does not bring interoperability
problems is totally transparent to other nodes. I
don't think it is a good idea to act as inquisition.
But I agree it makes sense to warn people about
non-MTP3 RK types and explain briefly how those might
be handled within the boundaries of M3UA -just from
M3UA point of view-. 
> 
> > > 
> > > The inclusion of the SCCP management procedures
> in
> > > M3UA is not that easy. I would suggest to people
> > > interested in that, to write a separate document
> > > with a clear proposal. 
> > [TOLGA] I think nobody proposes to include SCCP
> > management functions into M3UA. My proposal is to
> add
> > a few sentences for the non-MTP3 based RK types
> -about
> > implementation dependent management functionality
> and
> > that it shouldn't break interoperability etc..-.
> 
> A single method that does not break interoperablity
> has
> not yet been demonstrated.
[TOLGA] IMO SSN method works. And more important than
this, do you think that we need to investigate each
and every possible RK type to see whether the
necessary managament functionality might be
implemented or not? How can one decide, whether such a
functionality might be implemented or not?

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 09:09: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 JAA11890
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 09:09:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BEMCi23649
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 09:22:12 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BELeJ23594;
	Sat, 11 Jan 2003 09:21:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BEKPJ23538
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 09:20:25 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11800
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 09:07:12 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:/fRODoN1y6pCNEo/DFUGhZAUpK2UvE8G@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BEAUD01696;
	Sat, 11 Jan 2003 07:10:30 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BEAUv05354;
	Sat, 11 Jan 2003 07:10:30 -0700
Date: Sat, 11 Jan 2003 07:10:30 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111071030.O8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030110081346.I8782@openss7.org> <20030111132442.89057.qmail@web12804.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030111132442.89057.qmail@web12804.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 05:24:42AM -0800
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

Tolga,

Tolga Asveren wrote:                                                                 (Sat, 11 Jan 2003 05:24:42)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > TOLGA,
> > 
> > TOLGA ASVEREN wrote:                                
> >                                 (Fri, 10 Jan 2003
> > 16:11:37)
> > > 
> > > Brian,
> > > 
> > > 
> > > 
> > > [...snip...]
> > > > [TOLGA] This is responsibility of SCCP. M3UA-ASP
> > will just delºver the
> > > > messages to the corresponding entity, taking
> > care of traffic for the AS,
> > > > corresponding to RC in the message.
> > > 
> > > But the only reason for using SSN RK is because
> > SCCP is partitioned
> > > over multiple ASPs.  How can ASP get SCCP
> > management messagess to
> > > the correct SCCP user without knowing where they
> > appear?
> > > [TOLGA] It is not M3UA-ASPs responsibility to
> > toute messaegs to SCCP-Users.
> > > M3UA-ASP will deliver the message to the correct
> > SCCP entity based on RC.
> > > The rest belongs to SCCP itself.
> > 
> > But which SCCP management messages are arriving on
> > which RC?
> [TOLGA] Each AS will receive the necessary management
> messages. Now you might ask, which ones are
> "necessary"? As I said, for this one has to look to
> the relevant specification. There is no
> interoprability problem, let me explain why for the
> SSN case just as an example. The goal is to
> interoperate with a M3UA compliant ASP which has a
> SCCP stack compliant with relevant specification.So we
> have a regular M3UA and SCCP on ASP and we don't want
> to touch them and to assume any special behavior from
> them. Now, for each AS(which is based on DPC+SSN), SG
> will send management messages sent for this SSN and
> also management messages sent for the whole
> SCCP(requires duplication of SCCP message in this
> case). This IMO is not something to be described in
> M3UA RFC. Did we put any extra requirement to M3UA on
> ASP, or on any M3UA procedure or on SCCP on ASP side?
> And the decision how to implement the managemnt
> functionality was based just on SCCP specification
> itself. 

Say there are 8 ASPs in the AS.  Take one SCCP management
message: SST.  You send SST once to each ASP.  Each ASP
with a compliant SCCP will return one response (say SSP).
The distant end will receives 8 SSPs for each SST sent.
This is a violation of SCCP specifications.  Your
implementation is broken.

--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  Sat Jan 11 09:09: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 JAA11909
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 09:09:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BEMMe23676
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 09:22:22 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BEM9J23628;
	Sat, 11 Jan 2003 09:22:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BELLJ23575
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 09:21:21 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11841
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 09:08:08 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:v/aY59J9DCazKEXOwwxEwt/u5KjF39+d@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BEBQD01706;
	Sat, 11 Jan 2003 07:11:26 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BEBQG05366;
	Sat, 11 Jan 2003 07:11:26 -0700
Date: Sat, 11 Jan 2003 07:11:26 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111071126.P8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111061409.L8782@openss7.org> <20030111132812.26221.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: <20030111132812.26221.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 05:28:12AM -0800
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, 11 Jan 2003 05:28:12)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Sat, 11 Jan 2003
> > 05:07:53)
> > > Brian,
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > wrote:
> > > > TOLGA,
> > > > 
> > > > TOLGA ASVEREN wrote:                            
> >    
> > > >                                 (Fri, 10 Jan
> > 2003
> > > > 16:18:36)
> > > > > 
> > > > > Brian,
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > TOLGA,
> > > > > 
> > > > > While your at it, I think you should say which
> > > > SCCP management
> > > > > messages are intercepted by the SG in
> > performing
> > > > its SPMC-like
> > > > > management of SSNs and which are transparently
> > > > passed to the ASP.
> > > > > Otherwise, how is the ASP to know when it is
> > > > responsibile for
> > > > > SCCP management and when the SG is?
> > > > > (You have SUA re-specified before your done...
> > ;)
> > > > > [TOLGA]What I am trying is not to define, how
> > > > management logic in SG can be
> > > > > implemented for SSN based RKs. I think this is
> > out
> > > > of the scope of M3UA
> > > > > RFC(otherwise one could argue that each and
> > every
> > > > possible RK type should
> > > > > be explained). What I try is to make it
> > > > possible/clear using non-MTP3 RK
> > > > > types with M3UA.
> > > > 
> > > > But you have to say which SCCP management
> > functions
> > > > are performed where.
> > > > You have some at the SG and some at the AS. 
> > Which
> > > > ones are where?
> > > [TOLGA] Neither on M3UA-ASP nor on SCCP on ASP
> > side
> > > any special behavoir is expected. So, SCCP on ASP
> > side
> > > is a regular SCCP as defined by the relevant
> > standard,
> > > and it executes all of the procedures a regular
> > SCCP
> > > executes. That is the whole point I am trying to
> > > explain. Nothing special is necessary there, only
> > on
> > > SG side. Like one has SPMC management on SG one
> > can
> > > implement a SCCP management there -to present a
> > unique
> > > and global view of the SCCP entity to the rest of
> > the
> > > network-, without any additional requirement. 
> > 
> > No you can't.  SPMC management does not require the
> > involvement of the MTP-User.  SCCP management does.
> > So if you start performing any SCCP management on
> > the
> > SG, it affects the ASP because it affects the SCCP
> > user at the AS.
> [TOLGA] Can you give an example, how the method I
> propose affects the SCCP user at the ASP side?

Because the SCCP at the ASP is responsible for SCCP
management.  When you make the SG responsible for
any SCCP management you are affecting the SCCP at the
ASP.

--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  Sat Jan 11 09:09: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 JAA11922
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 09:09:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BEMRs23704
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 09:22:27 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BEMGJ23667;
	Sat, 11 Jan 2003 09:22:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BELoJ23599
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 09:21:50 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11849
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 09:08:38 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:0S49Js0gzGfuiY7rap/KjSwcnXZX8dej@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BEBtD01708;
	Sat, 11 Jan 2003 07:11:56 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BEBtA05374;
	Sat, 11 Jan 2003 07:11:55 -0700
Date: Sat, 11 Jan 2003 07:11:55 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111071155.Q8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111061459.M8782@openss7.org> <20030111133036.90270.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: <20030111133036.90270.qmail@web12806.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 05:30:36AM -0800
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, 11 Jan 2003 05:30:36)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Sat, 11 Jan 2003
> > 05:09:54)
> > > Joe,
> > > --- "Wung, Joseph" <JWung@sonusnet.com> wrote:
> > > > Brian,
> > > > Tolga,
> > > > 
> > > > I agree that interoperability is not just the 
> > > > syntax of messages being exchanged between
> > peers.
> > > > It is also about the procedures being executed
> > > > by the peers.  If it is implementation
> > dependent,
> > > > vendor SG-A can implement in the method A, and
> > > > vendor SG-B in method B, the question is that
> > can 
> > > > the ASP switch vendor from A to B without 
> > > > any changes on ASP?  If changes are needed when 
> > > > switching vendors occurs, then there is no 
> > > > interoperability.
> > > [TOLGA] I also agree with your understanding of
> > > interoperability but if one does not break
> > > interoperability one should be free to do
> > anything.
> > > This is what I mean with a implementation
> > dependent
> > > management functionality, which does not break
> > > interoperability.
> > 
> > Such an implementation does not exist for either
> > SSN or CIC routing keys.
> [TOLGA] IMO, the SSN method discussed ont he list is O.K.

Its broken as already demonstrated.

--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  Sat Jan 11 09:10: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 JAA12003
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 09:10:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BENLq23759
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 09:23:21 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BEN9J23750;
	Sat, 11 Jan 2003 09:23:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BEMxJ23727
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 09:22:59 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11936
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 09:09:47 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:ZlrPS+5/HqvMaA6EMnuaUe+zc870S31s@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BED5D01735;
	Sat, 11 Jan 2003 07:13:05 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BED4P05431;
	Sat, 11 Jan 2003 07:13:04 -0700
Date: Sat, 11 Jan 2003 07:13:04 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111071304.R8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111061756.N8782@openss7.org> <20030111133900.55283.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: <20030111133900.55283.qmail@web12808.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 05:39:00AM -0800
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, 11 Jan 2003 05:39:00)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Sat, 11 Jan 2003
> > 05:13:20)
> > > Javier,
> > > --- "Javier Pastor-Balbas (ECE)"
> > > <javier.pastor-balbas@ece.ericsson.se> wrote:
> > > > Hi guys, 
> > > > 
> > > > It was decided to remove SSN from the RK some
> > time
> > > > ago. But Samuel is right saying that there are
> > still
> > > > some "SSNs" throughout the text. I would agree
> > to
> > > > remove them.
> > > [TOLGA] Removing SSN from examples is not a
> > problem,
> > > but IMO RK type flexibility should be kept.
> > 
> > I disagree.  M3UA RKs SHOULD be restricted to MTP
> > Level 3
> > information only (i.e. information from the MTP
> > Routing
> > Label).
> [TOLGA] Why do you want to do this? Is there a pert of
> the core M3UA protocol, which relies on a specific RK
> type? IMO it is better to leave the people free for
> this decision. As I pointed out several times, in fact
> a solution, which does not bring interoperability
> problems is totally transparent to other nodes. I
> don't think it is a good idea to act as inquisition.
> But I agree it makes sense to warn people about
> non-MTP3 RK types and explain briefly how those might
> be handled within the boundaries of M3UA -just from
> M3UA point of view-. 

Because the SS7 protocol relies on the fact that MTP
only examines the MTP Routing Label for routing.

> > 
> > > > 
> > > > The inclusion of the SCCP management procedures
> > in
> > > > M3UA is not that easy. I would suggest to people
> > > > interested in that, to write a separate document
> > > > with a clear proposal. 
> > > [TOLGA] I think nobody proposes to include SCCP
> > > management functions into M3UA. My proposal is to
> > add
> > > a few sentences for the non-MTP3 based RK types
> > -about
> > > implementation dependent management functionality
> > and
> > > that it shouldn't break interoperability etc..-.
> > 
> > A single method that does not break interoperablity
> > has
> > not yet been demonstrated.
> [TOLGA] IMO SSN method works. And more important than
> this, do you think that we need to investigate each
> and every possible RK type to see whether the
> necessary managament functionality might be
> implemented or not? How can one decide, whether such a
> functionality might be implemented or not?

It is broken as demonstrated in previous note.

--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  Sat Jan 11 11:58: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 LAA14429
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 11:58:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BHBEh32284
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 12:11:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHAuJ32248;
	Sat, 11 Jan 2003 12:10:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BH6YJ31352
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 12:06:34 -0500
Received: from web12804.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA14356
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 11:53:17 -0500 (EST)
Message-ID: <20030111165636.14173.qmail@web12804.mail.yahoo.com>
Received: from [62.29.84.163] by web12804.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 08:56:36 PST
Date: Sat, 11 Jan 2003 08:56:36 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <20030111071126.P8782@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] Can you give an example, how the method I
> > propose affects the SCCP user at the ASP side?
> 
> Because the SCCP at the ASP is responsible for SCCP
> management.  When you make the SG responsible for
> any SCCP management you are affecting the SCCP at
> the
> ASP.
[TOLGA] Can you give a specific example?


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 11:58: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 LAA14442
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 11:58:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BHBFZ32296
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 12:11:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHAVJ32220;
	Sat, 11 Jan 2003 12:10:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BH4iJ31293
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 12:04:44 -0500
Received: from web12802.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA14333
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 11:51:27 -0500 (EST)
Message-ID: <20030111165446.62756.qmail@web12802.mail.yahoo.com>
Received: from [62.29.84.163] by web12802.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 08:54:46 PST
Date: Sat, 11 Jan 2003 08:54:46 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <20030111071030.O8782@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:                                
>                                 (Sat, 11 Jan 2003
> 05:24:42)
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > TOLGA,
> > > 
> > > TOLGA ASVEREN wrote:                            
>    
> > >                                 (Fri, 10 Jan
> 2003
> > > 16:11:37)
> > > > 
> > > > Brian,
> > > > 
> > > > 
> > > > 
> > > > [...snip...]
> > > > > [TOLGA] This is responsibility of SCCP.
> M3UA-ASP
> > > will just delºver the
> > > > > messages to the corresponding entity, taking
> > > care of traffic for the AS,
> > > > > corresponding to RC in the message.
> > > > 
> > > > But the only reason for using SSN RK is
> because
> > > SCCP is partitioned
> > > > over multiple ASPs.  How can ASP get SCCP
> > > management messagess to
> > > > the correct SCCP user without knowing where
> they
> > > appear?
> > > > [TOLGA] It is not M3UA-ASPs responsibility to
> > > toute messaegs to SCCP-Users.
> > > > M3UA-ASP will deliver the message to the
> correct
> > > SCCP entity based on RC.
> > > > The rest belongs to SCCP itself.
> > > 
> > > But which SCCP management messages are arriving
> on
> > > which RC?
> > [TOLGA] Each AS will receive the necessary
> management
> > messages. Now you might ask, which ones are
> > "necessary"? As I said, for this one has to look
> to
> > the relevant specification. There is no
> > interoprability problem, let me explain why for
> the
> > SSN case just as an example. The goal is to
> > interoperate with a M3UA compliant ASP which has a
> > SCCP stack compliant with relevant
> specification.So we
> > have a regular M3UA and SCCP on ASP and we don't
> want
> > to touch them and to assume any special behavior
> from
> > them. Now, for each AS(which is based on DPC+SSN),
> SG
> > will send management messages sent for this SSN
> and
> > also management messages sent for the whole
> > SCCP(requires duplication of SCCP message in this
> > case). This IMO is not something to be described
> in
> > M3UA RFC. Did we put any extra requirement to M3UA
> on
> > ASP, or on any M3UA procedure or on SCCP on ASP
> side?
> > And the decision how to implement the managemnt
> > functionality was based just on SCCP specification
> > itself. 
> 
> Say there are 8 ASPs in the AS.  Take one SCCP
> management
> message: SST.  You send SST once to each ASP.  Each
> ASP
> with a compliant SCCP will return one response (say
> SSP).
> The distant end will receives 8 SSPs for each SST
> sent.
> This is a violation of SCCP specifications.  Your
> implementation is broken.
[TOLGA]This is the reason why you have the management
functionality on SG. You get the responses and create
the global view of the corresponding subsystem. Not
all of the SSP is sent to SS7 network, only one. 

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 12:08: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 MAA14627
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 12:08:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BHKrR32493
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 12:20:53 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHK7J32475;
	Sat, 11 Jan 2003 12:20:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHJ6J32417
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 12:19:06 -0500
Received: from cerberus.intellinet-tech.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14565
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 12:05:50 -0500 (EST)
From: ngoel@cerberus.intellinet-tech.com
Received: from localhost (ngoel@localhost)
	by cerberus.intellinet-tech.com (8.11.6/8.11.6) with ESMTP id h0BH5Ml24883;
	Sat, 11 Jan 2003 12:05:23 -0500
Date: Sat, 11 Jan 2003 12:05:22 -0500 (EST)
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Tolga Asveren <tolga_asveren@yahoo.com>, <sigtran@ietf.org>
Subject: Re: [Sigtran] m3ua- IG
In-Reply-To: <20030111071030.O8782@openss7.org>
Message-ID: <Pine.LNX.4.44.0301111147470.23581-100000@cerberus.intellinet-tech.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/Tolga,
 Reading your discussion I have few thoughts/comments -
Are we not trying to violate principles of layered protocol here by trying 
to change M3UA to make distributed SCCP work. The point is we should 
not try to change M3UA behaviour to satisfy needs of M3UA user.
We should not assume how M3UA users will be distributed for example based 
on SSN or not. It is responsibility of distributed SCCP to handle 
possibilities of receiving SCMG messages for a given SSN on one or more 
ASP's. This can be easily acheived in implementation specific way. 
For example if we distribute single SSN across two ASP's then there is 
possibility of receiving TCAP response on wrong ASP. But M3UA should not 
be responsible for resolving this. This can be resolved in implementation 
specific way.
-Narender 

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



From mailnull@www1.ietf.org  Sat Jan 11 12:11: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 MAA14725
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 12:11:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BHOjM32576
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 12:24:45 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHO5J32560;
	Sat, 11 Jan 2003 12:24:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHNhJ32542
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 12:23:43 -0500
Received: from web12804.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA14701
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 12:10:26 -0500 (EST)
Message-ID: <20030111171345.16470.qmail@web12804.mail.yahoo.com>
Received: from [62.29.84.163] by web12804.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 09:13:45 PST
Date: Sat, 11 Jan 2003 09:13:45 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <20030111071304.R8782@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:                                
>                                 (Sat, 11 Jan 2003
> 05:39:00)
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Tolga Asveren wrote:                            
>    
> > >                                 (Sat, 11 Jan
> 2003
> > > 05:13:20)
> > > > Javier,
> > > > --- "Javier Pastor-Balbas (ECE)"
> > > > <javier.pastor-balbas@ece.ericsson.se> wrote:
> > > > > Hi guys, 
> > > > > 
> > > > > It was decided to remove SSN from the RK
> some
> > > time
> > > > > ago. But Samuel is right saying that there
> are
> > > still
> > > > > some "SSNs" throughout the text. I would
> agree
> > > to
> > > > > remove them.
> > > > [TOLGA] Removing SSN from examples is not a
> > > problem,
> > > > but IMO RK type flexibility should be kept.
> > > 
> > > I disagree.  M3UA RKs SHOULD be restricted to
> MTP
> > > Level 3
> > > information only (i.e. information from the MTP
> > > Routing
> > > Label).
> > [TOLGA] Why do you want to do this? Is there a
> pert of
> > the core M3UA protocol, which relies on a specific
> RK
> > type? IMO it is better to leave the people free
> for
> > this decision. As I pointed out several times, in
> fact
> > a solution, which does not bring interoperability
> > problems is totally transparent to other nodes. I
> > don't think it is a good idea to act as
> inquisition.
> > But I agree it makes sense to warn people about
> > non-MTP3 RK types and explain briefly how those
> might
> > be handled within the boundaries of M3UA -just
> from
> > M3UA point of view-. 
> 
> Because the SS7 protocol relies on the fact that MTP
> only examines the MTP Routing Label for routing.
[TOLGA] IMO that MTP3 uses Routing Label for
discrimination and SIO for distribution is the reason,
why MTP3-type RKs are easily supported without a need
of examining inside DATA messages. But why should we
forbid to implement an extra management functionality 
on SG to be able to use non-MTP3 RK types, if it is
totally transparent to other nodes? Which test case in
an interoperability event will fail for such a SG?

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 12:21: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 MAA14833
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 12:21:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BHXk000424
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 12:33:46 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHX5J00408;
	Sat, 11 Jan 2003 12:33:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHWRJ00390
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 12:32:27 -0500
Received: from web12808.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA14818
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 12:19:10 -0500 (EST)
Message-ID: <20030111172229.83254.qmail@web12808.mail.yahoo.com>
Received: from [62.29.84.163] by web12808.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 09:22:29 PST
Date: Sat, 11 Jan 2003 09:22:29 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <Pine.LNX.4.44.0301111147470.23581-100000@cerberus.intellinet-tech.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>

Narender,
--- ngoel@cerberus.intellinet-tech.com wrote:
> Brian/Tolga,
>  Reading your discussion I have few
> thoughts/comments -
> Are we not trying to violate principles of layered
> protocol here by trying
[TOLGA]I also would think this is against the spirit
of a layered approach. But with any non-MTP3 RK type
it is obvious that one has to dig in to the payload of
a message to reach the corresponding protocol part.
Not nice, but as long as there is no functional
problem, still I would think as doable.
> to change M3UA to make distributed SCCP work. The
> point is we should 
> not try to change M3UA behaviour to satisfy needs of
> M3UA user.
[TOLGA] For that I disagree. I said several times, it
is mandatory not to bring interoperability problems
while implementing necessary management functionality
to be able to handle non-MTP3 RKs. Such a managemnt
functionality would not change any M3UA behaviour at
all. 
> We should not assume how M3UA users will be
> distributed for example based 
> on SSN or not. It is responsibility of distributed
> SCCP to handle 
> possibilities of receiving SCMG messages for a given
> SSN on one or more 
[TOLGA] What you say is a possible way of doing things
and for most of the cases probably the better one. But
IMO there is no reason to put a restriction. 
> ASP's. This can be easily acheived in implementation
> specific way. 
> For example if we distribute single SSN across two
> ASP's then there is 
> possibility of receiving TCAP response on wrong ASP.
> But M3UA should not 
> be responsible for resolving this. This can be
> resolved in implementation 
> specific way.
[TOLGA] This won't create a problem. If you distribute
single SSN across two ASPs, this means tere is a
single SCCP entity on those ASPs. So, it doesn't
matter where the TCAP response is sent.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 12:34: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 MAA14974
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 12:34:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BHlUU01394
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 12:47:30 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHl7J01383;
	Sat, 11 Jan 2003 12:47:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHktJ01369
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 12:46:55 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14964
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 12:33:38 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:MccXhV7+M5PgiOdlIx3G/emTlJtYD/Nq@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BHauD04724;
	Sat, 11 Jan 2003 10:36:56 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BHauU09997;
	Sat, 11 Jan 2003 10:36:56 -0700
Date: Sat, 11 Jan 2003 10:36:56 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111103656.S8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111071126.P8782@openss7.org> <20030111165636.14173.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: <20030111165636.14173.qmail@web12804.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 08:56:36AM -0800
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, 11 Jan 2003 08:56:36)
> Brian,
> 
> [..snip...]
> > > [TOLGA] Can you give an example, how the method I
> > > propose affects the SCCP user at the ASP side?
> > 
> > Because the SCCP at the ASP is responsible for SCCP
> > management.  When you make the SG responsible for
> > any SCCP management you are affecting the SCCP at
> > the
> > ASP.
> [TOLGA] Can you give a specific example?

Example in previous note where SST is duplicated and
results in erroneous behaviour of conforming SCCP
users at ASP.

--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  Sat Jan 11 12:35: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 MAA14992
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 12:35:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BHmDw01450
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 12:48:13 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHm3J01435;
	Sat, 11 Jan 2003 12:48:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHljJ01408
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 12:47:45 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14972
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 12:34:28 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:IxROIXsHJFEpePl7HxVbqaMetsTo3DAa@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BHblD04737;
	Sat, 11 Jan 2003 10:37:47 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BHblD10023;
	Sat, 11 Jan 2003 10:37:47 -0700
Date: Sat, 11 Jan 2003 10:37:46 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111103746.T8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111071304.R8782@openss7.org> <20030111171345.16470.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: <20030111171345.16470.qmail@web12804.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 09:13:45AM -0800
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, 11 Jan 2003 09:13:45)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Sat, 11 Jan 2003
> > 05:39:00)
> > > Brian,
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > wrote:
> > > > Tolga,
> > > > 
> > > > Tolga Asveren wrote:                            
> >    
> > > >                                 (Sat, 11 Jan
> > 2003
> > > > 05:13:20)
> > > > > Javier,
> > > > > --- "Javier Pastor-Balbas (ECE)"
> > > > > <javier.pastor-balbas@ece.ericsson.se> wrote:
> > > > > > Hi guys, 
> > > > > > 
> > > > > > It was decided to remove SSN from the RK
> > some
> > > > time
> > > > > > ago. But Samuel is right saying that there
> > are
> > > > still
> > > > > > some "SSNs" throughout the text. I would
> > agree
> > > > to
> > > > > > remove them.
> > > > > [TOLGA] Removing SSN from examples is not a
> > > > problem,
> > > > > but IMO RK type flexibility should be kept.
> > > > 
> > > > I disagree.  M3UA RKs SHOULD be restricted to
> > MTP
> > > > Level 3
> > > > information only (i.e. information from the MTP
> > > > Routing
> > > > Label).
> > > [TOLGA] Why do you want to do this? Is there a
> > pert of
> > > the core M3UA protocol, which relies on a specific
> > RK
> > > type? IMO it is better to leave the people free
> > for
> > > this decision. As I pointed out several times, in
> > fact
> > > a solution, which does not bring interoperability
> > > problems is totally transparent to other nodes. I
> > > don't think it is a good idea to act as
> > inquisition.
> > > But I agree it makes sense to warn people about
> > > non-MTP3 RK types and explain briefly how those
> > might
> > > be handled within the boundaries of M3UA -just
> > from
> > > M3UA point of view-. 
> > 
> > Because the SS7 protocol relies on the fact that MTP
> > only examines the MTP Routing Label for routing.
> [TOLGA] IMO that MTP3 uses Routing Label for
> discrimination and SIO for distribution is the reason,
> why MTP3-type RKs are easily supported without a need
> of examining inside DATA messages. But why should we
> forbid to implement an extra management functionality 
> on SG to be able to use non-MTP3 RK types, if it is
> totally transparent to other nodes? Which test case in
> an interoperability event will fail for such a SG?

Because it is not totally transparent to other nodes.

--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  Sat Jan 11 12:36: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 MAA15020
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 12:36:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BHnGj01498
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 12:49:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHn6J01487;
	Sat, 11 Jan 2003 12:49:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHmkJ01471
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 12:48:46 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15006
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 12:35:28 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:DlMDlngEQqS3v5VOk5JOt8x/C8edHMBw@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BHclD04760;
	Sat, 11 Jan 2003 10:38:47 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BHclM10105;
	Sat, 11 Jan 2003 10:38:47 -0700
Date: Sat, 11 Jan 2003 10:38:47 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111103847.U8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111071030.O8782@openss7.org> <20030111165446.62756.qmail@web12802.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030111165446.62756.qmail@web12802.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 08:54:46AM -0800
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

Tolga,

Tolga Asveren wrote:                                                                 (Sat, 11 Jan 2003 08:54:46)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Sat, 11 Jan 2003
> > 05:24:42)
> > > Brian,
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > wrote:
> > > > TOLGA,
> > > > 
> > > > TOLGA ASVEREN wrote:                            
> >    
> > > >                                 (Fri, 10 Jan
> > 2003
> > > > 16:11:37)
> > > > > 
> > > > > Brian,
> > > > > 
> > > > > 
> > > > > 
> > > > > [...snip...]
> > > > > > [TOLGA] This is responsibility of SCCP.
> > M3UA-ASP
> > > > will just delºver the
> > > > > > messages to the corresponding entity, taking
> > > > care of traffic for the AS,
> > > > > > corresponding to RC in the message.
> > > > > 
> > > > > But the only reason for using SSN RK is
> > because
> > > > SCCP is partitioned
> > > > > over multiple ASPs.  How can ASP get SCCP
> > > > management messagess to
> > > > > the correct SCCP user without knowing where
> > they
> > > > appear?
> > > > > [TOLGA] It is not M3UA-ASPs responsibility to
> > > > toute messaegs to SCCP-Users.
> > > > > M3UA-ASP will deliver the message to the
> > correct
> > > > SCCP entity based on RC.
> > > > > The rest belongs to SCCP itself.
> > > > 
> > > > But which SCCP management messages are arriving
> > on
> > > > which RC?
> > > [TOLGA] Each AS will receive the necessary
> > management
> > > messages. Now you might ask, which ones are
> > > "necessary"? As I said, for this one has to look
> > to
> > > the relevant specification. There is no
> > > interoprability problem, let me explain why for
> > the
> > > SSN case just as an example. The goal is to
> > > interoperate with a M3UA compliant ASP which has a
> > > SCCP stack compliant with relevant
> > specification.So we
> > > have a regular M3UA and SCCP on ASP and we don't
> > want
> > > to touch them and to assume any special behavior
> > from
> > > them. Now, for each AS(which is based on DPC+SSN),
> > SG
> > > will send management messages sent for this SSN
> > and
> > > also management messages sent for the whole
> > > SCCP(requires duplication of SCCP message in this
> > > case). This IMO is not something to be described
> > in
> > > M3UA RFC. Did we put any extra requirement to M3UA
> > on
> > > ASP, or on any M3UA procedure or on SCCP on ASP
> > side?
> > > And the decision how to implement the managemnt
> > > functionality was based just on SCCP specification
> > > itself. 
> > 
> > Say there are 8 ASPs in the AS.  Take one SCCP
> > management
> > message: SST.  You send SST once to each ASP.  Each
> > ASP
> > with a compliant SCCP will return one response (say
> > SSP).
> > The distant end will receives 8 SSPs for each SST
> > sent.
> > This is a violation of SCCP specifications.  Your
> > implementation is broken.
> [TOLGA]This is the reason why you have the management
> functionality on SG. You get the responses and create
> the global view of the corresponding subsystem. Not
> all of the SSP is sent to SS7 network, only one. 

Not all the responses necessarily go through the same SG.

Still broken.

--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  Sat Jan 11 12:38: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 MAA15057
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 12:38:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BHpbb01576
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 12:51:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHp4J01555;
	Sat, 11 Jan 2003 12:51:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHo5J01527
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 12:50:05 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15034
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 12:36:47 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Wc6I36eE0YLDcoGaum1kPtYK0Wh6sWAt@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BHe6D04790;
	Sat, 11 Jan 2003 10:40:06 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BHe5q10150;
	Sat, 11 Jan 2003 10:40:05 -0700
Date: Sat, 11 Jan 2003 10:40:04 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111104004.V8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111071030.O8782@openss7.org> <20030111165446.62756.qmail@web12802.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030111165446.62756.qmail@web12802.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 08:54:46AM -0800
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

Tolga,

Tolga Asveren wrote:                                                                 (Sat, 11 Jan 2003 08:54:46)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Sat, 11 Jan 2003
> > 05:24:42)
> > > Brian,
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > wrote:
> > > > TOLGA,
> > > > 
> > > > TOLGA ASVEREN wrote:                            
> >    
> > > >                                 (Fri, 10 Jan
> > 2003
> > > > 16:11:37)
> > > > > 
> > > > > Brian,
> > > > > 
> > > > > 
> > > > > 
> > > > > [...snip...]
> > > > > > [TOLGA] This is responsibility of SCCP.
> > M3UA-ASP
> > > > will just delºver the
> > > > > > messages to the corresponding entity, taking
> > > > care of traffic for the AS,
> > > > > > corresponding to RC in the message.
> > > > > 
> > > > > But the only reason for using SSN RK is
> > because
> > > > SCCP is partitioned
> > > > > over multiple ASPs.  How can ASP get SCCP
> > > > management messagess to
> > > > > the correct SCCP user without knowing where
> > they
> > > > appear?
> > > > > [TOLGA] It is not M3UA-ASPs responsibility to
> > > > toute messaegs to SCCP-Users.
> > > > > M3UA-ASP will deliver the message to the
> > correct
> > > > SCCP entity based on RC.
> > > > > The rest belongs to SCCP itself.
> > > > 
> > > > But which SCCP management messages are arriving
> > on
> > > > which RC?
> > > [TOLGA] Each AS will receive the necessary
> > management
> > > messages. Now you might ask, which ones are
> > > "necessary"? As I said, for this one has to look
> > to
> > > the relevant specification. There is no
> > > interoprability problem, let me explain why for
> > the
> > > SSN case just as an example. The goal is to
> > > interoperate with a M3UA compliant ASP which has a
> > > SCCP stack compliant with relevant
> > specification.So we
> > > have a regular M3UA and SCCP on ASP and we don't
> > want
> > > to touch them and to assume any special behavior
> > from
> > > them. Now, for each AS(which is based on DPC+SSN),
> > SG
> > > will send management messages sent for this SSN
> > and
> > > also management messages sent for the whole
> > > SCCP(requires duplication of SCCP message in this
> > > case). This IMO is not something to be described
> > in
> > > M3UA RFC. Did we put any extra requirement to M3UA
> > on
> > > ASP, or on any M3UA procedure or on SCCP on ASP
> > side?
> > > And the decision how to implement the managemnt
> > > functionality was based just on SCCP specification
> > > itself. 
> > 
> > Say there are 8 ASPs in the AS.  Take one SCCP
> > management
> > message: SST.  You send SST once to each ASP.  Each
> > ASP
> > with a compliant SCCP will return one response (say
> > SSP).
> > The distant end will receives 8 SSPs for each SST
> > sent.
> > This is a violation of SCCP specifications.  Your
> > implementation is broken.
> [TOLGA]This is the reason why you have the management
> functionality on SG. You get the responses and create
> the global view of the corresponding subsystem. Not
> all of the SSP is sent to SS7 network, only one. 

In fact, the responses don't necessarily go through
the SG at all.  SCCP can use another network appearance
which is directly connected to the SS7 network to send
the message back.

--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  Sat Jan 11 12:39: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 MAA15085
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 12:39:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BHqF601614
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 12:52:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHq5J01605;
	Sat, 11 Jan 2003 12:52:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHpPJ01571
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 12:51:25 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15046
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 12:38:08 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:zonmr8Rp+egULYEV6zLaPN3aXq62/39E@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BHfRD04800;
	Sat, 11 Jan 2003 10:41:27 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BHfQj10204;
	Sat, 11 Jan 2003 10:41:26 -0700
Date: Sat, 11 Jan 2003 10:41:26 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ngoel@cerberus.intellinet-tech.com
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111104126.W8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ngoel@cerberus.intellinet-tech.com,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111071030.O8782@openss7.org> <Pine.LNX.4.44.0301111147470.23581-100000@cerberus.intellinet-tech.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.LNX.4.44.0301111147470.23581-100000@cerberus.intellinet-tech.com>; from ngoel@cerberus.intellinet-tech.com on Sat, Jan 11, 2003 at 12:05:22PM -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>

ngoel,

ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 12:05:22)
> Brian/Tolga,
>  Reading your discussion I have few thoughts/comments -
> Are we not trying to violate principles of layered protocol here by trying 
> to change M3UA to make distributed SCCP work. The point is we should 
> not try to change M3UA behaviour to satisfy needs of M3UA user.
> We should not assume how M3UA users will be distributed for example based 
> on SSN or not. It is responsibility of distributed SCCP to handle 
> possibilities of receiving SCMG messages for a given SSN on one or more 
> ASP's. This can be easily acheived in implementation specific way. 
> For example if we distribute single SSN across two ASP's then there is 
> possibility of receiving TCAP response on wrong ASP. But M3UA should not 
> be responsible for resolving this. This can be resolved in implementation 
> specific way.
> -Narender 

Or in a standard way using SUA.

--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  Sat Jan 11 12:40: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 MAA15107
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 12:40:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BHrCV01667
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 12:53:12 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHr3J01656;
	Sat, 11 Jan 2003 12:53:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHqRJ01631
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 12:52:27 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15080
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 12:39:09 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:k8yAfG0auDEp852yRWEFenQv2lyBAzSs@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BHgSD04817;
	Sat, 11 Jan 2003 10:42:28 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BHgS410248;
	Sat, 11 Jan 2003 10:42:28 -0700
Date: Sat, 11 Jan 2003 10:42:28 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111104228.X8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <Pine.LNX.4.44.0301111147470.23581-100000@cerberus.intellinet-tech.com> <20030111172229.83254.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: <20030111172229.83254.qmail@web12808.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 09:22:29AM -0800
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, 11 Jan 2003 09:22:29)
[snip]
> [TOLGA] This won't create a problem. If you distribute
> single SSN across two ASPs, this means tere is a
> single SCCP entity on those ASPs. So, it doesn't
> matter where the TCAP response is sent.

Huh?  Is your M3UA SG handling transactions state now too?

--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  Sat Jan 11 12:43:57 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 MAA15160
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 12:43:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BHuiO01799
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 12:56:44 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHu4J01760;
	Sat, 11 Jan 2003 12:56:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHteJ01738
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 12:55:40 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15131
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 12:42:22 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:UZYhKMlDn5ZIYWiN5/FdBTiav1ZqPoMD@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BHjfD04852;
	Sat, 11 Jan 2003 10:45:41 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BHjfQ10296;
	Sat, 11 Jan 2003 10:45:41 -0700
Date: Sat, 11 Jan 2003 10:45:41 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111104541.Y8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111071030.O8782@openss7.org> <20030111165446.62756.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: <20030111165446.62756.qmail@web12802.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 08:54:46AM -0800
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, 11 Jan 2003 08:54:46)
> > 
> > Say there are 8 ASPs in the AS.  Take one SCCP management message: SST.
> > You send SST once to each ASP.  Each ASP with a compliant SCCP will return
> > one response (say SSP).  The distant end will receives 8 SSPs for each SST
> > sent.  This is a violation of SCCP specifications.  Your implementation is
> > broken.
> [TOLGA]This is the reason why you have the management
> functionality on SG. You get the responses and create
> the global view of the corresponding subsystem. Not
> all of the SSP is sent to SS7 network, only one. 

M3UA supports multiple SGs.  How is one SG to know that
the other has sent SSP?

--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  Sat Jan 11 12:48: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 MAA15239
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 12:48:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BI0ri01959
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 13:00:53 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BI08J01924;
	Sat, 11 Jan 2003 13:00:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BHxEJ01867
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 12:59:14 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15189
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 12:45:56 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:/QMwXaKrhHLGoeatJgVEZk+RkKK21wug@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BHnFD04892;
	Sat, 11 Jan 2003 10:49:15 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BHnFt10355;
	Sat, 11 Jan 2003 10:49:15 -0700
Date: Sat, 11 Jan 2003 10:49:15 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111104915.Z8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111071030.O8782@openss7.org> <20030111165446.62756.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: <20030111165446.62756.qmail@web12802.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 08:54:46AM -0800
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, 11 Jan 2003 08:54:46)
> > 
> > Say there are 8 ASPs in the AS.  Take one SCCP management message: SST.
> > You send SST once to each ASP.  Each ASP with a compliant SCCP will return
> > one response (say SSP).  The distant end will receives 8 SSPs for each SST
> > sent.  This is a violation of SCCP specifications.  Your implementation is
> > broken.
> [TOLGA]This is the reason why you have the management
> functionality on SG. You get the responses and create
> the global view of the corresponding subsystem. Not
> all of the SSP is sent to SS7 network, only one. 

Now tell me how SOR/SOG is going to work.  Particularly when it
is for a subsystem with mated point codes both served by multiple
SG acting as STP.  They are signalling each other.  There are 8 ASPs
per AS on both point codes.  The algorithm can have no races and must
handle ASP failure and AS deactivation in the middle of the procedure
(or it will violate SCCP specifications).

--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  Sat Jan 11 13:11: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 NAA15506
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 13:11:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BIOOO03248
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 13:24:24 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BINaJ03226;
	Sat, 11 Jan 2003 13:23:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BIMPJ03196
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 13:22:25 -0500
Received: from cerberus.intellinet-tech.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15473
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 13:09:07 -0500 (EST)
From: ngoel@cerberus.intellinet-tech.com
Received: from localhost (ngoel@localhost)
	by cerberus.intellinet-tech.com (8.11.6/8.11.6) with ESMTP id h0BI8le27595;
	Sat, 11 Jan 2003 13:08:47 -0500
Date: Sat, 11 Jan 2003 13:08:47 -0500 (EST)
To: Tolga Asveren <tolga_asveren@yahoo.com>
cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
In-Reply-To: <20030111172229.83254.qmail@web12808.mail.yahoo.com>
Message-ID: <Pine.LNX.4.44.0301111240510.26229-100000@cerberus.intellinet-tech.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>

On Sat, 11 Jan 2003, Tolga Asveren wrote:
Tolga,
 My response is inline.
> Narender,
> --- ngoel@cerberus.intellinet-tech.com wrote:
> > Brian/Tolga,
> >  Reading your discussion I have few
> > thoughts/comments -
> > Are we not trying to violate principles of layered
> > protocol here by trying
> [TOLGA]I also would think this is against the spirit
> of a layered approach. But with any non-MTP3 RK type
> it is obvious that one has to dig in to the payload of
> a message to reach the corresponding protocol part.
> Not nice, but as long as there is no functional
> problem, still I would think as doable.
[Naren] There is a basic problem of taking a piece meal approach.
 We do not know what a M3UA user can do and we cannot limit the M3UA-user 
to a given set of behaviours. It might be possible to satisfy needs of 
SCMG but what about Connection Oriented SCCP. SCOC is not state less as is 
SCLC and there and many more issues involved with it, like sharing 
connection cotext across ASPs and handle connection inactivity,
handling error messages. But all these can be resolved in implementation
specific ways and better left to the implementation. 
> > to change M3UA to make distributed SCCP work. The
> > point is we should 
> > not try to change M3UA behaviour to satisfy needs of
> > M3UA user.
> [TOLGA] For that I disagree. I said several times, it
> is mandatory not to bring interoperability problems
> while implementing necessary management functionality
> to be able to handle non-MTP3 RKs. Such a managemnt
> functionality would not change any M3UA behaviour at
> all. 
> > We should not assume how M3UA users will be
> > distributed for example based 
> > on SSN or not. It is responsibility of distributed
> > SCCP to handle 
> > possibilities of receiving SCMG messages for a given
> > SSN on one or more 
> [TOLGA] What you say is a possible way of doing things
> and for most of the cases probably the better one. But
> IMO there is no reason to put a restriction. 
> > ASP's. This can be easily acheived in implementation
> > specific way. 
> > For example if we distribute single SSN across two
> > ASP's then there is 
> > possibility of receiving TCAP response on wrong ASP.
> > But M3UA should not 
> > be responsible for resolving this. This can be
> > resolved in implementation 
> > specific way.
> [TOLGA] This won't create a problem. If you distribute
> single SSN across two ASPs, this means tere is a
> single SCCP entity on those ASPs. So, it doesn't
> matter where the TCAP response is sent.
[Naren] Unfortunately TCAP is not stateless protocol. It is
important to share TCAP context to take advantage of 
distrbuted design of M3UA/sigtran stack. Even though M3UA
 spec is not expected to provide solution to this problem.
-Narender
> 
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.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  Sat Jan 11 13: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 NAA15793
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 13:30:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BIhXI04404
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 13:43:33 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BIh6J04393;
	Sat, 11 Jan 2003 13:43:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BIgHJ04377
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 13:42:17 -0500
Received: from cerberus.intellinet-tech.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15777
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 13:29:00 -0500 (EST)
From: ngoel@cerberus.intellinet-tech.com
Received: from localhost (ngoel@localhost)
	by cerberus.intellinet-tech.com (8.11.6/8.11.6) with ESMTP id h0BISWN28062;
	Sat, 11 Jan 2003 13:28:32 -0500
Date: Sat, 11 Jan 2003 13:28:32 -0500 (EST)
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Tolga Asveren <tolga_asveren@yahoo.com>, <sigtran@ietf.org>
Subject: Re: [Sigtran] m3ua- IG
In-Reply-To: <20030111104126.W8782@openss7.org>
Message-ID: <Pine.LNX.4.44.0301111319150.26229-100000@cerberus.intellinet-tech.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>

On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
Brian,
 SUA spec is does bot describe clearly how to handle SCOC and may not be 
better solution overall.
I believe it may be better if we general set of guidelines for M3UA users 
without assuming specific M3UA user like SCCP/ISUP/TUP etc. The main 
issues with distributed sigtran user are -
1. Sharing to user state/context across distributed ASPs.
2. Handling of broadcast messages.
Any any other generic behaviour that everyone agrees and try to present a 
common solution to the user and not link the solution to a specific 
protocol.
-Narender

  
 > ngoel,
> 
> ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 12:05:22)
> > Brian/Tolga,
> >  Reading your discussion I have few thoughts/comments -
> > Are we not trying to violate principles of layered protocol here by trying 
> > to change M3UA to make distributed SCCP work. The point is we should 
> > not try to change M3UA behaviour to satisfy needs of M3UA user.
> > We should not assume how M3UA users will be distributed for example based 
> > on SSN or not. It is responsibility of distributed SCCP to handle 
> > possibilities of receiving SCMG messages for a given SSN on one or more 
> > ASP's. This can be easily acheived in implementation specific way. 
> > For example if we distribute single SSN across two ASP's then there is 
> > possibility of receiving TCAP response on wrong ASP. But M3UA should not 
> > be responsible for resolving this. This can be resolved in implementation 
> > specific way.
> > -Narender 
> 
> Or in a standard way using SUA.
> 
> --brian
> 
> 

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



From mailnull@www1.ietf.org  Sat Jan 11 14:02: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 OAA16206
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 14:02:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BJFbG05655
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 14:15:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BJF9J05639;
	Sat, 11 Jan 2003 14:15:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BJE6J05614
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 14:14:06 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16163
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 14:00:48 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:kmacmoo/zzD6/5VA4jGyoceu9VOQ+sqc@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BJ45D06165;
	Sat, 11 Jan 2003 12:04:05 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BJ45O12258;
	Sat, 11 Jan 2003 12:04:05 -0700
Date: Sat, 11 Jan 2003 12:04:05 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ngoel@cerberus.intellinet-tech.com
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111120405.A8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ngoel@cerberus.intellinet-tech.com,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111104126.W8782@openss7.org> <Pine.LNX.4.44.0301111319150.26229-100000@cerberus.intellinet-tech.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.LNX.4.44.0301111319150.26229-100000@cerberus.intellinet-tech.com>; from ngoel@cerberus.intellinet-tech.com on Sat, Jan 11, 2003 at 01:28:32PM -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>

ngoel,

SUA clearly describes handling of connection oriented messages.  SCOC is
a SCCP protocol state machine that resides below SUA in a standard SCCP.
The SCOC for SUA is precisely the SCOC of Q.714, ANSI T1.112.4, etc.
It does not need any description in the SUA standard because it is adequately
described in the SCCP standards.  SUA is designed to export the SCCP/SCCP-User
interface, not to replace SCCP state machines.

--brian

ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 13:28:32)
> On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> Brian,
>  SUA spec is does bot describe clearly how to handle SCOC and may not be 
> better solution overall.
> I believe it may be better if we general set of guidelines for M3UA users 
> without assuming specific M3UA user like SCCP/ISUP/TUP etc. The main 
> issues with distributed sigtran user are -
> 1. Sharing to user state/context across distributed ASPs.
> 2. Handling of broadcast messages.
> Any any other generic behaviour that everyone agrees and try to present a 
> common solution to the user and not link the solution to a specific 
> protocol.
> -Narender
> 
>   
>  > ngoel,
> > 
> > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 12:05:22)
> > > Brian/Tolga,
> > >  Reading your discussion I have few thoughts/comments -
> > > Are we not trying to violate principles of layered protocol here by trying 
> > > to change M3UA to make distributed SCCP work. The point is we should 
> > > not try to change M3UA behaviour to satisfy needs of M3UA user.
> > > We should not assume how M3UA users will be distributed for example based 
> > > on SSN or not. It is responsibility of distributed SCCP to handle 
> > > possibilities of receiving SCMG messages for a given SSN on one or more 
> > > ASP's. This can be easily acheived in implementation specific way. 
> > > For example if we distribute single SSN across two ASP's then there is 
> > > possibility of receiving TCAP response on wrong ASP. But M3UA should not 
> > > be responsible for resolving this. This can be resolved in implementation 
> > > specific way.
> > > -Narender 
> > 
> > Or in a standard way using SUA.
> > 
> > --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  Sat Jan 11 14:32: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 OAA16645
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 14:32:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BJjeQ06993
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 14:45:40 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BJitJ06969;
	Sat, 11 Jan 2003 14:44:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BJh7J06870
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 14:43:07 -0500
Received: from cerberus.intellinet-tech.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16539
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 14:29:48 -0500 (EST)
From: ngoel@cerberus.intellinet-tech.com
Received: from localhost (ngoel@localhost)
	by cerberus.intellinet-tech.com (8.11.6/8.11.6) with ESMTP id h0BJTL528817;
	Sat, 11 Jan 2003 14:29:21 -0500
Date: Sat, 11 Jan 2003 14:29:21 -0500 (EST)
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Tolga Asveren <tolga_asveren@yahoo.com>, <sigtran@ietf.org>
Subject: Re: [Sigtran] m3ua- IG
In-Reply-To: <20030111120405.A8782@openss7.org>
Message-ID: <Pine.LNX.4.44.0301111412330.28634-100000@cerberus.intellinet-tech.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>

On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
Brian,
 Some of the problems with SCOC and SUA are -
1. Routing context is mandatory in SUA messages. SUA has DPC/SSN routing 
keys. SCOC DT1 message does not contain SCCP addressing information. It is 
not trivial to find the RC for a incoming DT1 at the SG. Do we mantain 
connection context at SG and no connection context at ASP level? Can a SUA 
user allocate or delete connection context? Or these functions be RPC 
calls which are implemnentation dependent? Does any SCCP Connection 
Oriented functionality is required on ASP  side in addition to what is 
defined in SUA draft. 
2. Problem similar to shring connection state. If one ASP sends a Connect 
Request what is the gurantee the same will receive Connection Confirm. 
This is much easier to handle with SCCP/M3UA. I think there are much more 
implementation dependent issues with SUA.
-Narender

 > ngoel,
> 
> SUA clearly describes handling of connection oriented messages.  SCOC is
> a SCCP protocol state machine that resides below SUA in a standard SCCP.
> The SCOC for SUA is precisely the SCOC of Q.714, ANSI T1.112.4, etc.
> It does not need any description in the SUA standard because it is adequately
> described in the SCCP standards.  SUA is designed to export the SCCP/SCCP-User
> interface, not to replace SCCP state machines.
> 
> --brian
> 
> ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 13:28:32)
> > On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> > Brian,
> >  SUA spec is does bot describe clearly how to handle SCOC and may not be 
> > better solution overall.
> > I believe it may be better if we general set of guidelines for M3UA users 
> > without assuming specific M3UA user like SCCP/ISUP/TUP etc. The main 
> > issues with distributed sigtran user are -
> > 1. Sharing to user state/context across distributed ASPs.
> > 2. Handling of broadcast messages.
> > Any any other generic behaviour that everyone agrees and try to present a 
> > common solution to the user and not link the solution to a specific 
> > protocol.
> > -Narender
> > 
> >   
> >  > ngoel,
> > > 
> > > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 12:05:22)
> > > > Brian/Tolga,
> > > >  Reading your discussion I have few thoughts/comments -
> > > > Are we not trying to violate principles of layered protocol here by trying 
> > > > to change M3UA to make distributed SCCP work. The point is we should 
> > > > not try to change M3UA behaviour to satisfy needs of M3UA user.
> > > > We should not assume how M3UA users will be distributed for example based 
> > > > on SSN or not. It is responsibility of distributed SCCP to handle 
> > > > possibilities of receiving SCMG messages for a given SSN on one or more 
> > > > ASP's. This can be easily acheived in implementation specific way. 
> > > > For example if we distribute single SSN across two ASP's then there is 
> > > > possibility of receiving TCAP response on wrong ASP. But M3UA should not 
> > > > be responsible for resolving this. This can be resolved in implementation 
> > > > specific way.
> > > > -Narender 
> > > 
> > > Or in a standard way using SUA.
> > > 
> > > --brian
> > > 
> > > 
> 
> 

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



From mailnull@www1.ietf.org  Sat Jan 11 14: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 OAA16979
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 14:45:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BJvvV07731
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 14:57:57 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BJvEJ07702;
	Sat, 11 Jan 2003 14:57:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BJubJ07676
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 14:56:37 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16953
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 14:43:17 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:6dJNFTDTDdmxez8hi1+rnB3W3oHMQKu2@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BJkZD06734;
	Sat, 11 Jan 2003 12:46:35 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BJkZL13183;
	Sat, 11 Jan 2003 12:46:35 -0700
Date: Sat, 11 Jan 2003 12:46:35 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ngoel@cerberus.intellinet-tech.com
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111124635.B8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ngoel@cerberus.intellinet-tech.com,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111120405.A8782@openss7.org> <Pine.LNX.4.44.0301111412330.28634-100000@cerberus.intellinet-tech.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.LNX.4.44.0301111412330.28634-100000@cerberus.intellinet-tech.com>; from ngoel@cerberus.intellinet-tech.com on Sat, Jan 11, 2003 at 02:29:21PM -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>

ngoel,

ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 14:29:21)
> On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> Brian,
>  Some of the problems with SCOC and SUA are -
> 1. Routing context is mandatory in SUA messages.

That is not a problem.

> SUA has DPC/SSN routing keys.

SUA has AMF (Address Mapping Function).  SUA has can route on GT and
can even route on SLR/DLR.

> SCOC DT1 message does not contain SCCP addressing information.

DT1 has SLR/DLR.

> It is not trivial to find the RC for a incoming DT1 at the SG.

It is trivial: lookup on DLR.

> Do we mantain connection context at SG and no connection context at ASP
> level?

Connection context is referenced both at SG and ASP by DPC/DLR.

> Can a SUA user allocate or delete connection context?

Allocated with CORE/COAK, deallocated with RELRE/RELCO.

> Or these functions be RPC calls which are implemnentation dependent?

Not implementation dependent.  Completely within the context of SCCP.

> Does any SCCP Connection Oriented functionality is required on ASP  side in
> addition to what is defined in SUA draft. 

No.

> 2. Problem similar to shring connection state. If one ASP sends a Connect 
> Request what is the gurantee the same will receive Connection Confirm. 

Base on the local reference in the CR.  SG sends CC to correct ASP.

> This is much easier to handle with SCCP/M3UA.

Very wrong.

> I think there are much more implementation dependent issues with SUA.

I think you just don't have a good understanding the SUA standard yet.

There are no issues other than DRN Label with multiple SGs under failure.
draft-bidulock-sigtran-regext-01.txt submitted to the I-D editor several days
ago which provides better solution for multiple SG case than DRN Labels.  You
can pick up a copy at

	http://www.openss7.org/sigtran01.html

until it appears on the I-D server.

But I think you should take some time to read carefully through the SUA spec,
ask some questions, and understand it well before making such sweeping
statements.

--brian

> -Narender
> 
>  > ngoel,
> > 
> > SUA clearly describes handling of connection oriented messages.  SCOC is
> > a SCCP protocol state machine that resides below SUA in a standard SCCP.
> > The SCOC for SUA is precisely the SCOC of Q.714, ANSI T1.112.4, etc.
> > It does not need any description in the SUA standard because it is adequately
> > described in the SCCP standards.  SUA is designed to export the SCCP/SCCP-User
> > interface, not to replace SCCP state machines.
> > 
> > --brian
> > 
> > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 13:28:32)
> > > On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> > > Brian,
> > >  SUA spec is does bot describe clearly how to handle SCOC and may not be 
> > > better solution overall.
> > > I believe it may be better if we general set of guidelines for M3UA users 
> > > without assuming specific M3UA user like SCCP/ISUP/TUP etc. The main 
> > > issues with distributed sigtran user are -
> > > 1. Sharing to user state/context across distributed ASPs.
> > > 2. Handling of broadcast messages.
> > > Any any other generic behaviour that everyone agrees and try to present a 
> > > common solution to the user and not link the solution to a specific 
> > > protocol.
> > > -Narender
> > > 
> > >   
> > >  > ngoel,
> > > > 
> > > > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 12:05:22)
> > > > > Brian/Tolga,
> > > > >  Reading your discussion I have few thoughts/comments -
> > > > > Are we not trying to violate principles of layered protocol here by trying 
> > > > > to change M3UA to make distributed SCCP work. The point is we should 
> > > > > not try to change M3UA behaviour to satisfy needs of M3UA user.
> > > > > We should not assume how M3UA users will be distributed for example based 
> > > > > on SSN or not. It is responsibility of distributed SCCP to handle 
> > > > > possibilities of receiving SCMG messages for a given SSN on one or more 
> > > > > ASP's. This can be easily acheived in implementation specific way. 
> > > > > For example if we distribute single SSN across two ASP's then there is 
> > > > > possibility of receiving TCAP response on wrong ASP. But M3UA should not 
> > > > > be responsible for resolving this. This can be resolved in implementation 
> > > > > specific way.
> > > > > -Narender 
> > > > 
> > > > Or in a standard way using SUA.
> > > > 
> > > > --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  Sat Jan 11 14:48:57 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 OAA17020
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 14:48:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BK1j107873
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 15:01:45 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BK14J07853;
	Sat, 11 Jan 2003 15:01:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BK0iJ07825
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 15:00:44 -0500
Received: from cerberus.intellinet-tech.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17003
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 14:47:25 -0500 (EST)
From: ngoel@cerberus.intellinet-tech.com
Received: from localhost (ngoel@localhost)
	by cerberus.intellinet-tech.com (8.11.6/8.11.6) with ESMTP id h0BJkwc29042;
	Sat, 11 Jan 2003 14:46:58 -0500
Date: Sat, 11 Jan 2003 14:46:58 -0500 (EST)
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Tolga Asveren <tolga_asveren@yahoo.com>, <sigtran@ietf.org>
Subject: Re: [Sigtran] m3ua- IG
In-Reply-To: <20030111120405.A8782@openss7.org>
Message-ID: <Pine.LNX.4.44.0301111444380.28970-100000@cerberus.intellinet-tech.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>

On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
Brian,
> ngoel,
> 
> SUA clearly describes handling of connection oriented messages.  SCOC is
> a SCCP protocol state machine that resides below SUA in a standard SCCP.

[Naren] Are you suggesting both SUA and SCCP should be present on ASP 
side?

> The SCOC for SUA is precisely the SCOC of Q.714, ANSI T1.112.4, etc.
> It does not need any description in the SUA standard because it is adequately
> described in the SCCP standards.  SUA is designed to export the SCCP/SCCP-User
> interface, not to replace SCCP state machines.
> 
> --brian
>
 
> ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 13:28:32)
> > On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> > Brian,
> >  SUA spec is does bot describe clearly how to handle SCOC and may not be 
> > better solution overall.
> > I believe it may be better if we general set of guidelines for M3UA users 
> > without assuming specific M3UA user like SCCP/ISUP/TUP etc. The main 
> > issues with distributed sigtran user are -
> > 1. Sharing to user state/context across distributed ASPs.
> > 2. Handling of broadcast messages.
> > Any any other generic behaviour that everyone agrees and try to present a 
> > common solution to the user and not link the solution to a specific 
> > protocol.
> > -Narender
> > 
> >   
> >  > ngoel,
> > > 
> > > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 12:05:22)
> > > > Brian/Tolga,
> > > >  Reading your discussion I have few thoughts/comments -
> > > > Are we not trying to violate principles of layered protocol here by trying 
> > > > to change M3UA to make distributed SCCP work. The point is we should 
> > > > not try to change M3UA behaviour to satisfy needs of M3UA user.
> > > > We should not assume how M3UA users will be distributed for example based 
> > > > on SSN or not. It is responsibility of distributed SCCP to handle 
> > > > possibilities of receiving SCMG messages for a given SSN on one or more 
> > > > ASP's. This can be easily acheived in implementation specific way. 
> > > > For example if we distribute single SSN across two ASP's then there is 
> > > > possibility of receiving TCAP response on wrong ASP. But M3UA should not 
> > > > be responsible for resolving this. This can be resolved in implementation 
> > > > specific way.
> > > > -Narender 
> > > 
> > > Or in a standard way using SUA.
> > > 
> > > --brian
> > > 
> > > 
> 
> 

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



From mailnull@www1.ietf.org  Sat Jan 11 14:55: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 OAA17134
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 14:55:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BK8l708685
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 15:08:47 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BK87J08666;
	Sat, 11 Jan 2003 15:08:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BK7eJ08650
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 15:07:40 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17082
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 14:54:21 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:T6XN1KW47PffUQScQq3BMX0W4n3wtcB6@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BJvcD06863;
	Sat, 11 Jan 2003 12:57:38 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BJvch13522;
	Sat, 11 Jan 2003 12:57:38 -0700
Date: Sat, 11 Jan 2003 12:57:38 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ngoel@cerberus.intellinet-tech.com
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111125738.C8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ngoel@cerberus.intellinet-tech.com,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111120405.A8782@openss7.org> <Pine.LNX.4.44.0301111444380.28970-100000@cerberus.intellinet-tech.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.LNX.4.44.0301111444380.28970-100000@cerberus.intellinet-tech.com>; from ngoel@cerberus.intellinet-tech.com on Sat, Jan 11, 2003 at 02:46:58PM -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>

ngoel,

ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 14:46:58)
> On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> Brian,
> > ngoel,
> > 
> > SUA clearly describes handling of connection oriented messages.  SCOC is
> > a SCCP protocol state machine that resides below SUA in a standard SCCP.
> 
> [Naren] Are you suggesting both SUA and SCCP should be present on ASP 
> side?

SCCP only needs to be present on SG side.

--brian

> 
> > The SCOC for SUA is precisely the SCOC of Q.714, ANSI T1.112.4, etc.
> > It does not need any description in the SUA standard because it is adequately
> > described in the SCCP standards.  SUA is designed to export the SCCP/SCCP-User
> > interface, not to replace SCCP state machines.
> > 
> > --brian
> >
>  
> > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 13:28:32)
> > > On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> > > Brian,
> > >  SUA spec is does bot describe clearly how to handle SCOC and may not be 
> > > better solution overall.
> > > I believe it may be better if we general set of guidelines for M3UA users 
> > > without assuming specific M3UA user like SCCP/ISUP/TUP etc. The main 
> > > issues with distributed sigtran user are -
> > > 1. Sharing to user state/context across distributed ASPs.
> > > 2. Handling of broadcast messages.
> > > Any any other generic behaviour that everyone agrees and try to present a 
> > > common solution to the user and not link the solution to a specific 
> > > protocol.
> > > -Narender
> > > 
> > >   
> > >  > ngoel,
> > > > 
> > > > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 12:05:22)
> > > > > Brian/Tolga,
> > > > >  Reading your discussion I have few thoughts/comments -
> > > > > Are we not trying to violate principles of layered protocol here by trying 
> > > > > to change M3UA to make distributed SCCP work. The point is we should 
> > > > > not try to change M3UA behaviour to satisfy needs of M3UA user.
> > > > > We should not assume how M3UA users will be distributed for example based 
> > > > > on SSN or not. It is responsibility of distributed SCCP to handle 
> > > > > possibilities of receiving SCMG messages for a given SSN on one or more 
> > > > > ASP's. This can be easily acheived in implementation specific way. 
> > > > > For example if we distribute single SSN across two ASP's then there is 
> > > > > possibility of receiving TCAP response on wrong ASP. But M3UA should not 
> > > > > be responsible for resolving this. This can be resolved in implementation 
> > > > > specific way.
> > > > > -Narender 
> > > > 
> > > > Or in a standard way using SUA.
> > > > 
> > > > --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  Sat Jan 11 15:02: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 PAA17239
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 15:02:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BKEsx08885
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 15:14:54 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BKE6J08868;
	Sat, 11 Jan 2003 15:14:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BKDqJ08854
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 15:13:52 -0500
Received: from web12808.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17219
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 15:00:33 -0500 (EST)
Message-ID: <20030111200350.4524.qmail@web12808.mail.yahoo.com>
Received: from [62.29.86.74] by web12808.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 12:03:50 PST
Date: Sat, 11 Jan 2003 12:03:50 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <20030111103847.U8782@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]This is the reason why you have the
> management
> > functionality on SG. You get the responses and
> create
> > the global view of the corresponding subsystem.
> Not
> > all of the SSP is sent to SS7 network, only one. 
> 
> Not all the responses necessarily go through the
> same SG.
> 
> Still broken.
[TOLGA] We were already here I think. The solution is
simple, do not use multiple SG configuration, which
anyhow is a strange mode of operation (multiple MTP3
logic for the same PC, working independently)


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 15:15: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 PAA17559
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 15:15:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BKSi709274
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 15:28:44 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BKSAJ09261;
	Sat, 11 Jan 2003 15:28:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BKRgJ09240
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 15:27:42 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17534
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 15:14:22 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:+7S3VYplfq6CDVuvOKahZAbLXjC5HqRN@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BKHeD07209;
	Sat, 11 Jan 2003 13:17:40 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BKHdh14407;
	Sat, 11 Jan 2003 13:17:39 -0700
Date: Sat, 11 Jan 2003 13:17:39 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111131739.D8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111103847.U8782@openss7.org> <20030111200350.4524.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: <20030111200350.4524.qmail@web12808.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 12:03:50PM -0800
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, 11 Jan 2003 12:03:50)
> Brian,
> [...snip....]
> > > [TOLGA]This is the reason why you have the
> > management
> > > functionality on SG. You get the responses and
> > create
> > > the global view of the corresponding subsystem.
> > Not
> > > all of the SSP is sent to SS7 network, only one. 
> > 
> > Not all the responses necessarily go through the
> > same SG.
> > 
> > Still broken.
> [TOLGA] We were already here I think. The solution is
> simple, do not use multiple SG configuration, which
> anyhow is a strange mode of operation (multiple MTP3
> logic for the same PC, working independently)

M3UA can support MTP3 routing keys on multiple SG.

Besides, its still broken.  How do you handle subsystem
congestion?

Also, you have race condition with your correlation of
SSP messages.  One ASP can issue SSA before the SSP
has arrived from other ASP.  Like so:

ASP1   SSA ----- SSP                            SGP1
ASP2                        SSA ----- SSP       SGP2
ASP3              SSA ----- SSP                 SGP3
ASP4         SSA ----- SSP                      SGP4
ASP5                             SSA ----- SSP  SGP5
ASP6                  SSA ----- SSP             SGP6
ASP7            SSA ----- SSP                   SGP7
ASP8                         SSA ----- SSP      SGP8

The SCCP thinks it has sent SSP followed by SSA.  The
SG receives:

  SSP, SSP, SSP, SSA, SSP, SSA, SSA, SSP, SSP, SSP,
  SSA, SSA, SSP, SSA, SSA, SSA

Some are responsive to SST, some are broadcast.  What
will the SG send?  Also note that SCCP management
messages are not send on the same SLS, so some of these
can get reversed in between ASP and SGP.

Your algorithm falls flat on its face because it
cannot tell the different between respones to SST and
broadcast messages (it is not contained in the message).

--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  Sat Jan 11 15:16: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 PAA17580
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 15:16:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BKTDP09307
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 15:29:13 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BKT3J09300;
	Sat, 11 Jan 2003 15:29:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BKSoJ09286
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 15:28:50 -0500
Received: from web12808.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17556
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 15:15:30 -0500 (EST)
Message-ID: <20030111201848.6715.qmail@web12808.mail.yahoo.com>
Received: from [62.29.86.74] by web12808.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 12:18:48 PST
Date: Sat, 11 Jan 2003 12:18:48 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <20030111104228.X8782@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:                                
>                                 (Sat, 11 Jan 2003
> 09:22:29)
> [snip]
> > [TOLGA] This won't create a problem. If you
> distribute
> > single SSN across two ASPs, this means tere is a
> > single SCCP entity on those ASPs. So, it doesn't
> > matter where the TCAP response is sent.
> 
> Huh?  Is your M3UA SG handling transactions state
> now too?
[TOLGA] Why do you think this? If ASPs are working in
loadshare mode for an AS, their corresponding user
parts are synchronized.
And let's say SG keeps also some TCAP info. Why would
M3UA care about this? The point I am trying to make
from the very beginning of this discussion is, please
don't try to put restrictions on SG itself, leave it
free as long as it is compliant with M3UA. But you
just focus on the specific SSN RK case and try to
finish a design for a implementation dependent
management functionality which can be used to be able
to support SSN based RKs on SG.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 15: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 PAA17688
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 15:22:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BKZlc09527
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 15:35:47 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BKZ7J09507;
	Sat, 11 Jan 2003 15:35:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BKYvJ09486
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 15:34:57 -0500
Received: from web12804.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17670
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 15:21:37 -0500 (EST)
Message-ID: <20030111202455.40513.qmail@web12804.mail.yahoo.com>
Received: from [62.29.86.74] by web12804.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 12:24:55 PST
Date: Sat, 11 Jan 2003 12:24:55 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <Pine.LNX.4.44.0301111240510.26229-100000@cerberus.intellinet-tech.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>

Narender,
--- ngoel@cerberus.intellinet-tech.com wrote:
> On Sat, 11 Jan 2003, Tolga Asveren wrote:
> Tolga,
>  My response is inline.
> > Narender,
> > --- ngoel@cerberus.intellinet-tech.com wrote:
> > > Brian/Tolga,
> > >  Reading your discussion I have few
> > > thoughts/comments -
> > > Are we not trying to violate principles of
> layered
> > > protocol here by trying
> > [TOLGA]I also would think this is against the
> spirit
> > of a layered approach. But with any non-MTP3 RK
> type
> > it is obvious that one has to dig in to the
> payload of
> > a message to reach the corresponding protocol
> part.
> > Not nice, but as long as there is no functional
> > problem, still I would think as doable.
> [Naren] There is a basic problem of taking a piece
> meal approach.
>  We do not know what a M3UA user can do and we
> cannot limit the M3UA-user 
> to a given set of behaviours. It might be possible
> to satisfy needs of 
> SCMG but what about Connection Oriented SCCP. SCOC
> is not state less as is 
> SCLC and there and many more issues involved with
> it, like sharing 
> connection cotext across ASPs and handle connection
> inactivity,
> handling error messages. But all these can be
> resolved in implementation
> specific ways and better left to the implementation.
[TOLGA] The main topic of this thread is non-MTP3 RK
types, so SSN based RKs are just an example. And for
that, I think at the very beginning I mentioned that
the management functionality we discuss is only about
class0/class1 SCCP (then Brian also added no GTT
routing)
My goal is not to modify M3UA to use SSN based RKs,
but the leave the way open -as long as it does not
bring interoperability problems- for non=MTP3 RK
types.
> 
> > > to change M3UA to make distributed SCCP work.
> The
> > > point is we should 
> > > not try to change M3UA behaviour to satisfy
> needs of
> > > M3UA user.
> > [TOLGA] For that I disagree. I said several times,
> it
> > is mandatory not to bring interoperability
> problems
> > while implementing necessary management
> functionality
> > to be able to handle non-MTP3 RKs. Such a
> managemnt
> > functionality would not change any M3UA behaviour
> at
> > all. 
> > > We should not assume how M3UA users will be
> > > distributed for example based 
> > > on SSN or not. It is responsibility of
> distributed
> > > SCCP to handle 
> > > possibilities of receiving SCMG messages for a
> given
> > > SSN on one or more 
> > [TOLGA] What you say is a possible way of doing
> things
> > and for most of the cases probably the better one.
> But
> > IMO there is no reason to put a restriction. 
> > > ASP's. This can be easily acheived in
> implementation
> > > specific way. 
> > > For example if we distribute single SSN across
> two
> > > ASP's then there is 
> > > possibility of receiving TCAP response on wrong
> ASP.
> > > But M3UA should not 
> > > be responsible for resolving this. This can be
> > > resolved in implementation 
> > > specific way.
> > [TOLGA] This won't create a problem. If you
> distribute
> > single SSN across two ASPs, this means tere is a
> > single SCCP entity on those ASPs. So, it doesn't
> > matter where the TCAP response is sent.
> [Naren] Unfortunately TCAP is not stateless
> protocol. It is
> important to share TCAP context to take advantage of
> 
> distrbuted design of M3UA/sigtran stack. Even though
> M3UA
>  spec is not expected to provide solution to this
> problem.
[TOLGA] If one uses ASPs in loadsharing mode for soem
AS, then the corresponding user parts should work as a
single entity. So, TCAP context will be shared, but
this is responsibility of TCAP itself.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 15:23: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 PAA17704
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 15:23:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BKaCp09558
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 15:36:12 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BKa2J09550;
	Sat, 11 Jan 2003 15:36:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BKZSJ09521
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 15:35:28 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17680
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 15:22:08 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:AXz6dOj8f0E6qeAtlls8GDyJm2kodIfo@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BKPQD07299;
	Sat, 11 Jan 2003 13:25:26 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BKPQr14648;
	Sat, 11 Jan 2003 13:25:26 -0700
Date: Sat, 11 Jan 2003 13:25:26 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111132526.E8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111104228.X8782@openss7.org> <20030111201848.6715.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: <20030111201848.6715.qmail@web12808.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 12:18:48PM -0800
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, 11 Jan 2003 12:18:48)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Sat, 11 Jan 2003
> > 09:22:29)
> > [snip]
> > > [TOLGA] This won't create a problem. If you
> > distribute
> > > single SSN across two ASPs, this means tere is a
> > > single SCCP entity on those ASPs. So, it doesn't
> > > matter where the TCAP response is sent.
> > 
> > Huh?  Is your M3UA SG handling transactions state
> > now too?
> [TOLGA] Why do you think this? If ASPs are working in
> loadshare mode for an AS, their corresponding user
> parts are synchronized.

Synchronization is costly and you cannot normally
strew pieces of transactions across processors.

> And let's say SG keeps also some TCAP info. Why would
> M3UA care about this? The point I am trying to make
> from the very beginning of this discussion is, please
> don't try to put restrictions on SG itself, leave it
> free as long as it is compliant with M3UA.

I would also like to see it compliant with MTP Level 3
as well and allow MTP User to be compliant with their
specifications.  All that you have proposed is to break
the MTP-User (and the SS7 network) for the cause of
keeping flexibility.  Flexibility at the cost of
interoperablity is not the IETF way.  Rigidity for the
sake of interoperability is.

> But you just focus on the specific SSN RK case and try to
> finish a design for a implementation dependent
> management functionality which can be used to be able
> to support SSN based RKs on SG.

Because there is no evidence that any such implementation
dependent management function can be made interoperable.
And, because of that, it needs to be restricted from the
specification to follow IETF principles.

You keep claiming that such an implementation exists: but
you have not presented one.  Lacking a single example of 
an interoperable implementation, exclusion is the only
course.

--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  Sat Jan 11 15:37: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 PAA17810
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 15:37:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BKo3U10582
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 15:50:03 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BKnYJ10552;
	Sat, 11 Jan 2003 15:49:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BKmAJ10520
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 15:48:10 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17798
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 15:34:49 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:PHKHz2fkTuzEBOEgCUQHppuenKFC2AzT@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BKc8D07541;
	Sat, 11 Jan 2003 13:38:08 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BKc7u15052;
	Sat, 11 Jan 2003 13:38:07 -0700
Date: Sat, 11 Jan 2003 13:38:07 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111133807.F8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <Pine.LNX.4.44.0301111240510.26229-100000@cerberus.intellinet-tech.com> <20030111202455.40513.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: <20030111202455.40513.qmail@web12804.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 12:24:55PM -0800
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, 11 Jan 2003 12:24:55)
> Narender,
> --- ngoel@cerberus.intellinet-tech.com wrote:
> > On Sat, 11 Jan 2003, Tolga Asveren wrote:
> > Tolga,
> >  My response is inline.
> > > Narender,
> > > --- ngoel@cerberus.intellinet-tech.com wrote:
> > > > Brian/Tolga,
> > > >  Reading your discussion I have few
> > > > thoughts/comments -
> > > > Are we not trying to violate principles of
> > layered
> > > > protocol here by trying
> > > [TOLGA]I also would think this is against the
> > spirit
> > > of a layered approach. But with any non-MTP3 RK
> > type
> > > it is obvious that one has to dig in to the
> > payload of
> > > a message to reach the corresponding protocol
> > part.
> > > Not nice, but as long as there is no functional
> > > problem, still I would think as doable.
> > [Naren] There is a basic problem of taking a piece
> > meal approach.
> >  We do not know what a M3UA user can do and we
> > cannot limit the M3UA-user 
> > to a given set of behaviours. It might be possible
> > to satisfy needs of 
> > SCMG but what about Connection Oriented SCCP. SCOC
> > is not state less as is 
> > SCLC and there and many more issues involved with
> > it, like sharing 
> > connection cotext across ASPs and handle connection
> > inactivity,
> > handling error messages. But all these can be
> > resolved in implementation
> > specific ways and better left to the implementation.
> [TOLGA] The main topic of this thread is non-MTP3 RK
> types, so SSN based RKs are just an example. And for
> that, I think at the very beginning I mentioned that
> the management functionality we discuss is only about
> class0/class1 SCCP (then Brian also added no GTT
> routing)

You can also add no multiple SG.

Also, no routing on SSN=0 (which will break Valerie's
approach), or do we allow that and break Tolga's approach?
You see they are not interoperable.

It think you will have to add no mated subsystems, because
Tolga doesn't have a SOR/SOG solution.

Also, I think you will have to share transaction state
in real-time (effectively makine it one big ASP) because
Tolga's approach cannot get transactions back to the correct
place.

Oh, and no congestion controls, because Tolga's approach
cannot handle SCCP congestion.

Oh, and one should mention that one shouldn't use load-sharing
or broadcast because race conditions at the SG will break SCCP
conformance.  And the ASP should send messagses to only one SGP
to avoid races between SGP.

And you could have load-shared over SSN instead of routing
on SSN in the first place a nothing would break.  But Tolga
wants to encourage non-interoperable solutions where
interoperable ones exist (loadsharing on SSN).

> My goal is not to modify M3UA to use SSN based RKs,
> but the leave the way open -as long as it does not
> bring interoperability problems- for non=MTP3 RK
> types.

It brings interoperablity problems.  Just use loadsharing
on SSN instead of routing.  Routing on SSN should be
prohibited by the specification.

--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  Sat Jan 11 16:04: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 QAA18226
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 16:04:13 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BLH3111837
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 16:17:03 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BLGNJ11813;
	Sat, 11 Jan 2003 16:16:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BLF9J11791
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 16:15:10 -0500
Received: from cerberus.intellinet-tech.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18199
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 16:01:48 -0500 (EST)
From: ngoel@cerberus.intellinet-tech.com
Received: from localhost (ngoel@localhost)
	by cerberus.intellinet-tech.com (8.11.6/8.11.6) with ESMTP id h0BL1JZ29754;
	Sat, 11 Jan 2003 16:01:19 -0500
Date: Sat, 11 Jan 2003 16:01:19 -0500 (EST)
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Tolga Asveren <tolga_asveren@yahoo.com>, <sigtran@ietf.org>
Subject: Re: [Sigtran] m3ua- IG
In-Reply-To: <20030111124635.B8782@openss7.org>
Message-ID: <Pine.LNX.4.44.0301111541340.29560-100000@cerberus.intellinet-tech.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>

On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
Brian,
> ngoel,
> 
> ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 14:29:21)
> > On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> > Brian,
> >  Some of the problems with SCOC and SUA are -
> > 1. Routing context is mandatory in SUA messages.
> 
> That is not a problem.
> 
> > SUA has DPC/SSN routing keys.
> 
> SUA has AMF (Address Mapping Function).  SUA has can route on GT and
> can even route on SLR/DLR.
> 
> > SCOC DT1 message does not contain SCCP addressing information.
> 
> DT1 has SLR/DLR.
> 
> > It is not trivial to find the RC for a incoming DT1 at the SG.
> 
> It is trivial: lookup on DLR.
State machine is duplicated on SG and ASP.
> 
> > Do we mantain connection context at SG and no connection context at ASP
> > level?
> 
> Connection context is referenced both at SG and ASP by DPC/DLR.
> 
> > Can a SUA user allocate or delete connection context?
> 
> Allocated with CORE/COAK, deallocated with RELRE/RELCO.
> 
> > Or these functions be RPC calls which are implemnentation dependent?
> 
> Not implementation dependent.  Completely within the context of SCCP.
> 
> > Does any SCCP Connection Oriented functionality is required on ASP  side in
> > addition to what is defined in SUA draft. 
> 
> No.
How about context management? What if SUA is acting as a internudiate on 
ASP with IPSP. Are you saying this cannot happen. I think you need to 
SCCP spec. Don't you think these cases can be much better handled by 
SCCP/M3UA.
> 
> > 2. Problem similar to shring connection state. If one ASP sends a Connect 
> > Request what is the gurantee the same will receive Connection Confirm. 
> 
> Base on the local reference in the CR.  SG sends CC to correct ASP.
> 
> > This is much easier to handle with SCCP/M3UA.
> 
> Very wrong.
Why? How can you say SUA is better solution than M3UA/SCCP.
> 
> > I think there are much more implementation dependent issues with SUA.
> 
> I think you just don't have a good understanding the SUA standard yet.
> 
> There are no issues other than DRN Label with multiple SGs under failure.
> draft-bidulock-sigtran-regext-01.txt submitted to the I-D editor several days
> ago which provides better solution for multiple SG case than DRN Labels.  You
> can pick up a copy at
> 
> 	http://www.openss7.org/sigtran01.html
> 
> until it appears on the I-D server.
I am talking about SUA draft not indvidual submissions.
> 
> But I think you should take some time to read carefully through the SUA spec,
> ask some questions, and understand it well before making such sweeping
> statements.
Sometime  back in our earlier discussion you yourself agreed that SUA was 
weak in supporting CO and also you mentioned that AMF was not clearly 
described. I don't know if things have changed much in SUA draft since 
then. You can check the mailing list on that.
I am not making any aweeping statements nut only saying that 
IMO SCCP/M3UA better capturees SCCP Connection Oriented functionality in 
sigtran world.
-Narender 
 > > --brian
> 
> > -Narender
> > 
> >  > ngoel,
> > > 
> > > SUA clearly describes handling of connection oriented messages.  SCOC is
> > > a SCCP protocol state machine that resides below SUA in a standard SCCP.
> > > The SCOC for SUA is precisely the SCOC of Q.714, ANSI T1.112.4, etc.
> > > It does not need any description in the SUA standard because it is adequately
> > > described in the SCCP standards.  SUA is designed to export the SCCP/SCCP-User
> > > interface, not to replace SCCP state machines.
> > > 
> > > --brian
> > > 
> > > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 13:28:32)
> > > > On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> > > > Brian,
> > > >  SUA spec is does bot describe clearly how to handle SCOC and may not be 
> > > > better solution overall.
> > > > I believe it may be better if we general set of guidelines for M3UA users 
> > > > without assuming specific M3UA user like SCCP/ISUP/TUP etc. The main 
> > > > issues with distributed sigtran user are -
> > > > 1. Sharing to user state/context across distributed ASPs.
> > > > 2. Handling of broadcast messages.
> > > > Any any other generic behaviour that everyone agrees and try to present a 
> > > > common solution to the user and not link the solution to a specific 
> > > > protocol.
> > > > -Narender
> > > > 
> > > >   
> > > >  > ngoel,
> > > > > 
> > > > > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 12:05:22)
> > > > > > Brian/Tolga,
> > > > > >  Reading your discussion I have few thoughts/comments -
> > > > > > Are we not trying to violate principles of layered protocol here by trying 
> > > > > > to change M3UA to make distributed SCCP work. The point is we should 
> > > > > > not try to change M3UA behaviour to satisfy needs of M3UA user.
> > > > > > We should not assume how M3UA users will be distributed for example based 
> > > > > > on SSN or not. It is responsibility of distributed SCCP to handle 
> > > > > > possibilities of receiving SCMG messages for a given SSN on one or more 
> > > > > > ASP's. This can be easily acheived in implementation specific way. 
> > > > > > For example if we distribute single SSN across two ASP's then there is 
> > > > > > possibility of receiving TCAP response on wrong ASP. But M3UA should not 
> > > > > > be responsible for resolving this. This can be resolved in implementation 
> > > > > > specific way.
> > > > > > -Narender 
> > > > > 
> > > > > Or in a standard way using SUA.
> > > > > 
> > > > > --brian
> > > > > 
> > > > > 
> > > 
> > > 
> 
> 

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



From mailnull@www1.ietf.org  Sat Jan 11 16:09: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 QAA18393
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 16:09:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BLMbf12036
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 16:22:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BLM8J12006;
	Sat, 11 Jan 2003 16:22:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BLLKJ11966
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 16:21:20 -0500
Received: from web12808.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA18289
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 16:07:59 -0500 (EST)
Message-ID: <20030111211117.13171.qmail@web12808.mail.yahoo.com>
Received: from [62.29.86.74] by web12808.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 13:11:17 PST
Date: Sat, 11 Jan 2003 13:11:17 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <20030111131739.D8782@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:                                
>                                 (Sat, 11 Jan 2003
> 12:03:50)
> > Brian,
> > [...snip....]
> > > > [TOLGA]This is the reason why you have the
> > > management
> > > > functionality on SG. You get the responses and
> > > create
> > > > the global view of the corresponding
> subsystem.
> > > Not
> > > > all of the SSP is sent to SS7 network, only
> one. 
> > > 
> > > Not all the responses necessarily go through the
> > > same SG.
> > > 
> > > Still broken.
> > [TOLGA] We were already here I think. The solution
> is
> > simple, do not use multiple SG configuration,
> which
> > anyhow is a strange mode of operation (multiple
> MTP3
> > logic for the same PC, working independently)
> 
> M3UA can support MTP3 routing keys on multiple SG.
[TOLGA] I think supporting multiple SG case is
optional. And I wouldn't consider not supporting it as
a modification to M3UA protocol but just as not
supporting one type of configuration.
> 
> Besides, its still broken.  How do you handle
> subsystem
> congestion?
[TOLGA] What is specail about it? How different it is
from congestion of signalling point case for ANSI
networks when multiple SGs are used? Again management
logic decides, when to declare the subsystem as
congested.
> 
> Also, you have race condition with your correlation
> of
> SSP messages.  One ASP can issue SSA before the SSP
> has arrived from other ASP.  Like so:
> 
> ASP1   SSA ----- SSP                            SGP1
> ASP2                        SSA ----- SSP       SGP2
> ASP3              SSA ----- SSP                 SGP3
> ASP4         SSA ----- SSP                      SGP4
> ASP5                             SSA ----- SSP  SGP5
> ASP6                  SSA ----- SSP             SGP6
> ASP7            SSA ----- SSP                   SGP7
> ASP8                         SSA ----- SSP      SGP8
> 
> The SCCP thinks it has sent SSP followed by SSA. 
> The
> SG receives:
> 
>   SSP, SSP, SSP, SSA, SSP, SSA, SSA, SSP, SSP, SSP,
>   SSA, SSA, SSP, SSA, SSA, SSA
> 
> Some are responsive to SST, some are broadcast. 
> What
> will the SG send?  Also note that SCCP management
> messages are not send on the same SLS, so some of
> these
> can get reversed in between ASP and SGP.
[TOLGA] For the ones which are not sent on the same
SLS, isn't there also the possibility that they get
missequenced in the TDM based SS7 network?
Although all of those are questions about the
implementation dependent part and are not related with
M3UA, still I would think:
For your scenario, SG would respond with SSA if it has
received one SSA from one ASP -and if it didn't
received SSP from it afterwards-, before the timer it
started after receiving SST, expires.

> 
> Your algorithm falls flat on its face because it
> cannot tell the different between respones to SST
> and
> broadcast messages (it is not contained in the
> message).
[TOLGA] Again my answer for the non-M3UA part:
Management logic on SG keeps global SSP states. When
this state is changed based on a message received from
an ASP, it can be considered as an event to be broadcasted.

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 16:22: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 QAA18614
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 16:22:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BLYol12282
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 16:34:50 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BLY8J12260;
	Sat, 11 Jan 2003 16:34:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BLXMJ12234
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 16:33:22 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18548
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 16:20:00 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:+JN2fXGvU6sarGFYM34F8GkmNLUaTDRF@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BLNID08133;
	Sat, 11 Jan 2003 14:23:19 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BLNIS16575;
	Sat, 11 Jan 2003 14:23:18 -0700
Date: Sat, 11 Jan 2003 14:23:18 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111142318.G8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111131739.D8782@openss7.org> <20030111211117.13171.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: <20030111211117.13171.qmail@web12808.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 01:11:17PM -0800
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, 11 Jan 2003 13:11:17)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Sat, 11 Jan 2003
> > 12:03:50)
> > > Brian,
> > > [...snip....]
> > > > > [TOLGA]This is the reason why you have the
> > > > management
> > > > > functionality on SG. You get the responses and
> > > > create
> > > > > the global view of the corresponding
> > subsystem.
> > > > Not
> > > > > all of the SSP is sent to SS7 network, only
> > one. 
> > > > 
> > > > Not all the responses necessarily go through the
> > > > same SG.
> > > > 
> > > > Still broken.
> > > [TOLGA] We were already here I think. The solution
> > is
> > > simple, do not use multiple SG configuration,
> > which
> > > anyhow is a strange mode of operation (multiple
> > MTP3
> > > logic for the same PC, working independently)
> > 
> > M3UA can support MTP3 routing keys on multiple SG.
> [TOLGA] I think supporting multiple SG case is
> optional. And I wouldn't consider not supporting it as
> a modification to M3UA protocol but just as not
> supporting one type of configuration.

MTP3 RKs are supported on multiple SG.  You will need
a statement saying the your SSN RKs are not supported
on mutliple SG (amoung other things).

> > 
> > Besides, its still broken.  How do you handle
> > subsystem
> > congestion?
> [TOLGA] What is specail about it? How different it is
> from congestion of signalling point case for ANSI
> networks when multiple SGs are used? Again management
> logic decides, when to declare the subsystem as
> congested.

Subsystem congestion is implementation dependent and
resides on the ASP.  The SGP cannot know the algorithm
and cannot correlate multiple congestion messages from
multiple ASPs.

> > 
> > Also, you have race condition with your correlation
> > of
> > SSP messages.  One ASP can issue SSA before the SSP
> > has arrived from other ASP.  Like so:
> > 
> > ASP1   SSA ----- SSP                            SGP1
> > ASP2                        SSA ----- SSP       SGP2
> > ASP3              SSA ----- SSP                 SGP3
> > ASP4         SSA ----- SSP                      SGP4
> > ASP5                             SSA ----- SSP  SGP5
> > ASP6                  SSA ----- SSP             SGP6
> > ASP7            SSA ----- SSP                   SGP7
> > ASP8                         SSA ----- SSP      SGP8
> > 
> > The SCCP thinks it has sent SSP followed by SSA. 
> > The
> > SG receives:
> > 
> >   SSP, SSP, SSP, SSA, SSP, SSA, SSA, SSP, SSP, SSP,
> >   SSA, SSA, SSP, SSA, SSA, SSA
> > 
> > Some are responsive to SST, some are broadcast. 
> > What
> > will the SG send?  Also note that SCCP management
> > messages are not send on the same SLS, so some of
> > these
> > can get reversed in between ASP and SGP.
> [TOLGA] For the ones which are not sent on the same
> SLS, isn't there also the possibility that they get
> missequenced in the TDM based SS7 network?

Only during failures or congestion (which almost never occur).
With your solution, because of the way SCTP treats streams,
it will occur as in normal operation with no failures.  This
will fail conformance tests.

> Although all of those are questions about the
> implementation dependent part and are not related with
> M3UA, still I would think:
> For your scenario, SG would respond with SSA if it has
> received one SSA from one ASP -and if it didn't
> received SSP from it afterwards-, before the timer it
> started after receiving SST, expires.

But SSA and SSP can get reversed by SCTP, them being on
different streams and even different associations to
different SGP.  Therefore, your algorithm is often wrong
in the normal course of affairs and cannot be shown to
meet SCCP conformance.  Your are breaking the MTP User by
mucking with its messages.

> 
> > 
> > Your algorithm falls flat on its face because it
> > cannot tell the different between respones to SST
> > and
> > broadcast messages (it is not contained in the
> > message).
> [TOLGA] Again my answer for the non-M3UA part:
> Management logic on SG keeps global SSP states. When
> this state is changed based on a message received from
> an ASP, it can be considered as an event to be broadcasted.

You cannot tell at the SG, only at the ASP.  Which was the
response to SST?  The SSA's above or the SSP's?

--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  Sat Jan 11 16:27: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 QAA18687
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 16:27:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BLdtX13066
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 16:39:55 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BLd4J13031;
	Sat, 11 Jan 2003 16:39:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BLcfJ13013
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 16:38:41 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18649
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 16:25:19 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:ZRQbvahP5FvD0JBoRk5mK0WduJZ444Z2@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BLSbD08190;
	Sat, 11 Jan 2003 14:28:37 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BLSbh16747;
	Sat, 11 Jan 2003 14:28:37 -0700
Date: Sat, 11 Jan 2003 14:28:36 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ngoel@cerberus.intellinet-tech.com
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111142836.H8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ngoel@cerberus.intellinet-tech.com,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111124635.B8782@openss7.org> <Pine.LNX.4.44.0301111541340.29560-100000@cerberus.intellinet-tech.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.LNX.4.44.0301111541340.29560-100000@cerberus.intellinet-tech.com>; from ngoel@cerberus.intellinet-tech.com on Sat, Jan 11, 2003 at 04:01:19PM -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>

ngoel,

ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 16:01:19)
> On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> Brian,
> > ngoel,
> > 
> > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 14:29:21)
> > > On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> > > Brian,
> > >  Some of the problems with SCOC and SUA are -
> > > 1. Routing context is mandatory in SUA messages.
> > 
> > That is not a problem.
> > 
> > > SUA has DPC/SSN routing keys.
> > 
> > SUA has AMF (Address Mapping Function).  SUA has can route on GT and
> > can even route on SLR/DLR.
> > 
> > > SCOC DT1 message does not contain SCCP addressing information.
> > 
> > DT1 has SLR/DLR.
> > 
> > > It is not trivial to find the RC for a incoming DT1 at the SG.
> > 
> > It is trivial: lookup on DLR.
> State machine is duplicated on SG and ASP.

No state machine duplication.  State machine resides on SG.  ASP merely
passed messages based on DRN to the correct connection.  ASP does not
need connection state machine.  SG exports SCCP-User connection interface
to AS.

> > 
> > > Do we mantain connection context at SG and no connection context at ASP
> > > level?
> > 
> > Connection context is referenced both at SG and ASP by DPC/DLR.
> > 
> > > Can a SUA user allocate or delete connection context?
> > 
> > Allocated with CORE/COAK, deallocated with RELRE/RELCO.
> > 
> > > Or these functions be RPC calls which are implemnentation dependent?
> > 
> > Not implementation dependent.  Completely within the context of SCCP.
> > 
> > > Does any SCCP Connection Oriented functionality is required on ASP  side in
> > > addition to what is defined in SUA draft. 
> > 
> > No.
> How about context management? What if SUA is acting as a internudiate on 
> ASP with IPSP. Are you saying this cannot happen. I think you need to 
> SCCP spec. Don't you think these cases can be much better handled by 
> SCCP/M3UA.

It am speaking of SG/ASP, not relay.  Relay is prohibited in M3UA by the RFC.
It cannot handle it at all.  SUA has relay built in.

> > 
> > > 2. Problem similar to shring connection state. If one ASP sends a Connect 
> > > Request what is the gurantee the same will receive Connection Confirm. 
> > 
> > Base on the local reference in the CR.  SG sends CC to correct ASP.
> > 
> > > This is much easier to handle with SCCP/M3UA.
> > 
> > Very wrong.
> Why? How can you say SUA is better solution than M3UA/SCCP.

How can you say M3UA/SCCP is better solution than SUA?

> > 
> > > I think there are much more implementation dependent issues with SUA.
> > 
> > I think you just don't have a good understanding the SUA standard yet.
> > 
> > There are no issues other than DRN Label with multiple SGs under failure.
> > draft-bidulock-sigtran-regext-01.txt submitted to the I-D editor several days
> > ago which provides better solution for multiple SG case than DRN Labels.  You
> > can pick up a copy at
> > 
> > 	http://www.openss7.org/sigtran01.html
> > 
> > until it appears on the I-D server.
> I am talking about SUA draft not indvidual submissions.
> > 
> > But I think you should take some time to read carefully through the SUA spec,
> > ask some questions, and understand it well before making such sweeping
> > statements.
> Sometime  back in our earlier discussion you yourself agreed that SUA was 
> weak in supporting CO and also you mentioned that AMF was not clearly 
> described. I don't know if things have changed much in SUA draft since 
> then. You can check the mailing list on that.

Weak on DRN Labels for multiple SG as STP case.  Tolga can't even get class 0
working on multiple SG for M3UA, so SUA is still far superior.

> I am not making any aweeping statements nut only saying that 
> IMO SCCP/M3UA better capturees SCCP Connection Oriented functionality in 
> sigtran world.

M3UA does not capture it at all.  M3UA cannot support class 2 or 3 routing
keys.  SUA can.

--brian

> -Narender 
>  > > --brian
> > 
> > > -Narender
> > > 
> > >  > ngoel,
> > > > 
> > > > SUA clearly describes handling of connection oriented messages.  SCOC is
> > > > a SCCP protocol state machine that resides below SUA in a standard SCCP.
> > > > The SCOC for SUA is precisely the SCOC of Q.714, ANSI T1.112.4, etc.
> > > > It does not need any description in the SUA standard because it is adequately
> > > > described in the SCCP standards.  SUA is designed to export the SCCP/SCCP-User
> > > > interface, not to replace SCCP state machines.
> > > > 
> > > > --brian
> > > > 
> > > > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 13:28:32)
> > > > > On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> > > > > Brian,
> > > > >  SUA spec is does bot describe clearly how to handle SCOC and may not be 
> > > > > better solution overall.
> > > > > I believe it may be better if we general set of guidelines for M3UA users 
> > > > > without assuming specific M3UA user like SCCP/ISUP/TUP etc. The main 
> > > > > issues with distributed sigtran user are -
> > > > > 1. Sharing to user state/context across distributed ASPs.
> > > > > 2. Handling of broadcast messages.
> > > > > Any any other generic behaviour that everyone agrees and try to present a 
> > > > > common solution to the user and not link the solution to a specific 
> > > > > protocol.
> > > > > -Narender
> > > > > 
> > > > >   
> > > > >  > ngoel,
> > > > > > 
> > > > > > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 12:05:22)
> > > > > > > Brian/Tolga,
> > > > > > >  Reading your discussion I have few thoughts/comments -
> > > > > > > Are we not trying to violate principles of layered protocol here by trying 
> > > > > > > to change M3UA to make distributed SCCP work. The point is we should 
> > > > > > > not try to change M3UA behaviour to satisfy needs of M3UA user.
> > > > > > > We should not assume how M3UA users will be distributed for example based 
> > > > > > > on SSN or not. It is responsibility of distributed SCCP to handle 
> > > > > > > possibilities of receiving SCMG messages for a given SSN on one or more 
> > > > > > > ASP's. This can be easily acheived in implementation specific way. 
> > > > > > > For example if we distribute single SSN across two ASP's then there is 
> > > > > > > possibility of receiving TCAP response on wrong ASP. But M3UA should not 
> > > > > > > be responsible for resolving this. This can be resolved in implementation 
> > > > > > > specific way.
> > > > > > > -Narender 
> > > > > > 
> > > > > > Or in a standard way using SUA.
> > > > > > 
> > > > > > --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  Sat Jan 11 17:08:19 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 RAA19802
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 17:08:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BMLBY15595
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 17:21:11 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BMKmJ15585;
	Sat, 11 Jan 2003 17:20:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BMJmJ15508
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 17:19:48 -0500
Received: from cerberus.intellinet-tech.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19772
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 17:06:25 -0500 (EST)
From: ngoel@cerberus.intellinet-tech.com
Received: from localhost (ngoel@localhost)
	by cerberus.intellinet-tech.com (8.11.6/8.11.6) with ESMTP id h0BM5wc30420;
	Sat, 11 Jan 2003 17:05:59 -0500
Date: Sat, 11 Jan 2003 17:05:58 -0500 (EST)
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Tolga Asveren <tolga_asveren@yahoo.com>, <sigtran@ietf.org>
Subject: Re: [Sigtran] m3ua- IG
In-Reply-To: <20030111142836.H8782@openss7.org>
Message-ID: <Pine.LNX.4.44.0301111644230.30224-100000@cerberus.intellinet-tech.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>

On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
Brian,
> ngoel,
> 
> ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 16:01:19)
> > On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> > Brian,
> > > ngoel,
> > > 
> > > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 14:29:21)
> > > > On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> > > > Brian,
> > > >  Some of the problems with SCOC and SUA are -
> > > > 1. Routing context is mandatory in SUA messages.
> > > 
> > > That is not a problem.
> > > 
> > > > SUA has DPC/SSN routing keys.
> > > 
> > > SUA has AMF (Address Mapping Function).  SUA has can route on GT and
> > > can even route on SLR/DLR.
> > > 
> > > > SCOC DT1 message does not contain SCCP addressing information.
> > > 
> > > DT1 has SLR/DLR.
> > > 
> > > > It is not trivial to find the RC for a incoming DT1 at the SG.
> > > 
> > > It is trivial: lookup on DLR.
> > State machine is duplicated on SG and ASP.
> 
> No state machine duplication.  State machine resides on SG.  ASP merely
> passed messages based on DRN to the correct connection.  ASP does not
> need connection state machine.  SG exports SCCP-User connection interface
> to AS.
How SG exports user connection interface. Is it specified in draft? If not 
this is a weakness/grey area.
> 
> > > 
> > > > Do we mantain connection context at SG and no connection context at ASP
> > > > level?
> > > 
> > > Connection context is referenced both at SG and ASP by DPC/DLR.
> > > 
> > > > Can a SUA user allocate or delete connection context?
> > > 
> > > Allocated with CORE/COAK, deallocated with RELRE/RELCO.
> > > 
> > > > Or these functions be RPC calls which are implemnentation dependent?
> > > 
> > > Not implementation dependent.  Completely within the context of SCCP.
> > > 
> > > > Does any SCCP Connection Oriented functionality is required on ASP  side in
> > > > addition to what is defined in SUA draft. 
> > > 
> > > No.
> > How about context management? What if SUA is acting as a internudiate on 
> > ASP with IPSP. Are you saying this cannot happen. I think you need to 
> > SCCP spec. Don't you think these cases can be much better handled by 
> > SCCP/M3UA.
> 
> It am speaking of SG/ASP, not relay.  Relay is prohibited in M3UA by the RFC.
> It cannot handle it at all.  SUA has relay built in.
I don't know why m3ua will need to perform relay here. In this case relay 
will be done by SCCP which is very well defined in SCCP spec.
> 
> > > 
> > > > 2. Problem similar to shring connection state. If one ASP sends a Connect 
> > > > Request what is the gurantee the same will receive Connection Confirm. 
> > > 
> > > Base on the local reference in the CR.  SG sends CC to correct ASP.
> > > 
> > > > This is much easier to handle with SCCP/M3UA.
> > > 
> > > Very wrong.
> > Why? How can you say SUA is better solution than M3UA/SCCP.
> 
> How can you say M3UA/SCCP is better solution than SUA?
> 
> > > 
> > > > I think there are much more implementation dependent issues with SUA.
> > > 
> > > I think you just don't have a good understanding the SUA standard yet.
> > > 
> > > There are no issues other than DRN Label with multiple SGs under failure.
> > > draft-bidulock-sigtran-regext-01.txt submitted to the I-D editor several days
> > > ago which provides better solution for multiple SG case than DRN Labels.  You
> > > can pick up a copy at
> > > 
> > > 	http://www.openss7.org/sigtran01.html
> > > 
> > > until it appears on the I-D server.
> > I am talking about SUA draft not indvidual submissions.
> > > 
> > > But I think you should take some time to read carefully through the SUA spec,
> > > ask some questions, and understand it well before making such sweeping
> > > statements.
> > Sometime  back in our earlier discussion you yourself agreed that SUA was 
> > weak in supporting CO and also you mentioned that AMF was not clearly 
> > described. I don't know if things have changed much in SUA draft since 
> > then. You can check the mailing list on that.
> 
> Weak on DRN Labels for multiple SG as STP case.  Tolga can't even get class 0
> working on multiple SG for M3UA, so SUA is still far superior.
I need to catch up with what tolga is doing in this case. But I don't 
understand how M3UA is preventing SCCP functions. M3UA definition should 
not depend on its user. But IMHO we should not try to define things which can 
be done in implementation dependent way and do not hurt interoperability. 
 
 > 
> > I am not making any aweeping statements nut only saying that 
> > IMO SCCP/M3UA better capturees SCCP Connection Oriented functionality in 
> > sigtran world.
> 
> M3UA does not capture it at all.  M3UA cannot support class 2 or 3 routing
> keys.  SUA can.
I don't understand why m3ua needs to support SCCP specific routing 
key. We had class 2 working with M3UA with no 
problems. How can M3UA impose limitations on SCCP functionality. If this 
is the case then may be SCCP needs to be fixed. But I don't think that is 
the case.

 > 
> --brian
-Narender
> 
> > -Narender 
> >  > > --brian
> > > 
> > > > -Narender
> > > > 
> > > >  > ngoel,
> > > > > 
> > > > > SUA clearly describes handling of connection oriented messages.  SCOC is
> > > > > a SCCP protocol state machine that resides below SUA in a standard SCCP.
> > > > > The SCOC for SUA is precisely the SCOC of Q.714, ANSI T1.112.4, etc.
> > > > > It does not need any description in the SUA standard because it is adequately
> > > > > described in the SCCP standards.  SUA is designed to export the SCCP/SCCP-User
> > > > > interface, not to replace SCCP state machines.
> > > > > 
> > > > > --brian
> > > > > 
> > > > > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 13:28:32)
> > > > > > On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> > > > > > Brian,
> > > > > >  SUA spec is does bot describe clearly how to handle SCOC and may not be 
> > > > > > better solution overall.
> > > > > > I believe it may be better if we general set of guidelines for M3UA users 
> > > > > > without assuming specific M3UA user like SCCP/ISUP/TUP etc. The main 
> > > > > > issues with distributed sigtran user are -
> > > > > > 1. Sharing to user state/context across distributed ASPs.
> > > > > > 2. Handling of broadcast messages.
> > > > > > Any any other generic behaviour that everyone agrees and try to present a 
> > > > > > common solution to the user and not link the solution to a specific 
> > > > > > protocol.
> > > > > > -Narender
> > > > > > 
> > > > > >   
> > > > > >  > ngoel,
> > > > > > > 
> > > > > > > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 12:05:22)
> > > > > > > > Brian/Tolga,
> > > > > > > >  Reading your discussion I have few thoughts/comments -
> > > > > > > > Are we not trying to violate principles of layered protocol here by trying 
> > > > > > > > to change M3UA to make distributed SCCP work. The point is we should 
> > > > > > > > not try to change M3UA behaviour to satisfy needs of M3UA user.
> > > > > > > > We should not assume how M3UA users will be distributed for example based 
> > > > > > > > on SSN or not. It is responsibility of distributed SCCP to handle 
> > > > > > > > possibilities of receiving SCMG messages for a given SSN on one or more 
> > > > > > > > ASP's. This can be easily acheived in implementation specific way. 
> > > > > > > > For example if we distribute single SSN across two ASP's then there is 
> > > > > > > > possibility of receiving TCAP response on wrong ASP. But M3UA should not 
> > > > > > > > be responsible for resolving this. This can be resolved in implementation 
> > > > > > > > specific way.
> > > > > > > > -Narender 
> > > > > > > 
> > > > > > > Or in a standard way using SUA.
> > > > > > > 
> > > > > > > --brian
> > > > > > > 
> > > > > > > 
> > > > > 
> > > > > 
> > > 
> > > 
> 
> 

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



From mailnull@www1.ietf.org  Sat Jan 11 17:32: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 RAA20166
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 17:32:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BMiv616852
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 17:44:57 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BMiHJ16838;
	Sat, 11 Jan 2003 17:44:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BMhEJ16807
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 17:43:14 -0500
Received: from web12801.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA20145
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 17:29:51 -0500 (EST)
Message-ID: <20030111223310.94737.qmail@web12801.mail.yahoo.com>
Received: from [62.29.86.74] by web12801.mail.yahoo.com via HTTP; Sat, 11 Jan 2003 14:33:10 PST
Date: Sat, 11 Jan 2003 14:33:10 -0800 (PST)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
In-Reply-To: <20030111142318.G8782@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,

Again some answers/questions below although I really
believe this is misuse of the SIGTRAN WG list, because
IMO those things are not related with M3UA, we are
discussing some hypothetical implementation dependent
functionality. For example, if a SG claims to support
RKs based on called party number just for
query/response scenarios, do you think this is the
place to discuss it? 
So, as a final word I want to say that I think RKs
should be kept flexible, as they are now. I don't see
a problem by removing SSN from examples, as they migth
bring some confusion.

[...snip...]
> MTP3 RKs are supported on multiple SG.  You will
> need
> a statement saying the your SSN RKs are not
> supported
> on mutliple SG (amoung other things).
[TOLGA] Yes this should be stated, but IMO not in M3UA
RFC but in the product specification of the SG itself.
For example there one can say that one just supports
single SG configurations, or just query/response
scenarios, only class0/class1 SCCP in case of SSN RKs
etc.... Personally I don't consider those things as
violation of the protocol, but just as limitations of
a specific SG.


[...snip...]
> > [TOLGA] What is specail about it? How different it
> is
> > from congestion of signalling point case for ANSI
> > networks when multiple SGs are used? Again
> management
> > logic decides, when to declare the subsystem as
> > congested.
> 
> Subsystem congestion is implementation dependent and
> resides on the ASP.  The SGP cannot know the
> algorithm
> and cannot correlate multiple congestion messages
> from
> multiple ASPs.
[TOLGA] IMO this is really very similar to the
signalling point congestion case for ANSI networks in
multiple SG case. The nodes decides by themselves,
when they are congested. And SG decides in an
implementation dependent way, what to do.


[..snip...]
> > [TOLGA] For the ones which are not sent on the
> same
> > SLS, isn't there also the possibility that they
> get
> > missequenced in the TDM based SS7 network?
> 
> Only during failures or congestion (which almost
> never occur).
> With your solution, because of the way SCTP treats
> streams,
> it will occur as in normal operation with no
> failures.  This
> will fail conformance tests.
[TOLGA]Why only during failures? Maybe for those
different SLS, they are follwoing different STPs on
their way to the peer SCCP. 


[...snip...]
> > [TOLGA] Again my answer for the non-M3UA part:
> > Management logic on SG keeps global SSP states.
> When
> > this state is changed based on a message received
> from
> > an ASP, it can be considered as an event to be
> broadcasted.
> 
> You cannot tell at the SG, only at the ASP.  Which
> was the
> response to SST?  The SSA's above or the SSP's?
[TOLGA]Important is, that SG knows that there is a
pending SST to be replied and when the corresponding
timer expires, it replies based on the global view of
the subsystem. And any SCCP management message
received from ASP, which changes global subsystem
state is sent to its destination.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sat Jan 11 18:26:50 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 SAA20822
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 18:26:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BNdhY19205
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 18:39:43 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BNd0J19192;
	Sat, 11 Jan 2003 18:39:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BNbsJ19171
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 18:37:54 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20807
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 18:24:29 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:2iQdERUSsFeZ6g31AR82aQ3nICl7kBZh@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BNRmD09944;
	Sat, 11 Jan 2003 16:27:48 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BNRla21097;
	Sat, 11 Jan 2003 16:27:47 -0700
Date: Sat, 11 Jan 2003 16:27:47 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111162747.I8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111142318.G8782@openss7.org> <20030111223310.94737.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: <20030111223310.94737.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jan 11, 2003 at 02:33:10PM -0800
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, 11 Jan 2003 14:33:10)
> Brian,
> 
> Again some answers/questions below although I really
> believe this is misuse of the SIGTRAN WG list, because
> IMO those things are not related with M3UA, we are
> discussing some hypothetical implementation dependent
> functionality. For example, if a SG claims to support
> RKs based on called party number just for
> query/response scenarios, do you think this is the
> place to discuss it? 

I think that M3UA routing keys should be restricted
to MTP L3 information and then there would be no need
to discuss interoperability of these solutions.

An IETF WG is a proper place to discuss interoperability.

> So, as a final word I want to say that I think RKs
> should be kept flexible, as they are now. I don't see
> a problem by removing SSN from examples, as they migth
> bring some confusion.
> 
> [...snip...]
> > MTP3 RKs are supported on multiple SG.  You will
> > need
> > a statement saying the your SSN RKs are not
> > supported
> > on mutliple SG (amoung other things).
> [TOLGA] Yes this should be stated, but IMO not in M3UA
> RFC but in the product specification of the SG itself.
> For example there one can say that one just supports
> single SG configurations, or just query/response
> scenarios, only class0/class1 SCCP in case of SSN RKs
> etc.... Personally I don't consider those things as
> violation of the protocol, but just as limitations of
> a specific SG.

No SG can support these things in an interoperable
fashion.  This is not just restricted to a specific
SG or a specific implementation.  No implementation
can support them and interoperate.

> 
> [...snip...]
> > > [TOLGA] What is specail about it? How different it
> > is
> > > from congestion of signalling point case for ANSI
> > > networks when multiple SGs are used? Again
> > management
> > > logic decides, when to declare the subsystem as
> > > congested.
> > 
> > Subsystem congestion is implementation dependent and
> > resides on the ASP.  The SGP cannot know the
> > algorithm
> > and cannot correlate multiple congestion messages
> > from
> > multiple ASPs.
> [TOLGA] IMO this is really very similar to the
> signalling point congestion case for ANSI networks in
> multiple SG case. The nodes decides by themselves,
> when they are congested. And SG decides in an
> implementation dependent way, what to do.

That is different: nodal TFC is optional even in ANSI.

Congestion is not optional in SCCP management.


> [..snip...]
> > > [TOLGA] For the ones which are not sent on the
> > same
> > > SLS, isn't there also the possibility that they
> > get
> > > missequenced in the TDM based SS7 network?
> > 
> > Only during failures or congestion (which almost
> > never occur).
> > With your solution, because of the way SCTP treats
> > streams,
> > it will occur as in normal operation with no
> > failures.  This
> > will fail conformance tests.
> [TOLGA]Why only during failures? Maybe for those
> different SLS, they are follwoing different STPs on
> their way to the peer SCCP. 

In the absence of failures and congestion they will
not be reversed.

> [...snip...]
> > > [TOLGA] Again my answer for the non-M3UA part:
> > > Management logic on SG keeps global SSP states.
> > When
> > > this state is changed based on a message received
> > from
> > > an ASP, it can be considered as an event to be
> > broadcasted.
> > 
> > You cannot tell at the SG, only at the ASP.  Which
> > was the
> > response to SST?  The SSA's above or the SSP's?
> [TOLGA]Important is, that SG knows that there is a
> pending SST to be replied and when the corresponding
> timer expires, it replies based on the global view of
> the subsystem. And any SCCP management message
> received from ASP, which changes global subsystem
> state is sent to its destination.

SST responses and broadcasts can occur close enough
together that your timer (which violates SCCP conformance
in itself) cannot tell the difference between them.


I will say again: there is a correct way to do this
in M3UA with load-sharing on SSN.  Routing keys using
SSN are not interoperable, but load-sharing on SSN is.

Routing keys should be restricted to MTP L3 information
only.  Load-sharing can be performed on any criteria
because the rule is that every ASP in a load-share AS
must be prepared to processs any message.  Therefore,
the SG can send management messages, messages not 
containing SSN, to whichever ASP in the load-share AS
is likes and the ASP must be prepared to process it.

So: loadsharing on SSN, CIC, color, smell of the message,
is interoperable.  Routing keys are 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 mailnull@www1.ietf.org  Sat Jan 11 18:38:02 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 SAA20966
	for <sigtran-archive@odin.ietf.org>; Sat, 11 Jan 2003 18:38:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0BNou419450
	for sigtran-archive@odin.ietf.org; Sat, 11 Jan 2003 18:50:56 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BNoDJ19427;
	Sat, 11 Jan 2003 18:50:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0BNnFJ19385
	for <sigtran@optimus.ietf.org>; Sat, 11 Jan 2003 18:49:15 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20924
	for <sigtran@ietf.org>; Sat, 11 Jan 2003 18:35:50 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:JZfwcbI2Ui+hW2WO1VeNCVt6qEksBjMM@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0BNd9D10181;
	Sat, 11 Jan 2003 16:39:09 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0BNd8Y21491;
	Sat, 11 Jan 2003 16:39:08 -0700
Date: Sat, 11 Jan 2003 16:39:08 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ngoel@cerberus.intellinet-tech.com
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030111163908.J8782@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ngoel@cerberus.intellinet-tech.com,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030111142836.H8782@openss7.org> <Pine.LNX.4.44.0301111644230.30224-100000@cerberus.intellinet-tech.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.LNX.4.44.0301111644230.30224-100000@cerberus.intellinet-tech.com>; from ngoel@cerberus.intellinet-tech.com on Sat, Jan 11, 2003 at 05:05:58PM -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>

ngoel,

ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 17:05:58)
> On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> Brian,
> > ngoel,
> > 
> > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 16:01:19)
> > > On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> > > Brian,
> > > > ngoel,
> > > > 
> > > > ngoel@cerberus.intellinet-tech.com wrote:                                            (Sat, 11 Jan 2003 14:29:21)
> > > > > On Sat, 11 Jan 2003, Brian F. G. Bidulock wrote:
> > > > > Brian,
> > > > >  Some of the problems with SCOC and SUA are -
> > > > > 1. Routing context is mandatory in SUA messages.
> > > > 
> > > > That is not a problem.
> > > > 
> > > > > SUA has DPC/SSN routing keys.
> > > > 
> > > > SUA has AMF (Address Mapping Function).  SUA has can route on GT and
> > > > can even route on SLR/DLR.
> > > > 
> > > > > SCOC DT1 message does not contain SCCP addressing information.
> > > > 
> > > > DT1 has SLR/DLR.
> > > > 
> > > > > It is not trivial to find the RC for a incoming DT1 at the SG.
> > > > 
> > > > It is trivial: lookup on DLR.
> > > State machine is duplicated on SG and ASP.
> > 
> > No state machine duplication.  State machine resides on SG.  ASP merely
> > passed messages based on DRN to the correct connection.  ASP does not
> > need connection state machine.  SG exports SCCP-User connection interface
> > to AS.
> How SG exports user connection interface. Is it specified in draft? If not 
> this is a weakness/grey area.

Please read the spec:

    1.4 Services Provided by the SUA Layer 
    
    1.4.1 Support for the transport of SCCP-User Messages 
    
       The SUA supports the transfer of SCCP-user messages. The SUA layer 
       at the SG and at the ASP support the seamless transport the user 
       messages between the SG and the ASP. 
    
...

    1.6 Definition of SUA Boundaries 
 
    1.6.1 Definition of the upper boundary 
    
       The following primitives are supported between the SUA and an SCCP-
       user (a reference to ITU and ANSI sections where these primitives 
       and corresponding parameters are described, is also given): 
    
       Generic     |Specific  |  
       Name        |Name      |ANSI/ITU Reference                           
       ------------+----------+-------------------------------------------  
       N-Connect   |Request   |ITU-Q.711   Chap 6.1.1.2.2 (Tab 2/Q.711)     
		   |Indication|ANSI-T1.112 Chap 2.1.1.2.2 (Tab 2/T1.112.1)  
		   |Response  |  
		   |Confirm   |  
       ------------+----------+------------------------------------------- 
       N-Data      |Request   |ITU-Q.711   Chap 6.1.1.2.3 (Tab 3/Q.711)     
		   |Indication|ANSI-T1.112 Chap 2.1.1.2.3 (Tab 3/T1.112.1)  
       ------------+----------+------------------------------------------- 
       N-Expedited |Request   |ITU-Q.711   Chap 6.1.1.2.3 (Tab 4/Q.711)     
       Data        |Indication|ANSI-T1.112 Chap 2.1.1.2.3 (Tab 4/T1.112.1)  
       ------------+----------+------------------------------------------- 
       N-Reset     |Request   |ITU-Q.711   Chap 6.1.1.2.3 (Tab 5/Q.711)     
		   |Indication|ANSI-T1.112 Chap 2.1.1.2.3 (Tab 5/T1.112.1)  
		   |Response  |  
		   |Confirm   |  
       ------------+----------+------------------------------------------- 
       N-Disconnect|Request   |ITU-Q.711   Chap 6.1.1.2.4 (Tab 6/Q.711)     
		   |Indication|ANSI-T1.112 Chap 2.1.1.2.4 (Tab 6/T1.112.1) 
       ------------+----------+------------------------------------------- 
       N-Inform    |Request   |ITU-Q.711   Chap 6.1.1.3.1 (Tab 7/Q.711)     
		   |Indication|ANSI-T1.112 Chap 2.1.1.2.5 (Tab 6A/T1.112.1) 
       ------------+----------+------------------------------------------- 
       N-Unit Data |Request   |ITU-Q.711   Chap 6.2.2.3.1 (Tab 10/Q.711)    
		   |Indication|ANSI-T1.112 Chap 2.2.2.3.1 (Tab 8A/T1.112.1) 
       ------------+----------+------------------------------------------- 
       N-Notice    |Indication|ITU-Q.711   Chap 6.2.2.3.2 (Tab 11/Q.711)    
		   |          |ANSI-T1.112 Chap 2.2.2.3.2 (Tab 8B/T1.112.1) 
    
> > 
> > > > 
> > > > > Do we mantain connection context at SG and no connection context at ASP
> > > > > level?
> > > > 
> > > > Connection context is referenced both at SG and ASP by DPC/DLR.
> > > > 
> > > > > Can a SUA user allocate or delete connection context?
> > > > 
> > > > Allocated with CORE/COAK, deallocated with RELRE/RELCO.
> > > > 
> > > > > Or these functions be RPC calls which are implemnentation dependent?
> > > > 
> > > > Not implementation dependent.  Completely within the context of SCCP.
> > > > 
> > > > > Does any SCCP Connection Oriented functionality is required on ASP  side in
> > > > > addition to what is defined in SUA draft. 
> > > > 
> > > > No.
> > > How about context management? What if SUA is acting as a internudiate on 
> > > ASP with IPSP. Are you saying this cannot happen. I think you need to 
> > > SCCP spec. Don't you think these cases can be much better handled by 
> > > SCCP/M3UA.
> > 
> > It am speaking of SG/ASP, not relay.  Relay is prohibited in M3UA by the RFC.
> > It cannot handle it at all.  SUA has relay built in.
> I don't know why m3ua will need to perform relay here. In this case relay 
> will be done by SCCP which is very well defined in SCCP spec.

SCCP cannot relay for an SCCP-User without also performing MTP transfer.
MTP transfer requires STP functionality.  M3UA forbids STP functionality
at the M3UA IPSP.  M3UA IPSPs are point-to-point only.  M3UA cannot
support SCCP relay.

> > > > 
> > > > > 2. Problem similar to shring connection state. If one ASP sends a Connect 
> > > > > Request what is the gurantee the same will receive Connection Confirm. 
> > > > 
> > > > Base on the local reference in the CR.  SG sends CC to correct ASP.
> > > > 
> > > > > This is much easier to handle with SCCP/M3UA.
> > > > 
> > > > Very wrong.
> > > Why? How can you say SUA is better solution than M3UA/SCCP.
> > 
> > How can you say M3UA/SCCP is better solution than SUA?
> > 
> > > > 
> > > > > I think there are much more implementation dependent issues with SUA.
> > > > 
> > > > I think you just don't have a good understanding the SUA standard yet.
> > > > 
> > > > There are no issues other than DRN Label with multiple SGs under failure.
> > > > draft-bidulock-sigtran-regext-01.txt submitted to the I-D editor several days
> > > > ago which provides better solution for multiple SG case than DRN Labels.  You
> > > > can pick up a copy at
> > > > 
> > > > 	http://www.openss7.org/sigtran01.html
> > > > 
> > > > until it appears on the I-D server.
> > > I am talking about SUA draft not indvidual submissions.
> > > > 
> > > > But I think you should take some time to read carefully through the SUA spec,
> > > > ask some questions, and understand it well before making such sweeping
> > > > statements.
> > > Sometime  back in our earlier discussion you yourself agreed that SUA was 
> > > weak in supporting CO and also you mentioned that AMF was not clearly 
> > > described. I don't know if things have changed much in SUA draft since 
> > > then. You can check the mailing list on that.
> > 
> > Weak on DRN Labels for multiple SG as STP case.  Tolga can't even get class 0
> > working on multiple SG for M3UA, so SUA is still far superior.
> I need to catch up with what tolga is doing in this case. But I don't 
> understand how M3UA is preventing SCCP functions. M3UA definition should 
> not depend on its user. But IMHO we should not try to define things which can 
> be done in implementation dependent way and do not hurt interoperability. 

What things are those?

>  
>  > 
> > > I am not making any aweeping statements nut only saying that 
> > > IMO SCCP/M3UA better capturees SCCP Connection Oriented functionality in 
> > > sigtran world.
> > 
> > M3UA does not capture it at all.  M3UA cannot support class 2 or 3 routing
> > keys.  SUA can.
> I don't understand why m3ua needs to support SCCP specific routing 
> key. We had class 2 working with M3UA with no 
> problems. How can M3UA impose limitations on SCCP functionality. If this 
> is the case then may be SCCP needs to be fixed. But I don't think that is 
> the case.

All classes work with SUA with no problem.

M3UA imposes limitations on SCCP functionality by being unable to
support MTP transfer at the IPSP, making it impossible to support
SCCP relay on an M3UA IPSP or ASP.  SUA supports SCCP relay on both
IPSP and ASP.

--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  Sun Jan 12 23:10: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 XAA20627
	for <sigtran-archive@odin.ietf.org>; Sun, 12 Jan 2003 23:10:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D4NdO12512
	for sigtran-archive@odin.ietf.org; Sun, 12 Jan 2003 23:23:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D4MpJ12483;
	Sun, 12 Jan 2003 23:22:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D4KZJ12436
	for <sigtran@optimus.ietf.org>; Sun, 12 Jan 2003 23:20:35 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20597
	for <sigtran@ietf.org>; Sun, 12 Jan 2003 23:06:36 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0D49maN013425;
	Sun, 12 Jan 2003 22:09:49 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id IAA06781; Mon, 13 Jan 2003 08:38:47 -0500 (GMT)
Message-ID: <3E223C19.B0A34CDA@axes-mach01.usa.alcatel.com>
Date: Mon, 13 Jan 2003 09:40:02 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: Latha <latha@indts.com>, sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
References: <F73B646FCC01D5118F530002B32C3372DB3021@INDTS_FS> <20030110010850.F8782@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

>>> Then the ASP could hardly be expected to correlate multiple ASPAC ACK
>>> responses to multiple ASPAC requests.  If IID is placed in ASPAC, then
>>> the SG MUST respond with IID in ASPAC ACK to be sure that the ASP can
>>> correlate the response with the request.


If SG is not Active for any of the IIDs received in ASPAC, then how will the SG respond with any IID. Moreover,
since IIDs are a MUST in ASPAC ACK when IIDs are placed in ASPAC, then IIDs in ASPAC ACK should have been
semi-optional.

--Srini

"Brian F. G. Bidulock" wrote:

> Latha,
>
> Latha wrote:                                                                         (Fri, 10 Jan 2003 13:17:33)
> > Hi,
> > we have a doubt regarding the IIDs exchanged in the ASP Active and
> > ASP ACTIVE ACK
> > If ASP Active is sent with a specific IId/IIds, is it mandatory for the SGF
> > to send ASP Active Ack with the specified IId/IIds.
> >
> > Or can it send the Ack without any IId. If that is the case then ASP has to
> > maintain the list of IIds on which the Active is sent.
> > Also what should the action on MGC side if it receives ASP Active Ack
> > without any IId as a response for ASP Active sent with a specific IId/IIds.
> > thanks
> > latha
> >
> Then the ASP could hardly be expected to correlate multiple ASPAC ACK
> responses to multiple ASPAC requests.  If IID is placed in ASPAC, then
> the SG MUST respond with IID in ASPAC ACK to be sure that the ASP can
> correlate the response with the request.
>
> --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 mailnull@www1.ietf.org  Sun Jan 12 23:37: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 XAA21027
	for <sigtran-archive@odin.ietf.org>; Sun, 12 Jan 2003 23:37:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D4oeW13833
	for sigtran-archive@odin.ietf.org; Sun, 12 Jan 2003 23:50:40 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D4o8J13814;
	Sun, 12 Jan 2003 23:50:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D4nFJ13782
	for <sigtran@optimus.ietf.org>; Sun, 12 Jan 2003 23:49:15 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21014
	for <sigtran@ietf.org>; Sun, 12 Jan 2003 23:35:16 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:eu3UxlBWVoFxSC6uMoiT6IkJF23xarUb@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0D4cZD06134;
	Sun, 12 Jan 2003 21:38:35 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0D4cZK31815;
	Sun, 12 Jan 2003 21:38:35 -0700
Date: Sun, 12 Jan 2003 21:38:35 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: Latha <latha@indts.com>, sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030112213835.A31712@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	Latha <latha@indts.com>, sigtran@ietf.org
References: <F73B646FCC01D5118F530002B32C3372DB3021@INDTS_FS> <20030110010850.F8782@openss7.org> <3E223C19.B0A34CDA@axes-mach01.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: <3E223C19.B0A34CDA@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Mon, Jan 13, 2003 at 09:40:02AM +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>

ksrinivas,

ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 09:40:02)
> Brian,
> 
> >>> Then the ASP could hardly be expected to correlate multiple ASPAC ACK
> >>> responses to multiple ASPAC requests.  If IID is placed in ASPAC, then
> >>> the SG MUST respond with IID in ASPAC ACK to be sure that the ASP can
> >>> correlate the response with the request.
> 
> 
> If SG is not Active for any of the IIDs received in ASPAC, then how
> will the SG respond with any IID.

ERR("Invalid Interface Identifier") containing the IIDs in the ASPAC
for which the SG refuses to activate.

> Moreover, since IIDs are a MUST in ASPAC ACK when IIDs are placed in
> ASPAC, then IIDs in ASPAC ACK should have been semi-optional.

IID is optional in ASPAC Ack.  The smart SG implementation will 
included the interface identifiers in the ASPAC Ack when they were
provided in the ASPAC, whether it is required with a MUST or not.

SGs that don't do so will not support multiple outstanding ASPAC
messages very well (because the ASP cannot necessarily correlate
the ASPAC Acks with the ASPACs).  But there is no requirement for
an ASP to send multiple concurrent ASPACs.  In fact, it is possible
to perform multiple activations in a single ASPAC, so that is not
som much of a limitation.

So the SG implementation would be smart to always put IID in ASPAC Ack
when it was included in ASPAC, and the ASP would be smart to never
send multiple concurrent ASPACs requiring correlation of the
subsequently received ASPAC Acks.

Perhaps it would be a good idea to mention the above in the IUA-IG.

--brian

> 
> --Srini
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Latha,
> >
> > Latha wrote:                                                                         (Fri, 10 Jan 2003 13:17:33)
> > > Hi,
> > > we have a doubt regarding the IIDs exchanged in the ASP Active and
> > > ASP ACTIVE ACK
> > > If ASP Active is sent with a specific IId/IIds, is it mandatory for the SGF
> > > to send ASP Active Ack with the specified IId/IIds.
> > >
> > > Or can it send the Ack without any IId. If that is the case then ASP has to
> > > maintain the list of IIds on which the Active is sent.
> > > Also what should the action on MGC side if it receives ASP Active Ack
> > > without any IId as a response for ASP Active sent with a specific IId/IIds.
> > > thanks
> > > latha
> > >
> > Then the ASP could hardly be expected to correlate multiple ASPAC ACK
> > responses to multiple ASPAC requests.  If IID is placed in ASPAC, then
> > the SG MUST respond with IID in ASPAC ACK to be sure that the ASP can
> > correlate the response with the request.
> >
> > --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 mailnull@www1.ietf.org  Mon Jan 13 00:34: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 AAA21869
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 00:34:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D5m8L16520
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 00:48:08 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D5lcJ16507;
	Mon, 13 Jan 2003 00:47:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D5kiJ16446
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 00:46:44 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21847
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 00:32:42 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0D5ZnBE002315;
	Sun, 12 Jan 2003 23:35:55 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id KAA08464; Mon, 13 Jan 2003 10:04:27 -0500 (GMT)
Message-ID: <3E22502E.2F951D7F@axes-mach01.usa.alcatel.com>
Date: Mon, 13 Jan 2003 11:05:43 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: Latha <latha@indts.com>, sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
References: <F73B646FCC01D5118F530002B32C3372DB3021@INDTS_FS> <20030110010850.F8782@openss7.org> <3E223C19.B0A34CDA@axes-mach01.usa.alcatel.com> <20030112213835.A31712@openss7.org>
Content-Type: multipart/alternative;
 boundary="------------BC05EC1EF6C7269E68794AAE"
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>


--------------BC05EC1EF6C7269E68794AAE
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 7bit



"Brian F. G. Bidulock" wrote:

> ksrinivas,
>
> ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 09:40:02)
> > Brian,
> >
> > >>> Then the ASP could hardly be expected to correlate multiple ASPAC ACK
> > >>> responses to multiple ASPAC requests.  If IID is placed in ASPAC, then
> > >>> the SG MUST respond with IID in ASPAC ACK to be sure that the ASP can
> > >>> correlate the response with the request.
> >
> >
> > If SG is not Active for any of the IIDs received in ASPAC, then how
> > will the SG respond with any IID.
>
> ERR("Invalid Interface Identifier") containing the IIDs in the ASPAC
> for which the SG refuses to activate.
>

RFC 3057 says,

The "Invalid Interface Identifier" error would be sent by a SG if an ASP sends a message with an invalid (unconfigured)
Interface Identifier value.

So, what the SG refuses to activate be treated as unconfigured?. The "Invalid Interface Identifier" error might mean a
different thing at the ASP.(i.e., IIDs configured at SG and ASP are inconsistent).

IMO, the Active and Active Ack procedures should be as follows:

1. ASP can send Active msg with or without IIDs.
2. ASP shall never send multiple concurrent ASPACs as there is no correlation identifier.
3. The ASP should be smart enough to remember whether it has sent any IIDs in the Active message.
4. If ASP sends Active without IIDs,
      the SGP shall respond with Active Ack without IIDs, if the SG activates all the IIDs. Also, the SGP shall respond
with Active Ack with IIDs only that are activated.
5. If ASP sends Active with IIDs,
      the SGP shall respond with Active Ack with IIDs only that are activated. Also, the SGP shall respond with Active
Ack without IIDs, if the SG refuses to activate all the IIDs.


--Srini

>
> > Moreover, since IIDs are a MUST in ASPAC ACK when IIDs are placed in
> > ASPAC, then IIDs in ASPAC ACK should have been semi-optional.
>
> IID is optional in ASPAC Ack.  The smart SG implementation will
> included the interface identifiers in the ASPAC Ack when they were
> provided in the ASPAC, whether it is required with a MUST or not.
>
> SGs that don't do so will not support multiple outstanding ASPAC
> messages very well (because the ASP cannot necessarily correlate
> the ASPAC Acks with the ASPACs).  But there is no requirement for
> an ASP to send multiple concurrent ASPACs.  In fact, it is possible
> to perform multiple activations in a single ASPAC, so that is not
> som much of a limitation.
>
> So the SG implementation would be smart to always put IID in ASPAC Ack
> when it was included in ASPAC, and the ASP would be smart to never
> send multiple concurrent ASPACs requiring correlation of the
> subsequently received ASPAC Acks.
>
> Perhaps it would be a good idea to mention the above in the IUA-IG.
>
> --brian
>
> >
> > --Srini
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > Latha,
> > >
> > > Latha wrote:                                                                         (Fri, 10 Jan 2003 13:17:33)
> > > > Hi,
> > > > we have a doubt regarding the IIDs exchanged in the ASP Active and
> > > > ASP ACTIVE ACK
> > > > If ASP Active is sent with a specific IId/IIds, is it mandatory for the SGF
> > > > to send ASP Active Ack with the specified IId/IIds.
> > > >
> > > > Or can it send the Ack without any IId. If that is the case then ASP has to
> > > > maintain the list of IIds on which the Active is sent.
> > > > Also what should the action on MGC side if it receives ASP Active Ack
> > > > without any IId as a response for ASP Active sent with a specific IId/IIds.
> > > > thanks
> > > > latha
> > > >
> > > Then the ASP could hardly be expected to correlate multiple ASPAC ACK
> > > responses to multiple ASPAC requests.  If IID is placed in ASPAC, then
> > > the SG MUST respond with IID in ASPAC ACK to be sure that the ASP can
> > > correlate the response with the request.
> > >
> > > --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/

--------------BC05EC1EF6C7269E68794AAE
Content-Type: text/html; charset=x-user-defined
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<p>"Brian F. G. Bidulock" wrote:
<blockquote TYPE=CITE>ksrinivas,
<p>ksrinivas wrote:&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
(Mon, 13 Jan 2003 09:40:02)
<br>> Brian,
<br>>
<br>> >>> Then the ASP could hardly be expected to correlate multiple ASPAC
ACK
<br>> >>> responses to multiple ASPAC requests.&nbsp; If IID is placed
in ASPAC, then
<br>> >>> the SG MUST respond with IID in ASPAC ACK to be sure that the
ASP can
<br>> >>> correlate the response with the request.
<br>>
<br>>
<br>> If SG is not Active for any of the IIDs received in ASPAC, then how
<br>> will the SG respond with any IID.
<p>ERR("Invalid Interface Identifier") containing the IIDs in the ASPAC
<br>for which the SG refuses to activate.
<br>&nbsp;</blockquote>
RFC 3057 says,
<p>The "Invalid Interface Identifier" error would be sent by a SG if an
ASP sends a message with an invalid (<u>unconfigured</u>) Interface Identifier
value.
<p>So, what the SG refuses to activate be treated as unconfigured?. The
"Invalid Interface Identifier" error might mean a different thing at the
ASP.(i.e., IIDs configured at SG and ASP are inconsistent).
<p>IMO, the Active and Active Ack procedures should be as follows:
<p>1. ASP can send Active msg with or without IIDs.
<br>2. ASP shall never send multiple concurrent ASPACs as there is no correlation
identifier.
<br>3. The ASP should be smart enough to remember whether it has sent any
IIDs in the Active message.
<br>4. If ASP sends Active <b>without</b> IIDs,
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the SGP shall respond with Active Ack
without IIDs, if the SG activates all the IIDs. Also, the SGP shall respond
with Active Ack with IIDs only that are activated.
<br>5. If ASP sends Active <b>with</b> IIDs,
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the SGP shall respond with Active Ack
with IIDs only that are activated. Also, the SGP shall respond with Active
Ack without IIDs, if the SG refuses to activate all the IIDs.
<br>&nbsp;
<p>--Srini
<blockquote TYPE=CITE>&nbsp;
<br>> Moreover, since IIDs are a MUST in ASPAC ACK when IIDs are placed
in
<br>> ASPAC, then IIDs in ASPAC ACK should have been semi-optional.
<p>IID is optional in ASPAC Ack.&nbsp; The smart SG implementation will
<br>included the interface identifiers in the ASPAC Ack when they were
<br>provided in the ASPAC, whether it is required with a MUST or not.
<p>SGs that don't do so will not support multiple outstanding ASPAC
<br>messages very well (because the ASP cannot necessarily correlate
<br>the ASPAC Acks with the ASPACs).&nbsp; But there is no requirement
for
<br>an ASP to send multiple concurrent ASPACs.&nbsp; In fact, it is possible
<br>to perform multiple activations in a single ASPAC, so that is not
<br>som much of a limitation.
<p>So the SG implementation would be smart to always put IID in ASPAC Ack
<br>when it was included in ASPAC, and the ASP would be smart to never
<br>send multiple concurrent ASPACs requiring correlation of the
<br>subsequently received ASPAC Acks.
<p>Perhaps it would be a good idea to mention the above in the IUA-IG.
<p>--brian
<p>>
<br>> --Srini
<br>>
<br>> "Brian F. G. Bidulock" wrote:
<br>>
<br>> > Latha,
<br>> >
<br>> > Latha wrote:&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;&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;
(Fri, 10 Jan 2003 13:17:33)
<br>> > > Hi,
<br>> > > we have a doubt regarding the IIDs exchanged in the ASP Active
and
<br>> > > ASP ACTIVE ACK
<br>> > > If ASP Active is sent with a specific IId/IIds, is it mandatory
for the SGF
<br>> > > to send ASP Active Ack with the specified IId/IIds.
<br>> > >
<br>> > > Or can it send the Ack without any IId. If that is the case then
ASP has to
<br>> > > maintain the list of IIds on which the Active is sent.
<br>> > > Also what should the action on MGC side if it receives ASP Active
Ack
<br>> > > without any IId as a response for ASP Active sent with a specific
IId/IIds.
<br>> > > thanks
<br>> > > latha
<br>> > >
<br>> > Then the ASP could hardly be expected to correlate multiple ASPAC
ACK
<br>> > responses to multiple ASPAC requests.&nbsp; If IID is placed in
ASPAC, then
<br>> > the SG MUST respond with IID in ASPAC ACK to be sure that the ASP
can
<br>> > correlate the response with the request.
<br>> >
<br>> > --brian
<br>> >
<br>> > --
<br>> > Brian F. G. Bidulock
<br>> > bidulock@openss7.org
<br>> > <a href="http://www.openss7.org/">http://www.openss7.org/</a>
<br>> > _______________________________________________
<br>> > Sigtran mailing list
<br>> > Sigtran@ietf.org
<br>> > <a href="https://www1.ietf.org/mailman/listinfo/sigtran">https://www1.ietf.org/mailman/listinfo/sigtran</a>
<p>--
<br>Brian F. G. Bidulock
<br>bidulock@openss7.org
<br><a href="http://www.openss7.org/">http://www.openss7.org/</a></blockquote>
</html>

--------------BC05EC1EF6C7269E68794AAE--

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



From mailnull@www1.ietf.org  Mon Jan 13 00:49: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 AAA22003
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 00:49:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D62ZJ16905
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 01:02:35 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D629J16886;
	Mon, 13 Jan 2003 01:02:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D61DJ16855
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 01:01:13 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21979
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 00:47:11 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:pyoPUQqYDzAPAYLjJty5GZDTepn6q2hD@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0D5oVD07081;
	Sun, 12 Jan 2003 22:50:31 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0D5oVZ00961;
	Sun, 12 Jan 2003 22:50:31 -0700
Date: Sun, 12 Jan 2003 22:50:30 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: Latha <latha@indts.com>, sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030112225030.A731@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	Latha <latha@indts.com>, sigtran@ietf.org
References: <F73B646FCC01D5118F530002B32C3372DB3021@INDTS_FS> <20030110010850.F8782@openss7.org> <3E223C19.B0A34CDA@axes-mach01.usa.alcatel.com> <20030112213835.A31712@openss7.org> <3E22502E.2F951D7F@axes-mach01.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: <3E22502E.2F951D7F@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Mon, Jan 13, 2003 at 11:05:43AM +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>

ksrinivas,

Your proposal represents a deviation from the RFC that I do not agree with.
The current RFC does not permit the SG to perform a "partial activation" of
some IIDs in a set.  Both in the ASPAC and ASPAC Ack, a subset of IIDs
represents the entire set of IIDs indicated by that subset.

--brian

ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 11:05:43)
> 
>    IMO, the Active and Active Ack procedures should be as follows:
> 
>    1. ASP can send Active msg with or without IIDs.
>    2.  ASP  shall  never  send  multiple concurrent ASPACs as there is no
>    correlation identifier.
>    3.  The ASP should be smart enough to remember whether it has sent any
>    IIDs in the Active message.
>    4. If ASP sends Active without IIDs,
>           the  SGP  shall respond with Active Ack without IIDs, if the SG
>    activates  all  the  IIDs. Also, the SGP shall respond with Active Ack
>    with IIDs only that are activated.
>    5. If ASP sends Active with IIDs,
>           the  SGP  shall respond with Active Ack with IIDs only that are
>    activated.  Also,  the SGP shall respond with Active Ack without IIDs,
>    if the SG refuses to activate all the IIDs.
> 
>    --Srini
> 

-- 
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 Jan 13 01:45: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 BAA22651
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 01:45:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D6xI719701
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 01:59:18 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D6wnJ19656;
	Mon, 13 Jan 2003 01:58:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D6vcJ19610
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 01:57:38 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22606
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 01:43:35 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0D6kmOZ025922;
	Mon, 13 Jan 2003 00:46:53 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id LAA10007; Mon, 13 Jan 2003 11:14:55 -0500 (GMT)
Message-ID: <3E2260AF.4358FBB1@axes-mach01.usa.alcatel.com>
Date: Mon, 13 Jan 2003 12:16:08 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: Latha <latha@indts.com>, sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
References: <F73B646FCC01D5118F530002B32C3372DB3021@INDTS_FS> <20030110010850.F8782@openss7.org> <3E223C19.B0A34CDA@axes-mach01.usa.alcatel.com> <20030112213835.A31712@openss7.org> <3E22502E.2F951D7F@axes-mach01.usa.alcatel.com> <20030112225030.A731@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

     If more than one subset of IIDs are sent in ASP AC to SG, still the SG may wish to activate only a few
subsets fully.

--Sini

"Brian F. G. Bidulock" wrote:

> ksrinivas,
>
> Your proposal represents a deviation from the RFC that I do not agree with.
> The current RFC does not permit the SG to perform a "partial activation" of
> some IIDs in a set.  Both in the ASPAC and ASPAC Ack, a subset of IIDs
> represents the entire set of IIDs indicated by that subset.
>
> --brian
>
> ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 11:05:43)
> >
> >    IMO, the Active and Active Ack procedures should be as follows:
> >
> >    1. ASP can send Active msg with or without IIDs.
> >    2.  ASP  shall  never  send  multiple concurrent ASPACs as there is no
> >    correlation identifier.
> >    3.  The ASP should be smart enough to remember whether it has sent any
> >    IIDs in the Active message.
> >    4. If ASP sends Active without IIDs,
> >           the  SGP  shall respond with Active Ack without IIDs, if the SG
> >    activates  all  the  IIDs. Also, the SGP shall respond with Active Ack
> >    with IIDs only that are activated.
> >    5. If ASP sends Active with IIDs,
> >           the  SGP  shall respond with Active Ack with IIDs only that are
> >    activated.  Also,  the SGP shall respond with Active Ack without IIDs,
> >    if the SG refuses to activate all the IIDs.
> >
> >    --Srini
> >
>
> --
> 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 mailnull@www1.ietf.org  Mon Jan 13 01:47: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 BAA22705
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 01:47:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D71GJ19879
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 02:01:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D717J19855;
	Mon, 13 Jan 2003 02:01:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D70mJ19808
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 02:00:48 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22673
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 01:46:45 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:gW/ZdP7aznLLym40LOksoTwcNBe9JIOk@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0D6o5D07831;
	Sun, 12 Jan 2003 23:50:05 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0D6o4w02540;
	Sun, 12 Jan 2003 23:50:04 -0700
Date: Sun, 12 Jan 2003 23:50:04 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: Latha <latha@indts.com>, sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030112235004.A2513@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	Latha <latha@indts.com>, sigtran@ietf.org
References: <F73B646FCC01D5118F530002B32C3372DB3021@INDTS_FS> <20030110010850.F8782@openss7.org> <3E223C19.B0A34CDA@axes-mach01.usa.alcatel.com> <20030112213835.A31712@openss7.org> <3E22502E.2F951D7F@axes-mach01.usa.alcatel.com> <20030112225030.A731@openss7.org> <3E2260AF.4358FBB1@axes-mach01.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: <3E2260AF.4358FBB1@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Mon, Jan 13, 2003 at 12:16:08PM +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>

ksrinivas,

But that is currently not supported.

--brian

ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 12:16:08)
> Brian,
> 
>      If more than one subset of IIDs are sent in ASP AC to SG, still the SG may wish to activate only a few
> subsets fully.
> 
> --Sini
> 
> "Brian F. G. Bidulock" wrote:
> 
> > ksrinivas,
> >
> > Your proposal represents a deviation from the RFC that I do not agree with.
> > The current RFC does not permit the SG to perform a "partial activation" of
> > some IIDs in a set.  Both in the ASPAC and ASPAC Ack, a subset of IIDs
> > represents the entire set of IIDs indicated by that subset.
> >
> > --brian
> >
> > ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 11:05:43)
> > >
> > >    IMO, the Active and Active Ack procedures should be as follows:
> > >
> > >    1. ASP can send Active msg with or without IIDs.
> > >    2.  ASP  shall  never  send  multiple concurrent ASPACs as there is no
> > >    correlation identifier.
> > >    3.  The ASP should be smart enough to remember whether it has sent any
> > >    IIDs in the Active message.
> > >    4. If ASP sends Active without IIDs,
> > >           the  SGP  shall respond with Active Ack without IIDs, if the SG
> > >    activates  all  the  IIDs. Also, the SGP shall respond with Active Ack
> > >    with IIDs only that are activated.
> > >    5. If ASP sends Active with IIDs,
> > >           the  SGP  shall respond with Active Ack with IIDs only that are
> > >    activated.  Also,  the SGP shall respond with Active Ack without IIDs,
> > >    if the SG refuses to activate all the IIDs.
> > >
> > >    --Srini
> > >
> >
> > --
> > 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 mailnull@www1.ietf.org  Mon Jan 13 01:55:25 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 BAA22772
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 01:55:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D78vb24503
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 02:08:57 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D787J24082;
	Mon, 13 Jan 2003 02:08:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D776J23187
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 02:07:06 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22754
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 01:52:38 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0D6tKBE006849;
	Mon, 13 Jan 2003 00:55:22 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id LAA10193; Mon, 13 Jan 2003 11:23:33 -0500 (GMT)
Message-ID: <3E2262BA.C3A37DE8@axes-mach01.usa.alcatel.com>
Date: Mon, 13 Jan 2003 12:24:50 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: Latha <latha@indts.com>, sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
References: <F73B646FCC01D5118F530002B32C3372DB3021@INDTS_FS> <20030110010850.F8782@openss7.org> <3E223C19.B0A34CDA@axes-mach01.usa.alcatel.com> <20030112213835.A31712@openss7.org> <3E22502E.2F951D7F@axes-mach01.usa.alcatel.com> <20030112225030.A731@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

    If SG has to send the same set of IIDs back to the ASP in an ASPAC Ack, the need for IIDs in ASPAC Ack is
insignificant.

"Brian F. G. Bidulock" wrote:

> ksrinivas,
>
> Your proposal represents a deviation from the RFC that I do not agree with.
> The current RFC does not permit the SG to perform a "partial activation" of
> some IIDs in a set.  Both in the ASPAC and ASPAC Ack, a subset of IIDs
> represents the entire set of IIDs indicated by that subset.
>
> --brian
>
> ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 11:05:43)
> >
> >    IMO, the Active and Active Ack procedures should be as follows:
> >
> >    1. ASP can send Active msg with or without IIDs.
> >    2.  ASP  shall  never  send  multiple concurrent ASPACs as there is no
> >    correlation identifier.
> >    3.  The ASP should be smart enough to remember whether it has sent any
> >    IIDs in the Active message.
> >    4. If ASP sends Active without IIDs,
> >           the  SGP  shall respond with Active Ack without IIDs, if the SG
> >    activates  all  the  IIDs. Also, the SGP shall respond with Active Ack
> >    with IIDs only that are activated.
> >    5. If ASP sends Active with IIDs,
> >           the  SGP  shall respond with Active Ack with IIDs only that are
> >    activated.  Also,  the SGP shall respond with Active Ack without IIDs,
> >    if the SG refuses to activate all the IIDs.
> >
> >    --Srini
> >
>
> --
> 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 mailnull@www1.ietf.org  Mon Jan 13 02:13: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 CAA02864
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 02:13:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D7QbZ31498
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 02:26:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D7QAJ31484;
	Mon, 13 Jan 2003 02:26:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D7P4J31462
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 02:25:04 -0500
Received: from mink.ecitele.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02849
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 02:10:59 -0500 (EST)
From: Lev.Finkel@ecitele.com
Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125])
	by mink.ecitele.com (8.9.1a/8.9.1) with ESMTP id JAA15296;
	Mon, 13 Jan 2003 09:09:01 +0200 (IST)
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
To: ksrini@axes-mach01.usa.alcatel.com
Cc: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OF8E8256BA.404F2C6C-ONC2256CAD.002677F5@ecitele.com>
Date: Mon, 13 Jan 2003 09:13:32 +0200
X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at
 01/13/2003 09:14:15 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>


Shrini,

- point 4 of you proposal may cause a problem. Suppose ASP has lost the
data and likes to bring all the interfaces back to active state. It sends
the ASP_ACTIVE without IID. If SG acknowledges just previously inactive
interfaces, the ASP will consider as active just these acknowledged
interfaces, and as inactive all interfaces that already active in SG. This
is a deadlock.
- see IUA implementation guide for point 5 of your proposal

I do not see a reason to change the RFC in this aspect.

Regards,
Lev



                                                                                                           
                      "Brian F. G.                                                                         
                      Bidulock"                To:      ksrinivas <ksrini@axes-mach01.usa.alcatel.com>     
                      <bidulock@openss         cc:      Latha <latha@indts.com>, sigtran@ietf.org          
                      7.org>                   Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK     
                      Sent by:                                                                             
                      sigtran-admin@ie                                                                     
                      tf.org                                                                               
                                                                                                           
                                                                                                           
                      13/01/03 07:50                                                                       
                      Please respond                                                                       
                      to bidulock                                                                          
                                                                                                           
                                                                                                           



ksrinivas,

Your proposal represents a deviation from the RFC that I do not agree with.
The current RFC does not permit the SG to perform a "partial activation" of
some IIDs in a set.  Both in the ASPAC and ASPAC Ack, a subset of IIDs
represents the entire set of IIDs indicated by that subset.

--brian

ksrinivas wrote:
(Mon, 13 Jan 2003 11:05:43)
>
>    IMO, the Active and Active Ack procedures should be as follows:
>
>    1. ASP can send Active msg with or without IIDs.
>    2.  ASP  shall  never  send  multiple concurrent ASPACs as there is no
>    correlation identifier.
>    3.  The ASP should be smart enough to remember whether it has sent any
>    IIDs in the Active message.
>    4. If ASP sends Active without IIDs,
>           the  SGP  shall respond with Active Ack without IIDs, if the SG
>    activates  all  the  IIDs. Also, the SGP shall respond with Active Ack
>    with IIDs only that are activated.
>    5. If ASP sends Active with IIDs,
>           the  SGP  shall respond with Active Ack with IIDs only that are
>    activated.  Also,  the SGP shall respond with Active Ack without IIDs,
>    if the SG refuses to activate all the IIDs.
>
>    --Srini
>

--
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 mailnull@www1.ietf.org  Mon Jan 13 02: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 CAA03035
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 02:21:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D7Yel32031
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 02:34:40 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D7Y9J32006;
	Mon, 13 Jan 2003 02:34:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D7X3J31974
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 02:33:03 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02960
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 02:18:59 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:QtmLzRnurP5Ib8stKgmJIDWFVYhVeW5U@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0D7MKD08318;
	Mon, 13 Jan 2003 00:22:20 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0D7MJ103165;
	Mon, 13 Jan 2003 00:22:19 -0700
Date: Mon, 13 Jan 2003 00:22:19 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: Latha <latha@indts.com>, sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030113002219.A2971@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	Latha <latha@indts.com>, sigtran@ietf.org
References: <F73B646FCC01D5118F530002B32C3372DB3021@INDTS_FS> <20030110010850.F8782@openss7.org> <3E223C19.B0A34CDA@axes-mach01.usa.alcatel.com> <20030112213835.A31712@openss7.org> <3E22502E.2F951D7F@axes-mach01.usa.alcatel.com> <20030112225030.A731@openss7.org> <3E2262BA.C3A37DE8@axes-mach01.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: <3E2262BA.C3A37DE8@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Mon, Jan 13, 2003 at 12:24:50PM +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>

ksrinivas,

But it doesn't have to: IIDs in ASPAC Ack is optional in the RFC.

--brian

ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 12:24:50)
> Brian,
> 
>     If SG has to send the same set of IIDs back to the ASP in an ASPAC Ack, the need for IIDs in ASPAC Ack is
> insignificant.
> 
> "Brian F. G. Bidulock" wrote:
> 
> > ksrinivas,
> >
> > Your proposal represents a deviation from the RFC that I do not agree with.
> > The current RFC does not permit the SG to perform a "partial activation" of
> > some IIDs in a set.  Both in the ASPAC and ASPAC Ack, a subset of IIDs
> > represents the entire set of IIDs indicated by that subset.
> >
> > --brian
> >
> > ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 11:05:43)
> > >
> > >    IMO, the Active and Active Ack procedures should be as follows:
> > >
> > >    1. ASP can send Active msg with or without IIDs.
> > >    2.  ASP  shall  never  send  multiple concurrent ASPACs as there is no
> > >    correlation identifier.
> > >    3.  The ASP should be smart enough to remember whether it has sent any
> > >    IIDs in the Active message.
> > >    4. If ASP sends Active without IIDs,
> > >           the  SGP  shall respond with Active Ack without IIDs, if the SG
> > >    activates  all  the  IIDs. Also, the SGP shall respond with Active Ack
> > >    with IIDs only that are activated.
> > >    5. If ASP sends Active with IIDs,
> > >           the  SGP  shall respond with Active Ack with IIDs only that are
> > >    activated.  Also,  the SGP shall respond with Active Ack without IIDs,
> > >    if the SG refuses to activate all the IIDs.
> > >
> > >    --Srini
> > >
> >
> > --
> > 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 mailnull@www1.ietf.org  Mon Jan 13 02:33: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 CAA03384
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 02:33:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D7lWW00918
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 02:47:32 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D7lCJ00896;
	Mon, 13 Jan 2003 02:47:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D7koJ00849
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 02:46:50 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03360
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 02:32:23 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0D7Z9aN025733;
	Mon, 13 Jan 2003 01:35:10 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id MAA00702; Mon, 13 Jan 2003 12:04:08 -0500 (GMT)
Message-ID: <3E226C37.3811AA5B@axes-mach01.usa.alcatel.com>
Date: Mon, 13 Jan 2003 13:05:20 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Lev.Finkel@ecitele.com
CC: sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
References: <OF8E8256BA.404F2C6C-ONC2256CAD.002677F5@ecitele.com>
Content-Type: text/plain; charset=x-user-defined
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

Lev,

>>> - point 4 of you proposal may cause a problem. Suppose ASP has lost the
>>> data and likes to bring all the interfaces back to active state. It sends
>>> the ASP_ACTIVE without IID. If SG acknowledges just previously inactive
>>> interfaces, the ASP will consider as active just these acknowledged
>>> interfaces, and as inactive all interfaces that already active in SG. This
>>> is a deadlock.

      Why does SG acknowledges just previously inactive interfaces only? IMO, it should acknowledge with
all the IIDs that are currently active at the SG, only if the list is partial. Otherwise, if all the
configured IIDs are Active at the SG, the SG should acknowledge without any IIDs(meaning, all the IIDs are
Active).

--Srini

Lev.Finkel@ecitele.com wrote:

> Shrini,
>
> - point 4 of you proposal may cause a problem. Suppose ASP has lost the
> data and likes to bring all the interfaces back to active state. It sends
> the ASP_ACTIVE without IID. If SG acknowledges just previously inactive
> interfaces, the ASP will consider as active just these acknowledged
> interfaces, and as inactive all interfaces that already active in SG. This
> is a deadlock.
> - see IUA implementation guide for point 5 of your proposal
>
> I do not see a reason to change the RFC in this aspect.
>
> Regards,
> Lev
>
>
>                       "Brian F. G.
>                       Bidulock"                To:      ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
>                       <bidulock@openss         cc:      Latha <latha@indts.com>, sigtran@ietf.org
>                       7.org>                   Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
>                       Sent by:
>                       sigtran-admin@ie
>                       tf.org
>
>
>                       13/01/03 07:50
>                       Please respond
>                       to bidulock
>
>
>
> ksrinivas,
>
> Your proposal represents a deviation from the RFC that I do not agree with.
> The current RFC does not permit the SG to perform a "partial activation" of
> some IIDs in a set.  Both in the ASPAC and ASPAC Ack, a subset of IIDs
> represents the entire set of IIDs indicated by that subset.
>
> --brian
>
> ksrinivas wrote:
> (Mon, 13 Jan 2003 11:05:43)
> >
> >    IMO, the Active and Active Ack procedures should be as follows:
> >
> >    1. ASP can send Active msg with or without IIDs.
> >    2.  ASP  shall  never  send  multiple concurrent ASPACs as there is no
> >    correlation identifier.
> >    3.  The ASP should be smart enough to remember whether it has sent any
> >    IIDs in the Active message.
> >    4. If ASP sends Active without IIDs,
> >           the  SGP  shall respond with Active Ack without IIDs, if the SG
> >    activates  all  the  IIDs. Also, the SGP shall respond with Active Ack
> >    with IIDs only that are activated.
> >    5. If ASP sends Active with IIDs,
> >           the  SGP  shall respond with Active Ack with IIDs only that are
> >    activated.  Also,  the SGP shall respond with Active Ack without IIDs,
> >    if the SG refuses to activate all the IIDs.
> >
> >    --Srini
> >
>
> --
> 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 mailnull@www1.ietf.org  Mon Jan 13 02:53: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 CAA03767
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 02:53:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D87AV02008
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 03:07:10 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D86uJ01828;
	Mon, 13 Jan 2003 03:06:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D851J01782
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 03:05:01 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03741
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 02:50:59 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0D7sAaN026625;
	Mon, 13 Jan 2003 01:54:11 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id MAA01098; Mon, 13 Jan 2003 12:23:08 -0500 (GMT)
Message-ID: <3E2270B1.B4DE4FCC@axes-mach01.usa.alcatel.com>
Date: Mon, 13 Jan 2003 13:24:25 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: Latha <latha@indts.com>, sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
References: <F73B646FCC01D5118F530002B32C3372DB3021@INDTS_FS> <20030110010850.F8782@openss7.org> <3E223C19.B0A34CDA@axes-mach01.usa.alcatel.com> <20030112213835.A31712@openss7.org> <3E22502E.2F951D7F@axes-mach01.usa.alcatel.com> <20030112225030.A731@openss7.org> <3E2262BA.C3A37DE8@axes-mach01.usa.alcatel.com> <20030113002219.A2971@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

     My meaning of "IIDs in ASPAC Ack is insignificant" is not that IIDs are optional or mandatory. IIDs serve no
purpose in the ASPAC Ack as per this thread.

--Srini.

"Brian F. G. Bidulock" wrote:

> ksrinivas,
>
> But it doesn't have to: IIDs in ASPAC Ack is optional in the RFC.
>
> --brian
>
> ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 12:24:50)
> > Brian,
> >
> >     If SG has to send the same set of IIDs back to the ASP in an ASPAC Ack, the need for IIDs in ASPAC Ack is
> > insignificant.
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > ksrinivas,
> > >
> > > Your proposal represents a deviation from the RFC that I do not agree with.
> > > The current RFC does not permit the SG to perform a "partial activation" of
> > > some IIDs in a set.  Both in the ASPAC and ASPAC Ack, a subset of IIDs
> > > represents the entire set of IIDs indicated by that subset.
> > >
> > > --brian
> > >
> > > ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 11:05:43)
> > > >
> > > >    IMO, the Active and Active Ack procedures should be as follows:
> > > >
> > > >    1. ASP can send Active msg with or without IIDs.
> > > >    2.  ASP  shall  never  send  multiple concurrent ASPACs as there is no
> > > >    correlation identifier.
> > > >    3.  The ASP should be smart enough to remember whether it has sent any
> > > >    IIDs in the Active message.
> > > >    4. If ASP sends Active without IIDs,
> > > >           the  SGP  shall respond with Active Ack without IIDs, if the SG
> > > >    activates  all  the  IIDs. Also, the SGP shall respond with Active Ack
> > > >    with IIDs only that are activated.
> > > >    5. If ASP sends Active with IIDs,
> > > >           the  SGP  shall respond with Active Ack with IIDs only that are
> > > >    activated.  Also,  the SGP shall respond with Active Ack without IIDs,
> > > >    if the SG refuses to activate all the IIDs.
> > > >
> > > >    --Srini
> > > >
> > >
> > > --
> > > 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 mailnull@www1.ietf.org  Mon Jan 13 03:16: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 DAA04053
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 03:16:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D8U9Z03295
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 03:30:09 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D8T9J03251;
	Mon, 13 Jan 2003 03:29:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D8SbJ03217
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 03:28:37 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04032
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 03:14:33 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:f1zNoGCkAx3i+9Shn53VOrXZBqnXR1RD@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0D8HqD09035;
	Mon, 13 Jan 2003 01:17:52 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0D8HpC04560;
	Mon, 13 Jan 2003 01:17:51 -0700
Date: Mon, 13 Jan 2003 01:17:51 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: Latha <latha@indts.com>, sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030113011751.A4492@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	Latha <latha@indts.com>, sigtran@ietf.org
References: <F73B646FCC01D5118F530002B32C3372DB3021@INDTS_FS> <20030110010850.F8782@openss7.org> <3E223C19.B0A34CDA@axes-mach01.usa.alcatel.com> <20030112213835.A31712@openss7.org> <3E22502E.2F951D7F@axes-mach01.usa.alcatel.com> <20030112225030.A731@openss7.org> <3E2262BA.C3A37DE8@axes-mach01.usa.alcatel.com> <20030113002219.A2971@openss7.org> <3E2270B1.B4DE4FCC@axes-mach01.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: <3E2270B1.B4DE4FCC@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Mon, Jan 13, 2003 at 01:24:25PM +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>

ksrinivas,

Well, they can be used by the ASP to correlate the received
ASPAC Ack with the sent ASPAC: which is not insignificant.

--brian

ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 13:24:25)
> Brian,
> 
>      My meaning of "IIDs in ASPAC Ack is insignificant" is not that IIDs are optional or mandatory. IIDs serve no
> purpose in the ASPAC Ack as per this thread.
> 
> --Srini.
> 
> "Brian F. G. Bidulock" wrote:
> 
> > ksrinivas,
> >
> > But it doesn't have to: IIDs in ASPAC Ack is optional in the RFC.
> >
> > --brian
> >
> > ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 12:24:50)
> > > Brian,
> > >
> > >     If SG has to send the same set of IIDs back to the ASP in an ASPAC Ack, the need for IIDs in ASPAC Ack is
> > > insignificant.
> > >
> > > "Brian F. G. Bidulock" wrote:
> > >
> > > > ksrinivas,
> > > >
> > > > Your proposal represents a deviation from the RFC that I do not agree with.
> > > > The current RFC does not permit the SG to perform a "partial activation" of
> > > > some IIDs in a set.  Both in the ASPAC and ASPAC Ack, a subset of IIDs
> > > > represents the entire set of IIDs indicated by that subset.
> > > >
> > > > --brian
> > > >
> > > > ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 11:05:43)
> > > > >
> > > > >    IMO, the Active and Active Ack procedures should be as follows:
> > > > >
> > > > >    1. ASP can send Active msg with or without IIDs.
> > > > >    2.  ASP  shall  never  send  multiple concurrent ASPACs as there is no
> > > > >    correlation identifier.
> > > > >    3.  The ASP should be smart enough to remember whether it has sent any
> > > > >    IIDs in the Active message.
> > > > >    4. If ASP sends Active without IIDs,
> > > > >           the  SGP  shall respond with Active Ack without IIDs, if the SG
> > > > >    activates  all  the  IIDs. Also, the SGP shall respond with Active Ack
> > > > >    with IIDs only that are activated.
> > > > >    5. If ASP sends Active with IIDs,
> > > > >           the  SGP  shall respond with Active Ack with IIDs only that are
> > > > >    activated.  Also,  the SGP shall respond with Active Ack without IIDs,
> > > > >    if the SG refuses to activate all the IIDs.
> > > > >
> > > > >    --Srini
> > > > >
> > > >
> > > > --
> > > > 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/

-- 
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 Jan 13 03:24: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 DAA04175
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 03:24:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D8cI204250
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 03:38:18 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D8c7J04239;
	Mon, 13 Jan 2003 03:38:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D8bsJ04216
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 03:37:54 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04155
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 03:23:50 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:z/WtHYUvGJ82mGRRMFcRxPGLRK3/mSmt@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0D8R9D09139;
	Mon, 13 Jan 2003 01:27:09 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0D8R9404733;
	Mon, 13 Jan 2003 01:27:09 -0700
Date: Mon, 13 Jan 2003 01:27:08 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: Lev.Finkel@ecitele.com, sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030113012708.B4492@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	Lev.Finkel@ecitele.com, sigtran@ietf.org
References: <OF8E8256BA.404F2C6C-ONC2256CAD.002677F5@ecitele.com> <3E226C37.3811AA5B@axes-mach01.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: <3E226C37.3811AA5B@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Mon, Jan 13, 2003 at 01:05:20PM +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>

ksrinivas,

Section 3.3.2.5:

"   If no Interface Identifiers are included, the message is for all
"   provisioned Interface Identifiers within the AS(s) in which the ASP
"   is provisioned.  If only a subset of Interface Identifiers are
"   included, the ASP is noted as Active for all the Interface
"   Identifiers provisioned for that AS.

A subset of IIDs merely identifies an AS, for which the AS is activated.
SGs do not activate IIDs, they activate Application Servers.  Application
Servers can consist of one or more IIDs, however, the entiere AS is either
active or inactive.

--brian

ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 13:05:20)
> Lev,
> 
> >>> - point 4 of you proposal may cause a problem. Suppose ASP has lost the
> >>> data and likes to bring all the interfaces back to active state. It sends
> >>> the ASP_ACTIVE without IID. If SG acknowledges just previously inactive
> >>> interfaces, the ASP will consider as active just these acknowledged
> >>> interfaces, and as inactive all interfaces that already active in SG. This
> >>> is a deadlock.
> 
>       Why does SG acknowledges just previously inactive interfaces only? IMO, it should acknowledge with
> all the IIDs that are currently active at the SG, only if the list is partial. Otherwise, if all the
> configured IIDs are Active at the SG, the SG should acknowledge without any IIDs(meaning, all the IIDs are
> Active).
> 
> --Srini
> 
> Lev.Finkel@ecitele.com wrote:
> 
> > Shrini,
> >
> > - point 4 of you proposal may cause a problem. Suppose ASP has lost the
> > data and likes to bring all the interfaces back to active state. It sends
> > the ASP_ACTIVE without IID. If SG acknowledges just previously inactive
> > interfaces, the ASP will consider as active just these acknowledged
> > interfaces, and as inactive all interfaces that already active in SG. This
> > is a deadlock.
> > - see IUA implementation guide for point 5 of your proposal
> >
> > I do not see a reason to change the RFC in this aspect.
> >
> > Regards,
> > Lev
> >
> >
> >                       "Brian F. G.
> >                       Bidulock"                To:      ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
> >                       <bidulock@openss         cc:      Latha <latha@indts.com>, sigtran@ietf.org
> >                       7.org>                   Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
> >                       Sent by:
> >                       sigtran-admin@ie
> >                       tf.org
> >
> >
> >                       13/01/03 07:50
> >                       Please respond
> >                       to bidulock
> >
> >
> >
> > ksrinivas,
> >
> > Your proposal represents a deviation from the RFC that I do not agree with.
> > The current RFC does not permit the SG to perform a "partial activation" of
> > some IIDs in a set.  Both in the ASPAC and ASPAC Ack, a subset of IIDs
> > represents the entire set of IIDs indicated by that subset.
> >
> > --brian
> >
> > ksrinivas wrote:
> > (Mon, 13 Jan 2003 11:05:43)
> > >
> > >    IMO, the Active and Active Ack procedures should be as follows:
> > >
> > >    1. ASP can send Active msg with or without IIDs.
> > >    2.  ASP  shall  never  send  multiple concurrent ASPACs as there is no
> > >    correlation identifier.
> > >    3.  The ASP should be smart enough to remember whether it has sent any
> > >    IIDs in the Active message.
> > >    4. If ASP sends Active without IIDs,
> > >           the  SGP  shall respond with Active Ack without IIDs, if the SG
> > >    activates  all  the  IIDs. Also, the SGP shall respond with Active Ack
> > >    with IIDs only that are activated.
> > >    5. If ASP sends Active with IIDs,
> > >           the  SGP  shall respond with Active Ack with IIDs only that are
> > >    activated.  Also,  the SGP shall respond with Active Ack without IIDs,
> > >    if the SG refuses to activate all the IIDs.
> > >
> > >    --Srini
> > >
> >
> > --
> > 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 mailnull@www1.ietf.org  Mon Jan 13 03:30: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 DAA04316
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 03:30:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D8iPW04557
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 03:44:25 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D8i9J04508;
	Mon, 13 Jan 2003 03:44:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D8gNJ04412
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 03:42:23 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04248
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 03:28:20 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0D8VZBE013013;
	Mon, 13 Jan 2003 02:31:36 -0600 (CST)
Received: from axsppc67 by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id NAA01797; Mon, 13 Jan 2003 13:00:20 -0500 (GMT)
Message-ID: <025501c2bade$2fac6b10$7501ff0a@axsppc67>
From: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
To: <bidulock@openss7.org>, "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
Cc: "Latha" <latha@indts.com>, <sigtran@ietf.org>
References: <F73B646FCC01D5118F530002B32C3372DB3021@INDTS_FS> <20030110010850.F8782@openss7.org> <3E223C19.B0A34CDA@axes-mach01.usa.alcatel.com> <20030112213835.A31712@openss7.org> <3E22502E.2F951D7F@axes-mach01.usa.alcatel.com> <20030112225030.A731@openss7.org> <3E2262BA.C3A37DE8@axes-mach01.usa.alcatel.com> <20030113002219.A2971@openss7.org> <3E2270B1.B4DE4FCC@axes-mach01.usa.alcatel.com> <20030113011751.A4492@openss7.org>
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Date: Mon, 13 Jan 2003 14:01:09 +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.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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

Brian,

Consider the following case:

1. ASP sends ASPAC for IIDS 1 to 10.
2. Due to some reason SG can bring up only IIDS 1 to 5.
3. Now, what does SG send in the ASPAC Ack? (w.r.t IIDS)

thanks
Chak

----- Original Message -----
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
Cc: "Latha" <latha@indts.com>; <sigtran@ietf.org>
Sent: Monday, January 13, 2003 1:47 PM
Subject: Re: [Sigtran] IUA - ASP Active and ACTIVE ACK


> ksrinivas,
>
> Well, they can be used by the ASP to correlate the received
> ASPAC Ack with the sent ASPAC: which is not insignificant.
>
> --brian
>
> ksrinivas wrote:
(Mon, 13 Jan 2003 13:24:25)
> > Brian,
> >
> >      My meaning of "IIDs in ASPAC Ack is insignificant" is not that IIDs
are optional or mandatory. IIDs serve no
> > purpose in the ASPAC Ack as per this thread.
> >
> > --Srini.
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > ksrinivas,
> > >
> > > But it doesn't have to: IIDs in ASPAC Ack is optional in the RFC.
> > >
> > > --brian
> > >
> > > ksrinivas wrote:
(Mon, 13 Jan 2003 12:24:50)
> > > > Brian,
> > > >
> > > >     If SG has to send the same set of IIDs back to the ASP in an
ASPAC Ack, the need for IIDs in ASPAC Ack is
> > > > insignificant.
> > > >
> > > > "Brian F. G. Bidulock" wrote:
> > > >
> > > > > ksrinivas,
> > > > >
> > > > > Your proposal represents a deviation from the RFC that I do not
agree with.
> > > > > The current RFC does not permit the SG to perform a "partial
activation" of
> > > > > some IIDs in a set.  Both in the ASPAC and ASPAC Ack, a subset of
IIDs
> > > > > represents the entire set of IIDs indicated by that subset.
> > > > >
> > > > > --brian
> > > > >
> > > > > ksrinivas wrote:
(Mon, 13 Jan 2003 11:05:43)
> > > > > >
> > > > > >    IMO, the Active and Active Ack procedures should be as
follows:
> > > > > >
> > > > > >    1. ASP can send Active msg with or without IIDs.
> > > > > >    2.  ASP  shall  never  send  multiple concurrent ASPACs as
there is no
> > > > > >    correlation identifier.
> > > > > >    3.  The ASP should be smart enough to remember whether it has
sent any
> > > > > >    IIDs in the Active message.
> > > > > >    4. If ASP sends Active without IIDs,
> > > > > >           the  SGP  shall respond with Active Ack without IIDs,
if the SG
> > > > > >    activates  all  the  IIDs. Also, the SGP shall respond with
Active Ack
> > > > > >    with IIDs only that are activated.
> > > > > >    5. If ASP sends Active with IIDs,
> > > > > >           the  SGP  shall respond with Active Ack with IIDs only
that are
> > > > > >    activated.  Also,  the SGP shall respond with Active Ack
without IIDs,
> > > > > >    if the SG refuses to activate all the IIDs.
> > > > > >
> > > > > >    --Srini
> > > > > >
> > > > >
> > > > > --
> > > > > 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/
>
> --
> 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 mailnull@www1.ietf.org  Mon Jan 13 03:43: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 DAA04525
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 03:43:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D8ugm05029
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 03:56:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D8u9J05014;
	Mon, 13 Jan 2003 03:56:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D8t4J04956
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 03:55:04 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04484
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 03:41:00 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:f6Fc0CCaxMRjobpqW3oP32Bbps9O6PRd@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0D8iJD09389;
	Mon, 13 Jan 2003 01:44:19 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0D8iJe05197;
	Mon, 13 Jan 2003 01:44:19 -0700
Date: Mon, 13 Jan 2003 01:44:18 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>
Cc: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>, Latha <latha@indts.com>,
        sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030113014418.A5008@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>,
	ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	Latha <latha@indts.com>, sigtran@ietf.org
References: <20030110010850.F8782@openss7.org> <3E223C19.B0A34CDA@axes-mach01.usa.alcatel.com> <20030112213835.A31712@openss7.org> <3E22502E.2F951D7F@axes-mach01.usa.alcatel.com> <20030112225030.A731@openss7.org> <3E2262BA.C3A37DE8@axes-mach01.usa.alcatel.com> <20030113002219.A2971@openss7.org> <3E2270B1.B4DE4FCC@axes-mach01.usa.alcatel.com> <20030113011751.A4492@openss7.org> <025501c2bade$2fac6b10$7501ff0a@axsppc67>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <025501c2bade$2fac6b10$7501ff0a@axsppc67>; from chak@axes-mach01.usa.alcatel.com on Mon, Jan 13, 2003 at 02:01:09PM +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>

Chak,

In your example, how are the IIDs configured
into Application Servers at the SG?


--brian

PSK Chakravarthi wrote:                                                                (Mon, 13 Jan 2003 14:01:09)
> Brian,
> 
> Consider the following case:
> 
> 1. ASP sends ASPAC for IIDS 1 to 10.
> 2. Due to some reason SG can bring up only IIDS 1 to 5.
> 3. Now, what does SG send in the ASPAC Ack? (w.r.t IIDS)
> 
> thanks
> Chak
> 

-- 
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 Jan 13 03: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 DAA04777
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 03:53:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D96sK05818
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 04:06:54 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D96VJ05787;
	Mon, 13 Jan 2003 04:06:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D961J05739
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 04:06:01 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04708
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 03:51:56 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0D8t3BE014308;
	Mon, 13 Jan 2003 02:55:09 -0600 (CST)
Received: from axsppc67 by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id NAA02317; Mon, 13 Jan 2003 13:23:05 -0500 (GMT)
Message-ID: <027901c2bae1$69f05040$7501ff0a@axsppc67>
From: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
To: <bidulock@openss7.org>
Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>,
        "Latha" <latha@indts.com>, <sigtran@ietf.org>
References: <20030110010850.F8782@openss7.org> <3E223C19.B0A34CDA@axes-mach01.usa.alcatel.com> <20030112213835.A31712@openss7.org> <3E22502E.2F951D7F@axes-mach01.usa.alcatel.com> <20030112225030.A731@openss7.org> <3E2262BA.C3A37DE8@axes-mach01.usa.alcatel.com> <20030113002219.A2971@openss7.org> <3E2270B1.B4DE4FCC@axes-mach01.usa.alcatel.com> <20030113011751.A4492@openss7.org> <025501c2bade$2fac6b10$7501ff0a@axsppc67> <20030113014418.A5008@openss7.org>
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Date: Mon, 13 Jan 2003 14:23:54 +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.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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

Brian,

All the IIDS are configured to one AS.

Thanks
Chak
----- Original Message -----
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>; "Latha"
<latha@indts.com>; <sigtran@ietf.org>
Sent: Monday, January 13, 2003 2:14 PM
Subject: Re: [Sigtran] IUA - ASP Active and ACTIVE ACK


> Chak,
>
> In your example, how are the IIDs configured
> into Application Servers at the SG?
>
>
> --brian
>
> PSK Chakravarthi wrote:
(Mon, 13 Jan 2003 14:01:09)
> > Brian,
> >
> > Consider the following case:
> >
> > 1. ASP sends ASPAC for IIDS 1 to 10.
> > 2. Due to some reason SG can bring up only IIDS 1 to 5.
> > 3. Now, what does SG send in the ASPAC Ack? (w.r.t IIDS)
> >
> > thanks
> > Chak
> >
>
> --
> 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 Jan 13 04:11: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 EAA05286
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 04:11:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D9OdJ08262
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 04:24:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D9ONJ08253;
	Mon, 13 Jan 2003 04:24:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D9LNJ08152
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 04:21:23 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05231
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 04:07:18 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:0iTR16H61qKYGL9ErK+h5kRKH76xmulq@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0D9AbD09865;
	Mon, 13 Jan 2003 02:10:37 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0D9AbZ05733;
	Mon, 13 Jan 2003 02:10:37 -0700
Date: Mon, 13 Jan 2003 02:10:37 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>
Cc: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>, Latha <latha@indts.com>,
        sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030113021037.A5532@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>,
	ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	Latha <latha@indts.com>, sigtran@ietf.org
References: <20030112213835.A31712@openss7.org> <3E22502E.2F951D7F@axes-mach01.usa.alcatel.com> <20030112225030.A731@openss7.org> <3E2262BA.C3A37DE8@axes-mach01.usa.alcatel.com> <20030113002219.A2971@openss7.org> <3E2270B1.B4DE4FCC@axes-mach01.usa.alcatel.com> <20030113011751.A4492@openss7.org> <025501c2bade$2fac6b10$7501ff0a@axsppc67> <20030113014418.A5008@openss7.org> <027901c2bae1$69f05040$7501ff0a@axsppc67>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <027901c2bae1$69f05040$7501ff0a@axsppc67>; from chak@axes-mach01.usa.alcatel.com on Mon, Jan 13, 2003 at 02:23:54PM +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>

Chak,

Then,

1. ASP sending ASPAC for IIDs 1 to 10, per the description under ASPAC
   is a request to configure all IIDs provisioned for the one big AS.

2. If there are no other AS configured, sending ASPAC without IIDs and
   ASPAC with IIDs 1 to 10 is no different.

To answer your question, answer this one:

If the SG manages to activate all the IIDs, and then, just after sending
ASPAC Ack, IIDs 6-10 fail, what does the SG send to the ASP?

IMO, the answer to the question above is the answer to your question below.
That is, the SG should treat it as though the failure was just after the
AS was activated, return ASPAC Ack, and then send the messages to treat
the failure.

--brian


PSK Chakravarthi wrote:                                                                (Mon, 13 Jan 2003 14:23:54)
> Brian,
> 
> All the IIDS are configured to one AS.
> 
> Thanks
> Chak
> ----- Original Message -----
> From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> To: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
> Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>; "Latha"
> <latha@indts.com>; <sigtran@ietf.org>
> Sent: Monday, January 13, 2003 2:14 PM
> Subject: Re: [Sigtran] IUA - ASP Active and ACTIVE ACK
> 
> 
> > Chak,
> >
> > In your example, how are the IIDs configured
> > into Application Servers at the SG?
> >
> >
> > --brian
> >
> > PSK Chakravarthi wrote:
> (Mon, 13 Jan 2003 14:01:09)
> > > Brian,
> > >
> > > Consider the following case:
> > >
> > > 1. ASP sends ASPAC for IIDS 1 to 10.
> > > 2. Due to some reason SG can bring up only IIDS 1 to 5.
> > > 3. Now, what does SG send in the ASPAC Ack? (w.r.t IIDS)
> > >
> > > thanks
> > > Chak
> > >
> >
> > --
> > 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 mailnull@www1.ietf.org  Mon Jan 13 04:12: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 EAA05382
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 04:12:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D9QQT08460
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 04:26:26 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D9Q7J08393;
	Mon, 13 Jan 2003 04:26:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D9PAJ08318
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 04:25:10 -0500
Received: from mink.ecitele.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05283;
	Mon, 13 Jan 2003 04:11:04 -0500 (EST)
From: Lev.Finkel@ecitele.com
Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125])
	by mink.ecitele.com (8.9.1a/8.9.1) with ESMTP id LAA02638;
	Mon, 13 Jan 2003 11:09:05 +0200 (IST)
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org, sigtran-admin@ietf.org
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OF118D4CF8.B7AAD7DE-ONC2256CAD.00313FBA@ecitele.com>
Date: Mon, 13 Jan 2003 11:11:13 +0200
X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at
 01/13/2003 11:14:19 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>


Shrini,
I understood your statement.

The ASP that sends IIDs or doesn't, actually defines the way it likes to
receive a response. If smart ASP wants to receive ACK on per IID base it
would send IID in ASP_ACTIVE.
In many applications misconfiguration is impossible (only one ASP and
common management for ASP and SG) and then exchange of IIDs looks
redundant.
Can you describe the expected problematical scenario with sending ACK
without IID if ASP_ACTIVE came also without IID?

Regards,
Lev



                                                                                                                    
                      ksrinivas                                                                                     
                      <ksrini@axes-mach01.usa.a         To:      Lev.Finkel@ecitele.com                             
                      lcatel.com>                       cc:      sigtran@ietf.org                                   
                      Sent by:                          Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK     
                      sigtran-admin@ietf.org                                                                        
                                                                                                                    
                                                                                                                    
                      13/01/03 09:35                                                                                
                                                                                                                    
                                                                                                                    



Lev,

>>> - point 4 of you proposal may cause a problem. Suppose ASP has lost the
>>> data and likes to bring all the interfaces back to active state. It
sends
>>> the ASP_ACTIVE without IID. If SG acknowledges just previously inactive
>>> interfaces, the ASP will consider as active just these acknowledged
>>> interfaces, and as inactive all interfaces that already active in SG.
This
>>> is a deadlock.

      Why does SG acknowledges just previously inactive interfaces only?
IMO, it should acknowledge with
all the IIDs that are currently active at the SG, only if the list is
partial. Otherwise, if all the
configured IIDs are Active at the SG, the SG should acknowledge without any
IIDs(meaning, all the IIDs are
Active).

--Srini

Lev.Finkel@ecitele.com wrote:

> Shrini,
>
> - point 4 of you proposal may cause a problem. Suppose ASP has lost the
> data and likes to bring all the interfaces back to active state. It sends
> the ASP_ACTIVE without IID. If SG acknowledges just previously inactive
> interfaces, the ASP will consider as active just these acknowledged
> interfaces, and as inactive all interfaces that already active in SG.
This
> is a deadlock.
> - see IUA implementation guide for point 5 of your proposal
>
> I do not see a reason to change the RFC in this aspect.
>
> Regards,
> Lev
>
>
>                       "Brian F. G.
>                       Bidulock"                To:      ksrinivas
<ksrini@axes-mach01.usa.alcatel.com>
>                       <bidulock@openss         cc:      Latha
<latha@indts.com>, sigtran@ietf.org
>                       7.org>                   Subject: Re: [Sigtran] IUA
-  ASP Active and ACTIVE ACK
>                       Sent by:
>                       sigtran-admin@ie
>                       tf.org
>
>
>                       13/01/03 07:50
>                       Please respond
>                       to bidulock
>
>
>
> ksrinivas,
>
> Your proposal represents a deviation from the RFC that I do not agree
with.
> The current RFC does not permit the SG to perform a "partial activation"
of
> some IIDs in a set.  Both in the ASPAC and ASPAC Ack, a subset of IIDs
> represents the entire set of IIDs indicated by that subset.
>
> --brian
>
> ksrinivas wrote:
> (Mon, 13 Jan 2003 11:05:43)
> >
> >    IMO, the Active and Active Ack procedures should be as follows:
> >
> >    1. ASP can send Active msg with or without IIDs.
> >    2.  ASP  shall  never  send  multiple concurrent ASPACs as there is
no
> >    correlation identifier.
> >    3.  The ASP should be smart enough to remember whether it has sent
any
> >    IIDs in the Active message.
> >    4. If ASP sends Active without IIDs,
> >           the  SGP  shall respond with Active Ack without IIDs, if the
SG
> >    activates  all  the  IIDs. Also, the SGP shall respond with Active
Ack
> >    with IIDs only that are activated.
> >    5. If ASP sends Active with IIDs,
> >           the  SGP  shall respond with Active Ack with IIDs only that
are
> >    activated.  Also,  the SGP shall respond with Active Ack without
IIDs,
> >    if the SG refuses to activate all the IIDs.
> >
> >    --Srini
> >
>
> --
> 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 mailnull@www1.ietf.org  Mon Jan 13 04:34:02 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 EAA05754
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 04:34:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D9laA09968
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 04:47:36 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D9l9J09935;
	Mon, 13 Jan 2003 04:47:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D9kZJ09905
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 04:46:35 -0500
Received: from mink.ecitele.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05727
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 04:32:29 -0500 (EST)
From: Lev.Finkel@ecitele.com
Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125])
	by mink.ecitele.com (8.9.1a/8.9.1) with ESMTP id LAA05176;
	Mon, 13 Jan 2003 11:30:28 +0200 (IST)
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
To: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OF23BDA91F.24534874-ONC2256CAD.00349873@ecitele.com>
Date: Mon, 13 Jan 2003 11:32:30 +0200
X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at
 01/13/2003 11:35:41 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>


Chak,
see implementation guide section 3.20

Regards,
Lev




                                                                                                                  
                      "PSK Chakravarthi"                                                                          
                      <chak@axes-mach01.usa.a         To:      <bidulock@openss7.org>, "ksrinivas"                
                      lcatel.com>                     <ksrini@axes-mach01.usa.alcatel.com>                        
                      Sent by:                        cc:      "Latha" <latha@indts.com>, <sigtran@ietf.org>      
                      sigtran-admin@ietf.org          Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK     
                                                                                                                  
                                                                                                                  
                      13/01/03 10:31                                                                              
                                                                                                                  
                                                                                                                  



Brian,

Consider the following case:

1. ASP sends ASPAC for IIDS 1 to 10.
2. Due to some reason SG can bring up only IIDS 1 to 5.
3. Now, what does SG send in the ASPAC Ack? (w.r.t IIDS)

thanks
Chak

----- Original Message -----
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
Cc: "Latha" <latha@indts.com>; <sigtran@ietf.org>
Sent: Monday, January 13, 2003 1:47 PM
Subject: Re: [Sigtran] IUA - ASP Active and ACTIVE ACK


> ksrinivas,
>
> Well, they can be used by the ASP to correlate the received
> ASPAC Ack with the sent ASPAC: which is not insignificant.
>
> --brian
>
> ksrinivas wrote:
(Mon, 13 Jan 2003 13:24:25)
> > Brian,
> >
> >      My meaning of "IIDs in ASPAC Ack is insignificant" is not that
IIDs
are optional or mandatory. IIDs serve no
> > purpose in the ASPAC Ack as per this thread.
> >
> > --Srini.
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > ksrinivas,
> > >
> > > But it doesn't have to: IIDs in ASPAC Ack is optional in the RFC.
> > >
> > > --brian
> > >
> > > ksrinivas wrote:
(Mon, 13 Jan 2003 12:24:50)
> > > > Brian,
> > > >
> > > >     If SG has to send the same set of IIDs back to the ASP in an
ASPAC Ack, the need for IIDs in ASPAC Ack is
> > > > insignificant.
> > > >
> > > > "Brian F. G. Bidulock" wrote:
> > > >
> > > > > ksrinivas,
> > > > >
> > > > > Your proposal represents a deviation from the RFC that I do not
agree with.
> > > > > The current RFC does not permit the SG to perform a "partial
activation" of
> > > > > some IIDs in a set.  Both in the ASPAC and ASPAC Ack, a subset of
IIDs
> > > > > represents the entire set of IIDs indicated by that subset.
> > > > >
> > > > > --brian
> > > > >
> > > > > ksrinivas wrote:
(Mon, 13 Jan 2003 11:05:43)
> > > > > >
> > > > > >    IMO, the Active and Active Ack procedures should be as
follows:
> > > > > >
> > > > > >    1. ASP can send Active msg with or without IIDs.
> > > > > >    2.  ASP  shall  never  send  multiple concurrent ASPACs as
there is no
> > > > > >    correlation identifier.
> > > > > >    3.  The ASP should be smart enough to remember whether it
has
sent any
> > > > > >    IIDs in the Active message.
> > > > > >    4. If ASP sends Active without IIDs,
> > > > > >           the  SGP  shall respond with Active Ack without IIDs,
if the SG
> > > > > >    activates  all  the  IIDs. Also, the SGP shall respond with
Active Ack
> > > > > >    with IIDs only that are activated.
> > > > > >    5. If ASP sends Active with IIDs,
> > > > > >           the  SGP  shall respond with Active Ack with IIDs
only
that are
> > > > > >    activated.  Also,  the SGP shall respond with Active Ack
without IIDs,
> > > > > >    if the SG refuses to activate all the IIDs.
> > > > > >
> > > > > >    --Srini
> > > > > >
> > > > >
> > > > > --
> > > > > 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/
>
> --
> 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 mailnull@www1.ietf.org  Mon Jan 13 04:41: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 EAA05861
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 04:41:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0D9tKL10300
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 04:55:20 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D9t6J10269;
	Mon, 13 Jan 2003 04:55:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0D9suJ10243
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 04:54:56 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05848
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 04:40:50 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:7fLGWRSDpZqNCwMHZ/psmWFKX5ScKBJN@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0D9i9D10367;
	Mon, 13 Jan 2003 02:44:10 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0D9i9A06719;
	Mon, 13 Jan 2003 02:44:09 -0700
Date: Mon, 13 Jan 2003 02:44:09 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Lev.Finkel@ecitele.com
Cc: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>, sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030113024409.A6582@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Lev.Finkel@ecitele.com,
	PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <OF23BDA91F.24534874-ONC2256CAD.00349873@ecitele.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: <OF23BDA91F.24534874-ONC2256CAD.00349873@ecitele.com>; from Lev.Finkel@ecitele.com on Mon, Jan 13, 2003 at 11:32: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>

Lev,

Lev.Finkel@ecitele.com wrote:                                                   (Mon, 13 Jan 2003 11:32:30)
> 
> Chak,
> see implementation guide section 3.20
> 

3.20 doesn't handle this case: only the case of misconfigured IIDs
(and not necessarily all in the same AS).

--brian


> Brian,
> 
> Consider the following case:
> 
> 1. ASP sends ASPAC for IIDS 1 to 10.
> 2. Due to some reason SG can bring up only IIDS 1 to 5.
> 3. Now, what does SG send in the ASPAC Ack? (w.r.t IIDS)
> 
> thanks
> Chak
> 

-- 
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 Jan 13 04:57:08 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 EAA06236
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 04:57:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DAAg211652
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 05:10:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DAARJ11628;
	Mon, 13 Jan 2003 05:10:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DA9FJ11556
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 05:09:15 -0500
Received: from mink.ecitele.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06163
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 04:55:09 -0500 (EST)
From: Lev.Finkel@ecitele.com
Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125])
	by mink.ecitele.com (8.9.1a/8.9.1) with ESMTP id LAA08049;
	Mon, 13 Jan 2003 11:53:08 +0200 (IST)
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
To: bidulock@openss7.org
Cc: chak@axes-mach01.usa.alcatel.com, sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OF8F3F4351.CC6C3369-ONC2256CAD.0035E719@ecitele.com>
Date: Mon, 13 Jan 2003 11:55:08 +0200
X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at
 01/13/2003 11:58:21 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>


Brian,
"misconfiguration" is really the title, but if SG makes unreasonable
decisions (no corresponding ERROR code) then such behavior must be out of
protocol scope.  Or a new ERROR code must be specified.

Regards,
Lev



                                                                                                           
                      "Brian F. G.                                                                         
                      Bidulock"                To:      Lev.Finkel@ecitele.com                             
                      <bidulock@openss         cc:      PSK Chakravarthi                                   
                      7.org>                   <chak@axes-mach01.usa.alcatel.com>, sigtran@ietf.org        
                                               Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK     
                      13/01/03 11:44                                                                       
                      Please respond                                                                       
                      to bidulock                                                                          
                                                                                                           
                                                                                                           



> Lev,
>
> Lev.Finkel@ecitele.com wrote:
(Mon, > 13 Jan 2003 11:32:30)
> >
> > Chak,
> > see implementation guide section 3.20
> >
>
> 3.20 doesn't handle this case: only the case of misconfigured IIDs
> (and not necessarily all in the same AS).
>
> --brian
>
>
> > Brian,
> >
> > Consider the following case:
> >
> > 1. ASP sends ASPAC for IIDS 1 to 10.
> > 2. Due to some reason SG can bring up only IIDS 1 to 5.
> > 3. Now, what does SG send in the ASPAC Ack? (w.r.t IIDS)
> >
> > thanks
> > Chak
> >

--
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 Jan 13 05:04: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 FAA06542
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 05:04:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DAIE212005
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 05:18:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DAI5J11998;
	Mon, 13 Jan 2003 05:18:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DAHaJ11961
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 05:17:36 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06526
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 05:03:30 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:IkAiwqt7gGii5vS45g4qulHGFdBA09UY@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0DA6nD10795;
	Mon, 13 Jan 2003 03:06:49 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0DA6np07228;
	Mon, 13 Jan 2003 03:06:49 -0700
Date: Mon, 13 Jan 2003 03:06:48 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Lev.Finkel@ecitele.com
Cc: chak@axes-mach01.usa.alcatel.com, sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030113030648.B6582@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Lev.Finkel@ecitele.com, chak@axes-mach01.usa.alcatel.com,
	sigtran@ietf.org
References: <OF8F3F4351.CC6C3369-ONC2256CAD.0035E719@ecitele.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: <OF8F3F4351.CC6C3369-ONC2256CAD.0035E719@ecitele.com>; from Lev.Finkel@ecitele.com on Mon, Jan 13, 2003 at 11:55:08AM +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>

Lev,

In 3.20 IIDs 6-10 are not configured at the SG.  Chak's case is where
they cannot be "brought up".

--brian

Lev.Finkel@ecitele.com wrote:                                                   (Mon, 13 Jan 2003 11:55:08)
> 
> Brian,
> "misconfiguration" is really the title, but if SG makes unreasonable
> decisions (no corresponding ERROR code) then such behavior must be out of
> protocol scope.  Or a new ERROR code must be specified.
> 
> Regards,
> Lev
> 
> 
> 
>                                                                                                            
>                       "Brian F. G.                                                                         
>                       Bidulock"                To:      Lev.Finkel@ecitele.com                             
>                       <bidulock@openss         cc:      PSK Chakravarthi                                   
>                       7.org>                   <chak@axes-mach01.usa.alcatel.com>, sigtran@ietf.org        
>                                                Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK     
>                       13/01/03 11:44                                                                       
>                       Please respond                                                                       
>                       to bidulock                                                                          
>                                                                                                            
>                                                                                                            
> 
> 
> 
> > Lev,
> >
> > Lev.Finkel@ecitele.com wrote:
> (Mon, > 13 Jan 2003 11:32:30)
> > >
> > > Chak,
> > > see implementation guide section 3.20
> > >
> >
> > 3.20 doesn't handle this case: only the case of misconfigured IIDs
> > (and not necessarily all in the same AS).
> >
> > --brian
> >
> >
> > > Brian,
> > >
> > > Consider the following case:
> > >
> > > 1. ASP sends ASPAC for IIDS 1 to 10.
> > > 2. Due to some reason SG can bring up only IIDS 1 to 5.
> > > 3. Now, what does SG send in the ASPAC Ack? (w.r.t IIDS)
> > >
> > > thanks
> > > Chak
> > >
> 
> --
> 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 mailnull@www1.ietf.org  Mon Jan 13 05:34: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 FAA07144
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 05:34:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DAm9W13575
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 05:48:09 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DAlbJ13558;
	Mon, 13 Jan 2003 05:47:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DAiSJ13472
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 05:44:28 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07060
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 05:30:21 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0DAUHD2020737
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 04:33:40 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0DATsM20949
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 04:29:55 -0600 (CST)
Date: Mon, 13 Jan 2003 04:29:54 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
In-Reply-To: <20030111163908.J8782@openss7.org>
Message-ID: <Pine.SOL.4.10.10301130421500.16353-100000@sun3271.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>


Hi,

So the concensus was M3UA can not be used effectively between
STP(SG) to SCP(AS) -- unawareness of SSN

can not be used effectively with MGC- unawareness of cic

now i have a doubt , Where M3UA can be used effectively?

any node which routes messae on DPC- here it is used , 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 mailnull@www1.ietf.org  Mon Jan 13 05:49: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 FAA07440
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 05:49:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DB3RN14373
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 06:03:27 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DB3EJ14359;
	Mon, 13 Jan 2003 06:03:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DB2cJ14315
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 06:02:38 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07399
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 05:48:31 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:KRSBNvGKX5Z2VDlcrT/Sp+5UGBU8912D@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0DAppD11355;
	Mon, 13 Jan 2003 03:51:51 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0DApow08007;
	Mon, 13 Jan 2003 03:51:50 -0700
Date: Mon, 13 Jan 2003 03:51:50 -0700
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] m3ua- IG
Message-ID: <20030113035150.A7367@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030111163908.J8782@openss7.org> <Pine.SOL.4.10.10301130421500.16353-100000@sun3271.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.10301130421500.16353-100000@sun3271.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Mon, Jan 13, 2003 at 04:29:54AM -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,

DPC, DPC/SI, even OPC/DPC, OPC/DPC/SI.

But don't forget that the SG can easily Load-Share on CIC, SSN,
DLR/SLR, TID, etc.  We have just been talking the use of Routing
Keys (which are 1:1 with the definition of the AS).

So we are saying that it doesn't make too much sense to split
Application Servers into sub-SI Application Servers.  SGs are
worried about point code status and user part status and don't
care about things like subsystem status.  Having Application
Servers (remember, defined by Routing Keys) that are either
point codes or user parts therefore makes a lot of sense.

But *within* an Application Server there can be multiple ASPs
serving the AS.  Load-sharing permits some messages to be sent
to some ASPs and other messages to be sent to others.  With an
extension such as draft-bidulock-sigtran-loadsel-01.txt or
draft-bidulock-sigtran-loadgrp-01.txt the ASP can even be under
control of which range of traffic it receives.  With a Broadcast
AS, the ASPs are in control over which messages it chooses to
process and which it does not choose to process.

So, to summarize, using Load-Share or Broadcast Application
Servers, everyting that one thought could be accomplished with
sub-SI granularity Routing Keys, is possible with Load-Sharing.
It, however, does not mess up the SG's view of PC and SI state
and is therefore interoperable.

Sub-SI RKs are just the wrong solution for the wrong problem.
Load distribution with Load-sharing or Broadcast is the
proscribed way of distributing traffic over multiple ASPs.

So, we should remove SSN and CIC from Routing Key (even restrict
RK to not have non-MTP3 RKs) and yet, keep the sections where
they are mentioned for load-sharing.  This gives maximum
interoperability without sacrificing any functionality.

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Mon, 13 Jan 2003 04:29:54)
> 
> Hi,
> 
> So the concensus was M3UA can not be used effectively between
> STP(SG) to SCP(AS) -- unawareness of SSN
> 
> can not be used effectively with MGC- unawareness of cic
> 
> now i have a doubt , Where M3UA can be used effectively?
> 
> any node which routes messae on DPC- here it is used , 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 mailnull@www1.ietf.org  Mon Jan 13 06:18: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 GAA07994
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 06:18:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DBVaF16133
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 06:31:36 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DBTYJ16036;
	Mon, 13 Jan 2003 06:29:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DBSWJ16000
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 06:28:32 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07950
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 06:14:23 -0500 (EST)
Subject: Re: [Sigtran] m3ua- IG
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFA471186E.5F208D0A-ONC2256CAD.003C72E5@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Mon, 13 Jan 2003 13:14:19 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/13/2003
 01:14:24 PM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0DBSWJ16001
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


Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> Samuel,
>
> DPC, DPC/SI, even OPC/DPC, OPC/DPC/SI.
>
> But don't forget that the SG can easily Load-Share
> on CIC, SSN,
> DLR/SLR, TID, etc.  We have just been talking the
> use of Routing
> Keys (which are 1:1 with the definition of the AS).
>
> So we are saying that it doesn't make too much sense
> to split
> Application Servers into sub-SI Application Servers.
>  SGs are
> worried about point code status and user part status
> and don't
> care about things like subsystem status.  Having
> Application
> Servers (remember, defined by Routing Keys) that are
> either
> point codes or user parts therefore makes a lot of
> sense.
>
> But *within* an Application Server there can be
> multiple ASPs
> serving the AS.  Load-sharing permits some messages
> to be sent
> to some ASPs and other messages to be sent to
> others.  With an
> extension such as
> draft-bidulock-sigtran-loadsel-01.txt or
> draft-bidulock-sigtran-loadgrp-01.txt the ASP can
> even be under
> control of which range of traffic it receives.  With
> a Broadcast
> AS, the ASPs are in control over which messages it
> chooses to
> process and which it does not choose to process.
>
> So, to summarize, using Load-Share or Broadcast
> Application
> Servers, everyting that one thought could be
> accomplished with
> sub-SI granularity Routing Keys, is possible with
> Load-Sharing.
> It, however, does not mess up the SG's view of PC
> and SI state
> and is therefore interoperable.
>
> Sub-SI RKs are just the wrong solution for the wrong
> problem.
> Load distribution with Load-sharing or Broadcast is
> the
> proscribed way of distributing traffic over multiple
> ASPs.
[TOLGA] I totally agree, if loadsaring addresses the needs, it is the way
to go. But not always it might be a perfect solution, one has to make the
upper layers distributed over multiple ASPs to work as a single entity. If
the number of ASPs serving the same AS increases, this might be too costly
and if one limits number of ASPs -let´s say they are low end systems- one
might not have desired processing power. With separete RKs, this wouldn´t
be a problem, one could slice the traffic into multiple AS, where each of
them is served by a reasonable number of ASPs -not as much as the
loadsharing case, so that synchronization is less costly- adn because there
are multiple AS, total number of ASPs is still big enough to have the
needed processing power. So, IMO loadsharing and separete RKs are not
exactly the same. But I also agree, trying to support non-MTP3 RKs is quite
ugly/for some of them maybe not possible.
>
> So, we should remove SSN and CIC from Routing Key
> (even restrict
> RK to not have non-MTP3 RKs) and yet, keep the
> sections where
> they are mentioned for load-sharing.  This gives
> maximum
> interoperability without sacrificing any
> functionality.
>
> --brian
>
> Samuel Dur D. Jeyaseelan wrote:
>                                (Mon, 13 Jan 2003
> 04:29:54)
> >
> > Hi,
> >
> > So the concensus was M3UA can not be used
> effectively between
> > STP(SG) to SCP(AS) -- unawareness of SSN
> >
> > can not be used effectively with MGC- unawareness
> of cic
> >
> > now i have a doubt , Where M3UA can be used
> effectively?
> >
> > any node which routes messae on DPC- here it is
> used , thats all?

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



From mailnull@www1.ietf.org  Mon Jan 13 06:22: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 GAA08096
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 06:22:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DBaYq16415
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 06:36:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DBa8J16389;
	Mon, 13 Jan 2003 06:36:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DBZxJ16353
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 06:35:59 -0500
Received: from mink.ecitele.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08068;
	Mon, 13 Jan 2003 06:21:50 -0500 (EST)
From: Lev.Finkel@ecitele.com
Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125])
	by mink.ecitele.com (8.9.1a/8.9.1) with ESMTP id NAA19834;
	Mon, 13 Jan 2003 13:19:47 +0200 (IST)
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
To: bidulock@openss7.org
Cc: chak@axes-mach01.usa.alcatel.com, sigtran@ietf.org, sigtran-admin@ietf.org
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OFC874E4AF.10B9B90E-ONC2256CAD.003E2A0A@ecitele.com>
Date: Mon, 13 Jan 2003 13:21:37 +0200
X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at
 01/13/2003 01:25: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>


Brian,
what may be the reason to reject setting of "ASP active" to configured
interface?

Regards, Lev.



                                                                                                           
                      "Brian F. G.                                                                         
                      Bidulock"                To:      Lev.Finkel@ecitele.com                             
                      <bidulock@openss         cc:      chak@axes-mach01.usa.alcatel.com, sigtran@ietf.org 
                      7.org>                   Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK     
                      Sent by:                                                                             
                      sigtran-admin@ie                                                                     
                      tf.org                                                                               
                                                                                                           
                                                                                                           
                      13/01/03 12:06                                                                       
                      Please respond                                                                       
                      to bidulock                                                                          
                                                                                                           
                                                                                                           



Lev,

In 3.20 IIDs 6-10 are not configured at the SG.  Chak's case is where
they cannot be "brought up".

--brian

Lev.Finkel@ecitele.com wrote:
(Mon, 13 Jan 2003 11:55:08)
>
> Brian,
> "misconfiguration" is really the title, but if SG makes unreasonable
> decisions (no corresponding ERROR code) then such behavior must be out of
> protocol scope.  Or a new ERROR code must be specified.
>
> Regards,
> Lev
>
>
>
>

>                       "Brian F. G.

>                       Bidulock"                To:
Lev.Finkel@ecitele.com
>                       <bidulock@openss         cc:      PSK Chakravarthi

>                       7.org>
<chak@axes-mach01.usa.alcatel.com>, sigtran@ietf.org
>                                                Subject: Re: [Sigtran] IUA
-  ASP Active and ACTIVE ACK
>                       13/01/03 11:44

>                       Please respond

>                       to bidulock

>

>

>
>
>
> > Lev,
> >
> > Lev.Finkel@ecitele.com wrote:
> (Mon, > 13 Jan 2003 11:32:30)
> > >
> > > Chak,
> > > see implementation guide section 3.20
> > >
> >
> > 3.20 doesn't handle this case: only the case of misconfigured IIDs
> > (and not necessarily all in the same AS).
> >
> > --brian
> >
> >
> > > Brian,
> > >
> > > Consider the following case:
> > >
> > > 1. ASP sends ASPAC for IIDS 1 to 10.
> > > 2. Due to some reason SG can bring up only IIDS 1 to 5.
> > > 3. Now, what does SG send in the ASPAC Ack? (w.r.t IIDS)
> > >
> > > thanks
> > > Chak
> > >
>
> --
> 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




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



From mailnull@www1.ietf.org  Mon Jan 13 06:32:57 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 GAA08305
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 06:32:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DBkYe17497
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 06:46:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DBkAJ17474;
	Mon, 13 Jan 2003 06:46:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DBj1J17437
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 06:45:01 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08264;
	Mon, 13 Jan 2003 06:30:53 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:PFJm8fSS11eI/MbrU5x/nZJ4ugqSBObQ@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0DBYDD12534;
	Mon, 13 Jan 2003 04:34:13 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0DBYCp09507;
	Mon, 13 Jan 2003 04:34:12 -0700
Date: Mon, 13 Jan 2003 04:34:12 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Lev.Finkel@ecitele.com
Cc: chak@axes-mach01.usa.alcatel.com, sigtran@ietf.org, sigtran-admin@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030113043412.A9450@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Lev.Finkel@ecitele.com, chak@axes-mach01.usa.alcatel.com,
	sigtran@ietf.org, sigtran-admin@ietf.org
References: <OFC874E4AF.10B9B90E-ONC2256CAD.003E2A0A@ecitele.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: <OFC874E4AF.10B9B90E-ONC2256CAD.003E2A0A@ecitele.com>; from Lev.Finkel@ecitele.com on Mon, Jan 13, 2003 at 01:21: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>

Lev,

Local hardware (e.g, i/f card) failure.

--brian

Lev.Finkel@ecitele.com wrote:                                                   (Mon, 13 Jan 2003 13:21:37)
> 
> Brian,
> what may be the reason to reject setting of "ASP active" to configured
> interface?
> 

-- 
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 Jan 13 06:34: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 GAA08347
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 06:34:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DBmOi17593
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 06:48:24 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DBmCJ17562;
	Mon, 13 Jan 2003 06:48:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DBlYJ17525
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 06:47:34 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08321;
	Mon, 13 Jan 2003 06:33:26 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0DBaYaN010853;
	Mon, 13 Jan 2003 05:36:40 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id QAA05983; Mon, 13 Jan 2003 16:05:17 -0500 (GMT)
Message-ID: <3E22A4C3.560A5DA9@axes-mach01.usa.alcatel.com>
Date: Mon, 13 Jan 2003 17:06:36 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Lev.Finkel@ecitele.com
CC: sigtran@ietf.org, sigtran-admin@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
References: <OF118D4CF8.B7AAD7DE-ONC2256CAD.00313FBA@ecitele.com>
Content-Type: text/plain; charset=x-user-defined
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

Lev,

>> Can you describe the expected problematical scenario with sending ACK
>> without IID if ASP_ACTIVE came also without IID?

There is no problem at all. If SG sends an Ack without any IIDs as a response to ASPAC without IIDs from ASP, then
all the IIDs are treated to be activated. This is as per my point# 4 below.

--Srini


Lev.Finkel@ecitele.com wrote:

> Shrini,
> I understood your statement.
>
> The ASP that sends IIDs or doesn't, actually defines the way it likes to
> receive a response. If smart ASP wants to receive ACK on per IID base it
> would send IID in ASP_ACTIVE.
> In many applications misconfiguration is impossible (only one ASP and
> common management for ASP and SG) and then exchange of IIDs looks
> redundant.
> Can you describe the expected problematical scenario with sending ACK
> without IID if ASP_ACTIVE came also without IID?
>
> Regards,
> Lev
>
>
>                       ksrinivas
>                       <ksrini@axes-mach01.usa.a         To:      Lev.Finkel@ecitele.com
>                       lcatel.com>                       cc:      sigtran@ietf.org
>                       Sent by:                          Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
>                       sigtran-admin@ietf.org
>
>
>                       13/01/03 09:35
>
>
>
> Lev,
>
> >>> - point 4 of you proposal may cause a problem. Suppose ASP has lost the
> >>> data and likes to bring all the interfaces back to active state. It
> sends
> >>> the ASP_ACTIVE without IID. If SG acknowledges just previously inactive
> >>> interfaces, the ASP will consider as active just these acknowledged
> >>> interfaces, and as inactive all interfaces that already active in SG.
> This
> >>> is a deadlock.
>
>       Why does SG acknowledges just previously inactive interfaces only?
> IMO, it should acknowledge with
> all the IIDs that are currently active at the SG, only if the list is
> partial. Otherwise, if all the
> configured IIDs are Active at the SG, the SG should acknowledge without any
> IIDs(meaning, all the IIDs are
> Active).
>
> --Srini
>
> Lev.Finkel@ecitele.com wrote:
>
> > Shrini,
> >
> > - point 4 of you proposal may cause a problem. Suppose ASP has lost the
> > data and likes to bring all the interfaces back to active state. It sends
> > the ASP_ACTIVE without IID. If SG acknowledges just previously inactive
> > interfaces, the ASP will consider as active just these acknowledged
> > interfaces, and as inactive all interfaces that already active in SG.
> This
> > is a deadlock.
> > - see IUA implementation guide for point 5 of your proposal
> >
> > I do not see a reason to change the RFC in this aspect.
> >
> > Regards,
> > Lev
> >
> >
> >                       "Brian F. G.
> >                       Bidulock"                To:      ksrinivas
> <ksrini@axes-mach01.usa.alcatel.com>
> >                       <bidulock@openss         cc:      Latha
> <latha@indts.com>, sigtran@ietf.org
> >                       7.org>                   Subject: Re: [Sigtran] IUA
> -  ASP Active and ACTIVE ACK
> >                       Sent by:
> >                       sigtran-admin@ie
> >                       tf.org
> >
> >
> >                       13/01/03 07:50
> >                       Please respond
> >                       to bidulock
> >
> >
> >
> > ksrinivas,
> >
> > Your proposal represents a deviation from the RFC that I do not agree
> with.
> > The current RFC does not permit the SG to perform a "partial activation"
> of
> > some IIDs in a set.  Both in the ASPAC and ASPAC Ack, a subset of IIDs
> > represents the entire set of IIDs indicated by that subset.
> >
> > --brian
> >
> > ksrinivas wrote:
> > (Mon, 13 Jan 2003 11:05:43)
> > >
> > >    IMO, the Active and Active Ack procedures should be as follows:
> > >
> > >    1. ASP can send Active msg with or without IIDs.
> > >    2.  ASP  shall  never  send  multiple concurrent ASPACs as there is
> no
> > >    correlation identifier.
> > >    3.  The ASP should be smart enough to remember whether it has sent
> any
> > >    IIDs in the Active message.
> > >    4. If ASP sends Active without IIDs,
> > >           the  SGP  shall respond with Active Ack without IIDs, if the
> SG
> > >    activates  all  the  IIDs. Also, the SGP shall respond with Active
> Ack
> > >    with IIDs only that are activated.
> > >    5. If ASP sends Active with IIDs,
> > >           the  SGP  shall respond with Active Ack with IIDs only that
> are
> > >    activated.  Also,  the SGP shall respond with Active Ack without
> IIDs,
> > >    if the SG refuses to activate all the IIDs.
> > >
> > >    --Srini
> > >
> >
> > --
> > 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 mailnull@www1.ietf.org  Mon Jan 13 06:34: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 GAA08360
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 06:34:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DBmS217605
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 06:48:28 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DBmFJ17581;
	Mon, 13 Jan 2003 06:48:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DBlvJ17543
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 06:47:57 -0500
Received: from mink.ecitele.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08332;
	Mon, 13 Jan 2003 06:33:48 -0500 (EST)
From: Lev.Finkel@ecitele.com
Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125])
	by mink.ecitele.com (8.9.1a/8.9.1) with ESMTP id NAA22324;
	Mon, 13 Jan 2003 13:31:34 +0200 (IST)
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
To: bidulock@openss7.org
Cc: chak@axes-mach01.usa.alcatel.com, ksrini@axes-mach01.usa.alcatel.com,
        latha@indts.com, sigtran@ietf.org, sigtran-admin@ietf.org
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OF3F5EA9AE.A52AEAA2-ONC2256CAD.003F634D@ecitele.com>
Date: Mon, 13 Jan 2003 13:33:23 +0200
X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at
 01/13/2003 01:36:48 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>


Brian,

>
>


                                                                                                           
                      "Brian F. G.                                                                         
                      Bidulock"                To:      PSK Chakravarthi                                   
                      <bidulock@openss         <chak@axes-mach01.usa.alcatel.com>                          
                      7.org>                   cc:      ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,    
                      Sent by:                 Latha <latha@indts.com>, sigtran@ietf.org                   
                      sigtran-admin@ie         Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK     
                      tf.org                                                                               
                                                                                                           
                                                                                                           
                      13/01/03 11:10                                                                       
                      Please respond                                                                       
                      to bidulock                                                                          
                                                                                                           
                                                                                                           



> Chak,
>
> Then,
>
> 1. ASP sending ASPAC for IIDs 1 to 10, per the description under ASPAC
>    is a request to configure all IIDs provisioned for the one big AS.
>
> 2. If there are no other AS configured, sending ASPAC without IIDs and
>    ASPAC with IIDs 1 to 10 is no different.
>
> To answer your question, answer this one:
>
> If the SG manages to activate all the IIDs, and then, just after sending
> ASPAC Ack, IIDs 6-10 fail, what does the SG send to the ASP?
>
> IMO, the answer to the question above is the answer to your question
below.
> That is, the SG should treat it as though the failure was just after the
> AS was activated, return ASPAC Ack, and then send the messages to treat
> the failure.
>
> --brian

Notify(AS_inactive) or another corresponding notify is the way provided in
RFC.

Regards, Lev



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



From mailnull@www1.ietf.org  Mon Jan 13 06:39:50 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 GAA08514
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 06:39:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DBrR017862
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 06:53:27 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DBr8J17841;
	Mon, 13 Jan 2003 06:53:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DBqwJ17780
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 06:52:58 -0500
Received: from mink.ecitele.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08475;
	Mon, 13 Jan 2003 06:38:49 -0500 (EST)
From: Lev.Finkel@ecitele.com
Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125])
	by mink.ecitele.com (8.9.1a/8.9.1) with ESMTP id NAA23084;
	Mon, 13 Jan 2003 13:36:48 +0200 (IST)
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
To: bidulock@openss7.org
Cc: chak@axes-mach01.usa.alcatel.com, sigtran@ietf.org, sigtran-admin@ietf.org
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OF60E5BB1D.DE39F1AA-ONC2256CAD.003FDD01@ecitele.com>
Date: Mon, 13 Jan 2003 13:38:35 +0200
X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at
 01/13/2003 01:42:01 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>


Brian,

the I/F failure is covered by RELEASE_PHYS reason in RELEASE_INDICATION or
RELEASE_CONFIRM message.
AS/ASP is active for certain D-channel independantly from its phisical
condition.

Regards,
Lev



                                                                                                           
                      "Brian F. G.                                                                         
                      Bidulock"                To:      Lev.Finkel@ecitele.com                             
                      <bidulock@openss         cc:      chak@axes-mach01.usa.alcatel.com,                  
                      7.org>                   sigtran@ietf.org, sigtran-admin@ietf.org                    
                                               Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK     
                      13/01/03 13:34                                                                       
                      Please respond                                                                       
                      to bidulock                                                                          
                                                                                                           
                                                                                                           



Lev,

Local hardware (e.g, i/f card) failure.

--brian

Lev.Finkel@ecitele.com wrote:
(Mon, 13 Jan 2003 13:21:37)
>
> Brian,
> what may be the reason to reject setting of "ASP active" to configured
> interface?
>

--
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 Jan 13 06:45: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 GAA08645
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 06:45:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DBxJT18080
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 06:59:19 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DBx6J18073;
	Mon, 13 Jan 2003 06:59:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DBweJ18043
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 06:58:40 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08636
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 06:44:32 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:viiJR0PJBD9Pb4EVNo4y8c43Vu9NS0Pd@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0DBlpD12701;
	Mon, 13 Jan 2003 04:47:51 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0DBloK09817;
	Mon, 13 Jan 2003 04:47:50 -0700
Date: Mon, 13 Jan 2003 04:47:50 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030113044750.B9450@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OFA471186E.5F208D0A-ONC2256CAD.003C72E5@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OFA471186E.5F208D0A-ONC2256CAD.003C72E5@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Mon, Jan 13, 2003 at 01:14:19PM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Mon, 13 Jan 2003 13:14:19)
> >
> > Sub-SI RKs are just the wrong solution for the wrong problem.  Load
> > distribution with Load-sharing or Broadcast is the proscribed way of
> > distributing traffic over multiple ASPs.
>
> [TOLGA] I totally agree, if loadsaring addresses the needs, it is the way
> to go. But not always it might be a perfect solution, one has to make the
> upper layers distributed over multiple ASPs to work as a single entity. If
> the number of ASPs serving the same AS increases, this might be too costly
> and if one limits number of ASPs -let´s say they are low end systems- one
> might not have desired processing power. With separete RKs, this wouldn´t
> be a problem, one could slice the traffic into multiple AS, where each of
> them is served by a reasonable number of ASPs -not as much as the
> loadsharing case, so that synchronization is less costly- adn because there
> are multiple AS, total number of ASPs is still big enough to have the
> needed processing power. So, IMO loadsharing and separete RKs are not
> exactly the same. But I also agree, trying to support non-MTP3 RKs is quite
> ugly/for some of them maybe not possible.

Loadsharing extensions are still better than non-MTP3 RKs because they
can be described in an interoperable way.  Also, loadsharing can be made
to scale by grouping even low-end ASPs in load groups.  See:

	draft-bidulock-sigtran-loadsel-01.txt
	draft-bidulock-sigtran-loadgrp-01.txt
	draft-bidulock-sigtran-regext-01.txt

available now on the I-D server.

Also, there's an example on how to do ISUA (ISUP User Adamptation Layer)
also on the I-D server, and a re-released TUA:

	draft-bidulock-sigtran-isua-00.txt
	draft-bidulock-sigtran-tua-01.txt

Also, ASP extrensions and an updated CORID draft:

	draft-bidulock-sigtran-aspext-01.txt
	draft-bidulock-sigtran-corid-01.txt

But the loadsharing extensions (registering a load selection key and
activating and deactivating within a load selection or load group)
are probably just what you're looking for.

--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 Jan 13 06:49: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 GAA08754
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 06:49:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DC3J218274
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 07:03:19 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DC34J18266;
	Mon, 13 Jan 2003 07:03:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DC2aJ18238
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 07:02:36 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08738;
	Mon, 13 Jan 2003 06:48:27 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:FbZAz4fJEIkp/W+aUzfigIFmFdSLo8jP@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0DBplD12750;
	Mon, 13 Jan 2003 04:51:47 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0DBplC09882;
	Mon, 13 Jan 2003 04:51:47 -0700
Date: Mon, 13 Jan 2003 04:51:46 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Lev.Finkel@ecitele.com
Cc: chak@axes-mach01.usa.alcatel.com, sigtran@ietf.org, sigtran-admin@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030113045146.C9450@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Lev.Finkel@ecitele.com, chak@axes-mach01.usa.alcatel.com,
	sigtran@ietf.org, sigtran-admin@ietf.org
References: <OF60E5BB1D.DE39F1AA-ONC2256CAD.003FDD01@ecitele.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: <OF60E5BB1D.DE39F1AA-ONC2256CAD.003FDD01@ecitele.com>; from Lev.Finkel@ecitele.com on Mon, Jan 13, 2003 at 01:38:35PM +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>

Lev,

Bingo.  That is why I said that the response before sending ASPAC Ack
is the correct response after sending ASPAC Ack.  The SG should always
respond with ASPAC Ack indicating that configured IIDs an an AS are all
activated and then use Release Indication/Confirmation with cause to
indicate the h/w failure when a DL-User actually attempts to do something
with the phsyical link.

So, Chak's proposal doesn't make sense to me: an SG which is improperly
configured follows the IG 3.20.  A SG which is properly configured always
responsds with ASPAC Ack indicating that the AS is active for *all* IIDs
in the AS, regardless of the number of IIDs in the ASPAC.

--brian

Lev.Finkel@ecitele.com wrote:                                                   (Mon, 13 Jan 2003 13:38:35)
> 
> Brian,
> 
> the I/F failure is covered by RELEASE_PHYS reason in RELEASE_INDICATION or
> RELEASE_CONFIRM message.
> AS/ASP is active for certain D-channel independantly from its phisical
> condition.
> 
> Regards,
> Lev
> 

-- 
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 Jan 13 06:51: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 GAA08790
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 06:51:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DC4wU18352
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 07:04:58 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DC4lJ18340;
	Mon, 13 Jan 2003 07:04:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DC3wJ18304
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 07:03:58 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08768;
	Mon, 13 Jan 2003 06:49:49 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:NoVw3+1mnM92ZGH9CEyQuKdHKxr1V5ty@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0DBr9D12778;
	Mon, 13 Jan 2003 04:53:09 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0DBr9409930;
	Mon, 13 Jan 2003 04:53:09 -0700
Date: Mon, 13 Jan 2003 04:53:09 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Lev.Finkel@ecitele.com
Cc: chak@axes-mach01.usa.alcatel.com, ksrini@axes-mach01.usa.alcatel.com,
        latha@indts.com, sigtran@ietf.org, sigtran-admin@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030113045309.D9450@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Lev.Finkel@ecitele.com, chak@axes-mach01.usa.alcatel.com,
	ksrini@axes-mach01.usa.alcatel.com, latha@indts.com,
	sigtran@ietf.org, sigtran-admin@ietf.org
References: <OF3F5EA9AE.A52AEAA2-ONC2256CAD.003F634D@ecitele.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: <OF3F5EA9AE.A52AEAA2-ONC2256CAD.003F634D@ecitele.com>; from Lev.Finkel@ecitele.com on Mon, Jan 13, 2003 at 01:33:23PM +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>

Lev.Finkel,

Notify(AS_inactive) is never sent after sending ASPAC Ack because the
AS is active.  Where in the RFC did you think this was stated?

--brian

Lev.Finkel@ecitele.com wrote:                                                   (Mon, 13 Jan 2003 13:33:23)
> 
> Notify(AS_inactive) or another corresponding notify is the way provided in
> RFC.
> 
> Regards, Lev
> 
> 

-- 
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 Jan 13 06:52: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 GAA08823
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 06:52:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DC6Fb18414
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 07:06:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DC64J18405;
	Mon, 13 Jan 2003 07:06:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DC5xJ18391
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 07:05:59 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08804
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 06:51:50 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0DBt7aP012049;
	Mon, 13 Jan 2003 05:55:10 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0DBsJM24971;
	Mon, 13 Jan 2003 05:54:19 -0600 (CST)
Date: Mon, 13 Jan 2003 05:54:19 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: bidulock@openss7.org, TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
In-Reply-To: <OFA471186E.5F208D0A-ONC2256CAD.003C72E5@LocalDomain>
Message-ID: <Pine.SOL.4.10.10301130526430.16353-100000@sun3271.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id h0DC5xJ18392
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


Brian,Tolga,

  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 Mon, 13 Jan 2003, TOLGA ASVEREN wrote:

> 
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > Samuel,
> >
> > DPC, DPC/SI, even OPC/DPC, OPC/DPC/SI.
> >
> > But don't forget that the SG can easily Load-Share
> > on CIC, SSN,
> > DLR/SLR, TID, etc.  We have just been talking the
> > use of Routing
> > Keys (which are 1:1 with the definition of the AS).
> >
Mean to say ,having multiple SGs pre-configured to serve
set of SSN and set of CIC range ...?

> > So we are saying that it doesn't make too much sense
> > to split
> > Application Servers into sub-SI Application Servers.

But SUA does it.

> >  SGs are
> > worried about point code status and user part status
> > and don't
> > care about things like subsystem status.  Having
> > Application
> > Servers (remember, defined by Routing Keys) that are
> > either
> > point codes or user parts therefore makes a lot of
> > sense.
disagree, Almost all STPs(SG) more worried about subsystem status...
because they are the only nodes which performs GTT to reach 'centralized
databse'

> >
> > But *within* an Application Server there can be
> > multiple ASPs
> > serving the AS.  Load-sharing permits some messages
> > to be sent
> > to some ASPs and other messages to be sent to
> > others.  With an
> > extension such as
> > draft-bidulock-sigtran-loadsel-01.txt or
> > draft-bidulock-sigtran-loadgrp-01.txt the ASP can
> > even be under
> > control of which range of traffic it receives.  With
> > a Broadcast
> > AS, the ASPs are in control over which messages it
> > chooses to
> > process and which it does not choose to process.

Load -sharing on SLS?

> >
> > So, to summarize, using Load-Share or Broadcast
> > Application
> > Servers, everyting that one thought could be
> > accomplished with
> > sub-SI granularity Routing Keys, is possible with
> > Load-Sharing.

what is 'sub-SI granularity Routing Keys' ?
(said below 'sub-SI granularity Routing Keys' wrong solution
for wrong problems)

> > It, however, does not mess up the SG's view of PC
> > and SI state
> > and is therefore interoperable.
> >
> > Sub-SI RKs are just the wrong solution for the wrong
> > problem.
> > Load distribution with Load-sharing or Broadcast is
> > the
> > proscribed way of distributing traffic over multiple
> > ASPs.
> [TOLGA] I totally agree, if loadsaring addresses the needs, it is the way
> to go. But not always it might be a perfect solution, one has to make the
> upper layers distributed over multiple ASPs to work as a single entity. If
> the number of ASPs serving the same AS increases, this might be too costly
> and if one limits number of ASPs -let´s say they are low end systems- one
> might not have desired processing power. With separete RKs, this wouldn´t
> be a problem, one could slice the traffic into multiple AS, where each of
> them is served by a reasonable number of ASPs -not as much as the
> loadsharing case, so that synchronization is less costly- adn because there
> are multiple AS, total number of ASPs is still big enough to have the
> needed processing power. So, IMO loadsharing and separete RKs are not
> exactly the same. But I also agree, trying to support non-MTP3 RKs is quite
> ugly/for some of them maybe not possible.
> >
> > So, we should remove SSN and CIC from Routing Key
> > (even restrict
> > RK to not have non-MTP3 RKs) and yet, keep the
> > sections where
> > they are mentioned for load-sharing.  This gives
> > maximum
> > interoperability without sacrificing any
> > functionality.
> >
> > --brian
> >
> > Samuel Dur D. Jeyaseelan wrote:
> >                                (Mon, 13 Jan 2003
> > 04:29:54)
> > >
> > > Hi,
> > >
> > > So the concensus was M3UA can not be used
> > effectively between
> > > STP(SG) to SCP(AS) -- unawareness of SSN
> > >
> > > can not be used effectively with MGC- unawareness
> > of cic
> > >
> > > now i have a doubt , Where M3UA can be used
> > effectively?
> > >
> > > any node which routes messae on DPC- here it is
> > used , thats all?
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 

I understood RFC 3332 was written with an idea of supporting 
SSN and CIC but after mail communication both were removed.

Instead of having separate RFC for SUA , we should have merged
both into a single RFC.
[just i put my thoughts :-)]

--Samuel

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



From mailnull@www1.ietf.org  Mon Jan 13 07:01: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 HAA09029
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 07:01:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DCFJF19436
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 07:15:19 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DCF9J19408;
	Mon, 13 Jan 2003 07:15:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DCDhJ19354
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 07:13:43 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08951
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 06:59:34 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0DC2paN012667;
	Mon, 13 Jan 2003 06:02:52 -0600 (CST)
Received: from axsppc67 by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id QAA06698; Mon, 13 Jan 2003 16:31:25 -0500 (GMT)
Message-ID: <02cb01c2bafb$a601ab00$7501ff0a@axsppc67>
From: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
To: <bidulock@openss7.org>
Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>,
        "Latha" <latha@indts.com>, <sigtran@ietf.org>
References: <20030112213835.A31712@openss7.org> <3E22502E.2F951D7F@axes-mach01.usa.alcatel.com> <20030112225030.A731@openss7.org> <3E2262BA.C3A37DE8@axes-mach01.usa.alcatel.com> <20030113002219.A2971@openss7.org> <3E2270B1.B4DE4FCC@axes-mach01.usa.alcatel.com> <20030113011751.A4492@openss7.org> <025501c2bade$2fac6b10$7501ff0a@axsppc67> <20030113014418.A5008@openss7.org> <027901c2bae1$69f05040$7501ff0a@axsppc67> <20030113021037.A5532@openss7.org>
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Date: Mon, 13 Jan 2003 17:32:13 +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.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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

Brian,

> IMO, the answer to the question above is the answer to your question
below.
> That is, the SG should treat it as though the failure was just after the
> AS was activated, return ASPAC Ack, and then send the messages to treat
> the failure.

How does SG indicate ASP that IIDS are failed?

Is there any message which can be sent from SG to ASP, to indicate IIDS are
failed before Establish request for an IID from ASP?


Thanks
Chak



----- Original Message -----
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>; "Latha"
<latha@indts.com>; <sigtran@ietf.org>
Sent: Monday, January 13, 2003 2:40 PM
Subject: Re: [Sigtran] IUA - ASP Active and ACTIVE ACK


> Chak,
>
> Then,
>
> 1. ASP sending ASPAC for IIDs 1 to 10, per the description under ASPAC
>    is a request to configure all IIDs provisioned for the one big AS.
>
> 2. If there are no other AS configured, sending ASPAC without IIDs and
>    ASPAC with IIDs 1 to 10 is no different.
>
> To answer your question, answer this one:
>
> If the SG manages to activate all the IIDs, and then, just after sending
> ASPAC Ack, IIDs 6-10 fail, what does the SG send to the ASP?
>
> IMO, the answer to the question above is the answer to your question
below.
> That is, the SG should treat it as though the failure was just after the
> AS was activated, return ASPAC Ack, and then send the messages to treat
> the failure.
>
> --brian
>
>
> PSK Chakravarthi wrote:
(Mon, 13 Jan 2003 14:23:54)
> > Brian,
> >
> > All the IIDS are configured to one AS.
> >
> > Thanks
> > Chak
> > ----- Original Message -----
> > From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > To: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
> > Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>; "Latha"
> > <latha@indts.com>; <sigtran@ietf.org>
> > Sent: Monday, January 13, 2003 2:14 PM
> > Subject: Re: [Sigtran] IUA - ASP Active and ACTIVE ACK
> >
> >
> > > Chak,
> > >
> > > In your example, how are the IIDs configured
> > > into Application Servers at the SG?
> > >
> > >
> > > --brian
> > >
> > > PSK Chakravarthi wrote:
> > (Mon, 13 Jan 2003 14:01:09)
> > > > Brian,
> > > >
> > > > Consider the following case:
> > > >
> > > > 1. ASP sends ASPAC for IIDS 1 to 10.
> > > > 2. Due to some reason SG can bring up only IIDS 1 to 5.
> > > > 3. Now, what does SG send in the ASPAC Ack? (w.r.t IIDS)
> > > >
> > > > thanks
> > > > Chak
> > > >
> > >
> > > --
> > > 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 mailnull@www1.ietf.org  Mon Jan 13 07:10: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 HAA09165
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 07:10:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DCOOo19801
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 07:24:24 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DCO9J19793;
	Mon, 13 Jan 2003 07:24:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DCNHJ19750
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 07:23:18 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09138
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 07:09:08 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:GUHhAwP3lQJcUCHpdZ5aHtDRVycVHg99@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0DCCSD13121;
	Mon, 13 Jan 2003 05:12:28 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0DCCRV10335;
	Mon, 13 Jan 2003 05:12:27 -0700
Date: Mon, 13 Jan 2003 05:12:27 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030113051227.A9997@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OFA471186E.5F208D0A-ONC2256CAD.003C72E5@LocalDomain> <Pine.SOL.4.10.10301130526430.16353-100000@sun3271.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.10301130526430.16353-100000@sun3271.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Mon, Jan 13, 2003 at 05:54:19AM -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,

Samuel Dur D. Jeyaseelan wrote:                                                     (Mon, 13 Jan 2003 05:54:19)
> 
> Brian,Tolga,
> 
>   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 Mon, 13 Jan 2003, TOLGA ASVEREN wrote:
> 
> > 
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > > Samuel,
> > >
> > > DPC, DPC/SI, even OPC/DPC, OPC/DPC/SI.
> > >
> > > But don't forget that the SG can easily Load-Share on CIC, SSN, DLR/SLR,
> > > TID, etc.  We have just been talking the use of Routing Keys (which are
> > > 1:1 with the definition of the AS).
> > >
> Mean to say ,having multiple SGs pre-configured to serve set of SSN and set
> of CIC range ...?

Having any number of SGs pre-configure to serve a set of SSN or set of CIC
range...

> 
> > > So we are saying that it doesn't make too much sense
> > > to split
> > > Application Servers into sub-SI Application Servers.
> 
> But SUA does it.

SUA sits above SCCP.  M3UA sits below SCCP.  Having M3UA try to
route to SCCP-User is a silly as having M2UA (yes, em-two-ua)
route to MTP Users.

> 
> > >  SGs are worried about point code status and user part status and don't
> > >  care about things like subsystem status.  Having Application Servers
> > >  (remember, defined by Routing Keys) that are either point codes or user
> > >  parts therefore makes a lot of sense.
>
> disagree, Almost all STPs(SG) more worried about subsystem status...
> because they are the only nodes which performs GTT to reach 'centralized
> databse'

M3UA SG's.  Subsystem status is peformed by SCCP.

> 
> > >
> > > But *within* an Application Server there can be multiple ASPs serving
> > > the AS.  Load-sharing permits some messages to be sent to some ASPs and
> > > other messages to be sent to others.  With an extension such as
> > > draft-bidulock-sigtran-loadsel-01.txt or
> > > draft-bidulock-sigtran-loadgrp-01.txt the ASP can even be under control
> > > of which range of traffic it receives.  With a Broadcast AS, the ASPs
> > > are in control over which messages it chooses to process and which it
> > > does not choose to process.
> 
> Load -sharing on SLS?

Load-sharing on anything.  SLS is a good one...

> 
> > >
> > > So, to summarize, using Load-Share or Broadcast Application Servers,
> > > everyting that one thought could be accomplished with sub-SI granularity
> > > Routing Keys, is possible with Load-Sharing.
> 
> what is 'sub-SI granularity Routing Keys' ?  (said below 'sub-SI granularity
> Routing Keys' wrong solution for wrong problems)

RKs with a granularity finer than a Service Indicator (or smaller
than an MTP-User).

> I understood RFC 3332 was written with an idea of supporting SSN and CIC but
> after mail communication both were removed.

SSN and CIC were placed in the draft before RKs and most of the model was
formalized.  Experience has shown that they are not very useful for routing,
but are quite useful for loadsharing.  This is because the RK:AS:RC concept
had to be formalized to permit the SG management of the SPMC, making it no
longer suited to other more esoteric tasks better addressed with load-sharing
and broadcast.

> 
> Instead of having separate RFC for SUA , we should have merged both into a
> single RFC.  [just i put my thoughts :-)]

There is nothing stopping an implementor from runnign M3UA and SUA over the
same association (with different PPI).  Most of the messaging and and
proceudre text is identical (even with M2UA).  These protocols reside at
different layers in the protocol stack and work at different layer interfaces
within the SS7 stack.  Attempting to generalize all provider/user interfaces
at all levels of the SS7 stack would have been a recipe for failure.

Nevertheless, a one point I did say that SUA could have been easily  adjusted
to do what M3UA claimed to do as well.  All that was necessary was the
trivial MTP-TRANSFER primitive representation.  SUA supports all other
necessary message classes and parameters to perform all of M3UA's functions.

But, SUA still cannot handle CIC routing keys.  But ISUA can: see

	draft-bidulock-sigtran-isua-00.txt

With ISUP and SCCP covered by ISUA and SUA, who needs no stinkin' M3UA?

--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 Jan 13 07:13: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 HAA09202
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 07:13:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DCREj19947
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 07:27:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DCR4J19940;
	Mon, 13 Jan 2003 07:27:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DCQkJ19902
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 07:26:47 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09194
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 07:12:35 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:TDNQpeyBsUiSRBxCVj20sLcan/JtT0HH@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0DCFtD13159;
	Mon, 13 Jan 2003 05:15:55 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0DCFtv10387;
	Mon, 13 Jan 2003 05:15:55 -0700
Date: Mon, 13 Jan 2003 05:15:55 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>
Cc: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>, Latha <latha@indts.com>,
        sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030113051555.B9997@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>,
	ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	Latha <latha@indts.com>, sigtran@ietf.org
References: <20030112225030.A731@openss7.org> <3E2262BA.C3A37DE8@axes-mach01.usa.alcatel.com> <20030113002219.A2971@openss7.org> <3E2270B1.B4DE4FCC@axes-mach01.usa.alcatel.com> <20030113011751.A4492@openss7.org> <025501c2bade$2fac6b10$7501ff0a@axsppc67> <20030113014418.A5008@openss7.org> <027901c2bae1$69f05040$7501ff0a@axsppc67> <20030113021037.A5532@openss7.org> <02cb01c2bafb$a601ab00$7501ff0a@axsppc67>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <02cb01c2bafb$a601ab00$7501ff0a@axsppc67>; from chak@axes-mach01.usa.alcatel.com on Mon, Jan 13, 2003 at 05:32:13PM +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>

PSK,

The point is that IIDs can't fail.  They can only be configured or
unconfigured.  The physical layer upon which the data link is
established can fail, but that is addressed with Release Indication/
Confirmation on an active IID in an AS.

If your phsyical layer fails, send Release Indication with cause
indicating phsyical layer failure to all establsihed signalling
connections: the IID stays active until the ASP sends ASPIA or
ASPDN or the SCTP association is lost.

--brian

PSK Chakravarthi wrote:                                                                (Mon, 13 Jan 2003 17:32:13)
> Brian,
> 
> > IMO, the answer to the question above is the answer to your question
> below.
> > That is, the SG should treat it as though the failure was just after the
> > AS was activated, return ASPAC Ack, and then send the messages to treat
> > the failure.
> 
> How does SG indicate ASP that IIDS are failed?
> 
> Is there any message which can be sent from SG to ASP, to indicate IIDS are
> failed before Establish request for an IID from ASP?
> 
> 
> Thanks
> Chak
> 
> 
> 
> ----- Original Message -----
> From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> To: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
> Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>; "Latha"
> <latha@indts.com>; <sigtran@ietf.org>
> Sent: Monday, January 13, 2003 2:40 PM
> Subject: Re: [Sigtran] IUA - ASP Active and ACTIVE ACK
> 
> 
> > Chak,
> >
> > Then,
> >
> > 1. ASP sending ASPAC for IIDs 1 to 10, per the description under ASPAC
> >    is a request to configure all IIDs provisioned for the one big AS.
> >
> > 2. If there are no other AS configured, sending ASPAC without IIDs and
> >    ASPAC with IIDs 1 to 10 is no different.
> >
> > To answer your question, answer this one:
> >
> > If the SG manages to activate all the IIDs, and then, just after sending
> > ASPAC Ack, IIDs 6-10 fail, what does the SG send to the ASP?
> >
> > IMO, the answer to the question above is the answer to your question
> below.
> > That is, the SG should treat it as though the failure was just after the
> > AS was activated, return ASPAC Ack, and then send the messages to treat
> > the failure.
> >
> > --brian
> >
> >
> > PSK Chakravarthi wrote:
> (Mon, 13 Jan 2003 14:23:54)
> > > Brian,
> > >
> > > All the IIDS are configured to one AS.
> > >
> > > Thanks
> > > Chak
> > > ----- Original Message -----
> > > From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > To: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
> > > Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>; "Latha"
> > > <latha@indts.com>; <sigtran@ietf.org>
> > > Sent: Monday, January 13, 2003 2:14 PM
> > > Subject: Re: [Sigtran] IUA - ASP Active and ACTIVE ACK
> > >
> > >
> > > > Chak,
> > > >
> > > > In your example, how are the IIDs configured
> > > > into Application Servers at the SG?
> > > >
> > > >
> > > > --brian
> > > >
> > > > PSK Chakravarthi wrote:
> > > (Mon, 13 Jan 2003 14:01:09)
> > > > > Brian,
> > > > >
> > > > > Consider the following case:
> > > > >
> > > > > 1. ASP sends ASPAC for IIDS 1 to 10.
> > > > > 2. Due to some reason SG can bring up only IIDS 1 to 5.
> > > > > 3. Now, what does SG send in the ASPAC Ack? (w.r.t IIDS)
> > > > >
> > > > > thanks
> > > > > Chak
> > > > >
> > > >
> > > > --
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > >
> >
> > --
> > 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 mailnull@www1.ietf.org  Mon Jan 13 07:34: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 HAA09495
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 07:34:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DClrG21415
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 07:47:53 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DClaJ21401;
	Mon, 13 Jan 2003 07:47:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DCkwJ21364
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 07:46:58 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09475
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 07:32:48 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0DCa8BE029233;
	Mon, 13 Jan 2003 06:36:08 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0DCZKM08522;
	Mon, 13 Jan 2003 06:35:20 -0600 (CST)
Date: Mon, 13 Jan 2003 06:35:20 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
In-Reply-To: <20030113051227.A9997@openss7.org>
Message-ID: <Pine.SOL.4.10.10301130624200.26959-100000@sun3271.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 Mon, 13 Jan 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Mon, 13 Jan 2003 05:54:19)
> > 
> > Brian,Tolga,
> > 
> >   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 Mon, 13 Jan 2003, TOLGA ASVEREN wrote:
> > 
> > > 
> > > Brian,
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > > > Samuel,
> > > >
> > > > DPC, DPC/SI, even OPC/DPC, OPC/DPC/SI.
> > > >
> > > > But don't forget that the SG can easily Load-Share on CIC, SSN, DLR/SLR,
> > > > TID, etc.  We have just been talking the use of Routing Keys (which are
> > > > 1:1 with the definition of the AS).
> > > >
> > Mean to say ,having multiple SGs pre-configured to serve set of SSN and set
> > of CIC range ...?
> 
> Having any number of SGs pre-configure to serve a set of SSN or set of CIC
> range...

repeated same.
IMO, dynamic ocnfiguration is better than static.

> 
> > 
> > > > So we are saying that it doesn't make too much sense
> > > > to split
> > > > Application Servers into sub-SI Application Servers.
> > 
> > But SUA does it.
> 
> SUA sits above SCCP.  M3UA sits below SCCP.  Having M3UA try to
> route to SCCP-User is a silly as having M2UA (yes, em-two-ua)
> route to MTP Users.
> 
> > 
> > > >  SGs are worried about point code status and user part status and don't
> > > >  care about things like subsystem status.  Having Application Servers
> > > >  (remember, defined by Routing Keys) that are either point codes or user
> > > >  parts therefore makes a lot of sense.
> >
> > disagree, Almost all STPs(SG) more worried about subsystem status...
> > because they are the only nodes which performs GTT to reach 'centralized
> > databse'
> 
> M3UA SG's.  Subsystem status is peformed by SCCP.
> 
> > 
> > > >
> > > > But *within* an Application Server there can be multiple ASPs serving
> > > > the AS.  Load-sharing permits some messages to be sent to some ASPs and
> > > > other messages to be sent to others.  With an extension such as
> > > > draft-bidulock-sigtran-loadsel-01.txt or
> > > > draft-bidulock-sigtran-loadgrp-01.txt the ASP can even be under control
> > > > of which range of traffic it receives.  With a Broadcast AS, the ASPs
> > > > are in control over which messages it chooses to process and which it
> > > > does not choose to process.
> > 
> > Load -sharing on SLS?
> 
> Load-sharing on anything.  SLS is a good one...

Can please give an example other than SLS?

> 
> > 
> > > >
> > > > So, to summarize, using Load-Share or Broadcast Application Servers,
> > > > everyting that one thought could be accomplished with sub-SI granularity
> > > > Routing Keys, is possible with Load-Sharing.
> > 
> > what is 'sub-SI granularity Routing Keys' ?  (said below 'sub-SI granularity
> > Routing Keys' wrong solution for wrong problems)
> 
> RKs with a granularity finer than a Service Indicator (or smaller
> than an MTP-User).

Can you give an example?

> 
> > I understood RFC 3332 was written with an idea of supporting SSN and CIC but
> > after mail communication both were removed.
> 
> SSN and CIC were placed in the draft before RKs and most of the model was
> formalized.  Experience has shown that they are not very useful for routing,
> but are quite useful for loadsharing.  This is because the RK:AS:RC concept
> had to be formalized to permit the SG management of the SPMC, making it no
> longer suited to other more esoteric tasks better addressed with load-sharing
> and broadcast.
> 
> > 
> > Instead of having separate RFC for SUA , we should have merged both into a
> > single RFC.  [just i put my thoughts :-)]
> 
> There is nothing stopping an implementor from runnign M3UA and SUA over the
> same association (with different PPI).  Most of the messaging and and
> proceudre text is identical (even with M2UA).  These protocols reside at
> different layers in the protocol stack and work at different layer interfaces
> within the SS7 stack.  Attempting to generalize all provider/user interfaces
> at all levels of the SS7 stack would have been a recipe for failure.
> 
> Nevertheless, a one point I did say that SUA could have been easily  adjusted
> to do what M3UA claimed to do as well.  All that was necessary was the
> trivial MTP-TRANSFER primitive representation.  SUA supports all other
> necessary message classes and parameters to perform all of M3UA's functions.
> 
> But, SUA still cannot handle CIC routing keys.  But ISUA can: see
> 
> 	draft-bidulock-sigtran-isua-00.txt

Where this is available?
 
> 
> With ISUP and SCCP covered by ISUA and SUA, who needs no stinkin' M3UA?

means what?


> 
> --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 mailnull@www1.ietf.org  Mon Jan 13 07:57: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 HAA10051
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 07:57:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DDBLW23095
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 08:11:21 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DDBBJ23055;
	Mon, 13 Jan 2003 08:11:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DDA1J22975
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 08:10:01 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09994
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 07:55:49 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:m9C3TZ4Iry/48ELhj4jnOXqic6C5N87F@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0DCx9D13854;
	Mon, 13 Jan 2003 05:59:09 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0DCx9I11495;
	Mon, 13 Jan 2003 05:59:09 -0700
Date: Mon, 13 Jan 2003 05:59:09 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030113055909.A11154@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <20030113051227.A9997@openss7.org> <Pine.SOL.4.10.10301130624200.26959-100000@sun3271.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.10301130624200.26959-100000@sun3271.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Mon, Jan 13, 2003 at 06:35:20AM -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,

Samuel Dur D. Jeyaseelan wrote:                                                     (Mon, 13 Jan 2003 06:35:20)
> 
> 
> 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 Mon, 13 Jan 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > Samuel Dur D. Jeyaseelan wrote:                                                     (Mon, 13 Jan 2003 05:54:19)
> > > 
> > > Brian,Tolga,
> > > 
> > >   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 Mon, 13 Jan 2003, TOLGA ASVEREN wrote:
> > > 
> > > > 
> > > > Brian,
> > > > --- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> > > > > Samuel,
> > > > >
> > > > > DPC, DPC/SI, even OPC/DPC, OPC/DPC/SI.
> > > > >
> > > > > But don't forget that the SG can easily Load-Share on CIC, SSN, DLR/SLR,
> > > > > TID, etc.  We have just been talking the use of Routing Keys (which are
> > > > > 1:1 with the definition of the AS).
> > > > >
> > > Mean to say ,having multiple SGs pre-configured to serve set of SSN and set
> > > of CIC range ...?
> > 
> > Having any number of SGs pre-configure to serve a set of SSN or set of CIC
> > range...
> 
> repeated same.

I wrote "any number" of SGs, you wrote "multiple".

> IMO, dynamic ocnfiguration is better than static.

What has that to do with the CIC/SSN dicussion?

> 
> > 
> > > 
> > > > > So we are saying that it doesn't make too much sense
> > > > > to split
> > > > > Application Servers into sub-SI Application Servers.
> > > 
> > > But SUA does it.
> > 
> > SUA sits above SCCP.  M3UA sits below SCCP.  Having M3UA try to
> > route to SCCP-User is a silly as having M2UA (yes, em-two-ua)
> > route to MTP Users.
> > 
> > > 
> > > > >  SGs are worried about point code status and user part status and don't
> > > > >  care about things like subsystem status.  Having Application Servers
> > > > >  (remember, defined by Routing Keys) that are either point codes or user
> > > > >  parts therefore makes a lot of sense.
> > >
> > > disagree, Almost all STPs(SG) more worried about subsystem status...
> > > because they are the only nodes which performs GTT to reach 'centralized
> > > databse'
> > 
> > M3UA SG's.  Subsystem status is peformed by SCCP.
> > 
> > > 
> > > > >
> > > > > But *within* an Application Server there can be multiple ASPs serving
> > > > > the AS.  Load-sharing permits some messages to be sent to some ASPs and
> > > > > other messages to be sent to others.  With an extension such as
> > > > > draft-bidulock-sigtran-loadsel-01.txt or
> > > > > draft-bidulock-sigtran-loadgrp-01.txt the ASP can even be under control
> > > > > of which range of traffic it receives.  With a Broadcast AS, the ASPs
> > > > > are in control over which messages it chooses to process and which it
> > > > > does not choose to process.
> > > 
> > > Load -sharing on SLS?
> > 
> > Load-sharing on anything.  SLS is a good one...
> 
> Can please give an example other than SLS?

CIC, SSN, TID, SLR/DLR.

> 
> > 
> > > 
> > > > >
> > > > > So, to summarize, using Load-Share or Broadcast Application Servers,
> > > > > everyting that one thought could be accomplished with sub-SI granularity
> > > > > Routing Keys, is possible with Load-Sharing.
> > > 
> > > what is 'sub-SI granularity Routing Keys' ?  (said below 'sub-SI granularity
> > > Routing Keys' wrong solution for wrong problems)
> > 
> > RKs with a granularity finer than a Service Indicator (or smaller
> > than an MTP-User).
> 
> Can you give an example?

CIC, SSN.

> 
> > 
> > > I understood RFC 3332 was written with an idea of supporting SSN and CIC but
> > > after mail communication both were removed.
> > 
> > SSN and CIC were placed in the draft before RKs and most of the model was
> > formalized.  Experience has shown that they are not very useful for routing,
> > but are quite useful for loadsharing.  This is because the RK:AS:RC concept
> > had to be formalized to permit the SG management of the SPMC, making it no
> > longer suited to other more esoteric tasks better addressed with load-sharing
> > and broadcast.
> > 
> > > 
> > > Instead of having separate RFC for SUA , we should have merged both into a
> > > single RFC.  [just i put my thoughts :-)]
> > 
> > There is nothing stopping an implementor from runnign M3UA and SUA over the
> > same association (with different PPI).  Most of the messaging and and
> > proceudre text is identical (even with M2UA).  These protocols reside at
> > different layers in the protocol stack and work at different layer interfaces
> > within the SS7 stack.  Attempting to generalize all provider/user interfaces
> > at all levels of the SS7 stack would have been a recipe for failure.
> > 
> > Nevertheless, a one point I did say that SUA could have been easily  adjusted
> > to do what M3UA claimed to do as well.  All that was necessary was the
> > trivial MTP-TRANSFER primitive representation.  SUA supports all other
> > necessary message classes and parameters to perform all of M3UA's functions.
> > 
> > But, SUA still cannot handle CIC routing keys.  But ISUA can: see
> > 
> > 	draft-bidulock-sigtran-isua-00.txt
> 
> Where this is available?

   The list of current Internet-Drafts can be accessed at 
   http://www.ietf.org/ietf/1id-abstracts.txt 
    
   The list of Internet-Draft Shadow Directories can be accessed at 
   http://www.ietf.org/shadow.html. 

   but you can find it here too:

	ftp://ftp.ietf.org/internet-drafts/draft-bidulock-sigtran-isua-00.txt
	http://www.ietf.org/internet-drafts/draft-bidulock-sigtran-isua-00.txt
	http://www.openss7.org/sigtran01.html
	
>  
> > 
> > With ISUP and SCCP covered by ISUA and SUA, who needs no stinkin' M3UA?
> 
> means what?

means that!

-- 
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 Jan 13 08:51: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 IAA10883
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 08:51:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DE50H25860
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 09:05:00 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DE4dJ25823;
	Mon, 13 Jan 2003 09:04:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DE3JJ25780
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 09:03:19 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10838
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 08:49:06 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0DDqNOZ001700;
	Mon, 13 Jan 2003 07:52:24 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id SAA08641; Mon, 13 Jan 2003 18:21:32 -0500 (GMT)
Message-ID: <3E22C4B3.A5106283@axes-mach01.usa.alcatel.com>
Date: Mon, 13 Jan 2003 19:22:52 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M2PA two out of three
References: <3E153380.ACD487B0@axes-mach01.usa.alcatel.com> <20030103012425.A10860@openss7.org> <3E155467.7E0C192E@axes-mach01.usa.alcatel.com> <20030103022225.A11987@openss7.org> <3E193095.BAFC0B1D@axes-mach01.usa.alcatel.com> <20030106005410.B7546@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

Brian,

For the following

"M2PA should follow the criterion of [2] Q.703, section 5.3.1 for
incorrect BSNs: If any two BSNs in three consecutively received User
Data messages are not the same as the previous one or any of the FSNs
of the User Data messages in the M2PA transmit buffer at the time they
are received, then MTP3 should be informed that the link is faulty."

Can you please tell me whether my assumption is correct.

(let us think that all the consecutively received User Data messages are
different and also '0' means valid BSN is received and '1' means invalid BSN is
received)

0  0  0       Do not fail the link
0  0  1       Do not fail the link
0  1  0       Do not fail the link
0  1  1       Fail the link
1  0  0       Do not fail the link
1  0  1       Fail the link
1  1  0       Fail the link
1  1  1       Fail the link

--Srini

"Brian F. G. Bidulock" wrote:

> Srini,
>
> In fact, if the BSNR is outside the range (inclusive) from FSNF-1 to FSNT
> twice consecutively, then the link should fail.  Note that FSNT is always
> set to the last correct BSNR.  See the SDLs in Q.703 or T1.111.
>
> I would agree that M2PA should not repeat statements from these
> specifications, but should merely reference them.  (Particularly as some
> corrections were made to SDLs in the Q.703 IG.)
>
> --brian
>
> ksrinivas wrote:                               (Mon, 06 Jan 2003 13:00:30)
> >
> >    Brian,
> >                                                    _    _
> >          If  one  reads  the sentence as A + B, then the following can be
> >    interpreted.
> >
> >    Fail the link, if
> >
> >          either
> >           any two BSNs in three consecutively received User Data messages
> >    are not the same as the previous one
> >          or
> >          not the same as any of the FSNs of the User Data messages in the
> >    M2PA transmit buffer at the time they are received
> >
> >
> >                                                         _  _
> >    But I feel this is mis-leading, We should fail the link only when both
> >    the conditions(A.B) are met.
> >
> >    --Srini
> >
>
> --
> 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 mailnull@www1.ietf.org  Mon Jan 13 08:51: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 IAA10896
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 08:51:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DE56t25896
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 09:05:06 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DE4oJ25852;
	Mon, 13 Jan 2003 09:04:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DE3lJ25794
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 09:03:47 -0500
Received: from tank.fr.ulticom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10843
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 08:49:34 -0500 (EST)
Received: from PCGASTAUDL (pc-gastaud-l.fr.ulticom.com [172.26.32.87])
	by tank.fr.ulticom.com (8.8.8+Sun/8.8.8) with SMTP id OAA11848
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 14:52:54 +0100 (MET)
From: "Valerie Gastaud" <valerie.gastaud@ulticom.com>
To: <sigtran@ietf.org>
Subject: RE: [Sigtran] m3ua- IG
Date: Mon, 13 Jan 2003 15:17:21 +0100
Message-ID: <NDBBIHAOCKGAMIKNLALOOECPDKAA.valerie.gastaud@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <OFA471186E.5F208D0A-ONC2256CAD.003C72E5@LocalDomain>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 8bit
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

I don't want to restart the debate, I think we all agree that M3UA must be
preferably used with PC and/or SIO type of RK.
Can we however add a section in the M3UA-IG indicating that M3UA RK=SSN

is limited to:
- class 0/1
- single SG

and requires:
- NIF to intercept SCCP management messages received from SS7 and to send
them to all the SSNs (AS), with the exception of SST which should only be
sent to the Affected SSN (AS).
The SCCP management message must be sent within the AS depending on the
traffic mode and ASP status.

Valerie

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
TOLGA ASVEREN
Sent: lundi 13 janvier 2003 12:14
To: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG



Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org> wrote:
> Samuel,
>
> DPC, DPC/SI, even OPC/DPC, OPC/DPC/SI.
>
> But don't forget that the SG can easily Load-Share
> on CIC, SSN,
> DLR/SLR, TID, etc.  We have just been talking the
> use of Routing
> Keys (which are 1:1 with the definition of the AS).
>
> So we are saying that it doesn't make too much sense
> to split
> Application Servers into sub-SI Application Servers.
>  SGs are
> worried about point code status and user part status
> and don't
> care about things like subsystem status.  Having
> Application
> Servers (remember, defined by Routing Keys) that are
> either
> point codes or user parts therefore makes a lot of
> sense.
>
> But *within* an Application Server there can be
> multiple ASPs
> serving the AS.  Load-sharing permits some messages
> to be sent
> to some ASPs and other messages to be sent to
> others.  With an
> extension such as
> draft-bidulock-sigtran-loadsel-01.txt or
> draft-bidulock-sigtran-loadgrp-01.txt the ASP can
> even be under
> control of which range of traffic it receives.  With
> a Broadcast
> AS, the ASPs are in control over which messages it
> chooses to
> process and which it does not choose to process.
>
> So, to summarize, using Load-Share or Broadcast
> Application
> Servers, everyting that one thought could be
> accomplished with
> sub-SI granularity Routing Keys, is possible with
> Load-Sharing.
> It, however, does not mess up the SG's view of PC
> and SI state
> and is therefore interoperable.
>
> Sub-SI RKs are just the wrong solution for the wrong
> problem.
> Load distribution with Load-sharing or Broadcast is
> the
> proscribed way of distributing traffic over multiple
> ASPs.
[TOLGA] I totally agree, if loadsaring addresses the needs, it is the way
to go. But not always it might be a perfect solution, one has to make the
upper layers distributed over multiple ASPs to work as a single entity. If
the number of ASPs serving the same AS increases, this might be too costly
and if one limits number of ASPs -let´s say they are low end systems- one
might not have desired processing power. With separete RKs, this wouldn´t
be a problem, one could slice the traffic into multiple AS, where each of
them is served by a reasonable number of ASPs -not as much as the
loadsharing case, so that synchronization is less costly- adn because there
are multiple AS, total number of ASPs is still big enough to have the
needed processing power. So, IMO loadsharing and separete RKs are not
exactly the same. But I also agree, trying to support non-MTP3 RKs is quite
ugly/for some of them maybe not possible.
>
> So, we should remove SSN and CIC from Routing Key
> (even restrict
> RK to not have non-MTP3 RKs) and yet, keep the
> sections where
> they are mentioned for load-sharing.  This gives
> maximum
> interoperability without sacrificing any
> functionality.
>
> --brian
>
> Samuel Dur D. Jeyaseelan wrote:
>                                (Mon, 13 Jan 2003
> 04:29:54)
> >
> > Hi,
> >
> > So the concensus was M3UA can not be used
> effectively between
> > STP(SG) to SCP(AS) -- unawareness of SSN
> >
> > can not be used effectively with MGC- unawareness
> of cic
> >
> > now i have a doubt , Where M3UA can be used
> effectively?
> >
> > any node which routes messae on DPC- here it is
> used , thats all?

_______________________________________________
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 Jan 13 08:57: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 IAA10961
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 08:57:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DEBJT26740
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 09:11:19 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DEB6J26725;
	Mon, 13 Jan 2003 09:11:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DEABJ26699
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 09:10:11 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10954
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 08:56:01 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:8EA/tv1fwzLlWIJS/mrt44EYsLYaLY8k@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0DDxJD14634;
	Mon, 13 Jan 2003 06:59:19 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0DDxJR12902;
	Mon, 13 Jan 2003 06:59:19 -0700
Date: Mon, 13 Jan 2003 06:59:19 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Valerie Gastaud <valerie.gastaud@ulticom.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030113065919.A12809@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Valerie Gastaud <valerie.gastaud@ulticom.com>,
	sigtran@ietf.org
References: <OFA471186E.5F208D0A-ONC2256CAD.003C72E5@LocalDomain> <NDBBIHAOCKGAMIKNLALOOECPDKAA.valerie.gastaud@ulticom.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: <NDBBIHAOCKGAMIKNLALOOECPDKAA.valerie.gastaud@ulticom.com>; from valerie.gastaud@ulticom.com on Mon, Jan 13, 2003 at 03:17:21PM +0100
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>

Valerie,

An editor of the IG thought it was worth a separate draft.
Would you care to start one seeing as you seem to have an
idea how your would like to see it set up?

--brian

Valerie Gastaud wrote:                                                             (Mon, 13 Jan 2003 15:17:21)
> I don't want to restart the debate, I think we all agree that M3UA must be
> preferably used with PC and/or SIO type of RK.
> Can we however add a section in the M3UA-IG indicating that M3UA RK=SSN
> 
> is limited to:
> - class 0/1
> - single SG
> 
> and requires:
> - NIF to intercept SCCP management messages received from SS7 and to send
> them to all the SSNs (AS), with the exception of SST which should only be
> sent to the Affected SSN (AS).
> The SCCP management message must be sent within the AS depending on the
> traffic mode and ASP status.
> 
> Valerie
> 

-- 
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 Jan 13 09:07: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 JAA11182
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 09:07:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DELHp27055
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 09:21:17 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DEKwJ27026;
	Mon, 13 Jan 2003 09:20:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DEJbJ26937
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 09:19:37 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11161
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 09:05:26 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:77cVuwPE+T+bP5Gm8QtiZa15gfF2x0M3@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0DE8jD14814;
	Mon, 13 Jan 2003 07:08:45 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0DE8jC13331;
	Mon, 13 Jan 2003 07:08:45 -0700
Date: Mon, 13 Jan 2003 07:08:45 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M2PA two out of three
Message-ID: <20030113070845.B12809@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <3E153380.ACD487B0@axes-mach01.usa.alcatel.com> <20030103012425.A10860@openss7.org> <3E155467.7E0C192E@axes-mach01.usa.alcatel.com> <20030103022225.A11987@openss7.org> <3E193095.BAFC0B1D@axes-mach01.usa.alcatel.com> <20030106005410.B7546@openss7.org> <3E22C4B3.A5106283@axes-mach01.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: <3E22C4B3.A5106283@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Mon, Jan 13, 2003 at 07:22:52PM +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>

ksrinivas,

ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 19:22:52)
> Brian,
> 
> For the following
> 
> "M2PA should follow the criterion of [2] Q.703, section 5.3.1 for
> incorrect BSNs: If any two BSNs in three consecutively received User
> Data messages are not the same as the previous one or any of the FSNs
> of the User Data messages in the M2PA transmit buffer at the time they
> are received, then MTP3 should be informed that the link is faulty."
> 
> Can you please tell me whether my assumption is correct.
> 
> (let us think that all the consecutively received User Data messages are
> different and also '0' means valid BSN is received and '1' means invalid BSN is
> received)
> 
> 0  0  0       Do not fail the link
> 0  0  1       Do not fail the link
> 0  1  0       Do not fail the link
> 0  1  1       Fail the link
> 1  0  0       Do not fail the link
> 1  0  1       Fail the link
> 1  1  0       Fail the link
> 1  1  1       Fail the link


Write it this way:

0 0 0 0   don't fail
0 0 0 1   don't fail
0 0 1 0   don't fail
0 0 1 1   fail
0 1 0 1   fail

--brian


> 
> --Srini
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Srini,
> >
> > In fact, if the BSNR is outside the range (inclusive) from FSNF-1 to FSNT
> > twice consecutively, then the link should fail.  Note that FSNT is always
> > set to the last correct BSNR.  See the SDLs in Q.703 or T1.111.
> >
> > I would agree that M2PA should not repeat statements from these
> > specifications, but should merely reference them.  (Particularly as some
> > corrections were made to SDLs in the Q.703 IG.)
> >
> > --brian
> >
> > ksrinivas wrote:                               (Mon, 06 Jan 2003 13:00:30)
> > >
> > >    Brian,
> > >                                                    _    _
> > >          If  one  reads  the sentence as A + B, then the following can be
> > >    interpreted.
> > >
> > >    Fail the link, if
> > >
> > >          either
> > >           any two BSNs in three consecutively received User Data messages
> > >    are not the same as the previous one
> > >          or
> > >          not the same as any of the FSNs of the User Data messages in the
> > >    M2PA transmit buffer at the time they are received
> > >
> > >
> > >                                                         _  _
> > >    But I feel this is mis-leading, We should fail the link only when both
> > >    the conditions(A.B) are met.
> > >
> > >    --Srini
> > >
> >
> > --
> > 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 mailnull@www1.ietf.org  Mon Jan 13 09:17: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 JAA11509
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 09:17:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DEVU927670
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 09:31:30 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DEVEJ27598;
	Mon, 13 Jan 2003 09:31:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DEU0J27483
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 09:30:00 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11355
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 09:15:50 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:K5WXzFbxVEy4GoUtRTUwHDFJhh5dkTAv@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0DEJ9D14944;
	Mon, 13 Jan 2003 07:19:09 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0DEJ8C13629;
	Mon, 13 Jan 2003 07:19:08 -0700
Date: Mon, 13 Jan 2003 07:19:08 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: M2PA two out of three
Message-ID: <20030113071908.A13505@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <3E153380.ACD487B0@axes-mach01.usa.alcatel.com> <20030103012425.A10860@openss7.org> <3E155467.7E0C192E@axes-mach01.usa.alcatel.com> <20030103022225.A11987@openss7.org> <3E193095.BAFC0B1D@axes-mach01.usa.alcatel.com> <20030106005410.B7546@openss7.org> <3E22C4B3.A5106283@axes-mach01.usa.alcatel.com> <20030113070845.B12809@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: <20030113070845.B12809@openss7.org>; from bidulock@openss7.org on Mon, Jan 13, 2003 at 07:08:45AM -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>

ksrinivas,

Brian F. G. Bidulock wrote:                                                      (Mon, 13 Jan 2003 07:08:45)
> ksrinivas,
> 
> ksrinivas wrote:                                                                 (Mon, 13 Jan 2003 19:22:52)
> > Brian,
> > 
> > For the following
> > 
> > "M2PA should follow the criterion of [2] Q.703, section 5.3.1 for
> > incorrect BSNs: If any two BSNs in three consecutively received User
> > Data messages are not the same as the previous one or any of the FSNs
> > of the User Data messages in the M2PA transmit buffer at the time they
> > are received, then MTP3 should be informed that the link is faulty."
> > 
> > Can you please tell me whether my assumption is correct.
> > 
> > (let us think that all the consecutively received User Data messages are
> > different and also '0' means valid BSN is received and '1' means invalid BSN is
> > received)
> > 
> > 0  0  0       Do not fail the link
> > 0  0  1       Do not fail the link
> > 0  1  0       Do not fail the link
> > 0  1  1       Fail the link
> > 1  0  0       Do not fail the link
> > 1  0  1       Fail the link
> > 1  1  0       Fail the link
> > 1  1  1       Fail the link
> 
> 
> Write it this way:
> 
> 0 0 0 0   don't fail
> 0 0 0 1   don't fail
> 0 0 1 0   don't fail
> 0 0 1 1   fail
> 0 1 0 1   fail
> 
> --brian

Err, one more time....

0 0 0 0   don't fail
0 0 0 1   don't fail
0 0 1 0   don't fail
0 1 0 0   don't fail
1 0 0 0   don't fail
1 0 0 1   don't fail
0 0 1 1   fail
0 1 0 1   fail

--brian

> 
> 
> > 
> > --Srini
> > 
> > "Brian F. G. Bidulock" wrote:
> > 
> > > Srini,
> > >
> > > In fact, if the BSNR is outside the range (inclusive) from FSNF-1 to FSNT
> > > twice consecutively, then the link should fail.  Note that FSNT is always
> > > set to the last correct BSNR.  See the SDLs in Q.703 or T1.111.
> > >
> > > I would agree that M2PA should not repeat statements from these
> > > specifications, but should merely reference them.  (Particularly as some
> > > corrections were made to SDLs in the Q.703 IG.)
> > >
> > > --brian
> > >
> > > ksrinivas wrote:                               (Mon, 06 Jan 2003 13:00:30)
> > > >
> > > >    Brian,
> > > >                                                    _    _
> > > >          If  one  reads  the sentence as A + B, then the following can be
> > > >    interpreted.
> > > >
> > > >    Fail the link, if
> > > >
> > > >          either
> > > >           any two BSNs in three consecutively received User Data messages
> > > >    are not the same as the previous one
> > > >          or
> > > >          not the same as any of the FSNs of the User Data messages in the
> > > >    M2PA transmit buffer at the time they are received
> > > >
> > > >
> > > >                                                         _  _
> > > >    But I feel this is mis-leading, We should fail the link only when both
> > > >    the conditions(A.B) are met.
> > > >
> > > >    --Srini
> > > >
> > >
> > > --
> > > 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 mailnull@www1.ietf.org  Mon Jan 13 10:41: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 KAA13822
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 10:40:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DFsf100957
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 10:54:41 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DFsGJ00930;
	Mon, 13 Jan 2003 10:54:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DFrMJ00860
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 10:53:22 -0500
Received: from cerberus.intellinet-tech.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13781
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 10:39:09 -0500 (EST)
Received: from coolcat (coolcat.internal.net [192.168.1.46])
	by cerberus.intellinet-tech.com (8.11.6/8.11.6) with SMTP id h0DFcgb16277;
	Mon, 13 Jan 2003 10:38:42 -0500
From: "Narendar Goel" <ngoel@intellinet-tech.com>
To: <bidulock@openss7.org>,
        "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: <sigtran@ietf.org>
Subject: RE: [Sigtran] m3ua- IG
Date: Mon, 13 Jan 2003 10:34:43 -0500
Message-ID: <PGELKEIGGCBDEJFINJFEEEANCGAA.ngoel@intellinet-tech.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)
Importance: Normal
In-Reply-To: <20030113035150.A7367@openss7.org>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
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

Brian,
 I agree adding sub SIO routing keys is not a good ides at m3ua level. But
loading sharing traffic based on SSN, CIC or TID is only one possible
solution
to the problem of destributing application traffic. One of the other
possible
solution is using distributed shared memory (DSM) for sharing context among
ASPs. This DSM approach is simpler in certain implementation conditions. DSM
solution provides truly distributed and fault tolerant application server.

-Narender

~
~

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
Brian F. G. Bidulock
Sent: Monday, January 13, 2003 5:52 AM
To: Samuel Dur D. Jeyaseelan
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG


Samuel,

DPC, DPC/SI, even OPC/DPC, OPC/DPC/SI.

But don't forget that the SG can easily Load-Share on CIC, SSN,
DLR/SLR, TID, etc.  We have just been talking the use of Routing
Keys (which are 1:1 with the definition of the AS).

So we are saying that it doesn't make too much sense to split
Application Servers into sub-SI Application Servers.  SGs are
worried about point code status and user part status and don't
care about things like subsystem status.  Having Application
Servers (remember, defined by Routing Keys) that are either
point codes or user parts therefore makes a lot of sense.

But *within* an Application Server there can be multiple ASPs
serving the AS.  Load-sharing permits some messages to be sent
to some ASPs and other messages to be sent to others.  With an
extension such as draft-bidulock-sigtran-loadsel-01.txt or
draft-bidulock-sigtran-loadgrp-01.txt the ASP can even be under
control of which range of traffic it receives.  With a Broadcast
AS, the ASPs are in control over which messages it chooses to
process and which it does not choose to process.

So, to summarize, using Load-Share or Broadcast Application
Servers, everyting that one thought could be accomplished with
sub-SI granularity Routing Keys, is possible with Load-Sharing.
It, however, does not mess up the SG's view of PC and SI state
and is therefore interoperable.

Sub-SI RKs are just the wrong solution for the wrong problem.
Load distribution with Load-sharing or Broadcast is the
proscribed way of distributing traffic over multiple ASPs.

So, we should remove SSN and CIC from Routing Key (even restrict
RK to not have non-MTP3 RKs) and yet, keep the sections where
they are mentioned for load-sharing.  This gives maximum
interoperability without sacrificing any functionality.

--brian

Samuel Dur D. Jeyaseelan wrote:
(Mon, 13 Jan 2003 04:29:54)
>
> Hi,
>
> So the concensus was M3UA can not be used effectively between
> STP(SG) to SCP(AS) -- unawareness of SSN
>
> can not be used effectively with MGC- unawareness of cic
>
> now i have a doubt , Where M3UA can be used effectively?
>
> any node which routes messae on DPC- here it is used , 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

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



From mailnull@www1.ietf.org  Mon Jan 13 11:21:25 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 LAA15696
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 11:21:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DGZ7003833
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 11:35:07 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DGYVJ03776;
	Mon, 13 Jan 2003 11:34:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DGXoJ03696
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 11:33:50 -0500
Received: from mink.ecitele.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15623;
	Mon, 13 Jan 2003 11:19:33 -0500 (EST)
From: Lev.Finkel@ecitele.com
Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125])
	by mink.ecitele.com (8.9.1a/8.9.1) with ESMTP id SAA00266;
	Mon, 13 Jan 2003 18:17:07 +0200 (IST)
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
To: bidulock@openss7.org
Cc: chak@axes-mach01.usa.alcatel.com, ksrini@axes-mach01.usa.alcatel.com,
        latha@indts.com, sigtran@ietf.org, sigtran-admin@ietf.org
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OFF961A7B4.4A5E3809-ONC2256CAD.0056FC68@ecitele.com>
Date: Mon, 13 Jan 2003 18:17:47 +0200
X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at
 01/13/2003 06:22:22 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>


Brian,

I mean NOTIFY message exists and must be sent when the AS status is
changed.
I agree that ACTIVE ACK is to be send on response on ACTIVE. If for
internal SG reason the AS is down for certain IID, the SG must send NOTIFY
to the ASPs.
This just to confirm your statement, that inability to answer OK is just
the same as a failure at any moment later.

Thanks,
Lev



                                                                                                           
                      "Brian F. G.                                                                         
                      Bidulock"                To:      Lev.Finkel@ecitele.com                             
                      <bidulock@openss         cc:      chak@axes-mach01.usa.alcatel.com,                  
                      7.org>                   ksrini@axes-mach01.usa.alcatel.com, latha@indts.com,        
                                               sigtran@ietf.org, sigtran-admin@ietf.org                    
                      13/01/03 13:53           Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK     
                      Please respond                                                                       
                      to bidulock                                                                          
                                                                                                           
                                                                                                           



Lev.Finkel,

Notify(AS_inactive) is never sent after sending ASPAC Ack because the
AS is active.  Where in the RFC did you think this was stated?

--brian

Lev.Finkel@ecitele.com wrote:
(Mon, 13 Jan 2003 13:33:23)
>
> Notify(AS_inactive) or another corresponding notify is the way provided
in
> RFC.
>
> Regards, Lev
>
>

--
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 Jan 13 17:28: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 RAA26332
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 17:28:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DMfpP28699
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 17:41:51 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DMfXJ28692;
	Mon, 13 Jan 2003 17:41:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DMaDJ27846
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 17:36:13 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26163
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 17:21:51 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:HDgflcA60cWHh8JmI3AX5jT0USVW9ioy@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0DMPBD22855;
	Mon, 13 Jan 2003 15:25:11 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0DMPBA00920;
	Mon, 13 Jan 2003 15:25:11 -0700
Date: Mon, 13 Jan 2003 15:25:10 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Narendar Goel <ngoel@intellinet-tech.com>
Cc: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030113152510.A330@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Narendar Goel <ngoel@intellinet-tech.com>,
	"Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030113035150.A7367@openss7.org> <PGELKEIGGCBDEJFINJFEEEANCGAA.ngoel@intellinet-tech.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: <PGELKEIGGCBDEJFINJFEEEANCGAA.ngoel@intellinet-tech.com>; from ngoel@intellinet-tech.com on Mon, Jan 13, 2003 at 10:34:43AM -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>

Narendar,

Yes, loadsharing on CIC, SSN should not be mandatory.  ASP can use
other communications mechanisms (e.g. a ASP-ASP protocol) to transfer
messages to the correct place.  Also, there is broadcast mode where
each ASP gets each message and the ASP itself can decide which messages
to process and which to leave for other ASPs.

--brian

Narendar Goel wrote:                                                              (Mon, 13 Jan 2003 10:34:43)
> Brian,
>  I agree adding sub SIO routing keys is not a good ides at m3ua level. But
> loading sharing traffic based on SSN, CIC or TID is only one possible
> solution
> to the problem of destributing application traffic. One of the other
> possible
> solution is using distributed shared memory (DSM) for sharing context among
> ASPs. This DSM approach is simpler in certain implementation conditions. DSM
> solution provides truly distributed and fault tolerant application server.
> 
> -Narender
> 

-- 
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 Jan 13 17:29: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 RAA26376
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 17:29:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0DMhCm28812
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 17:43:12 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DMh3J28803;
	Mon, 13 Jan 2003 17:43:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0DMgIJ28752
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 17:42:18 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26330;
	Mon, 13 Jan 2003 17:27:56 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:EVTPQGm2B0HahkofPgPq4z+ouMb2wFXf@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0DMVFD22984;
	Mon, 13 Jan 2003 15:31:15 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0DMVFw01235;
	Mon, 13 Jan 2003 15:31:15 -0700
Date: Mon, 13 Jan 2003 15:31:15 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Lev.Finkel@ecitele.com
Cc: chak@axes-mach01.usa.alcatel.com, ksrini@axes-mach01.usa.alcatel.com,
        latha@indts.com, sigtran@ietf.org, sigtran-admin@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030113153115.B330@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Lev.Finkel@ecitele.com, chak@axes-mach01.usa.alcatel.com,
	ksrini@axes-mach01.usa.alcatel.com, latha@indts.com,
	sigtran@ietf.org, sigtran-admin@ietf.org
References: <OFF961A7B4.4A5E3809-ONC2256CAD.0056FC68@ecitele.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: <OFF961A7B4.4A5E3809-ONC2256CAD.0056FC68@ecitele.com>; from Lev.Finkel@ecitele.com on Mon, Jan 13, 2003 at 06:17:47PM +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>

Lev.Finkel,

Lev.Finkel@ecitele.com wrote:                                                   (Mon, 13 Jan 2003 18:17:47)
> 
> Brian,
> 
> I mean NOTIFY message exists and must be sent when the AS status is
> changed.
> I agree that ACTIVE ACK is to be send on response on ACTIVE. If for
> internal SG reason the AS is down for certain IID, the SG must send NOTIFY
> to the ASPs.

The procedure for doing this that was imported into M2UA from the
other UAs by the IG is to send ASPIA Ack.  Notify is only advisory
and will not illicit the correct response in the ASP.  In response
to ASPIA Ack, the ASP must put itself in the ASP-INACTIVE state for
the AS, and then issue ASPAC.  Then the SG can return ERR("Invalid
IID") to the ASPAC if, indeed, the AS has been "unconfigured".  If
the AS has not been "unconfigured" in the first place, the SG should
not be deactivating the AS at all.   It should be clearing the
signalling connection with a Release Indication.

--brian

> This just to confirm your statement, that inability to answer OK is just
> the same as a failure at any moment later.
> 
> Thanks,
> Lev
> 
> 
> 
>                                                                                                            
>                       "Brian F. G.                                                                         
>                       Bidulock"                To:      Lev.Finkel@ecitele.com                             
>                       <bidulock@openss         cc:      chak@axes-mach01.usa.alcatel.com,                  
>                       7.org>                   ksrini@axes-mach01.usa.alcatel.com, latha@indts.com,        
>                                                sigtran@ietf.org, sigtran-admin@ietf.org                    
>                       13/01/03 13:53           Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK     
>                       Please respond                                                                       
>                       to bidulock                                                                          
>                                                                                                            
>                                                                                                            
> 
> 
> 
> Lev.Finkel,
> 
> Notify(AS_inactive) is never sent after sending ASPAC Ack because the
> AS is active.  Where in the RFC did you think this was stated?
> 
> --brian
> 
> Lev.Finkel@ecitele.com wrote:
> (Mon, 13 Jan 2003 13:33:23)
> >
> > Notify(AS_inactive) or another corresponding notify is the way provided
> in
> > RFC.
> >
> > Regards, Lev
> >
> >
> 
> --
> 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 mailnull@www1.ietf.org  Mon Jan 13 18:54:23 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 SAA28856
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 18:54:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0E08FG01803
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 19:08:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E083J01789;
	Mon, 13 Jan 2003 19:08:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E05oJ01028
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 19:05:51 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28802
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 18:51:26 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Ww82BGpvCM+/GhDgSVzxV2gS0KKcrpp7@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0DNsjD24342;
	Mon, 13 Jan 2003 16:54:46 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0DNsj605655;
	Mon, 13 Jan 2003 16:54:45 -0700
Date: Mon, 13 Jan 2003 16:54:45 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Wung, Joseph" <JWung@sonusnet.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA default AS
Message-ID: <20030113165445.B3638@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Wung, Joseph" <JWung@sonusnet.com>, sigtran@ietf.org
References: <4CF48720B6E9D4118D040060CF2074E9072F6BD3@sonusdc3.sonusnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <4CF48720B6E9D4118D040060CF2074E9072F6BD3@sonusdc3.sonusnet.com>; from JWung@sonusnet.com on Mon, Jan 13, 2003 at 01:59:33PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

Joseph,

Load sharing follows the rule that any ASP in the AS must be prepared to
receive any message for that AS.  Routing does not follow (and cannot be
made to follow) this rule.  draft-bidulock-sigtran-loadsel-01.txt
follows this precept as well.

That's why RK is so problematic at CIC granularity, whereas loadsharing
on CIC is not.  The SG can try to get the message to the correct place
in loadsharing, and failing a match on a load selection, can distribute
message over the ASPs in the AS using some other rule (round-robin,
default, etc.), or can loadshare based on Message Type (such as
distributing CGB differently than IAM, and IAM differently than other
call processing messages), but the ASPs must be designed to handle
messages outside of their load selection (but still within the Routing
Key/Application Server/Routing Context).  So, if the message goes
astray within the AS (i.e. is sent to any ASP instead of particular
ASPs) it is the responsibility of the ASP to treat the message in the
context of the MTP-User and not the SG's responsibility.

Also, loadsharing does not change the scope of the AS which remains as
an SEP or MTP-User, permitting the SG to reflect AS state to the SS7
network as SEP or MTP-User state.

Perhaps the reason that you don't see the difference is because you were
thinking that Routing Keys were useful for load distribution.  They are
not.

Routing includes the concept of management of a route and reflection of
the state of a route (RK:AS:RC) to the SS7 network.  By definition it
should be no more granular than SSNM permits.

Loadsharing is splitting the offered traffic load within an Application
Server over multiple ASPs that clients of the SG within that Application
Server.  By definition it must be more granular than the Application
Server/Routing Key/Routing Context.  Loadsharing for M3UA must preserve
ordering, so all loadsharing algorithms must not split traffic across
multiple streams or multiple ASPs to avoid re-ordering.  Loadsharing
must therefore be performed on SLS or a parameter which is invariant
with respect to SLS (e.g. CIC, DLR/SLR, TID).

Does that clarify it better?

--brian

On Mon, 13 Jan 2003, Wung, Joseph wrote:

> Brain,
> 
> I'm reading your LOADSEL, but can't distinguish loading
> sharing from routing.  It seems to me that the loadsharing
> is just another layer of routing using finer granularity.
> Can you help here?
> 
> Joe
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Thursday, January 09, 2003 8:56 PM
> > To: Wung, Joseph
> > Cc: 'sigtran@ietf.org'
> > Subject: Re: [Sigtran] M3UA default AS
> > 
> > 
> > Joseph,
> > 
> > Don't try to use CIC routing for this: use CIC load-sharing.
> > Then the SG knows that it can send CIC=100 to any of the ASPs in
> > the load-share AS.  If you need to have controlled load-sharing
> > consider:
> > 
> > 	draft-bidulock-sigtran-loadsel-01.txt and
> > 	draft-bidulock-sigtran-loadgrp-01.txt
> > 
> > that I have just submitted to the I-D drafts editor.
> > 
> > Until they are available on the I-D server, you will find a copy
> > here:
> > 
> > 	http://www.openss7.org/sigtran01.html
> > 
> > --brian
> > 
> > Wung, Joseph wrote:                                           
> >                        (Thu, 09 Jan 2003 19:02:49)
> > > M3UA section 1.4.2.4 says
> > > 
> > > 	"When there is no matching Routing Key entry for an
> > > 	incoming SS7 message, a default treatment MAY be
> > > 	specified.  Possible solutions are to provide a default
> > > 	AS at the SGP that directs all unallocated traffic to a
> > > 	(set of) default ASP(s), or to drop the message and
> > > 	provide a notification to layer management."
> > > 
> > > I have, say, 3 ASPs:
> > > 	ASP-1 for OPC/DPC/CIC=1-24
> > > 	ASP-2 for OPC/DPC/CIC=25-48
> > > 	ASP-3 for OPC/DPC/CIC=49-72,
> > > 	where OPC/DPC are the same.
> > > 
> > > How would the SGP route an incoming message with OPC/DPC/CIC=100.
> > > My question is since the default AS is not registered, thus no
> > > associated traffic mode, how does the SGP know the received 
> > > message should be broadcast to all 3 of the ASPs or select one 
> > > of them to send to?
> > > 
> > > Joe
> > > _______________________________________________
> > > 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    ¦ 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 Jan 13 20:52: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 UAA01337
	for <sigtran-archive@odin.ietf.org>; Mon, 13 Jan 2003 20:52:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0E26gF08194
	for sigtran-archive@odin.ietf.org; Mon, 13 Jan 2003 21:06:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E26UJ08163;
	Mon, 13 Jan 2003 21:06:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E25VJ08118
	for <sigtran@optimus.ietf.org>; Mon, 13 Jan 2003 21:05:31 -0500
Received: from cerberus.intellinet-tech.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01311
	for <sigtran@ietf.org>; Mon, 13 Jan 2003 20:51:04 -0500 (EST)
From: ngoel@cerberus.intellinet-tech.com
Received: from localhost (ngoel@localhost)
	by cerberus.intellinet-tech.com (8.11.6/8.11.6) with ESMTP id h0E1oec02652;
	Mon, 13 Jan 2003 20:50:40 -0500
Date: Mon, 13 Jan 2003 20:50:40 -0500 (EST)
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: "Wung, Joseph" <JWung@sonusnet.com>, <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA default AS
In-Reply-To: <20030113165445.B3638@openss7.org>
Message-ID: <Pine.LNX.4.44.0301132041310.2221-100000@cerberus.intellinet-tech.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>

On Mon, 13 Jan 2003, Brian F. G. Bidulock wrote:
Brian,
 Have to considered protocol error conditions in load sharing model. Do SG 
need to handle respective error conditiond? Do loadsharing always be 
specified for entire spectrum of traffic. For example -
1. If sccp receives message with return option and ssn is unknown then 
SCCP is supposed to generate UDTS with reason=unequipped SSN. Does SG 
generate this UDTS? Or which ASP shall receive this message?
2. Same is the case for TCAP, if it receives a message with invalid TID 
P-Abort is generated. If TID is not present in load shared TID then does 
SG generate p-abort?
Do you recommend load sharing for entire spectrum of traffic or some kind 
of default behaviour at the SG.
-Narender
 
> Joseph,
> 
> Load sharing follows the rule that any ASP in the AS must be prepared to
> receive any message for that AS.  Routing does not follow (and cannot be
> made to follow) this rule.  draft-bidulock-sigtran-loadsel-01.txt
> follows this precept as well.
> 
> That's why RK is so problematic at CIC granularity, whereas loadsharing
> on CIC is not.  The SG can try to get the message to the correct place
> in loadsharing, and failing a match on a load selection, can distribute
> message over the ASPs in the AS using some other rule (round-robin,
> default, etc.), or can loadshare based on Message Type (such as
> distributing CGB differently than IAM, and IAM differently than other
> call processing messages), but the ASPs must be designed to handle
> messages outside of their load selection (but still within the Routing
> Key/Application Server/Routing Context).  So, if the message goes
> astray within the AS (i.e. is sent to any ASP instead of particular
> ASPs) it is the responsibility of the ASP to treat the message in the
> context of the MTP-User and not the SG's responsibility.
> 
> Also, loadsharing does not change the scope of the AS which remains as
> an SEP or MTP-User, permitting the SG to reflect AS state to the SS7
> network as SEP or MTP-User state.
> 
> Perhaps the reason that you don't see the difference is because you were
> thinking that Routing Keys were useful for load distribution.  They are
> not.
> 
> Routing includes the concept of management of a route and reflection of
> the state of a route (RK:AS:RC) to the SS7 network.  By definition it
> should be no more granular than SSNM permits.
> 
> Loadsharing is splitting the offered traffic load within an Application
> Server over multiple ASPs that clients of the SG within that Application
> Server.  By definition it must be more granular than the Application
> Server/Routing Key/Routing Context.  Loadsharing for M3UA must preserve
> ordering, so all loadsharing algorithms must not split traffic across
> multiple streams or multiple ASPs to avoid re-ordering.  Loadsharing
> must therefore be performed on SLS or a parameter which is invariant
> with respect to SLS (e.g. CIC, DLR/SLR, TID).
> 
> Does that clarify it better?
> 
> --brian
> 
> On Mon, 13 Jan 2003, Wung, Joseph wrote:
> 
> > Brain,
> > 
> > I'm reading your LOADSEL, but can't distinguish loading
> > sharing from routing.  It seems to me that the loadsharing
> > is just another layer of routing using finer granularity.
> > Can you help here?
> > 
> > Joe
> > 
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: Thursday, January 09, 2003 8:56 PM
> > > To: Wung, Joseph
> > > Cc: 'sigtran@ietf.org'
> > > Subject: Re: [Sigtran] M3UA default AS
> > > 
> > > 
> > > Joseph,
> > > 
> > > Don't try to use CIC routing for this: use CIC load-sharing.
> > > Then the SG knows that it can send CIC=100 to any of the ASPs in
> > > the load-share AS.  If you need to have controlled load-sharing
> > > consider:
> > > 
> > > 	draft-bidulock-sigtran-loadsel-01.txt and
> > > 	draft-bidulock-sigtran-loadgrp-01.txt
> > > 
> > > that I have just submitted to the I-D drafts editor.
> > > 
> > > Until they are available on the I-D server, you will find a copy
> > > here:
> > > 
> > > 	http://www.openss7.org/sigtran01.html
> > > 
> > > --brian
> > > 
> > > Wung, Joseph wrote:                                           
> > >                        (Thu, 09 Jan 2003 19:02:49)
> > > > M3UA section 1.4.2.4 says
> > > > 
> > > > 	"When there is no matching Routing Key entry for an
> > > > 	incoming SS7 message, a default treatment MAY be
> > > > 	specified.  Possible solutions are to provide a default
> > > > 	AS at the SGP that directs all unallocated traffic to a
> > > > 	(set of) default ASP(s), or to drop the message and
> > > > 	provide a notification to layer management."
> > > > 
> > > > I have, say, 3 ASPs:
> > > > 	ASP-1 for OPC/DPC/CIC=1-24
> > > > 	ASP-2 for OPC/DPC/CIC=25-48
> > > > 	ASP-3 for OPC/DPC/CIC=49-72,
> > > > 	where OPC/DPC are the same.
> > > > 
> > > > How would the SGP route an incoming message with OPC/DPC/CIC=100.
> > > > My question is since the default AS is not registered, thus no
> > > > associated traffic mode, how does the SGP know the received 
> > > > message should be broadcast to all 3 of the ASPs or select one 
> > > > of them to send to?
> > > > 
> > > > Joe
> > > > _______________________________________________
> > > > 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 Jan 14 01:00:17 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 BAA06166
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 01:00:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0E6EGt22823
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 01:14:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E6DnJ22811;
	Tue, 14 Jan 2003 01:13:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E6CdJ22775
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 01:12:39 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06135
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 00:58:07 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:DujbMaEpF4hUUdCFA3bXKfB5jMK5eXxX@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0E61RD29788;
	Mon, 13 Jan 2003 23:01:27 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0E61Rf18567;
	Mon, 13 Jan 2003 23:01:27 -0700
Date: Mon, 13 Jan 2003 23:01:27 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ngoel@cerberus.intellinet-tech.com
Cc: "Wung, Joseph" <JWung@sonusnet.com>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA default AS
Message-ID: <20030113230127.B17229@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ngoel@cerberus.intellinet-tech.com,
	"Wung, Joseph" <JWung@sonusnet.com>, sigtran@ietf.org
References: <20030113165445.B3638@openss7.org> <Pine.LNX.4.44.0301132041310.2221-100000@cerberus.intellinet-tech.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.LNX.4.44.0301132041310.2221-100000@cerberus.intellinet-tech.com>; from ngoel@cerberus.intellinet-tech.com on Mon, Jan 13, 2003 at 08:50:40PM -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>

Narender,

ngoel@cerberus.intellinet-tech.com wrote:                                            (Mon, 13 Jan 2003 20:50:40)
> On Mon, 13 Jan 2003, Brian F. G. Bidulock wrote:
> Brian,
>  Have to considered protocol error conditions in load sharing model. Do SG 
> need to handle respective error conditiond? Do loadsharing always be 
> specified for entire spectrum of traffic. For example -
> 1. If sccp receives message with return option and ssn is unknown then 
> SCCP is supposed to generate UDTS with reason=unequipped SSN. Does SG 
> generate this UDTS? Or which ASP shall receive this message?

The loadsharing rule is that any ASP in the loadshare AS must be prepared to
receive any message.  A policy at the SG could send these messages round-robin
to ASPs active in the AS or could send them to a particular ASP according to
the loadsharing algorithm.

For M3UA, the ASP generates the UDTS, for SUA and TUA the SG generates the
UDTS.

> 2. Same is the case for TCAP, if it receives a message with invalid TID 
> P-Abort is generated. If TID is not present in load shared TID then does 
> SG generate p-abort?

For SUA the ASP generates the P-Abort, for TUA the SG generates the P-Abort.
For TUA see draft-bidulock-sigtran-tua-01.txt currently on the I-D server.

> Do you recommend load sharing for entire spectrum of traffic or some kind 
> of default behaviour at the SG.

Traffic which matches a load selection can be routed to the ASP currently
responsible for that load selection.  Traffic which does not match any load
selection can be passed to any active ASP in the AS.  The SG could implement
policies that might be of use (round-robin, default ASP) for traffic not
maching a load selection and stil remain completely interoperable and within
the specification.

In particular, in the case of UDTS, a compliant SCCP implementation at any of
the ASPs in the AS will return UDTS properly if sent the offending message.
The same is true for TID if loadsharing on TID is performed.  Any complilant
TCAP implementation on any of the ASPs in the AS will return P-Abort.

The problem with trying to use loadsharing on SSN or TID with M3UA is that the
ASPs in the AS are collectively responsible for all subsystem management.
M3UA should not broadcast SCMG messages.

In fact, this is a problem for MTP Level 3 in M3UA: the specification says
that (a copy of each) SNMM are sent to each active ASP in the AS.

" 4.5.1 At an SGP
" 
"    On receiving an MTP-PAUSE, MTP-RESUME or MTP-STATUS indication
"    primitive from the nodal interworking function at an SGP, the SGP
"    M3UA layer will send a corresponding SS7 Signalling Network
"    Management (SSNM) DUNA, DAVA, SCON, or DUPU message (see Section 3.4)
"    to the M3UA peers at concerned ASPs.  The M3UA layer must fill in
"    various fields of the SSNM messages consistently with the information
"    received in the primitives.
" 
"    The SGP M3UA layer determines the set of concerned ASPs to be
"    informed based on the specific SS7 network for which the primitive
"    indication is relevant. In this way, all ASPs configured to
"    send/receive traffic within a particular network appearance are
"    informed.  If the SGP operates within a single SS7 network
"    appearance, then all ASPs are informed.

(And, of course, SSNM are not sent to ASPs in the ASP-INACTIVE state for an
AS.)

This can have a disasterous effect on ITU-T congestion management at the AS,
if the ASPs were to indicate each SCON received by an ASP to a combined AS
congestion state machine, but there may be cases where an ASP will never
receive one of these SSNM.  Consider the following:


                  SG
             +-----------+                +-----------+
             |           |    Assoc 1     |           |
             |   SGP1    |----------------|   ASP1    |
             |           |\   Assoc 2     |           |
             +-----------+ \___________   +-----------+
                   |                   \
             +-----------+              \ +-----------+
             |           |    Assoc 3    \|           |
             |   SGP2    |----------------|   ASP2    |
             |           |                |           |
             +-----------+                +-----------+


When SGP2 issues a SCON, according to the M3UA spec, it will be sent to APS2
only (because it is only sent to APSs which are active for the AS at the SGP).
So ASP1 does not receive SCON and continues sending traffic at full rate to
SGP1.  When the distant point in the network response with TFC, it might again
appear at SGP2, only informing ASP2 and traffic is not throttled at ASP1.  If
ASP1 is, indeed, responsible for the congestion, part of the SS7 network will
eventually fail with this approach.

Then there is this horrendous situation:

                  SG
             +-----------+                +-----------+
             |           |    Assoc 1     |           |
             |   SGP1    |----------------|   ASP1    |
             |           |                |           |
             +-----------+                +-----------+
                   |                    
             +-----------+                +-----------+
             |           |    Assoc 2     |           |
             |   SGP2    |----------------|   ASP2    |
             |           |                |           |
             +-----------+                +-----------+
                   |                    
             +-----------+                +-----------+
             |           |    Assoc 3     |           |
             |   SGP3    |----------------|   ASP3    |
             |           |                |           |
             +-----------+                +-----------+
                   |                    
             +-----------+                +-----------+
             |           |    Assoc 4     |           |
             |   SGP4    |----------------|   ASP4    |
             |           |                |           |
             +-----------+                +-----------+

In the case above, only one ASP will ever receive an SSNM message under the
curent rule (because the SGP determines the concerned ASPs, not the SG).

If the requirement were that the "SG" (instead of SGP) sends a copy to each
ASP, then the SG would need a way to identify which ASP was which to avoid
sending a given ASP multiple copies (and breaking ITU-T congestion algoritms
at the MTP-User).  It might be possible to use ASP Id (or its equivalent in
terms of the transport addresses of the connecting ASPs) to accomplish this
under normal operating conditions.

So it appears that even getting SSNM messages correct give the M3UA SG some
grief.  How do you ever expect it to get SCCP or TCAP management correct?

M3UA terminates and handles signalling-route-set-test and signalling-route-
set-congestion-test messages at the SG and maintains the signalling point and
user state at the SG to respond to these messages.  The ASP never sees these
messages.  This avoids having to figure out which ASP is going to respond to
the test.  But for SCMG and in particular subsystem-test messages (SST), the
M3UA SG cannot handle responding to the messages itself.  Using the
loadsharing rule, the M3UA SG could send a single copy of the SST to any one
of the ASPs active in the AS for DPC/SI=SCCP, and that ASP would be
responsible for the response.  SCCP congestion messages (as well as SSP,SSA)
would still need to be broadcast to ASPs on an SG-wide basis as with SCON
above.  But this broadcast within an load-share AS is not within the rules for
load-share AS in the M3UA specification.  M3UA addresses SSNM separate from
DATA to handle this, but SCCP management messages are just DATA and are only
sent to one ASP in a load-share AS, not all of them on an SG-wide restricted
basis.

Rather than try to overload all of this into M3UA, it is still better to use
SUA.  SUA includes all of these considerations by placing a standards
compliant SCCP at the SG.

TCAP gets even more interesting, because TCAP management is not even specified
in the scope of the TCAP protocol (other than echoing through SCCP
management).  It is at the discretion  of the application to implement
whatever management is necessary.  So, for example, IN/AIN uses ACG (automatic
code gapping) parameters in TCAP transaction to throttle transaction rates.
Ensuring that ACG gets to the correct ASP(s) in loadshare AS at the M3UA level
would require large chunks of SCCP and TCAP state machines.  It is simpler to
address TCAP with SUA (or better still TUA).

Error situations such as you mention are simple compared to management
messages.

Now, if you are stuck using M3UA (because some foolish people specified it
for, say, 3GPP, and at draft level 7, which should never have been referenced)
then you can still use SUA _between_ ASPs (or some other state sharing or
message passing) to redistribute traffic at the AS as you had mentioned in
your previous note.  In that case, loadsharing on SLS is the wisest thing to
do to equally distribute the load within the AS.  Then the ASP itself is
responsible for distributing copies of SSP, etc., to its brethren, and the
exercise at the ASP is a simple one of building a distributed SCCP
implementation.

Wel, I could go on... ;)

--brian

> -Narender
>  
> > Joseph,
> > 
> > Load sharing follows the rule that any ASP in the AS must be prepared to
> > receive any message for that AS.  Routing does not follow (and cannot be
> > made to follow) this rule.  draft-bidulock-sigtran-loadsel-01.txt
> > follows this precept as well.
> > 
> > That's why RK is so problematic at CIC granularity, whereas loadsharing
> > on CIC is not.  The SG can try to get the message to the correct place
> > in loadsharing, and failing a match on a load selection, can distribute
> > message over the ASPs in the AS using some other rule (round-robin,
> > default, etc.), or can loadshare based on Message Type (such as
> > distributing CGB differently than IAM, and IAM differently than other
> > call processing messages), but the ASPs must be designed to handle
> > messages outside of their load selection (but still within the Routing
> > Key/Application Server/Routing Context).  So, if the message goes
> > astray within the AS (i.e. is sent to any ASP instead of particular
> > ASPs) it is the responsibility of the ASP to treat the message in the
> > context of the MTP-User and not the SG's responsibility.
> > 
> > Also, loadsharing does not change the scope of the AS which remains as
> > an SEP or MTP-User, permitting the SG to reflect AS state to the SS7
> > network as SEP or MTP-User state.
> > 
> > Perhaps the reason that you don't see the difference is because you were
> > thinking that Routing Keys were useful for load distribution.  They are
> > not.
> > 
> > Routing includes the concept of management of a route and reflection of
> > the state of a route (RK:AS:RC) to the SS7 network.  By definition it
> > should be no more granular than SSNM permits.
> > 
> > Loadsharing is splitting the offered traffic load within an Application
> > Server over multiple ASPs that clients of the SG within that Application
> > Server.  By definition it must be more granular than the Application
> > Server/Routing Key/Routing Context.  Loadsharing for M3UA must preserve
> > ordering, so all loadsharing algorithms must not split traffic across
> > multiple streams or multiple ASPs to avoid re-ordering.  Loadsharing
> > must therefore be performed on SLS or a parameter which is invariant
> > with respect to SLS (e.g. CIC, DLR/SLR, TID).
> > 
> > Does that clarify it better?
> > 
> > --brian
> > 
> > On Mon, 13 Jan 2003, Wung, Joseph wrote:
> > 
> > > Brain,
> > > 
> > > I'm reading your LOADSEL, but can't distinguish loading
> > > sharing from routing.  It seems to me that the loadsharing
> > > is just another layer of routing using finer granularity.
> > > Can you help here?
> > > 
> > > Joe
> > > 
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: Thursday, January 09, 2003 8:56 PM
> > > > To: Wung, Joseph
> > > > Cc: 'sigtran@ietf.org'
> > > > Subject: Re: [Sigtran] M3UA default AS
> > > > 
> > > > 
> > > > Joseph,
> > > > 
> > > > Don't try to use CIC routing for this: use CIC load-sharing.
> > > > Then the SG knows that it can send CIC=100 to any of the ASPs in
> > > > the load-share AS.  If you need to have controlled load-sharing
> > > > consider:
> > > > 
> > > > 	draft-bidulock-sigtran-loadsel-01.txt and
> > > > 	draft-bidulock-sigtran-loadgrp-01.txt
> > > > 
> > > > that I have just submitted to the I-D drafts editor.
> > > > 
> > > > Until they are available on the I-D server, you will find a copy
> > > > here:
> > > > 
> > > > 	http://www.openss7.org/sigtran01.html
> > > > 
> > > > --brian
> > > > 
> > > > Wung, Joseph wrote:                                           
> > > >                        (Thu, 09 Jan 2003 19:02:49)
> > > > > M3UA section 1.4.2.4 says
> > > > > 
> > > > > 	"When there is no matching Routing Key entry for an
> > > > > 	incoming SS7 message, a default treatment MAY be
> > > > > 	specified.  Possible solutions are to provide a default
> > > > > 	AS at the SGP that directs all unallocated traffic to a
> > > > > 	(set of) default ASP(s), or to drop the message and
> > > > > 	provide a notification to layer management."
> > > > > 
> > > > > I have, say, 3 ASPs:
> > > > > 	ASP-1 for OPC/DPC/CIC=1-24
> > > > > 	ASP-2 for OPC/DPC/CIC=25-48
> > > > > 	ASP-3 for OPC/DPC/CIC=49-72,
> > > > > 	where OPC/DPC are the same.
> > > > > 
> > > > > How would the SGP route an incoming message with OPC/DPC/CIC=100.
> > > > > My question is since the default AS is not registered, thus no
> > > > > associated traffic mode, how does the SGP know the received 
> > > > > message should be broadcast to all 3 of the ASPs or select one 
> > > > > of them to send to?
> > > > > 
> > > > > Joe
> > > > > _______________________________________________
> > > > > 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 mailnull@www1.ietf.org  Tue Jan 14 01: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 BAA06601
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 01:30:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0E6icI24593
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 01:44:38 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E6iKJ24564;
	Tue, 14 Jan 2003 01:44:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E6huJ24542
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 01:43:56 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06565
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 01:29:23 -0500 (EST)
Subject: Re: [Sigtran] M3UA default AS
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF5EA56AB8.36803F8D-ONC2256CAE.0022E8CC@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Tue, 14 Jan 2003 08:29:19 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/14/2003
 08:29:24 AM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0E6huJ24543
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

                                                                            
                                                                            
                                                                            
                                                                            
                                                                            
                                                                            
                                                                            
   Brian,                                                                   
                                                                            
   [...snip....]                                                            
   This can have a disasterous effect on ITU-T congestion management at     
   the AS,                                                                  
   if the ASPs were to indicate each SCON received by an ASP to a combined  
   AS                                                                       
   congestion state machine, but there may be cases where an ASP will       
   never                                                                    
   receive one of these SSNM.  Consider the following:                      
                                                                            
                                                                            
                     SG                                                     
                +-----------+                +-----------+                  
                |           |    Assoc 1     |           |                  
                |   SGP1    |----------------|   ASP1    |                  
                |           |\   Assoc 2     |           |                  
                +-----------+ \___________   +-----------+                  
                      |                   \                                 
                +-----------+              \ +-----------+                  
                |           |    Assoc 3    \|           |                  
                |   SGP2    |----------------|   ASP2    |                  
                |           |                |           |                  
                +-----------+                +-----------+                  
                                                                            
                                                                            
   When SGP2 issues a SCON, according to the M3UA spec, it will be sent to  
   APS2                                                                     
   only (because it is only sent to APSs which are active for the AS at     
   the SGP).                                                                
   So ASP1 does not receive SCON and continues sending traffic at full      
   rate to                                                                  
   SGP1.  When the distant point in the network response with TFC, it       
   might again                                                              
   appear at SGP2, only informing ASP2 and traffic is not throttled at      
   ASP1.  If                                                                
   ASP1 is, indeed, responsible for the congestion, part of the SS7         
   network will                                                             
   eventually fail with this approach.                                      
                                                                            
   [TOLGA]If ASP1 is INACTIVE, why is it used to send DATA? If both ASPs    
   are serving the same AS, shouldn´t the user part running on top of them  
   work as a single entity? In such a case, why is SCON arriving via ASP2   
   not enough to execute necessary procedures on user part level? I would   
   think it is the user part not the M3UA at ASP, which throttles traffic   
   when necessary.                                                          
                                                                            
                                                                            
                                                                            
                                                                            





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



From mailnull@www1.ietf.org  Tue Jan 14 01:53: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 BAA07107
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 01:53:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0E77bT29260
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 02:07:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E77DJ28916;
	Tue, 14 Jan 2003 02:07:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E76OJ27928
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 02:06:24 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07094
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 01:51:51 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0E6tABE010173;
	Tue, 14 Jan 2003 00:55:11 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0E6stM04064;
	Tue, 14 Jan 2003 00:54:55 -0600 (CST)
Date: Tue, 14 Jan 2003 00:54:55 -0600 (CST)
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] m3ua- IG
In-Reply-To: <20030113152510.A330@openss7.org>
Message-ID: <Pine.SOL.4.10.10301140048100.26959-100000@sun3271.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,

section A.2.2

   .............................................The distribution of
   the MTP3-user messages over the SGPs should be done in such a way to
   minimize message missequencing, as required by the SS7 User Parts.

How ASP sends message to SGP?

 The point codes ASP has registered , only to those point codes
 ASP can generate messages?

 or 

ASP can send message to any point codes (which even he has not
regsitered)?

--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 mailnull@www1.ietf.org  Tue Jan 14 02:17:56 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 CAA17392
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 02:17:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0E7Vvc05414
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 02:31:57 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E7VYJ05378;
	Tue, 14 Jan 2003 02:31:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E7UoJ05090
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 02:30:50 -0500
Received: from ganesh.ctd.hctech.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17352
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 02:16:16 -0500 (EST)
Received: by GANESH with Internet Mail Service (5.5.2653.19)
	id <CL2F2HLV>; Tue, 14 Jan 2003 12:49:27 +0530
Message-ID: <55E277B99171E041ABF5F4B1C6DDCA0601171C03@haritha.hclt.com>
From: "Vishwanatham Mallik - CTD, Chennai." <pvmallik@ctd.hcltech.com>
To: sigtran@ietf.org
Date: Tue, 14 Jan 2003 12:51:56 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] pls. UNSUBSCRIBE me from the mailing list.
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>

Can somebody here unsubscribe me from the SIGTRAN mailing list.

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



From mailnull@www1.ietf.org  Tue Jan 14 02:42: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 CAA17814
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 02:42:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0E7uoH07277
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 02:56:50 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E7uNJ07252;
	Tue, 14 Jan 2003 02:56:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E7tJJ07213
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 02:55:19 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17783
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 02:40:46 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:XQFb/UHLvygKKsuMNlo60IhLhvB4Qwrz@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0E7i6D31244;
	Tue, 14 Jan 2003 00:44:06 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0E7i6h20273;
	Tue, 14 Jan 2003 00:44:06 -0700
Date: Tue, 14 Jan 2003 00:44:06 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA default AS
Message-ID: <20030114004406.A18871@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF5EA56AB8.36803F8D-ONC2256CAE.0022E8CC@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF5EA56AB8.36803F8D-ONC2256CAE.0022E8CC@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Tue, Jan 14, 2003 at 08:29:19AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                            (Tue, 14 Jan 2003 08:29:19)
>                                                                             
>                      SG                                                     
>                 +-----------+                +-----------+                  
>                 |           |    Assoc 1     |           |                  
>                 |   SGP1    |----------------|   ASP1    |                  
>                 |           |\   Assoc 2     |           |                  
>                 +-----------+ \___________   +-----------+                  
>                       |                   \                                 
>                 +-----------+              \ +-----------+                  
>                 |           |    Assoc 3    \|           |                  
>                 |   SGP2    |----------------|   ASP2    |                  
>                 |           |                |           |                  
>                 +-----------+                +-----------+                  
>                                                                             
>                                                                             
>    [TOLGA]If ASP1 is INACTIVE, why is it used to send DATA? If both ASPs    
>    are serving the same AS, shouldn´t the user part running on top of them  
>    work as a single entity? In such a case, why is SCON arriving via ASP2   
>    not enough to execute necessary procedures on user part level? I would   
>    think it is the user part not the M3UA at ASP, which throttles traffic   
>    when necessary.                                                          

No, both ASP1 and ASP2 are ASP-ACTIVE for the AS.  Its just that SGP2 has
not association with ASP1 and SSNM is stated as being sent on by an SGP
(not by an SG).

If the ASPs deliver SCON to a "combined" view of the AS, then when SGP1
sends SCON to both ASP1 and ASP2 per the procedure, MTP-STATUS will appear
twice at the AS.  For ANSI (with level indicated) this might not be a problem,
but for ITU-T it is: the number of times within an interval that MTP-STATUS
indicating congestion is delivered to an MTP-User such as ISUP affects the
congestion algorithm.  The ASPs cannot correlate the SSNM, because it cannot
due to diagram and the current procedure.

--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  Tue Jan 14 02:47: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 CAA17918
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 02:47:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0E81SO07540
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 03:01:28 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E815J07487;
	Tue, 14 Jan 2003 03:01:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E80UJ07452
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 03:00:30 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17892
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 02:45:56 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:HSfgfanUNQe/+M8nuwf1+oAg4O/56UpK@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0E7nHD31302;
	Tue, 14 Jan 2003 00:49:17 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0E7nHv20359;
	Tue, 14 Jan 2003 00:49:17 -0700
Date: Tue, 14 Jan 2003 00:49:17 -0700
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] m3ua- IG
Message-ID: <20030114004917.B18871@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030113152510.A330@openss7.org> <Pine.SOL.4.10.10301140048100.26959-100000@sun3271.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.10301140048100.26959-100000@sun3271.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Tue, Jan 14, 2003 at 12:54:55AM -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,

The Routing Context identifies a traffic flow (in both directions).  In
general an ASP should not send traffic for a Routing Context to point codes
from which it cannot receive traffic for the same Routing Context.

This is only an issue for non-MTP-SAP routing keys.  MTP-SAP routing keys
are those which identify either a complete signalling point (DPC) or which
identify an MTP-User at a signalling point (DPC/SI).

For security and screening purposes, an SG cannot be expected to transfer
messages which do not belong to the Application Server.

--brian


Samuel Dur D. Jeyaseelan wrote:                  (Tue, 14 Jan 2003 00:54:55)
> 
> Brian,
> 
> section A.2.2
> 
>    .............................................The distribution of
>    the MTP3-user messages over the SGPs should be done in such a way to
>    minimize message missequencing, as required by the SS7 User Parts.
> 
> How ASP sends message to SGP?
> 
>  The point codes ASP has registered , only to those point codes
>  ASP can generate messages?
> 
>  or 
> 
> ASP can send message to any point codes (which even he has not
> regsitered)?
> 
> --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. *******
> 

-- 
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 Jan 14 04:04: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 EAA19445
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 04:04:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0E9IN212905
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 04:18:23 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E9HsJ12879;
	Tue, 14 Jan 2003 04:17:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E9GRJ12828
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 04:16:27 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19416
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 04:01:53 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0E957BS006474;
	Tue, 14 Jan 2003 03:05:09 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id NAA24943; Tue, 14 Jan 2003 13:32:55 -0500 (GMT)
Message-ID: <3E23D299.D2ED57A1@axes-mach01.usa.alcatel.com>
Date: Tue, 14 Jan 2003 14:34:25 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
References: <20030113152510.A330@openss7.org> <Pine.SOL.4.10.10301140048100.26959-100000@sun3271.ssd.usa.alcatel.com> <20030114004917.B18871@openss7.org>
Content-Type: multipart/alternative;
 boundary="------------BC61892F1F471D4EB407F80C"
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>


--------------BC61892F1F471D4EB407F80C
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 7bit

Brian,

   Does the OPC list in the REG Req indicates to the SGP that the AS can send or
receive traffic from these point codes (of OPC list) only?.

If true then, Does the OPC list skipped in the REG Req indicates to the SGP that
the AS can send or receive traffic from any point code?.

--Srini

"Brian F. G. Bidulock" wrote:

> Samuel,
>
> The Routing Context identifies a traffic flow (in both directions).  In
> general an ASP should not send traffic for a Routing Context to point codes
> from which it cannot receive traffic for the same Routing Context.
>
> This is only an issue for non-MTP-SAP routing keys.  MTP-SAP routing keys
> are those which identify either a complete signalling point (DPC) or which
> identify an MTP-User at a signalling point (DPC/SI).
>
> For security and screening purposes, an SG cannot be expected to transfer
> messages which do not belong to the Application Server.
>
> --brian
>
> Samuel Dur D. Jeyaseelan wrote:                  (Tue, 14 Jan 2003 00:54:55)
> >
> > Brian,
> >
> > section A.2.2
> >
> >    .............................................The distribution of
> >    the MTP3-user messages over the SGPs should be done in such a way to
> >    minimize message missequencing, as required by the SS7 User Parts.
> >
> > How ASP sends message to SGP?
> >
> >  The point codes ASP has registered , only to those point codes
> >  ASP can generate messages?
> >
> >  or
> >
> > ASP can send message to any point codes (which even he has not
> > regsitered)?
> >
> > --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. *******
> >
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

--------------BC61892F1F471D4EB407F80C
Content-Type: text/html; charset=x-user-defined
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Brian,
<p>&nbsp;&nbsp; Does the OPC list in the REG Req indicates to the SGP that
the AS can <b>send</b> or <b>receive</b> traffic from these point codes
(of OPC list) only?.
<p>If true then, Does the OPC list skipped in the REG Req indicates to
the SGP that the AS can <b>send</b> or <b>receive</b> traffic from any
point code?.
<p>--Srini
<p>"Brian F. G. Bidulock" wrote:
<blockquote TYPE=CITE>Samuel,
<p>The Routing Context identifies a traffic flow (in both directions).&nbsp;
In
<br>general an ASP should not send traffic for a Routing Context to point
codes
<br>from which it cannot receive traffic for the same Routing Context.
<p>This is only an issue for non-MTP-SAP routing keys.&nbsp; MTP-SAP routing
keys
<br>are those which identify either a complete signalling point (DPC) or
which
<br>identify an MTP-User at a signalling point (DPC/SI).
<p>For security and screening purposes, an SG cannot be expected to transfer
<br>messages which do not belong to the Application Server.
<p>--brian
<p>Samuel Dur D. Jeyaseelan wrote:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
(Tue, 14 Jan 2003 00:54:55)
<br>>
<br>> Brian,
<br>>
<br>> section A.2.2
<br>>
<br>>&nbsp;&nbsp;&nbsp; .............................................The
distribution of
<br>>&nbsp;&nbsp;&nbsp; the MTP3-user messages over the SGPs should be
done in such a way to
<br>>&nbsp;&nbsp;&nbsp; minimize message missequencing, as required by
the SS7 User Parts.
<br>>
<br>> How ASP sends message to SGP?
<br>>
<br>>&nbsp; The point codes ASP has registered , only to those point codes
<br>>&nbsp; ASP can generate messages?
<br>>
<br>>&nbsp; or
<br>>
<br>> ASP can send message to any point codes (which even he has not
<br>> regsitered)?
<br>>
<br>> --Samuel
<br>>
<br>>
<br>>&nbsp;&nbsp; Alcatel USA, Inc.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet: &lt;userid>@ssd.usa.alcatel.com
<br>>&nbsp;&nbsp; 1000 Coit Road, Plano, Texas 75075
<br>>&nbsp;&nbsp; ******* The opinions expressed are not those of Alcatel
USA, Inc. *******
<br>>
<p>--
<br>Brian F. G. Bidulock
<br>bidulock@openss7.org
<br><a href="http://www.openss7.org/">http://www.openss7.org/</a>
<br>_______________________________________________
<br>Sigtran mailing list
<br>Sigtran@ietf.org
<br><a href="https://www1.ietf.org/mailman/listinfo/sigtran">https://www1.ietf.org/mailman/listinfo/sigtran</a></blockquote>
</html>

--------------BC61892F1F471D4EB407F80C--

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



From mailnull@www1.ietf.org  Tue Jan 14 04:05: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 EAA19463
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 04:05:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0E9JEU12957
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 04:19:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E9J5J12949;
	Tue, 14 Jan 2003 04:19:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E9HfJ12873
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 04:17:41 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19436
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 04:03:07 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0E96PBS006541;
	Tue, 14 Jan 2003 03:06:25 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0E964M08448;
	Tue, 14 Jan 2003 03:06:04 -0600 (CST)
Date: Tue, 14 Jan 2003 03:06:04 -0600 (CST)
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] m3ua- IG
In-Reply-To: <20030114004917.B18871@openss7.org>
Message-ID: <Pine.SOL.4.10.10301140249230.26959-100000@sun3271.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 Tue, 14 Jan 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> The Routing Context identifies a traffic flow (in both directions).  In
> general an ASP should not send traffic for a Routing Context to point codes
> from which it cannot receive traffic for the same Routing Context.
> 
                                (PC 333)
                                STP/SG-------------------AS
                               |  
                               |  
    NODE-A(PC 111)-------------+
    |
    |  
    +------NODE-B(PC 222)

AS registers PC 111 with SG.

Say NODE-A sends query to PC 333( performs GTT and reaches AS) AS returns
a LRN number to NODE-A.

NODE-A finds that LRN is actually a subcriber of NODE-B
But at NODE-B MTP-restart procedure is going on.

So NODE-A sends TFP(PC 222) to STP.
In this scenario Will SG send DUNA(affected PC 222) to AS?
(note AS is unware of PC 222)

--Samuel

> This is only an issue for non-MTP-SAP routing keys.  MTP-SAP routing keys
> are those which identify either a complete signalling point (DPC) or which
> identify an MTP-User at a signalling point (DPC/SI).
> 
> For security and screening purposes, an SG cannot be expected to transfer
> messages which do not belong to the Application Server.
> 
> --brian
> 
> 
> Samuel Dur D. Jeyaseelan wrote:                  (Tue, 14 Jan 2003 00:54:55)
> > 
> > Brian,
> > 
> > section A.2.2
> > 
> >    .............................................The distribution of
> >    the MTP3-user messages over the SGPs should be done in such a way to
> >    minimize message missequencing, as required by the SS7 User Parts.
> > 
> > How ASP sends message to SGP?
> > 
> >  The point codes ASP has registered , only to those point codes
> >  ASP can generate messages?
> > 
> >  or 
> > 
> > ASP can send message to any point codes (which even he has not
> > regsitered)?
> > 
> > --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. *******
> > 
> 
> -- 
> 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 mailnull@www1.ietf.org  Tue Jan 14 04:38: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 EAA19968
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 04:38:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0E9qVp14948
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 04:52:31 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E9q9J14929;
	Tue, 14 Jan 2003 04:52:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E9pRJ14873
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 04:51:27 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19935
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 04:36:52 -0500 (EST)
Subject: Re: [Sigtran] M3UA default AS
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF29F5AD75.1D17007B-ONC2256CAE.003234C9@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Tue, 14 Jan 2003 11:36:48 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/14/2003
 11:36:54 AM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0E9pRJ14874
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


Brian,
> TOLGA,
>
> TOLGA ASVEREN wrote:
> (Tue, 14 Jan 2003 08:29:19)
> >
>
> >                      SG
>
> >                 +-----------+
> +-----------+
> >                 |           |    Assoc 1     |
>       |
> >                 |   SGP1    |----------------|
> ASP1    |
> >                 |           |\   Assoc 2     |
>       |
> >                 +-----------+ \___________
> +-----------+
> >                       |                   \
>
> >                 +-----------+              \
> +-----------+
> >                 |           |    Assoc 3    \|
>       |
> >                 |   SGP2    |----------------|
> ASP2    |
> >                 |           |                |
>       |
> >                 +-----------+
> +-----------+
> >
>
> >
>
> >    [TOLGA]If ASP1 is INACTIVE, why is it used to
> send DATA? If both ASPs
> >    are serving the same AS, shouldn´t the user
> part running on top of them
> >    work as a single entity? In such a case, why is
> SCON arriving via ASP2
> >    not enough to execute necessary procedures on
> user part level? I would
> >    think it is the user part not the M3UA at ASP,
> which throttles traffic
> >    when necessary.
>
>
> No, both ASP1 and ASP2 are ASP-ACTIVE for the AS.
> Its just that SGP2 has
> not association with ASP1 and SSNM is stated as
> being sent on by an SGP
> (not by an SG).
[TOLGA] IMO, should be sent by SG. In fact for the well designed SG, where
there is internal routing between SGPs(when a message can´t be delivered by
a SGP because there is no ACTIVE ASP, it might be checked whether there is
another SGP, which can deliver the message), this won´t cause a problem but
because this is not mandatory still a clarification might be usefull.
>
> If the ASPs deliver SCON to a "combined" view of the
> AS, then when SGP1
> sends SCON to both ASP1 and ASP2 per the procedure,
> MTP-STATUS will appear
> twice at the AS.  For ANSI (with level indicated)
> this might not be a problem,
> but for ITU-T it is: the number of times within an
> interval that MTP-STATUS
> indicating congestion is delivered to an MTP-User
> such as ISUP affects the
> congestion algorithm.  The ASPs cannot correlate the
> SSNM, because it cannot
> due to diagram and the current procedure.
[TOLGA] For that specific case, I wouldn´t expect a big problem considering
that T29 has a range of 300-600 ms (but yes, still not nice).(BTW what
about this, SGP1 sends DUNA, after some time SGP2 sends DAVA for the same
PC. DAVA might arrive before DUNA to the ASP1)
In general I don´t know whether it is a good idea to base M3UA procedures
on the assumption that there will be a distributed entity for an AS over
multiple ASPs, because this distribution(or the lack of it) is a decision
on the upper layer. But this combined view will be most probably the case.

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



From mailnull@www1.ietf.org  Tue Jan 14 05:30: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 FAA20583
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 05:30:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0EAiT018228
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 05:44:29 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EAhhJ18199;
	Tue, 14 Jan 2003 05:43:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EAgNJ18116
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 05:42:23 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20553
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 05:27:47 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:KnTaxP1VR+zOPrGYnqpCqEi3YuV6kLE2@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0EAV6D01353;
	Tue, 14 Jan 2003 03:31:06 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0EAV5O23235;
	Tue, 14 Jan 2003 03:31:05 -0700
Date: Tue, 14 Jan 2003 03:31:05 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        sigtran@ietf.org
Subject: Re: [Sigtran] m3ua- IG
Message-ID: <20030114033105.A23008@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	"Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030113152510.A330@openss7.org> <Pine.SOL.4.10.10301140048100.26959-100000@sun3271.ssd.usa.alcatel.com> <20030114004917.B18871@openss7.org> <3E23D299.D2ED57A1@axes-mach01.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: <3E23D299.D2ED57A1@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Tue, Jan 14, 2003 at 02:34:25PM +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>

ksrinivas,

ksrinivas wrote:                                                                 (Tue, 14 Jan 2003 14:34:25)
> 
>    Brian,
> 
>        Does  the OPC list in the REG Req indicates to the SGP that the AS
>    can  send  or  receive  traffic  from  these point codes (of OPC list)
>    only?.
> 
>    If  true  then,  Does the OPC list skipped in the REG Req indicates to
>    the SGP that the AS can send or receive traffic from any point code?.
> 
>    --Srini

Yes and yes: that's my understanding.

--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  Tue Jan 14 05:33: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 FAA20630
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 05:33:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0EAlGE18352
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 05:47:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EAl4J18340;
	Tue, 14 Jan 2003 05:47:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EAkPJ18317
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 05:46:25 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20618
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 05:31:49 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:qLoTQe0clqVgyRurMAULqaKzigaqL3S/@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0EAZ8D01404;
	Tue, 14 Jan 2003 03:35:08 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0EAZ8j23276;
	Tue, 14 Jan 2003 03:35:08 -0700
Date: Tue, 14 Jan 2003 03:35:07 -0700
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] m3ua- IG
Message-ID: <20030114033507.B23008@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030114004917.B18871@openss7.org> <Pine.SOL.4.10.10301140249230.26959-100000@sun3271.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.10301140249230.26959-100000@sun3271.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Tue, Jan 14, 2003 at 03:06:04AM -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,

Samuel Dur D. Jeyaseelan wrote:                                                     (Tue, 14 Jan 2003 03:06:04)
> 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, 14 Jan 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > The Routing Context identifies a traffic flow (in both directions).  In
> > general an ASP should not send traffic for a Routing Context to point codes
> > from which it cannot receive traffic for the same Routing Context.
> > 
>                                 (PC 333)
>                                 STP/SG-------------------AS
>                                |  
>                                |  
>     NODE-A(PC 111)-------------+
>     |
>     |  
>     +------NODE-B(PC 222)
> 
> AS registers PC 111 with SG.
> 
> Say NODE-A sends query to PC 333( performs GTT and reaches AS) AS returns
> a LRN number to NODE-A.
> 
> NODE-A finds that LRN is actually a subcriber of NODE-B
> But at NODE-B MTP-restart procedure is going on.
> 
> So NODE-A sends TFP(PC 222) to STP.
> In this scenario Will SG send DUNA(affected PC 222) to AS?
> (note AS is unware of PC 222)

If the AS is unaware of PC 222, it doesn't matter whether the SG
sends it DUNA(222) or 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 mailnull@www1.ietf.org  Tue Jan 14 05:58: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 FAA20996
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 05:58:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0EBCaE20012
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 06:12:36 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EBCCJ19970;
	Tue, 14 Jan 2003 06:12:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EBBYJ19884
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 06:11:34 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20942
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 05:56:57 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Qmf63AZFayV3CpV5jhXy5fO1k/4DOi1H@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0EB0HD01775;
	Tue, 14 Jan 2003 04:00:17 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0EB0Ht23669;
	Tue, 14 Jan 2003 04:00:17 -0700
Date: Tue, 14 Jan 2003 04:00:16 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA default AS
Message-ID: <20030114040016.C23008@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF29F5AD75.1D17007B-ONC2256CAE.003234C9@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF29F5AD75.1D17007B-ONC2256CAE.003234C9@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Tue, Jan 14, 2003 at 11:36:48AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Tue, 14 Jan 2003 11:36:48)
> 
> Brian,
> > TOLGA,
> >
> > TOLGA ASVEREN wrote:
> > (Tue, 14 Jan 2003 08:29:19)
> > >
> >
> > >      SG
> > > +-----------+                +-----------+
> > > |           |    Assoc 1     |           |
> > > |   SGP1    |----------------|   ASP1    |
> > > |           |\   Assoc 2     |           |
> > > +-----------+ \___________   +-----------+
> > >       |                   \ 
> > > +-----------+              \ +-----------+
> > > |           |    Assoc 3    \|           |
> > > |   SGP2    |----------------|   ASP2    |
> > > |           |                |           |
> > > +-----------+                +-----------+
> > >
> >
> > >    [TOLGA]If ASP1 is INACTIVE, why is it used to send
> > >    DATA? If both ASPs are serving the same AS, shouldn´t
> > >    the user part running on top of them work as a single
> > >    entity? In such a case, why is SCON arriving via ASP2
> > >    not enough to execute necessary procedures on user part
> > >    level? I would think it is the user part not the M3UA
> > >    at ASP, which throttles traffic when necessary.
> >
> > No, both ASP1 and ASP2 are ASP-ACTIVE for the AS.  Its just
> > that SGP2 has not association with ASP1 and SSNM is stated
> > as being sent on by an SGP (not by an SG).
>
> [TOLGA] IMO, should be sent by SG. In fact for the well
> designed SG, where there is internal routing between SGPs
> (when a message can´t be delivered by a SGP because there is
> no ACTIVE ASP, it might be checked whether there is another
> SGP, which can deliver the message), this won´t cause a
> problem but because this is not mandatory still a
> clarification might be usefull.

Some well designed SGs would not send messages to an SGP which
was isolated from all ASPs in an AS.  There is no requirement in
M3UA for SGP to route messages between them.

Although sending SSNM on an SG-wide basis seems to solve the
ASPs problem, it causes significant problems for the SG.
Because, for an SGP to determine which ASPs to send a SNMM
message to, it must know the state of all of the ASPs to all of
the other SGPs.  If there are 16 of your low-end SGPs and 16 of
your low-end ASPs, each SGP must keep track of 256 ASP states
for each AS!  There will also be 256 race conditions per AS
when ASPs activate, deactivate or fail.

This is far more complicated that the thought of routing DATA
messages between SGP.

Sending SSNM on an SG-wide basis is a good idea, however, the
specification should not presume how that is accomplished at
the SG.

> >
> > If the ASPs deliver SCON to a "combined" view of the AS,
> > then when SGP1 sends SCON to both ASP1 and ASP2 per the
> > procedure, MTP-STATUS will appear twice at the AS.  For ANSI
> > (with level indicated) this might not be a problem, but for
> > ITU-T it is: the number of times within an interval that
> > MTP-STATUS indicating congestion is delivered to an MTP-User
> > such as ISUP affects the congestion algorithm.  The ASPs
> > cannot correlate the SSNM, because it cannot due to diagram
> > and the current procedure.
>
> [TOLGA] For that specific case, I wouldn´t expect a big
> problem considering that T29 has a range of 300-600 ms (but
> yes, still not nice).(BTW what about this, SGP1 sends DUNA,
> after some time SGP2 sends DAVA for the same PC. DAVA might
> arrive before DUNA to the ASP1) In general I don´t know
> whether it is a good idea to base M3UA procedures on the
> assumption that there will be a distributed entity for an AS
> over multiple ASPs, because this distribution(or the lack of
> it) is a decision on the upper layer. But this combined view
> will be most probably the case.

Reversals of DUNA and DAVA are almost impossible.  The reason is
that it takes a long time in the SS7 network for a signalling
point to restart (even if the inaccessibility was only due to a
link failure).  Also, DUNA and DAVA only apply to the ASP/SG
case. DUNA and DAVA are never used for point-to-point IPSP.

--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  Tue Jan 14 07:55:25 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 HAA22927
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 07:55:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ED9XY26814
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 08:09:33 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ED8qJ26768;
	Tue, 14 Jan 2003 08:08:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ED7JJ26571
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 08:07:19 -0500
Received: from domino2.nc.tekelec.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22848
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 07:52:39 -0500 (EST)
From: jeffrey.craig@tekelec.com
Received: from domino4.nc.tekelec.com ([198.89.40.9])
          by domino2.nc.tekelec.com (Lotus Domino Release 5.0.7)
          with ESMTP id 2003011407500491:14563 ;
          Tue, 14 Jan 2003 07:50:04 -0500 
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.7  March 21, 2001
Message-ID: <OFB3D3BFBA.7686DEF1-ON85256CAE.004633C7@nc.tekelec.com>
Date: Tue, 14 Jan 2003 07:51:54 -0500
MIME-Version: 1.0
X-MIMETrack: Serialize by Router on Domino4/Raleigh/TEKELEC(Release 5.0.10 |March 22, 2002) at
 01/14/2003 07:51:55 AM,
	Itemize by SMTP Server on Domino2/Raleigh/TEKELEC(Release 5.0.7 |March 21, 2001) at
 01/14/2003 07:50:05 AM,
	Serialize by Router on Domino2/Raleigh/TEKELEC(Release 5.0.7 |March 21, 2001) at
 01/14/2003 07:50:07 AM,
	Serialize complete at 01/14/2003 07:50:07 AM
Content-type: text/plain; charset=us-ascii
Subject: [Sigtran] (M2PA) Any word on when we can expect a M2PA v7?
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 All,

Given the lack of M2PA activity on the list, I am curious:
Is there any word on when we can expect the next draft, M2PA v7?

Are there any unresolved M2PA issues?
If memory serves, the issues had mainly involved making M2PA better match
Q.703
in terms of states, procedures, and timers.

Regards,

Jeff


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



From mailnull@www1.ietf.org  Tue Jan 14 08:50: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 IAA24087
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 08:50:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0EE4Vc30256
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 09:04:31 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EE47J30239;
	Tue, 14 Jan 2003 09:04:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EE33J30175
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 09:03:03 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24072
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 08:48:22 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:3RIQBz6vc+rz+32RScGChJFoAJL0h1RL@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0EDphD04382;
	Tue, 14 Jan 2003 06:51:43 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0EDphQ28498;
	Tue, 14 Jan 2003 06:51:43 -0700
Date: Tue, 14 Jan 2003 06:51:43 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: jeffrey.craig@tekelec.com
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Any word on when we can expect a M2PA v7?
Message-ID: <20030114065143.A26540@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: jeffrey.craig@tekelec.com, sigtran@ietf.org
References: <OFB3D3BFBA.7686DEF1-ON85256CAE.004633C7@nc.tekelec.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: <OFB3D3BFBA.7686DEF1-ON85256CAE.004633C7@nc.tekelec.com>; from jeffrey.craig@tekelec.com on Tue, Jan 14, 2003 at 07:51:54AM -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>

Jeffrey,

You can take a look at:

	http://www.openss7.org/docs/draft-ietf-sigtran-m2pa-07.txt
	http://www.openss7.org/docs/draft-ietf-sigtran-m2pa-07.ps
	http://www.openss7.org/docs/draft-ietf-sigtran-m2pa-07.pdf

for my take on the next version.  I sent these to Tom George
over a week ago and he said he would have a draft out "next
week".  I offerred to edit the dcoument if he didn't have time,
but he declined.  If it pleases the WG, we can make the above
the "official" draft 7 until Tom has time to issue a draft 8.

The changes made from draft 6 to these documents is described in
section 1.2.1 of the draft:

    1.2.1.  Changes from Version 0.6 to Version 0.7

       - added this section
       - reformatted document
       - updated references and version number
       - updated state transition diagrams
       - changed timer names to align with Q.703 [Q.703]
       - added proving state and procedure for timer T3
       - fixed nits from the mailing list
       - adjusted recommended timer values for alignment with Q.703 [Q.703]
       - adjusted language on T7 timer to match WG comments
       - created postscript diagrams
       - spelling corrections


--brian

jeffrey.craig@tekelec.com wrote:                                             (Tue, 14 Jan 2003 07:51:54)
> Hello All,
> 
> Given the lack of M2PA activity on the list, I am curious:
> Is there any word on when we can expect the next draft, M2PA v7?
> 
> Are there any unresolved M2PA issues?
> If memory serves, the issues had mainly involved making M2PA better match
> Q.703
> in terms of states, procedures, and timers.
> 
> Regards,
> 
> Jeff
> 
> 
> _______________________________________________
> 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 Jan 14 09:23: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 JAA24861
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 09:23:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0EEbJf32584
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 09:37:19 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EEamJ32040;
	Tue, 14 Jan 2003 09:36:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EEZKJ31984
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 09:35:20 -0500
Received: from mail-gw.radisys.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24787
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 09:20:38 -0500 (EST)
From: Barry.Nagelberg@radisys.com
Received: by mail-gw.radisys.com (Postfix, from userid 5)
	id B36934E927; Tue, 14 Jan 2003 06:19:55 -0800 (PST)
Received: from notes.radisys.com(206.103.52.220)
 via SMTP by mail-gw.radisys.com, id smtpdAAAhsa4nP; Tue Jan 14 06:19:40 2003
To: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Any word on when we can expect a M2PA v7?
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF8522E459.E1BFE35E-ON05256CAE.004C77AA@radisys.com>
Date: Tue, 14 Jan 2003 08:59:27 -0500
X-MIMETrack: Serialize by Router on HQ_ACS_1/Radisys_Corporation/US(Release 5.0.9a |January
 7, 2002) at 01/14/2003 06:16:08 AM,
	Serialize complete at 01/14/2003 06:16:08 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>

Brian,

I'm sure that everyone welcomes your M2PA suggestions, but I don't think 
that it is appropriate for you to offer your draft as the "official" 
draft. The latest word from Lyndon is that Tom George is still the editor. 
Please offer your suggestions to the editor.

Barry Nagelberg





"Brian F. G. Bidulock" <bidulock@openss7.org>
Sent by: sigtran-admin@ietf.org
 01/14/2003 08:51 AM
 Please respond to bidulock

 
        To:     jeffrey.craig@tekelec.com
        cc:     sigtran@ietf.org
        Subject:        Re: [Sigtran] (M2PA) Any word on when we can expect a M2PA v7?


Jeffrey,

You can take a look at:

                 http://www.openss7.org/docs/draft-ietf-sigtran-m2pa-07.txt
                 http://www.openss7.org/docs/draft-ietf-sigtran-m2pa-07.ps
                 http://www.openss7.org/docs/draft-ietf-sigtran-m2pa-07.pdf

for my take on the next version.  I sent these to Tom George
over a week ago and he said he would have a draft out "next
week".  I offerred to edit the dcoument if he didn't have time,
but he declined.  If it pleases the WG, we can make the above
the "official" draft 7 until Tom has time to issue a draft 8.

The changes made from draft 6 to these documents is described in
section 1.2.1 of the draft:

    1.2.1.  Changes from Version 0.6 to Version 0.7

       - added this section
       - reformatted document
       - updated references and version number
       - updated state transition diagrams
       - changed timer names to align with Q.703 [Q.703]
       - added proving state and procedure for timer T3
       - fixed nits from the mailing list
       - adjusted recommended timer values for alignment with Q.703 
[Q.703]
       - adjusted language on T7 timer to match WG comments
       - created postscript diagrams
       - spelling corrections


--brian

jeffrey.craig@tekelec.com wrote:   (Tue, 14 Jan 2003 07:51:54)
> Hello All,
> 
> Given the lack of M2PA activity on the list, I am curious:
> Is there any word on when we can expect the next draft, M2PA v7?
> 
> Are there any unresolved M2PA issues?
> If memory serves, the issues had mainly involved making M2PA better 
match
> Q.703
> in terms of states, procedures, and timers.
> 
> Regards,
> 
> Jeff
> 
> 
> _______________________________________________
> 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 mailnull@www1.ietf.org  Tue Jan 14 09:58: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 JAA25916
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 09:58:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0EFD8102912
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 10:13:08 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EFCSJ02885;
	Tue, 14 Jan 2003 10:12:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EFBjJ02839
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 10:11:45 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25882
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 09:57:04 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:YQDpSIjanuvs2FQhhzvOJniYqXWxSdKF@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0EF0MD05364;
	Tue, 14 Jan 2003 08:00:22 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0EF0Mo29794;
	Tue, 14 Jan 2003 08:00:22 -0700
Date: Tue, 14 Jan 2003 08:00:22 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry.Nagelberg@radisys.com
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Any word on when we can expect a M2PA v7?
Message-ID: <20030114080022.A29592@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry.Nagelberg@radisys.com, sigtran@ietf.org
References: <OF8522E459.E1BFE35E-ON05256CAE.004C77AA@radisys.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: <OF8522E459.E1BFE35E-ON05256CAE.004C77AA@radisys.com>; from Barry.Nagelberg@radisys.com on Tue, Jan 14, 2003 at 08:59:27AM -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>

Barry,

Barry.Nagelberg@radisys.com wrote:                                         (Tue, 14 Jan 2003 08:59:27)
> Brian,
> 
> I'm sure that everyone welcomes your M2PA suggestions, but I don't think 
> that it is appropriate for you to offer your draft as the "official" 
> draft. The latest word from Lyndon is that Tom George is still the editor. 
> Please offer your suggestions to the editor.
> 
> Barry Nagelberg

Already offered, Jan 7th.

--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  Tue Jan 14 11:09: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 LAA00115
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 11:09:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0EGNqT08740
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 11:23:52 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EGNSJ08713;
	Tue, 14 Jan 2003 11:23:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EGMaJ08624
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 11:22:36 -0500
Received: from mink.ecitele.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00021
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 11:07:52 -0500 (EST)
From: Lev.Finkel@ecitele.com
Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125])
	by mink.ecitele.com (8.9.1a/8.9.1) with ESMTP id SAA02067;
	Tue, 14 Jan 2003 18:05:39 +0200 (IST)
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
To: bidulock@openss7.org
Cc: chak@axes-mach01.usa.alcatel.com, ksrini@axes-mach01.usa.alcatel.com,
        latha@indts.com, sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OF244D77CB.0D63ABD8-ONC2256CAE.0025116C@ecitele.com>
Date: Tue, 14 Jan 2003 18:10:48 +0200
X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at
 01/14/2003 06:10:50 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>


Brian,

>


                                                                                                           
                      "Brian F. G.                                                                         
                      Bidulock"                To:      Lev.Finkel@ecitele.com                             
                      <bidulock@openss         cc:      chak@axes-mach01.usa.alcatel.com,                  
                      7.org>                   ksrini@axes-mach01.usa.alcatel.com, latha@indts.com,        
                      Sent by:                 sigtran@ietf.org, sigtran-admin@ietf.org                    
                      sigtran-admin@ie         Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK     
                      tf.org                                                                               
                                                                                                           
                                                                                                           
                      14/01/03 00:31                                                                       
                      Please respond                                                                       
                      to bidulock                                                                          
                                                                                                           
                                                                                                           



> Lev.Finkel,
>
> Lev.Finkel@ecitele.com wrote:
(Mon, > 13 Jan 2003 18:17:47)
> >
> > Brian,
> >
> > I mean NOTIFY message exists and must be sent when the AS status is
> > changed.
> > I agree that ACTIVE ACK is to be send on response on ACTIVE. If for
> > internal SG reason the AS is down for certain IID, the SG must send
NOTIFY
> > to the ASPs.
>
> The procedure for doing this that was imported into M2UA from the
> vother UAs by the IG is to send ASPIA Ack.
Where is it defined?
What I see in RFC3331 section 4.3.4.3 is "The SGP MUST send an Error
message ("Invalid Interface Identifier") for each Interface Identifier
value that cannot be successfully activated".
This statement is like section 3.20 of IUA IG.

> Notify is only advisory
> and will not illicit the correct response in the ASP.  In response
> to ASPIA Ack, the ASP must put itself in the ASP-INACTIVE state for
> the AS, and then issue ASPAC. Then the SG can return ERR("Invalid
> IID") to the ASPAC if, indeed, the AS has been "unconfigured".  If
> the AS has not been "unconfigured" in the first place, the SG should
> not be deactivating the AS at all. It should be clearing the
> signalling connection with a Release Indication.\

I agree with sending of ASP Active Ack and "activating" of all configured
interfaces. The real problematical case is at the moment when ASP does not
activate-deactivate. This case is following: Interface/D-channel removed
from SG configuration and again introduced without reconfiguring of ASP. SG
sends Release Indication upon management removal action. ASP periodically
sends Establish Request. When Interface again configured the SG can not
define ASP active for it, even if ASP is configured. SG expects ASP Active
for this interface. It must inform ASP. We use Notify to force ASP sending
ASP Active.
Do you know any other procedure defined in any UA?

Regards,
Lev

>
> --brian
>
> > This just to confirm your statement, that inability to answer OK is
just
> > the same as a failure at any moment later.
> >
> > Thanks,
> > Lev
> >
> >
> >
> >

> >                       "Brian F. G.

> >                       Bidulock"                To:
Lev.Finkel@ecitele.com
> >                       <bidulock@openss         cc:
chak@axes-mach01.usa.alcatel.com,
> >                       7.org>
ksrini@axes-mach01.usa.alcatel.com, latha@indts.com,
> >                                                sigtran@ietf.org,
sigtran-admin@ietf.org
> >                       13/01/03 13:53           Subject: Re: [Sigtran]
IUA -  ASP Active and ACTIVE ACK
> >                       Please respond

> >                       to bidulock

> >

> >

> >
> >
> >
> > Lev.Finkel,
> >
> > Notify(AS_inactive) is never sent after sending ASPAC Ack because the
> > AS is active.  Where in the RFC did you think this was stated?
> >
> > --brian
> >
> > Lev.Finkel@ecitele.com wrote:
> > (Mon, 13 Jan 2003 13:33:23)
> > >
> > > Notify(AS_inactive) or another corresponding notify is the way
provided in
> > > RFC.
> > >
> > > Regards, Lev
> > >
> > >
> >
> > --
> > 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




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



From mailnull@www1.ietf.org  Tue Jan 14 12:12: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 MAA03628
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 12:12:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0EHQmR14600
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 12:26:48 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EHQ1J14532;
	Tue, 14 Jan 2003 12:26:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EHOsJ14437
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 12:24:54 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03548
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 12:10:10 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:8Ey3FEwKCSYudCDYmtiltomAPYRKlFpN@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0EHDUD07663;
	Tue, 14 Jan 2003 10:13:30 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0EHDUd02635;
	Tue, 14 Jan 2003 10:13:30 -0700
Date: Tue, 14 Jan 2003 10:13:30 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Lev.Finkel@ecitele.com
Cc: chak@axes-mach01.usa.alcatel.com, ksrini@axes-mach01.usa.alcatel.com,
        latha@indts.com, sigtran@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030114101330.B31701@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Lev.Finkel@ecitele.com, chak@axes-mach01.usa.alcatel.com,
	ksrini@axes-mach01.usa.alcatel.com, latha@indts.com,
	sigtran@ietf.org
References: <OF244D77CB.0D63ABD8-ONC2256CAE.0025116C@ecitele.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: <OF244D77CB.0D63ABD8-ONC2256CAE.0025116C@ecitele.com>; from Lev.Finkel@ecitele.com on Tue, Jan 14, 2003 at 06:10:48PM +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>

Lev,

Lev.Finkel@ecitele.com wrote:                                                   (Tue, 14 Jan 2003 18:10:48)
> 
> > vother UAs by the IG is to send ASPIA Ack.
> Where is it defined?
> What I see in RFC3331 section 4.3.4.3 is "The SGP MUST send an Error
> message ("Invalid Interface Identifier") for each Interface Identifier
> value that cannot be successfully activated".
> This statement is like section 3.20 of IUA IG.

And why cannot an IID be activated?

> 
> > Notify is only advisory
> > and will not illicit the correct response in the ASP.  In response
> > to ASPIA Ack, the ASP must put itself in the ASP-INACTIVE state for
> > the AS, and then issue ASPAC. Then the SG can return ERR("Invalid
> > IID") to the ASPAC if, indeed, the AS has been "unconfigured".  If
> > the AS has not been "unconfigured" in the first place, the SG should
> > not be deactivating the AS at all. It should be clearing the
> > signalling connection with a Release Indication.\
> 
> I agree with sending of ASP Active Ack and "activating" of all configured
> interfaces. The real problematical case is at the moment when ASP does not
> activate-deactivate. This case is following: Interface/D-channel removed
> from SG configuration and again introduced without reconfiguring of ASP. SG
> sends Release Indication upon management removal action. ASP periodically
> sends Establish Request. When Interface again configured the SG can not
> define ASP active for it, even if ASP is configured. SG expects ASP Active
> for this interface. It must inform ASP. We use Notify to force ASP sending
> ASP Active.
> Do you know any other procedure defined in any UA?

None of the UAs handle misconfiguration well.  Nevertheless, it appears
that Q.921 DL-ESTABLISH procedures would apply.  Sending a Notify can never
"force" an ASP to do anything.  Notifications are advisory only.
Nevertheless, sending NTFY("AS_Inactive") when an AS is first configured
at an SG makes some sense.

--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  Tue Jan 14 12:47: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 MAA04588
	for <sigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 12:47:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0EI1nD16864
	for sigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 13:01:49 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EI1CJ16834;
	Tue, 14 Jan 2003 13:01:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EI0tJ16792
	for <sigtran@optimus.ietf.org>; Tue, 14 Jan 2003 13:00:55 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04560
	for <sigtran@ietf.org>; Tue, 14 Jan 2003 12:46:11 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0EHnUBE007719;
	Tue, 14 Jan 2003 11:49:30 -0600 (CST)
Message-ID: <3E244DAA.10C4A6BA@alcatel.com>
Date: Tue, 14 Jan 2003 11:49:30 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Any word on when we can expect a M2PA v7?
References: <OF8522E459.E1BFE35E-ON05256CAE.004C77AA@radisys.com> <20030114080022.A29592@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

I will indeed have version 7 out this week. It will be very similar to
Brian's version, though I do not promise it will be identical.

tomG.

"Brian F. G. Bidulock" wrote:
> 
> Barry,
> 
> Barry.Nagelberg@radisys.com wrote:                                         (Tue, 14 Jan 2003 08:59:27)
> > Brian,
> >
> > I'm sure that everyone welcomes your M2PA suggestions, but I don't think
> > that it is appropriate for you to offer your draft as the "official"
> > draft. The latest word from Lyndon is that Tom George is still the editor.
> > Please offer your suggestions to the editor.
> >
> > Barry Nagelberg
> 
> Already offered, Jan 7th.
> 
> --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

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 15 03:02: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 DAA19238
	for <sigtran-archive@odin.ietf.org>; Wed, 15 Jan 2003 03:02:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0F8Gxu20800
	for sigtran-archive@odin.ietf.org; Wed, 15 Jan 2003 03:16:59 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0F8GQJ20762;
	Wed, 15 Jan 2003 03:16:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0F8D3J20646
	for <sigtran@optimus.ietf.org>; Wed, 15 Jan 2003 03:13:03 -0500
Received: from mink.ecitele.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19137;
	Wed, 15 Jan 2003 02:57:57 -0500 (EST)
From: Lev.Finkel@ecitele.com
Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125])
	by mink.ecitele.com (8.9.1a/8.9.1) with ESMTP id JAA22356;
	Wed, 15 Jan 2003 09:55:33 +0200 (IST)
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
To: bidulock@openss7.org
Cc: chak@axes-mach01.usa.alcatel.com, ksrini@axes-mach01.usa.alcatel.com,
        latha@indts.com, sigtran@ietf.org, sigtran-admin@ietf.org
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OF0672E04B.FD0A9435-ONC2256CAF.002B22F8@ecitele.com>
Date: Wed, 15 Jan 2003 10:00:04 +0200
X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at
 01/15/2003 10:00:48 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>


Brian,




> >
> > > vother UAs by the IG is to send ASPIA Ack.
> > Where is it defined?
Can you answer the above question?

> > What I see in RFC3331 section 4.3.4.3 is "The SGP MUST send an Error
> > message ("Invalid Interface Identifier") for each Interface Identifier
> > value that cannot be successfully activated".
> > This statement is like section 3.20 of IUA IG.
>
> And why cannot an IID be activated?
>
The answer on this rhetorical question is "misconfiguration". I do not
expect other reasons except SW bug which is never for the protocol
treatment.

Regards,
Lev




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



From mailnull@www1.ietf.org  Wed Jan 15 03:50: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 DAA20273
	for <sigtran-archive@odin.ietf.org>; Wed, 15 Jan 2003 03:50:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0F94sA23921
	for sigtran-archive@odin.ietf.org; Wed, 15 Jan 2003 04:04:54 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0F94BJ23888;
	Wed, 15 Jan 2003 04:04:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0F93KJ23859
	for <sigtran@optimus.ietf.org>; Wed, 15 Jan 2003 04:03:20 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20261;
	Wed, 15 Jan 2003 03:48:14 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:OLg0XkfRVJWdSkyGEoEfYdVegJdmhgxL@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0F8paD21334;
	Wed, 15 Jan 2003 01:51:36 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0F8pas24650;
	Wed, 15 Jan 2003 01:51:36 -0700
Date: Wed, 15 Jan 2003 01:51:36 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Lev.Finkel@ecitele.com
Cc: chak@axes-mach01.usa.alcatel.com, ksrini@axes-mach01.usa.alcatel.com,
        latha@indts.com, sigtran@ietf.org, sigtran-admin@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030115015136.B24185@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Lev.Finkel@ecitele.com, chak@axes-mach01.usa.alcatel.com,
	ksrini@axes-mach01.usa.alcatel.com, latha@indts.com,
	sigtran@ietf.org, sigtran-admin@ietf.org
References: <OF0672E04B.FD0A9435-ONC2256CAF.002B22F8@ecitele.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: <OF0672E04B.FD0A9435-ONC2256CAF.002B22F8@ecitele.com>; from Lev.Finkel@ecitele.com on Wed, Jan 15, 2003 at 10:00:04AM +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>

Lev.Finkel,

Lev.Finkel@ecitele.com wrote:                                                   (Wed, 15 Jan 2003 10:00:04)
> 
> Brian,
> 
> > >
> > > > vother UAs by the IG is to send ASPIA Ack.
> > > Where is it defined?
> Can you answer the above question?

IUA IG Verion 2 Section 3.16.2 new text for Section 4.3.3.5, third paragraph.

Wouldn't it be a good idea to start drafting an RFC3057bis.

> 
> > > What I see in RFC3331 section 4.3.4.3 is "The SGP MUST send an Error
> > > message ("Invalid Interface Identifier") for each Interface Identifier
> > > value that cannot be successfully activated".
> > > This statement is like section 3.20 of IUA IG.
> >
> > And why cannot an IID be activated?
> >
> The answer on this rhetorical question is "misconfiguration". I do not
> expect other reasons except SW bug which is never for the protocol
> treatment.

That is the answer for IUA, however, you have referenced RFC3331 section
4.3.4.3 which is M2UA.

Section 3.3.3.1 of RFC3057 says:

  The "Invalid Interface Identifier" error would be sent by an SG if an
  ASP sends a messages with an invalid (unconfigured) Interface
  Identifier value.

And is again repeated in secion 3.19.2 of the IUA IG Version 2.

Which is quite clear.

Strangely, RFC3331 says in section 3.3.1:

   The "Invalid Interface Identifier" error would be sent by a SGP if an
   ASP sends a message (i.e. an ASP Active message) with an invalid (not
   configured) Interface Identifier value.  One of the optional
   Interface Identifier parameters (Integer-based, text-based or integer
   range) MUST be used with this error code to identify the invalid
   Interface Identifier(s) received.

Which again says "not configured."

Now, although RFC3331 (M2UA) says:

                                          ...  The SGP MUST send an
   Error message ("Invalid Interface Identifier") for each Interface
   Identifier value that cannot be successfully activated.

This text is not in RFC3057 or the IUA-IG and cannot be considered applicable
to IUA.

For M2UA, failure to activate might not only be caused by misconfiguration.
(e.g. failure of switching elements at the SG for automatic allocation of
signalling terminals or signalling data links or both, no reminaing signalling
terminals, etc...).

--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  Wed Jan 15 05:04:56 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 FAA21525
	for <sigtran-archive@odin.ietf.org>; Wed, 15 Jan 2003 05:04:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FAJTJ29285
	for sigtran-archive@odin.ietf.org; Wed, 15 Jan 2003 05:19:29 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FAIbJ29253;
	Wed, 15 Jan 2003 05:18:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FAHXJ29201
	for <sigtran@optimus.ietf.org>; Wed, 15 Jan 2003 05:17:33 -0500
Received: from mink.ecitele.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21466;
	Wed, 15 Jan 2003 05:02:28 -0500 (EST)
From: Lev.Finkel@ecitele.com
Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125])
	by mink.ecitele.com (8.9.1a/8.9.1) with ESMTP id MAA09900;
	Wed, 15 Jan 2003 12:00:14 +0200 (IST)
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
To: bidulock@openss7.org
Cc: chak@axes-mach01.usa.alcatel.com, ksrini@axes-mach01.usa.alcatel.com,
        latha@indts.com, sigtran@ietf.org, sigtran-admin@ietf.org
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OF045DBD96.A1F61F5C-ONC2256CAF.003291AC@ecitele.com>
Date: Wed, 15 Jan 2003 12:04:23 +0200
X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at
 01/15/2003 12:05:26 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>

                                                                                                           
                      "Brian F. G.                                                                         
                      Bidulock"                To:      Lev.Finkel@ecitele.com                             
                      <bidulock@openss         cc:      chak@axes-mach01.usa.alcatel.com,                  
                      7.org>                   ksrini@axes-mach01.usa.alcatel.com, latha@indts.com,        
                                               sigtran@ietf.org, sigtran-admin@ietf.org                    
                      15/01/03 10:51           Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK     
                      Please respond                                                                       
                      to bidulock                                                                          
                                                                                                           
                                                                                                           








> IUA IG Verion 2 Section 3.16.2 new text for Section 4.3.3.5, third
paragraph.

I see. The paragraph describes only ASP behavior. To be consistent the SG
behavior must be respectively described and section 3.3.2.6 to be changed.
Now 3.3.2.6 says:
   The ASPAC Ack message is used to acknowledge an ASP-Active message
   received from a remote IUA peer.
Personally I do not like to define sending of ACK not triggered by any
request.

>
> Wouldn't it be a good idea to start drafting an RFC3057bis.

In light of interop problems we met till today with different respect to IG
document I'd welcome RFC3057bis.

> Strangely, RFC3331 says in section 3.3.1:
>
>    The "Invalid Interface Identifier" error would be sent by a SGP if an
>    ASP sends a message (i.e. an ASP Active message) with an invalid (not
>    configured) Interface Identifier value.  One of the optional
>    Interface Identifier parameters (Integer-based, text-based or integer
>    range) MUST be used with this error code to identify the invalid
>    Interface Identifier(s) received.
>
> Which again says "not configured."
>
> Now, although RFC3331 (M2UA) says:
>
>                                           ...  The SGP MUST send an
>    Error message ("Invalid Interface Identifier") for each Interface
>    Identifier value that cannot be successfully activated.
>
> This text is not in RFC3057 or the IUA-IG and cannot be considered
applicable
> to IUA.
> For M2UA, failure to activate might not only be caused by
misconfiguration.
> (e.g. failure of switching elements at the SG for automatic allocation of
> signalling terminals or signalling data links or both, no reminaing
signalling
> terminals, etc...).
>

Thanks for explanation. Not only Error code description in (3.3.1) but also
its "name" does not sound for me covering the cases you have described.

Regards,
Lev


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



From mailnull@www1.ietf.org  Wed Jan 15 05:23:23 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 FAA21792
	for <sigtran-archive@odin.ietf.org>; Wed, 15 Jan 2003 05:23:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FAbuj30590
	for sigtran-archive@odin.ietf.org; Wed, 15 Jan 2003 05:37:56 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FAbEJ30270;
	Wed, 15 Jan 2003 05:37:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FAaoJ29879
	for <sigtran@optimus.ietf.org>; Wed, 15 Jan 2003 05:36:50 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21771;
	Wed, 15 Jan 2003 05:21:45 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:pzvyQZqFAIfVTg28owcK43EAvZJtZ3yg@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0FAP5D22745;
	Wed, 15 Jan 2003 03:25:05 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0FAP4T26846;
	Wed, 15 Jan 2003 03:25:04 -0700
Date: Wed, 15 Jan 2003 03:25:03 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Lev.Finkel@ecitele.com
Cc: chak@axes-mach01.usa.alcatel.com, ksrini@axes-mach01.usa.alcatel.com,
        latha@indts.com, sigtran@ietf.org, sigtran-admin@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030115032503.B26480@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Lev.Finkel@ecitele.com, chak@axes-mach01.usa.alcatel.com,
	ksrini@axes-mach01.usa.alcatel.com, latha@indts.com,
	sigtran@ietf.org, sigtran-admin@ietf.org
References: <OF045DBD96.A1F61F5C-ONC2256CAF.003291AC@ecitele.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: <OF045DBD96.A1F61F5C-ONC2256CAF.003291AC@ecitele.com>; from Lev.Finkel@ecitele.com on Wed, Jan 15, 2003 at 12:04:23PM +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>

Lev.Finkel,

Lev.Finkel@ecitele.com wrote:                                                   (Wed, 15 Jan 2003 12:04:23)
>                                                                                                            
> > IUA IG Verion 2 Section 3.16.2 new text for Section 4.3.3.5, third
> paragraph.
> 
> I see. The paragraph describes only ASP behavior. To be consistent the SG
> behavior must be respectively described and section 3.3.2.6 to be changed.
> Now 3.3.2.6 says:
>    The ASPAC Ack message is used to acknowledge an ASP-Active message
>    received from a remote IUA peer.
> Personally I do not like to define sending of ACK not triggered by any
> request.

Sorry, but the unsolicited behavior is permitted by all the UAs.  Section
3.3.2.6 does not need to be changed: it doesn't say "is _only_ used".

> 
> >
> > Wouldn't it be a good idea to start drafting an RFC3057bis.
> 
> In light of interop problems we met till today with different respect to IG
> document I'd welcome RFC3057bis.

I really meant just because there are all these modifications strewn across
a number of documents and it is getting difficult to piece the bits together
to get a complete picture.  If we had a RFC3057bis draft, then at least we
could see the changes in one coherent document.

> 
> > Strangely, RFC3331 says in section 3.3.1:
> >
> >    The "Invalid Interface Identifier" error would be sent by a SGP if an
> >    ASP sends a message (i.e. an ASP Active message) with an invalid (not
> >    configured) Interface Identifier value.  One of the optional
> >    Interface Identifier parameters (Integer-based, text-based or integer
> >    range) MUST be used with this error code to identify the invalid
> >    Interface Identifier(s) received.
> >
> > Which again says "not configured."
> >
> > Now, although RFC3331 (M2UA) says:
> >
> >                                           ...  The SGP MUST send an
> >    Error message ("Invalid Interface Identifier") for each Interface
> >    Identifier value that cannot be successfully activated.
> >
> > This text is not in RFC3057 or the IUA-IG and cannot be considered applicable
> > to IUA.  For M2UA, failure to activate might not only be caused by misconfiguration.
> > (e.g. failure of switching elements at the SG for automatic allocation of
> > signalling terminals or signalling data links or both, no reminaing signalling
> > terminals, etc...).
> >
> 
> Thanks for explanation. Not only Error code description in (3.3.1) but also
> its "name" does not sound for me covering the cases you have described.

I agree, but RFC3331 does say "successfully activated" in section 4.whatever.
I would have no problems placing "(not configured)" in section 4.whatever of
RFC3331.  One of the M2UA-IG.

--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  Wed Jan 15 05:35: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 FAA21908
	for <sigtran-archive@odin.ietf.org>; Wed, 15 Jan 2003 05:35:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FAncC31097
	for sigtran-archive@odin.ietf.org; Wed, 15 Jan 2003 05:49:38 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FAnOJ31090;
	Wed, 15 Jan 2003 05:49:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FAmaJ31034
	for <sigtran@optimus.ietf.org>; Wed, 15 Jan 2003 05:48:36 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21891
	for <sigtran@ietf.org>; Wed, 15 Jan 2003 05:33:29 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:ClmX2bEs3mGzNvm6tZy/xaSVANO7ck3w@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0FAahD22909;
	Wed, 15 Jan 2003 03:36:43 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0FAahA27066;
	Wed, 15 Jan 2003 03:36:43 -0700
Date: Wed, 15 Jan 2003 03:36:43 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: sigtran@ietf.org
Cc: Ken Morneault <kmorneau@cisco.com>
Subject: Re: [Sigtran] I-D ACTION:draft-ietf-sigtran-m3ua-implementors-guide-02.txt
Message-ID: <20030115033643.B26872@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: sigtran@ietf.org, Ken Morneault <kmorneau@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
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>

Resend...

SIGTRAN,

Ken Morneault wrote:                                                                   (Fri, 20 Dec 2002 13:22:50)
> 
> 
> Brian,
> 
> Pls see my feedback below.   I removed the items that already
> had consensus or were minor edits.  For the rest, we need more
> feedback on the list before progressing.
> 
> Regards,
> 
> Ken
> 
> At 02:51 PM 12/19/2002 -0700, Brian F. G. Bidulock wrote:
> >Ken,
> >
> >Please see additional comments below...
> >
> >Ken Morneault wrote:                              (Thu, 19 Dec 2002 15:14:57)
> >> 
> >> 
> >> Brian,
> >> 
> >> Pls see comments below.
> >> 
> >> Ken / Javier
> >> 
> >> At 03:43 AM 12/18/2002 -0700, Brian F. G. Bidulock wrote:
> >> >Some comments on this version of the IG:
> >> >
> >> >Section 3.2
> >> >
> >> >  This section is unnecessary.  It was always intended that the M3UA entity
> >> >  sending the ERR message include the offending message in the Diagnostic.
> >> >  This appears in RFC 3332 section 3.8.1:
> >> >
> >> >   Diagnostic Information: variable length
> >> >
> >> >      When included, the optional Diagnostic information can be any
> >> >      information germane to the error condition, to assist in
> >> >      identification of the error condition. The Diagnostic information
> >> >      SHOULD contain the offending message.
> >> >
> >> >  I don't see any reason to say MUST for REG REQ.  The SHOULD is sufficient
> >> >  to cover all cases.  It was clear from discussions that if the Diagnostic
> >> >  information does not contain the offending message, that correlation of
> >> >  Error messages with the messages that cause them will be impossible in
> >> >  many circumstances.
> >> 
> >> 
> >> This ambiguity is exactly what folks wanted to avoid in the case of REG REQ.  Having
> >> "MUST instead of "SHOULD" does provide a benefit in this case.
> >
> >And what is that benefit?  A requirement to support a Error procedure at
> >the SG for an optional feature of the protocol?  I don't see a
> >interoperability need for an SG to support this procedure if the SG knows
> >that it will never connect to an ASP which dynamic registers.  Dynamic
> >registration is, after all, OPTIONAL.
> >
> >Change "MUST" to "SHOULD".
> 
> Although the feature is optional, the SG must return an error.  The
> change to the text just makes it mandatory for the ASP and SG
> to always include the Diagnostic information for Msg Class/Type
> errors so that the other side can correlate.  

So why should correlation be mandatory for this case and not all others?
There are many other cases where correlation causes problems.  I think it
is time to revisit the SHOULD or the MUST.  As I recall you were the one
advocating SHOULD in the first place for offending messages in Diagnostic
and those that reported correlation problems were asking for MUST.  Can
you continue to defend SHOULD for other cases?  If you are making a unilateral
decision to say MUST for the one error, also remove "germane" and change
"SHOULD" to "MUST" under "Diagnostic Information" above.

> 
> 
> 
> >> 
> >> 
> >> 
> >> 
> >> >Section 3.4
> >> >
> >> >  This section is against the concensus in the RFC.  The concensus was
> >> >  that if an SGP suffers a partial failure, it should send ASP Inactive
> >> >  Ack for the affected AS, and that if it should suffer a complete
> >> >  failure, it should send ASP Down Ack.
> >> 
> >> Most of this text came from some of your proposed text in a long thread 
> >> (titled "NIF not available") after the M3UA draft was frozen.  I think the only 
> >> conflict with your proposal is sending DUNA(s) in the case of the partial
> >> failure case.  
> >
> >It was discussed long before that.  That is why there is the wording
> >in the RFC concerning the response to ASP Down Ack and ASP Inactive Ack
> >in the case that no ASP Down or ASP Inactive has been sent: it is because
> >we discussed partial and complete failure in the WG perviously (at the
> >same time as we changed SNMM back from being per-SGP to being per-SG,
> >shortly after the s/SG/SGP/g fiassco) which was back at about Draft7 or 8.
> >
> >At that time we agreed that SSNM was per-SG (e.g. DRST cannot be used to
> >redirect traffic between SGP in the same SG) and that ASPSM/ASPTM was
> >per-SGP.  We also agreed at that time that DUNA was inappropriate in
> >response to SGP failures (because they are per-SG, and intended to
> >reflect SS7 network management and not ASP management) and the ASP
> >Inactive Ack and ASP Down Ack were the appropriate response to partial
> >and complete failures of the SGP (because they are per-SGP and intended
> >to reflect ASP management, not SS7 network management).
> >
> >I can dig up the threads if you'd like, but the matter was settled
> >a long time ago.  It just resurfaced after the draft was frozen.
> 
> I know it was discussed before that.  However, that thread was the final
> discussion and the one from which the test changes were pulled.  

Sending DUNA for partial failure does not appear in that discussion:
what that your own invention?  Strike it.  It was never discussed.

On the other hand, ASP Down Ack was discussed in that thread.

Also, DUNA(*) was mentioned as appropriate, but so was ASP Inactive Ack
and ASP Down Ack.  I don't know how you could possible state DUNA(*)
as a MUST when there are other options for the SG designer to respond
to what is clearly an event which is outside the scope of the document:
an event of the "implementation-depdendent NIF."

Strike the "MUSTs" and put "MAY," or "MAY, for example," because it is an
implemetation issue and not a protocol issue.  The results from sending
any of these messages is clearly stated in the protocol.  When to send
them is an implementation matter.

> 
> 
> >Now, the IG attempts to again use SSNM where ASPSM/ASPTM is proscribed.
> >
> >
> >> 
> >> >  DUNA(*) is completely incorrect, particularly because the ASP is
> >> >  permitted to interpret DUNA(*) from one SGP to mean DUNA(*) from
> >> >  all SGPs in an SG.  SNMM are not per-SGP messages and were kept
> >> >  as indicating routing at SG scope.  Section 3.4 is in conflict with
> >> >  this.
> >
> >I should have said DUNA not DUNA(*) above, but,
> >
> >> 
> >> DUNA(*) is only proposed in the case in which the SG (all SGPs) have
> >> lost contact with the NIF (or SS7 network).
> >
> >DUNA(*) is inappropriate because the SG has not lost accessibility to these
> >destinations.  When the NIF recovers. there is no procedure to inform
> >the AS that these destinations are indeed available.  ASP Down Ack is
> >appropriate because it informs all AS at all ASPs that they have lost
> >connectivity to the NIF from a given SGP.  When the NIF recovers and
> >the ASP performs its normal startup DAUD procedure (if required).
> >With DUNA(*) the ASP is given no indication when the NIF recovers and
> >does not know to perform DAUD.
> >
> >MTP/MTP-User interfaces use means other than MTP-PAUSE to indicate
> >whether the MTP-User is "connected" to MTP or not (bind, attach),
> >and when that connection fails (error return, exception).  MTP-PAUSE is
> >reserved for MTP to inform its user that a remote destination is
> >inaccessible to MTP, not when the local MTP is inaccessible to the
> >MTP-User.
> >
> >DUNA (without the *) is inappropriate for the reasons cited.  It falsely
> >indicates to the AS that the destination is inaccessible to the SG rather
> >than the fact that a single SGP is suffering a partial failure.  In the
> >world of MTP/MTP-User interfaces there is no "partial failure", it is
> >an all or nothing deal: either the MTP can provide service or it cannot.
> >When an SGP suffers a partial failure, it should send ASP Inactive Ack
> >so that the ASP knows to route traffic to alternate SGPs.
> >
> >So, again, please change DUNA(*) to ASP Down Ack and DUNA to ASP Inactive
> >Ack in this passage.  There should be no mention of SSNM being sent in
> >regard to SGP failures.
> 
> While I'm not necessarily opposed to making some mods to this text, I
> still think we need more feedback before we start making changes.

Here's feedback: its broken; fix it.

> 
> >> 
> >> >Section 3.9
> >> >
> >> >  SCON(0) was always intended to be optional.  Strike the requirement
> >> >  to send SCON(0) (i.e. strike Section 3.9).  Again this was discussed
> >> >  at length on the list we arrived again at SCON(0) being optional.
> >> >  Strike section 3.9.
> >> 
> >> I think you are referring to the thread "Another Congestion/SCON Question".
> >> This outcome of this thread has not been worked into the IG yet.
> >
> >You can work it into the IG by striking section 3.9.
> 
> I believe there is value in Section 3.9 as there had been comments about what
> the SG should send when audited.  Section 3.9 provides a clear description
> which was lacking in the RFC.

The description is not clear, because as it stands it is incorrect.

> 
> >> 
> >> >Section 3.10
> >> >
> >> >  This section is unnecesary.  The RFC clearly states in Section 4.3.4.4:
> >> >
> >> >    "The SGP MUST send an ASP Inactive Ack message in response to a
> >> >     received ASP Inactive message from the ASP and the ASP is already
> >> >     marked as ASP-INACTIVE at the SGP."
> >> >
> >> >  Deregistration does not change the state of the ASP in the AS.  In
> >> >  particular it does not move it to the ASP-DOWN state.  The only actions
> >> >  moving an ASP to the ASP-DOWN state are the successfuly completion of
> >> >  the ASP Down Procedure or the loss of the SCTP association.  Therefore,
> >> >  in the example, according to section 4.3.4.4 the SGP MUST send ASPIA Ack
> >> >  regardless of the fact that the ASP has deregistered for the routing key.
> >> >
> >> >  Then new text for Section 4.5.3 is in conflict with the MUST in
> >> >  section 4.3.4.4, becuase it requires an Error instead of an ASP Inactive
> >> >  Ack in the same situation (ASP in the ASP-INACTIVE state).
> >> >
> >> >  Strike section 3.10.
> >> 
> >> I don't see how it conflicts with Section 4.3.4.4.  In the case of a static
> >> Routing Key, a SG would not return ASP Inactive Ack if the Routing
> >> Context was invalid.  Instead, it would return an error.  The new text
> >> clarifies the same for the dynamically configured Routing Key.
> >
> >The Routing Context is valid in the example case that the solution
> >is claiming to address.
> >
> >Also, just because the RK is not registered does not mean that the
> >Routing Context is invalid.  The Routing Context being an index
> >into the routing table, means that it can be valid as long as there
> >is a Routing Key in the table.  It is at the SG's discretion upon the
> >last ASP deregistering for a key whether to leave it in the routing
> >table or to strike it.  Therefore, where the IG says:
> >
> >       -  If the RK is not registered, or the RC information is not valid,
> >          the peer must respond with an ERROR message with Error Code =
> >          "Invalid Routing Context".
> >
> >is incorect, because the RK being not registered does not necessarily
> >mean that the Routing Context is invalid.  
> 
> 
> While I agree that RK may exist in the database, the ASP has deregistered.
> Therefore, the RK would no longer be associated with that ASP (of course,
> it may be associated with other ASPs).


Are you saying that the ASP is moved to the ASP-DOWN state?  This is
incorrect (and the RFC does not agree with you).  ASP Down is required to move
the ASP to the ASP-DOWN state.  Therefore, the ASP is in the ASP-INACTIVE
state for the AS and the text is clear in the RFC that the SGP "MUST" send
ASP Inactive Ack.

If you don't want that to be the case, you need to change the state diagrams,
and the registration procedures, and a lot of things in a lot of places.
Where do you get the mandate to make all these changes to the registration
procedure?

You should get more feedback before placing such things in the IG.

Strike section 3.10.

> 
> >See RFC section 4.4.2 which
> >states:
> >
> >     The deregistration procedure does not necessarily imply the deletion
> >     of Routing Key and Application Server configuration data at the SG.
> >     Other ASPs may continue to be associated with the Application Server,
> >     in which case the Routing Key data SHOULD NOT be deleted.  If a
> >     Deregistration results in no more ASPs in an Application Server, an
> >     SG MAY delete the Routing Key data.
> >
> >The remainder of the IG section is either wrong, already stated in
> >the RFC or contradictatory:
> >
> >For annother example of wrong:
> >
> >  the IG says
> >
> >    ---------
> >    New text: (Section 4.5.3)
> >    ---------
> >
> >  The section is 4.3.4.4.
> >
> >
> >For example of contradictory:
> >
> >  the IG says:
> >
> >       - If the corresponding RK is registered (statically or
> >         dynamically), the peer should respond with an ASP Inactive Ack
> >         message.
> 
> Right, but it is no longer registered so this statement doesn't apply.
             ^^

"It," being the RK in the statement above, can continue to be registered.


> 
> >  the RFC (later in section 4.3.4.4) says:
> >
> >     The SGP MUST send an ASP Inactive Ack message in response to a
> >     received ASP Inactive message from the ASP and the ASP is already
> >     marked as ASP-INACTIVE at the SGP.
> 
> Granted, but the SGP would first validate the ASP Inactive message before
> replying.  If it found the RC in the message did not match any RKs the
> ASP was registered to, it would return an Error.

Nowhere does it say in the RFC that the SGP screens messages for RC values
that are only registered to ASPs.

There is also nothing in the RFC requiring that the SGP "forget" its static
configuration information just because an ASP deregisters.  Otherwise, the
static and dynamic approaches could not co-exist.  You must leave room for
the case where an SGP supports both static and dynamic configuration to ASPs
because it is permitted.  So the SGP in fact is permitted not to remove
Routing Keys and is also permitted to treat and ASP as though it is statically
registered after it deregisters.  This is why the section is contradictory,
it presupposes to tell the SG how to treat the ASP when the option is no
longer in effect.

> 
> 
> >For an example of duplication:
> >
> >  the IG says:
> >
> >       -  If the RK is not registered, or the RC information is not valid,
> >          the peer must respond with an ERROR message with Error Code =
> >          "Invalid Routing Context".
> >
> >  the RFC (later in section 4.3.4.4) says:
> >
> >                    ... The SGP or IPSP sends an Error message ("Invalid
> >     Routing Context") message for each invalid or unconfigured Routing
> >     Context value in a received ASP Inactive message.
> >
> >And that covers all the proposed changes for the section, so please
> >strike the section.
> 
> One could argue that this text in the RFC is sufficient, but there was
> enough confusion for people to request some clarifying text.

Repeating the same statements with errors, contradictions, and repetitions
in the same section does not qualify as "clarifying text".

Strike the section.   Or, rewrite it to remove the errors, contradictions
and repetitions.

> 
> >> 
> >> >Section 3.12
> >> >
> >> >  Strike this section.  It precludes DE which is allowed as an alternative
> >> >  in the the RFC.  SE and DE were never intended to interoperate with each
> >> >  other.  IPSPs that communicate with each other must operate in either SE
> >> >  mode or DE mode, but not a mixture.  As there is no interoperability
> >> >  concern, there is no reason to preclude DE.
> >> 
> >> We should make one option mandatory as it is right now (SE, as it is
> >> simpler) and have the DE as optional, since there are implementations that
> >> use it. The best way forward to ensure a minimum interoperability... 
> >
> >I disagree.  The best way forward is to write a proper extension draft
> >for peer-to-peer operation as was agreed when we let the RFC pass WG LC.
> >SE does not required any special IPSP description in the draft (because
> >it is exactly the way that an ASP talks to an SGP), and is already
> >supported by any node that supports ASP or SG operation.  IPSP is optional.
> >The only special treatment required for IPSP operation is DE, therefore
> >I take it that DE is clearly optional.
> >
> >So there is really no need to go to all that extent, all you are saying
> >is that SE is already there and DE is optional which is what was agreed
> >at WG LC and already reflected in the RFC.  I can give you pointers to
> >message threads if you would like to look back.
> >
> >Please strike the section.
> 
> Hopefully, there will be more comments on IPSP.  In regards to the SG-SG I-D,
> Tolga recently pitched that it move forward as a WG doc and I certainly support
> that.

Then let's strike this section and move these issues to the extension draft
as was agreed at LC.

If the WG, and particularly the WG chair and editors of these documents
don't start honoring some of the "promises" that were made at LC that
persuaded us into letting the drafts pass WG LC with outstanding issues,
I for one will certainly never let another RFC pass WG LC again with
outstanding issues.  That includes the IG.

This document (the IG) appears filled with implementation concerns rather
than interoperabiltiy issues.  That would be fine if the implementations
concerns were not being permitted to make "MUST" and "SHOULD" requirements.

If any implementor cannot see how to implement DE, the recomendation to
them is to not implement it.  The last thing that should be done is to
say that DE is "forbidden" because some implementors are short-signted.
Yet, this seems to be the case.

Strike the section.  Some implementors wish to implement the DE OPTION
as described in the RFC.  It is not the IGs place to remove this option
at this point.  Strike the section.

> 
> >> 
> >> 
> >> >Section 3.13
> >> >
> >> >  There are situations in which a MGMT message (Notify) must be sent
> >> >  on a stream other than "0".  This is where a Notify is required to
> >> >  be synchronized with ASPTM and DATA messages.  For example, when an
> >> >  SG sends Notify("Alternate ASP Active") it serves to move the active
> >> >  ASP to the ASP-INACTIVE state (just as an ASP Inactive Ack would do)
> >> >  and the ASP should not process DATA received after the Notify.  To
> >> >  avoid the race condition between a Notify("Alternate ASP Active")
> >> >  on stream "0" with data not on stream "0" would require sending the
> >> >  Notify on the same stream as the data.
> >> 
> >> Are you recommending that Notify be sent on all non-zero streams 
> >> in this case?  Otherwise, how do you select which stream to use?
> >
> >See draft-bidulock-sigtran-corid-00.txt for synchronization of data
> >flows across multiple streams.  Without those procedures, sending
> >DATA for one AS on multiple streams will result in a high probability
> >of mis-sequencing under failover conditions which an MTP-User is not
> >prepared to accept.
> >
> >If you use CORID, the Notify would only have to be sent on one of the
> >synchronized streams.
> 
> CORID no longer exists and cannot be considered normative.

You asked

>> how do you select which stream to use?

I was answering your question, not making a normative reference.

Besides, what has "normative" got to do with the discussion?--The IG
is in draft and cannot be considered normative.

> 
> >If you don't, you will get mis-sequencing of DATA if you send on
> >multiple streams regardless of which stream you choose for Notify.
> >
> >The RFC/IG should not tell the SG which stream it must send Notify on
> >otherwise, it will preclude the SG from synchronizing Notify with DATA.
> 
> I don't have a major problem with removing this restriction... again, hopefully
> we'll get more feedback.

Anybody disagree?  No?  Good.  Please remove the restriction.

This is a draft for heaven's sake, not a final draft of an RFC hanging on
being advanced.  Make the edits.  If someone disagrees they can bring it
up now, on the next version of the draft, or at LC, or not at all.

> 
> >> 
> >
> >> 
> >> 
> >> >Section 3.14
> >> >
> >> >  Remove "For AS-SG communication this parameter MUST NOT be used."
> >> >
> >> >  ASP Id in the ASP Up Ack would serve to identify the SGP in cases
> >> >  where Middle boxes and NAT make it impossible for the ASP to determine
> >> >  to which of several SGP it has connected.
> >> 
> >> Can you explain how the ASP would determine which SGP is had connected
> >> to based on ASP ID in the case of a NAT.  
> >
> >The ASP would determine which SGP it had connected to by examining the
> >ASP Id (really the SGP Id) returned in the ASP Up Ack.  This Id would
> >uniquely identify the SGP to the ASP.
> 
> Since the ASP is acting as the client, it will have to have an external address/port
> configured for the SGP in order to establish the association.  As SGP acts as
> a server behind the NAT, this external address/port would be statically provisioned
> to an internal address/port.  Allowing the SGP to return a SGP ID does not seem
> to provide much.

> Since the ASP is acting as the client
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Incorrect assumption.  The ASP is not required to act as a client from the
SCTP perspective.  The SG may also connect to the ASP.  In which case, it is
still the responsibiliy of the ASP to send ASP Up, but it does not necessarily
know which SGP has connected to it if dynamic port assignment and address
translation is being performed on the SGP side.

> 
> >> 
> >> 
> >> >Section 3.15
> >> >
> >> >  The change from MAY to SHOULD NOT is against consensus on the n+k
> >> >  model as described in the RFC.  Unless the "n" value is required to
> >> >  be provisioned by the SG and somehow coordinated between ASP and SG
> >> >  the SG cannot know when to do this an SHOULD NOT is not appropriate.
> >> >  "MAY chose not" was deemed appropriate in the last long discussion
> >> >  on this topic.
> >> >
> >> >  Please review post-LC threads on n+k and change SHOULD NOT back to
> >> >  "MAY chose not".
> >> 
> >> Wasn't there a discussion (thread "m3ua: IG : n+k redundancy - AS state
> >> machine") in which it was concluded that n is *required*. The SHOULD NOT is
> >> in line with that discussion. If "n" is required, it means that SG will have
> >> to know that value. It is a clear consequence.
> >
> >No, it was determined that "n" would be required to perform these
> >procedures.  Rather than require "n" (because many implementations
> >have no use for it), we made the procedure OPTIONAL with the MAY
> >that you just removed!  Please put it back the way it was before.
> 
> I'll review the thread.

Thank you for considering my lowly comments as worthy, master, for you
to perform a review, and for possibly considering making a change to
what must be an almost perfect document: because at revision number 1
it must have already been so thoroughly reviewed as to represent world
concensus. ;)

--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 mailnull@www1.ietf.org  Wed Jan 15 05:35: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 FAA21920
	for <sigtran-archive@odin.ietf.org>; Wed, 15 Jan 2003 05:35:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FAndA31109
	for sigtran-archive@odin.ietf.org; Wed, 15 Jan 2003 05:49:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FAn8J31057;
	Wed, 15 Jan 2003 05:49:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FAm1J31018
	for <sigtran@optimus.ietf.org>; Wed, 15 Jan 2003 05:48:01 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21888
	for <sigtran@ietf.org>; Wed, 15 Jan 2003 05:32:57 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:iAbS9Wp6QZGcoL1fXHV+HPh9uckUDSM7@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0FAZUD22898;
	Wed, 15 Jan 2003 03:35:30 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0FAZUQ27059;
	Wed, 15 Jan 2003 03:35:30 -0700
Date: Wed, 15 Jan 2003 03:35:30 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: sigtran@ietf.org
Cc: Ken Morneault <kmorneau@cisco.com>
Subject: Re: [Sigtran] I-D ACTION:draft-ietf-sigtran-m3ua-implementors-guide-02.txt
Message-ID: <20030115033530.A26872@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: sigtran@ietf.org, Ken Morneault <kmorneau@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
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>

Resend...

Ken Morneault wrote:                             (Thu, 02 Jan 2003 09:05:39)
> 
> 
> Brian,
> 
> Please address your concerns to the entire group as your proposed
> change is something for all to discuss.
> 
> Regards,
> 
> Ken


SIGTRAN,

Section 3.2.

What does it matter if the SGP sends "Unsupported Message Type" or
"Unsupported Message Class"?  Acutally, if we ever add a message to the class,
"Unsupport Message Class" might no longer be correct, whereas "Unsupported
Message Type" survives the addition of new message types to the class.

Also, as the only necessary piece of information given in the Error message
is the Message Class and Type, why force an implementation to include the
first 40 bytes of the message?  That's ridiculous.  All that needs to be
included a couple bytes of the message header.

Also, there is no more need to correlate this error than others.  The
ASP is obviously misconfigured (it figures it can register with an SGP
that does not even supoprt registration), so it really doesn't matter
what happens to it: there are many ways to misconfigure an ASP so that
it will not be caught by the protocol.

Please strike section 3.2.

Also note that M2UA and SUA also use the same text.  It makes no sense to
have M3UA act differently in this regard than M2UA and SUA.

--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 mailnull@www1.ietf.org  Wed Jan 15 06:37: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 GAA22842
	for <sigtran-archive@odin.ietf.org>; Wed, 15 Jan 2003 06:37:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FBq5m02593
	for sigtran-archive@odin.ietf.org; Wed, 15 Jan 2003 06:52:05 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FBpWJ02573;
	Wed, 15 Jan 2003 06:51:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FBoNJ02530
	for <sigtran@optimus.ietf.org>; Wed, 15 Jan 2003 06:50:23 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22784
	for <sigtran@ietf.org>; Wed, 15 Jan 2003 06:35:15 -0500 (EST)
Subject: Re: [Sigtran] I-D ACTION:draft-ietf-sigtran-m3ua-implementors-guide-02.txt
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF3591EBED.CDBC8501-ONC2256CAF.003F02EC@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Wed, 15 Jan 2003 13:35:13 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/15/2003
 01:35:17 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>


Brian,
> Resend...
>
> Ken Morneault wrote:
> (Thu, 02 Jan 2003 09:05:39)
> >
> >
> > Brian,
> >
> > Please address your concerns to the entire group
> as your proposed
> > change is something for all to discuss.
> >
> > Regards,
> >
> > Ken
>
>
> SIGTRAN,
>
> Section 3.2.
>
> What does it matter if the SGP sends "Unsupported
> Message Type" or
> "Unsupported Message Class"?  Acutally, if we ever
> add a message to the class,
> "Unsupport Message Class" might no longer be
> correct, whereas "Unsupported
> Message Type" survives the addition of new message
> types to the class.
[TOLGA]Although IMO not very important to send which one still just my 2
cents: Personally I would prefer "Unsupported Message Class" because it
suits better for the case, where registration procedure and so all of the
related messages in the message class is not supported.
>
> Also, as the only necessary piece of information
> given in the Error message
> is the Message Class and Type, why force an
> implementation to include the
> first 40 bytes of the message?  That's ridiculous.
> All that needs to be
> included a couple bytes of the message header.
[TOLGA] For that I agree. For those error types, reporting message class
and type should be enough.
>
> Also, there is no more need to correlate this error
> than others.  The
> ASP is obviously misconfigured (it figures it can
> register with an SGP
> that does not even supoprt registration), so it
> really doesn't matter
> what happens to it: there are many ways to
> misconfigure an ASP so that
> it will not be caught by the protocol.
>
> Please strike section 3.2.
>
> Also note that M2UA and SUA also use the same text.
> It makes no sense to
> have M3UA act differently in this regard than M2UA
> and SUA.

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



From mailnull@www1.ietf.org  Wed Jan 15 06:45:17 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 GAA22994
	for <sigtran-archive@odin.ietf.org>; Wed, 15 Jan 2003 06:45:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FBxqN03003
	for sigtran-archive@odin.ietf.org; Wed, 15 Jan 2003 06:59:52 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FBx6J02976;
	Wed, 15 Jan 2003 06:59:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FBwdJ02925
	for <sigtran@optimus.ietf.org>; Wed, 15 Jan 2003 06:58:39 -0500
Received: from mink.ecitele.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22979;
	Wed, 15 Jan 2003 06:43:31 -0500 (EST)
From: Lev.Finkel@ecitele.com
Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125])
	by mink.ecitele.com (8.9.1a/8.9.1) with ESMTP id NAA21535;
	Wed, 15 Jan 2003 13:41:11 +0200 (IST)
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
To: bidulock@openss7.org
Cc: chak@axes-mach01.usa.alcatel.com, ksrini@axes-mach01.usa.alcatel.com,
        latha@indts.com, sigtran@ietf.org, sigtran-admin@ietf.org
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OF9C1FBECF.9978B18A-ONC2256CAF.003E21B9@ecitele.com>
Date: Wed, 15 Jan 2003 13:45:06 +0200
X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at
 01/15/2003 01:46:24 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>


Brian,



                                                                                                           
                      "Brian F. G.                                                                         
                      Bidulock"                To:      Lev.Finkel@ecitele.com                             
                      <bidulock@openss         cc:      chak@axes-mach01.usa.alcatel.com,                  
                      7.org>                   ksrini@axes-mach01.usa.alcatel.com, latha@indts.com,        
                      Sent by:                 sigtran@ietf.org, sigtran-admin@ietf.org                    
                      sigtran-admin@ie         Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK     
                      tf.org                                                                               
                                                                                                           
                                                                                                           
                      15/01/03 12:25                                                                       
                      Please respond                                                                       
                      to bidulock                                                                          
                                                                                                           
                                                                                                           



> Lev.Finkel,
>
> Lev.Finkel@ecitele.com wrote:
(Wed, > 15 Jan 2003 12:04:23)
> >

> > > IUA IG Verion 2 Section 3.16.2 new text for Section 4.3.3.5, third
paragraph.
> >
> > I see. The paragraph describes only ASP behavior. To be consistent the
SG
> > behavior must be respectively described and section 3.3.2.6 to be
changed.
> > Now 3.3.2.6 says:
> >    The ASPAC Ack message is used to acknowledge an ASP-Active message
> >    received from a remote IUA peer.
> > Personally I do not like to define sending of ACK not triggered by any
> > request.
>
> Sorry, but the unsolicited behavior is permitted by all the UAs.  Section
> 3.3.2.6 does not need to be changed: it doesn't say "is _only_ used".

I agree. It states that the behavior of SG is implementation dependent (may
be covered in real Implementation Guide, not in protocol definition).
Any way if section 4.3.3.5 updated in future bis draft, then in 3.3.2.8
(not 3.3.2.6 - sorry) would be better to say
  "The ASP Inactive (ASPIA) ACK message is used to acknowledge an ASP
Inactive message
   received from remote IUA peer or to inform the remote IUA peer about
current ASP
   state".
It will also clarify that ASPAC may be replied by ASPIA ACK.
>
> >
> > >
> > > Wouldn't it be a good idea to start drafting an RFC3057bis.
> >
> > In light of interop problems we met till today with different respect
to IG
> > document I'd welcome RFC3057bis.
>
> I really meant just because there are all these modifications strewn
across
> a number of documents and it is getting difficult to piece the bits
together
> to get a complete picture.

What are other docs (except mails) that cover issues not included to the
IG?

>  If we had a RFC3057bis draft, then at least we
> could see the changes in one coherent document.
>

Can you trigger this activity?
>
> > > Strangely, RFC3331 says in section 3.3.1:
> > >
> > >    The "Invalid Interface Identifier" error would be sent by a SGP if
an
> > >    ASP sends a message (i.e. an ASP Active message) with an invalid
(not
> > >    configured) Interface Identifier value.  One of the optional
> > >    Interface Identifier parameters (Integer-based, text-based or
integer
> > >    range) MUST be used with this error code to identify the invalid
> > >    Interface Identifier(s) received.
> > >
> > > Which again says "not configured."
> > >
> > > Now, although RFC3331 (M2UA) says:
> > >
> > >                                           ...  The SGP MUST send an
> > >    Error message ("Invalid Interface Identifier") for each Interface
> > >    Identifier value that cannot be successfully activated.
> > >
> > > This text is not in RFC3057 or the IUA-IG and cannot be considered
applicable
> > > to IUA.  For M2UA, failure to activate might not only be caused by
misconfiguration.
> > > (e.g. failure of switching elements at the SG for automatic
allocation of
> > > signalling terminals or signalling data links or both, no reminaing
signalling
> > > terminals, etc...).
> > >
> >
> > Thanks for explanation. Not only Error code description in (3.3.1) but
also
> > its "name" does not sound for me covering the cases you have described.
>
> I agree, but RFC3331 does say "successfully activated" in section
4.whatever.
> I would have no problems placing "(not configured)" in section 4.whatever
of
> RFC3331.  One of the M2UA-IG.
>
> --brian

Regards,
Lev






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



From mailnull@www1.ietf.org  Wed Jan 15 06:58: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 GAA23255
	for <sigtran-archive@odin.ietf.org>; Wed, 15 Jan 2003 06:58:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FCCiG04153
	for sigtran-archive@odin.ietf.org; Wed, 15 Jan 2003 07:12:44 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FCCCJ04125;
	Wed, 15 Jan 2003 07:12:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FCBxJ04076
	for <sigtran@optimus.ietf.org>; Wed, 15 Jan 2003 07:11:59 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23201
	for <sigtran@ietf.org>; Wed, 15 Jan 2003 06:56:50 -0500 (EST)
Subject: Re: [Sigtran] I-D ACTION:draft-ietf-sigtran-m3ua-implementors-guide-02.txt
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF56D6A147.17ABB237-ONC2256CAF.00411C74@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Wed, 15 Jan 2003 13:56:48 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/15/2003
 01:56:52 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>

                                                                            
                                                                            
                                                                            
                                                                            
                                                                            
 Brian,                                                                     
                                                                            
   > >> >Section 3.14                                                       
   > >> >                                                                   
   > >> >  Remove "For AS-SG communication this parameter MUST NOT be       
   used."                                                                   
   > >> >                                                                   
   > >> >  ASP Id in the ASP Up Ack would serve to identify the SGP in      
   cases                                                                    
   > >> >  where Middle boxes and NAT make it impossible for the ASP to     
   determine                                                                
   > >> >  to which of several SGP it has connected.                        
   > >>                                                                     
   > >> Can you explain how the ASP would determine which SGP is had        
   connected                                                                
   > >> to based on ASP ID in the case of a NAT.                            
   > >                                                                      
   > >The ASP would determine which SGP it had connected to by examining    
   the                                                                      
   > >ASP Id (really the SGP Id) returned in the ASP Up Ack.  This Id       
   would                                                                    
   > >uniquely identify the SGP to the ASP.                                 
   >                                                                        
   > Since the ASP is acting as the client, it will have to have an         
   external address/port                                                    
   > configured for the SGP in order to establish the association.  As SGP  
   acts as                                                                  
   > a server behind the NAT, this external address/port would be           
   statically provisioned                                                   
   > to an internal address/port.  Allowing the SGP to return a SGP ID      
   does not seem                                                            
   > to provide much.                                                       
                                                                            
   > Since the ASP is acting as the client                                  
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^                                  
                                                                            
   Incorrect assumption.  The ASP is not required to act as a client from   
   the                                                                      
   SCTP perspective.  The SG may also connect to the ASP.  In which case,   
   it is                                                                    
   still the responsibiliy of the ASP to send ASP Up, but it does not       
   necessarily                                                              
   know which SGP has connected to it if dynamic port assignment and        
   address                                                                  
   translation is being performed on the SGP side.                          
   [TOLGA] In fact in such a case I think there might be another problem.   
   How will ASP fill AspId in ASPUP, without knowing which SGP is           
   connected?                                                               
   What was the reason to allow SGPs to connect to ASPs -just not to bring  
   a restriction unless it is really required?- ?.                          
                                                                            
                                                                            
                                                                            
                                                                            
                                                                            






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



From mailnull@www1.ietf.org  Wed Jan 15 07:10: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 HAA23388
	for <sigtran-archive@odin.ietf.org>; Wed, 15 Jan 2003 07:10:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FCOif04476
	for sigtran-archive@odin.ietf.org; Wed, 15 Jan 2003 07:24:44 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FCODJ04441;
	Wed, 15 Jan 2003 07:24:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FCNEJ04410
	for <sigtran@optimus.ietf.org>; Wed, 15 Jan 2003 07:23:14 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23371
	for <sigtran@ietf.org>; Wed, 15 Jan 2003 07:08:06 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:TUrHvX3UYoo6n5Rnt+N2g4yjYzHlAeQ3@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0FCBQD24630;
	Wed, 15 Jan 2003 05:11:27 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0FCBQn29695;
	Wed, 15 Jan 2003 05:11:26 -0700
Date: Wed, 15 Jan 2003 05:11:26 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] I-D ACTION:draft-ietf-sigtran-m3ua-implementors-guide-02.txt
Message-ID: <20030115051126.A29347@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF3591EBED.CDBC8501-ONC2256CAF.003F02EC@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF3591EBED.CDBC8501-ONC2256CAF.003F02EC@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Wed, Jan 15, 2003 at 01:35:13PM +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>

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Wed, 15 Jan 2003 13:35:13)
> 
> Brian,
> > Resend...
> >
> > Ken Morneault wrote:
> > (Thu, 02 Jan 2003 09:05:39)
> > >
> > >
> > > Brian,
> > >
> > > Please address your concerns to the entire group
> > as your proposed
> > > change is something for all to discuss.
> > >
> > > Regards,
> > >
> > > Ken
> >
> >
> > SIGTRAN,
> >
> > Section 3.2.
> >
> > What does it matter if the SGP sends "Unsupported
> > Message Type" or
> > "Unsupported Message Class"?  Acutally, if we ever
> > add a message to the class,
> > "Unsupport Message Class" might no longer be
> > correct, whereas "Unsupported
> > Message Type" survives the addition of new message
> > types to the class.
> [TOLGA]Although IMO not very important to send which one still just my 2
> cents: Personally I would prefer "Unsupported Message Class" because it
> suits better for the case, where registration procedure and so all of the
> related messages in the message class is not supported.

Well, the ASP didn't send every message type in the class, it just
sent one message type.  It is easy to conceiver that an implementation
could support DEREG REQ without supporting REG REQ.  When an ASP sends
DEREG REQ, it is responded to with a DEREG RSP with a Deregistration
Result indicating "Error - Not Registered".  So it is possible that
an implementation supports DEREG REQ without supporting REG REQ.

In fact, an SGP not supporting dynamic registration could easily
send REG RSP with Registration Result "Error - Unsupported RK parameter
field" or some such.  Just because an SGP "does not suppor the
registration procedure" does not mean that it cannot respond to
any message in the class.

At best, section 3.2 of the IG needs to be reworked in light of the
above.

Comments?

--brian


> >
> > Also, as the only necessary piece of information
> > given in the Error message
> > is the Message Class and Type, why force an
> > implementation to include the
> > first 40 bytes of the message?  That's ridiculous.
> > All that needs to be
> > included a couple bytes of the message header.
> [TOLGA] For that I agree. For those error types, reporting message class
> and type should be enough.
> >
> > Also, there is no more need to correlate this error
> > than others.  The
> > ASP is obviously misconfigured (it figures it can
> > register with an SGP
> > that does not even supoprt registration), so it
> > really doesn't matter
> > what happens to it: there are many ways to
> > misconfigure an ASP so that
> > it will not be caught by the protocol.
> >
> > Please strike section 3.2.
> >
> > Also note that M2UA and SUA also use the same text.
> > It makes no sense to
> > have M3UA act differently in this regard than M2UA
> > and SUA.
> 
> _______________________________________________
> 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 Jan 15 07:16: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 HAA23479
	for <sigtran-archive@odin.ietf.org>; Wed, 15 Jan 2003 07:16:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FCUaM04697
	for sigtran-archive@odin.ietf.org; Wed, 15 Jan 2003 07:30:36 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FCU6J04683;
	Wed, 15 Jan 2003 07:30:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FCTMJ04648
	for <sigtran@optimus.ietf.org>; Wed, 15 Jan 2003 07:29:22 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23461;
	Wed, 15 Jan 2003 07:14:13 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:dhcOukB56v2GTRsIxieqIqLyNBzZ0mH2@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0FCHXD24692;
	Wed, 15 Jan 2003 05:17:33 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0FCHXs29743;
	Wed, 15 Jan 2003 05:17:33 -0700
Date: Wed, 15 Jan 2003 05:17:33 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Lev.Finkel@ecitele.com
Cc: chak@axes-mach01.usa.alcatel.com, ksrini@axes-mach01.usa.alcatel.com,
        latha@indts.com, sigtran@ietf.org, sigtran-admin@ietf.org
Subject: Re: [Sigtran] IUA -  ASP Active and ACTIVE ACK
Message-ID: <20030115051733.B29347@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Lev.Finkel@ecitele.com, chak@axes-mach01.usa.alcatel.com,
	ksrini@axes-mach01.usa.alcatel.com, latha@indts.com,
	sigtran@ietf.org, sigtran-admin@ietf.org
References: <OF9C1FBECF.9978B18A-ONC2256CAF.003E21B9@ecitele.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: <OF9C1FBECF.9978B18A-ONC2256CAF.003E21B9@ecitele.com>; from Lev.Finkel@ecitele.com on Wed, Jan 15, 2003 at 01:45:06PM +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>

Lev,

Lev.Finkel@ecitele.com wrote:                                                   (Wed, 15 Jan 2003 13:45:06)
> 
> > > > IUA IG Verion 2 Section 3.16.2 new text for Section 4.3.3.5, third paragraph.
> > >
> > > I see. The paragraph describes only ASP behavior. To be consistent the SG
> > > behavior must be respectively described and section 3.3.2.6 to be changed.
> > > Now 3.3.2.6 says:
> > >    The ASPAC Ack message is used to acknowledge an ASP-Active message
> > >    received from a remote IUA peer.
> > > Personally I do not like to define sending of ACK not triggered by any
> > > request.
> >
> > Sorry, but the unsolicited behavior is permitted by all the UAs.  Section
> > 3.3.2.6 does not need to be changed: it doesn't say "is _only_ used".
> 
> I agree. It states that the behavior of SG is implementation dependent (may
> be covered in real Implementation Guide, not in protocol definition).
> Any way if section 4.3.3.5 updated in future bis draft, then in 3.3.2.8
> (not 3.3.2.6 - sorry) would be better to say

>   "The ASP Inactive (ASPIA) ACK message is used to acknowledge an ASP Inactive message
>    received from remote IUA peer or to inform the remote IUA peer about current ASP
>    state".

> It will also clarify that ASPAC may be replied by ASPIA ACK.

I agree.

> >
> > >
> > > >
> > > > Wouldn't it be a good idea to start drafting an RFC3057bis.
> > >
> > > In light of interop problems we met till today with different respect to IG
> > > document I'd welcome RFC3057bis.
> >
> > I really meant just because there are all these modifications strewn across
> > a number of documents and it is getting difficult to piece the bits together
> > to get a complete picture.
> 
> What are other docs (except mails) that cover issues not included to the
> IG?

Well, the IUA-IG imports text wholesale from the other UAs.  However, some
of that text is being modified by other IGs.  For RFC3057 in particular it
becomes difficult to understand all the changes without considering the
IUA-IG, the M2UA IG, the M3UA IG, etc.

> 
> >  If we had a RFC3057bis draft, then at least we
> > could see the changes in one coherent document.
> >
> 
> Can you trigger this activity?

Well, I could write a draft-*-sigtran-RFC3057bis-00.txt that incorporates the
changes of the IG and pulls in changes from the other IGs.  But I think that
it would take endorsement of the WG and our WG Chair to slate the work.

--brain

-- 
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 Jan 15 09:22: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 JAA28169
	for <sigtran-archive@odin.ietf.org>; Wed, 15 Jan 2003 09:22:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FEapA13554
	for sigtran-archive@odin.ietf.org; Wed, 15 Jan 2003 09:36:51 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FEZeJ13507;
	Wed, 15 Jan 2003 09:35:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FEYaJ13423
	for <sigtran@optimus.ietf.org>; Wed, 15 Jan 2003 09:34:36 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28108
	for <sigtran@ietf.org>; Wed, 15 Jan 2003 09:19:25 -0500 (EST)
Received: from esealnt610.al.sw.ericsson.se (esealnt610.al.sw.ericsson.se [153.88.254.69])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id h0FEMjKV002730;
	Wed, 15 Jan 2003 15:22:45 +0100 (MET)
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 ZGNBD0YT; Wed, 15 Jan 2003 15:22:45 +0100
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <Y826NWCG>; Wed, 15 Jan 2003 15:22:45 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C475A1F@EESTQNT105.es.eu.ericsson.se>
X-Sybari-Trust: 2ef3b0af 1864f774 206fc897 00000138
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>,
        TOLGA ASVEREN
	 <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] I-D ACTION:draft-ietf-sigtran-m3ua-implementors-gui
	de-02.txt
Date: Wed, 15 Jan 2003 15:22:44 +0100
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, 

IMHO an implementation supports or not the registration procedures. Supporting some of the messages means increasing the coding without getting any practical advantage. I agree with Tolga on this point: it is not a vital decission, but it makes sense to choose the message class error.

The inclusion of 40 bytes of the message was decided in order to find what message you sent. If you don't do that way you may not find what was the origin of the failure. Since the source of the failure could have been a software bug, you may have produced a lot of messages with the erroneous message class/type and can not find which one was the faulty one. I might help in the debugging process...

Cheers // Javier. 

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Wednesday, January 15, 2003 1:11 PM
> To: TOLGA ASVEREN
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] I-D
> ACTION:draft-ietf-sigtran-m3ua-implementors-guide-02.txt
> 
> 
> TOLGA,
> 
> TOLGA ASVEREN wrote:                                          
>                        (Wed, 15 Jan 2003 13:35:13)
> > 
> > Brian,
> > > Resend...
> > >
> > > Ken Morneault wrote:
> > > (Thu, 02 Jan 2003 09:05:39)
> > > >
> > > >
> > > > Brian,
> > > >
> > > > Please address your concerns to the entire group
> > > as your proposed
> > > > change is something for all to discuss.
> > > >
> > > > Regards,
> > > >
> > > > Ken
> > >
> > >
> > > SIGTRAN,
> > >
> > > Section 3.2.
> > >
> > > What does it matter if the SGP sends "Unsupported
> > > Message Type" or
> > > "Unsupported Message Class"?  Acutally, if we ever
> > > add a message to the class,
> > > "Unsupport Message Class" might no longer be
> > > correct, whereas "Unsupported
> > > Message Type" survives the addition of new message
> > > types to the class.
> > [TOLGA]Although IMO not very important to send which one 
> still just my 2
> > cents: Personally I would prefer "Unsupported Message 
> Class" because it
> > suits better for the case, where registration procedure and 
> so all of the
> > related messages in the message class is not supported.
> 
> Well, the ASP didn't send every message type in the class, it just
> sent one message type.  It is easy to conceiver that an implementation
> could support DEREG REQ without supporting REG REQ.  When an ASP sends
> DEREG REQ, it is responded to with a DEREG RSP with a Deregistration
> Result indicating "Error - Not Registered".  So it is possible that
> an implementation supports DEREG REQ without supporting REG REQ.
> 
> In fact, an SGP not supporting dynamic registration could easily
> send REG RSP with Registration Result "Error - Unsupported RK 
> parameter
> field" or some such.  Just because an SGP "does not suppor the
> registration procedure" does not mean that it cannot respond to
> any message in the class.
> 
> At best, section 3.2 of the IG needs to be reworked in light of the
> above.
> 
> Comments?
> 
> --brian
> 
> 
> > >
> > > Also, as the only necessary piece of information
> > > given in the Error message
> > > is the Message Class and Type, why force an
> > > implementation to include the
> > > first 40 bytes of the message?  That's ridiculous.
> > > All that needs to be
> > > included a couple bytes of the message header.
> > [TOLGA] For that I agree. For those error types, reporting 
> message class
> > and type should be enough.
> > >
> > > Also, there is no more need to correlate this error
> > > than others.  The
> > > ASP is obviously misconfigured (it figures it can
> > > register with an SGP
> > > that does not even supoprt registration), so it
> > > really doesn't matter
> > > what happens to it: there are many ways to
> > > misconfigure an ASP so that
> > > it will not be caught by the protocol.
> > >
> > > Please strike section 3.2.
> > >
> > > Also note that M2UA and SUA also use the same text.
> > > It makes no sense to
> > > have M3UA act differently in this regard than M2UA
> > > and SUA.
> > 
> > _______________________________________________
> > 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 mailnull@www1.ietf.org  Wed Jan 15 13:24:56 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 NAA05882
	for <sigtran-archive@odin.ietf.org>; Wed, 15 Jan 2003 13:24:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FIdeW32681
	for sigtran-archive@odin.ietf.org; Wed, 15 Jan 2003 13:39:40 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FIcxJ32651;
	Wed, 15 Jan 2003 13:39:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FIb3J31958
	for <sigtran@optimus.ietf.org>; Wed, 15 Jan 2003 13:37:03 -0500
Received: from web8205.mail.in.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA05714
	for <sigtran@ietf.org>; Wed, 15 Jan 2003 13:21:48 -0500 (EST)
Message-ID: <20030115182508.553.qmail@web8205.mail.in.yahoo.com>
Received: from [61.1.106.78] by web8205.mail.in.yahoo.com via HTTP; Wed, 15 Jan 2003 18:25:08 GMT
Date: Wed, 15 Jan 2003 18:25:08 +0000 (GMT)
From: =?iso-8859-1?q?amit=20somani?= <amitksomani@yahoo.co.in>
To: lksctp developers <sctp-developers-list@cig.mot.com>,
        Sigtran <sigtran@ietf.org>, tsvwg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Sigtran] SS7 signal
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

hello everyone,
we are a group of 3 students from pune institute of
computer technology,pune ,india. we are doing a
project on SS7. for that we want to know how the SS7
signals look? Though we`ve read many tutorials from
net and also read a book on SS7 by travis russel but
still could not get the exact details of the SS7
signals ( especially Message Signal Units). My exact
doubt is how does SS7 signals look exactly on a SS7
link?
Can someone send us the message which are practically
extracted from SS7 link as we do not have access to
SS7 link and give us the details of the message? or
else can someone give the signals which might be used
for demo purpose like some signal xxxxxxxxxxx for call
establishment , xxxxxx..xx for canceling a call and so
on.

plz do reply.

thank you.
amit. 

________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
       visit http://in.tv.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Wed Jan 15 17:00: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 RAA11367
	for <sigtran-archive@odin.ietf.org>; Wed, 15 Jan 2003 17:00:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FMFT213992
	for sigtran-archive@odin.ietf.org; Wed, 15 Jan 2003 17:15:29 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FMElJ13881;
	Wed, 15 Jan 2003 17:14:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FFo6J19275
	for <sigtran@optimus.ietf.org>; Wed, 15 Jan 2003 10:50:06 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00170;
	Wed, 15 Jan 2003 10:34:52 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (esealnt612.al.sw.ericsson.se [153.88.254.71])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id h0FFcCKV029914;
	Wed, 15 Jan 2003 16:38:12 +0100 (MET)
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2655.55)
	id <ZGNDD7GV>; Wed, 15 Jan 2003 16:38:12 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E324CE@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EAB)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>,
        "'tsvwg@ietf.org'"
	 <tsvwg@ietf.org>,
        "Allison Mankin (E-mail)" <mankin@psg.com>
Date: Wed, 15 Jan 2003 16:38:03 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] Removing SCTP header compression from the ROHC charter
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>

ROHCers (cc sigtran & tsvwg),

The current ROHC WG charter has SCTP header compression listed as
one of our work items.  When this item was added, activity within
the ROHC WG was high, and the addition was made as a prediction of
future expectations rather than an outcome of well justified
immediate requirements.

Trying to fulfill this work item during the last year, we have
repeatedly asked for contributions to SCTP header compression, but
we have not received a single response.

Given that this work item was originally added without immediate
market pull, and considering the lack of current interest in doing
the work (or even having it done at all), we intend to remove SCTP
header compression from the ROHC WG charter.  To keep it in the
charter, justifications for developing SCTP header compression now
would have to be presented, as well as industry support and
commitments for doing the actual work.

Barring further input, we will send a request to the ADs by Jan 24,
so please reply before this date if you believe SCTP header
compression should be on the agenda now.

/Lars-Erik & Carsten
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Wed Jan 15 22:45: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 WAA19973
	for <sigtran-archive@odin.ietf.org>; Wed, 15 Jan 2003 22:45:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0G40Uk05776
	for sigtran-archive@odin.ietf.org; Wed, 15 Jan 2003 23:00:30 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G3xdJ05687;
	Wed, 15 Jan 2003 22:59:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G3w6J05635
	for <sigtran@optimus.ietf.org>; Wed, 15 Jan 2003 22:58:06 -0500
Received: from wiprom2mx1.wipro.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19945;
	Wed, 15 Jan 2003 22:42:35 -0500 (EST)
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5])
	by wiprom2mx1.wipro.com (8.11.3/8.11.3) with SMTP id h0G3jtv29572;
	Thu, 16 Jan 2003 09:15:55 +0530 (IST)
Received: from blr-k1-msg.wipro.com ([10.117.50.99]) by blr-m1-bh1.wipro.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 16 Jan 2003 09:15:49 +0530
Received: from blr-k1-msg.wipro.com ([10.117.50.99]) by blr-k1-msg.wipro.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 16 Jan 2003 09:15:49 +0530
Received: from wslexch.nortel-k1.wipro.com ([192.219.223.59]) by blr-k1-msg.wipro.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 16 Jan 2003 09:15:49 +0530
Received: by wslexch.nortel-k1.wipro.com with Internet Mail Service (5.5.2653.19)
	id <CYNA179J>; Thu, 16 Jan 2003 09:29:54 +0530
Message-ID: <96EEAF0DC507D6118AB60000E2293D1F01A69CF4@wslexch.nortel-k1.wipro.com>
From: Anil Kumar <anil.vydyam@wipro.com>
To: amit somani <amitksomani@yahoo.co.in>,
        lksctp developers
	 <sctp-developers-list@cig.mot.com>,
        Sigtran <sigtran@ietf.org>, tsvwg@ietf.org
Subject: RE: [Sigtran] SS7 signal
Date: Thu, 16 Jan 2003 09:29:53 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C2BD13.B9B30260"
X-OriginalArrivalTime: 16 Jan 2003 03:45:49.0632 (UTC) FILETIME=[C2934400:01C2BD11]
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 message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C2BD13.B9B30260
Content-Type: text/plain

I hope this will help, if not, please let me know ...

- Anil.V
 <<ISUP_MSGS.doc>> 

> -----Original Message-----
> From:	amit somani [SMTP:amitksomani@yahoo.co.in]
> Sent:	Wednesday, January 15, 2003 11:55 PM
> To:	lksctp developers; Sigtran; tsvwg@ietf.org
> Subject:	[Sigtran] SS7 signal
> 
> hello everyone,
> we are a group of 3 students from pune institute of
> computer technology,pune ,india. we are doing a
> project on SS7. for that we want to know how the SS7
> signals look? Though we`ve read many tutorials from
> net and also read a book on SS7 by travis russel but
> still could not get the exact details of the SS7
> signals ( especially Message Signal Units). My exact
> doubt is how does SS7 signals look exactly on a SS7
> link?
> Can someone send us the message which are practically
> extracted from SS7 link as we do not have access to
> SS7 link and give us the details of the message? or
> else can someone give the signals which might be used
> for demo purpose like some signal xxxxxxxxxxx for call
> establishment , xxxxxx..xx for canceling a call and so
> on.
> 
> plz do reply.
> 
> thank you.
> amit. 
> 
> ________________________________________________________________________
> Missed your favourite TV serial last night? Try the new, Yahoo! TV.
>        visit http://in.tv.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

------_=_NextPart_000_01C2BD13.B9B30260
Content-Type: application/msword;
	name="ISUP_MSGS.doc"
Content-Disposition: attachment;
	filename="ISUP_MSGS.doc"
Content-Transfer-Encoding: base64

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAJgAAAAAAAAAA
EAAAKAAAAAEAAAD+////AAAAACUAAAD/////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////s
pcEAWQAJBAAAABK/AAAAAAAAEAAAAAAABAAACAwAAA4AYmpiavNX81cAAAAAAAAAAAAAAAAAAAAA
AAAJBBYALRgAAJE9AQCRPQEACAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD//w8AAAAA
AAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAAAAAAAAAAAAF0AAAAAAPYAAAAAAAAA9gAAAPYA
AAAAAAAA9gAAAAAAAAD2AAAAAAAAAPYAAAAAAAAA9gAAABQAAAAAAAAAAAAAAAoBAAAAAAAACgEA
AAAAAAAKAQAAAAAAAAoBAAAAAAAACgEAAAwAAAAWAQAAFAAAAAoBAAAAAAAAqwIAAC4BAAA2AQAA
AAAAADYBAAAAAAAANgEAAAAAAAA2AQAAAAAAADYBAAAAAAAANgEAAAAAAAA2AQAAAAAAADYBAAAA
AAAAcAIAAAIAAAByAgAAAAAAAHICAAAAAAAAcgIAAAAAAAByAgAAAAAAAHICAAAAAAAAcgIAACQA
AADZAwAA9AEAAM0FAACsAAAAlgIAABUAAAAAAAAAAAAAAAAAAAAAAAAA9gAAAAAAAAA2AQAAAAAA
AAAAAAAAAAAAAAAAAAAAAAA2AQAAAAAAADYBAAAAAAAANgEAAAAAAAA2AQAAAAAAAJYCAAAAAAAA
uAEAAAAAAAD2AAAAAAAAAPYAAAAAAAAANgEAAAAAAAAAAAAAAAAAADYBAAAAAAAANgEAAAAAAAC4
AQAAAAAAALgBAAAAAAAAuAEAAAAAAAA2AQAAAAAAAPYAAAAAAAAANgEAAAAAAAD2AAAAAAAAADYB
AAAAAAAAcAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAACgEAAAAAAAAKAQAAAAAAAPYAAAAAAAAA9gAA
AAAAAAD2AAAAAAAAAPYAAAAAAAAANgEAAAAAAABwAgAAAAAAALgBAAC4AAAAuAEAAAAAAAAAAAAA
AAAAAHACAAAAAAAA9gAAAAAAAAD2AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAcAIAAAAAAAA2AQAAAAAAACoBAAAMAAAAAEYH0Ei8
wgEKAQAAAAAAAAoBAAAAAAAANgEAAIIAAABwAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAASVNV
UCBNZXNzYWdlIHN0cnVjdHVyZSBjYXB0dXJlZCBvbiBTUzcgbGluay4NDQ1KVU4xOSAxNTo0Mjo1
NCAwNDAxIElORk8gSU5DT01JTkcgTElOSyBNU0cNQzcgSEVBREVSOiBMRU49NDcgTVNHPSMwMSBM
SU5LPTIgU0xDPTAgQ0xMST1DN0xLU0VUMA1DNyBTSU86ICAgIE5FVFdPUks9IDAgICBQUklPUklU
WT0gMCAgIFNFUlYgSU5EPSA1DUM3IExBQkVMOiBEUEMgPSBBTlNJNyAwMDAgMDAwIDAwMSAgT1BD
ID0gQU5TSTcgMDAwIDAwMCAwMTggIFNMUyA9IDANUzcgREFUQSBGT0xMT1dJTkcgUk9VVElORyBM
QUJFTDoNQ0EgMDAgMDEgMDAgNDggMDAgMDAgMDMgMDYgMEQgMDMgODAgOTAgQTIgMDcgMDMNMTAg
MDUgODEgMzQgMzQgMTIgMEEgMDcgMDMgMTAgMDIgNTEgNTUgMjEgMjEgRUENMDEgMDAgRkUgMDIg
MDAgMDAgMDANDUpVTjE5IDE1OjQyOjU1IDA1MDIgSU5GTyBPVVRHT0lORyBMSU5LIE1TRw1DNyBI
RUFERVI6IExFTj0xOSBNU0c9IzA2IExJTks9MiBTTEM9MCBDTExJPUM3TEtTRVQwDUM3IFNJTzog
ICAgTkVUV09SSz0gMCAgIFBSSU9SSVRZPSAyICAgU0VSViBJTkQ9IDUNQzcgTEFCRUw6ICBEUEMg
PSBBTlNJNyAwMDAgMDAwIDAxOCAgT1BDID0gQU5TSTcgMDAwIDAwMCAwMDEgIFNMUyA9IDE4DVM3
IERBVEEgRk9MTE9XSU5HIFJPVVRJTkcgTEFCRUw6DUNBIDAwIDA2IDE0IEQxIDAxIEZEIDAyIDg0
IDAwIDAwDQ1KVU4xOSAxNTo0Mjo1NyAwNjAzIElORk8gT1VUR09JTkcgTElOSyBNU0cNQzcgSEVB
REVSOiBMRU49MTIgTVNHPSMwOSBMSU5LPTIgU0xDPTAgQ0xMST1DN0xLU0VUMA1DNyBTSU86ICAg
IE5FVFdPUks9IDAgICBQUklPUklUWT0gMiAgIFNFUlYgSU5EPSA1DUM3IExBQkVMOiAgRFBDID0g
QU5TSTcgMDAwIDAwMCAwMTggIE9QQyA9IEFOU0k3IDAwMCAwMDAgMDAxICBTTFMgPSAxOA1TNyBE
QVRBIEZPTExPV0lORyBST1VUSU5HIExBQkVMOg1DQSAwMCAwOSAwMA0NSlVOMTkgMTU6NDM6MjMg
MTYwNCBJTkZPIE9VVEdPSU5HIExJTksgTVNHDUM3IEhFQURFUjogTEVOPTI2IE1TRz0jMEMgTElO
Sz0yIFNMQz0wIENMTEk9QzdMS1NFVDANQzcgU0lPOiAgICBORVRXT1JLPSAwICAgUFJJT1JJVFk9
IDIgICBTRVJWIElORD0gNQ1DNyBMQUJFTDogIERQQyA9IEFOU0k3IDAwMCAwMDAgMDE4ICBPUEMg
PSBBTlNJNyAwMDAgMDAwIDAwMSAgU0xTID0gMTgNUzcgREFUQSBGT0xMT1dJTkcgUk9VVElORyBM
QUJFTDoNQ0EgMDAgMEMgMDIgMDQgMDIgODMgOUYgMUUgMDMgMDEgMDAgMDAgRkQgMDIgMDQNMDAg
MDANDUpVTjE5IDE1OjQzOjI1IDE5MDYgSU5GTyBPVVRHT0lORyBMSU5LIE1TRw1DNyBIRUFERVI6
IExFTj0xMSBNU0c9IzEwIExJTks9MiBTTEM9MCBDTExJPUM3TEtTRVQwDUM3IFNJTzogICAgTkVU
V09SSz0gMCAgIFBSSU9SSVRZPSAyICAgU0VSViBJTkQ9IDUNQzcgTEFCRUw6ICBEUEMgPSBBTlNJ
NyAwMDAgMDAwIDAxOCAgT1BDID0gQU5TSTcgMDAwIDAwMCAwMDEgIFNMUyA9IDE4DVM3IERBVEEg
Rk9MTE9XSU5HIFJPVVRJTkcgTEFCRUw6DUNBIDAwIDEwDQkNVGhlIG1lc3NhZ2Ugc3RhcnRzIHdp
dGggdGhlIENJQyAoQ0EgMDAgPSAyMDIge3R3byBieXRlcyBhcmUgYmFja3dhcmRzfSkuIFRoZSBu
ZXh0IGJ5dGUgaXMgdGhlIG1lc3NhZ2UgdHlwZTogMDEgPSBJbml0aWFsIEFkZHJlc3MgTWVzc2Fn
ZSAoSUFNKSwgMDYgPSBBZGRyZXNzIENvbXBsZXRlIE1lc3NhZ2UgKEFDTSksIDA5ID0gQW5zd2Vy
IE1lc3NhZ2UgKEFOTSksIDBDID0gUmVsZWFzZSBNZXNzYWdlIChSRUwpLCAxMCA9IFJlbGVhc2Ug
Q29tcGxldGUgTWVzc2FnZSAoUkxDKS4gDU5leHQgd2Ugd2lsbCBpbnRlcmNlcHQgYSBtZXNzYWdl
IHNvIHRoYXQgd2UgY2FuIGJ1aWxkIG9uZSBvZiBvdXIgb3duLiBMZXQncyBzYXkgd2Ugd2FudCB0
byBpbnRlcmNlcHQgdGhlIEFDTSBtZXNzYWdlLiANDQ0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
DQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAC0EAADx
CQAAeAsAAAgMAAD3APAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAADENKFgBPSgMAUUoDAAAPNQiBQ0oWAE9KAwBRSgMAAAQABAAALQQAAC4E
AAAvBAAAWgQAAI8EAADBBAAABQUAACYFAABWBQAAhgUAAJsFAACcBQAAxwUAAPwFAAAuBgAAdAYA
AJUGAAC2BgAAtwYAAOIGAAAXBwAASQcAAI8HAACwBwAAvAcAAL0HAADoBwAAHQgAAPgAAAAAAAAA
AAAAAADzAAAAAAAAAAAAAAAA8wAAAAAAAAAAAAAAAPMAAAAAAAAAAAAAAADzAAAAAAAAAAAAAAAA
8wAAAAAAAAAAAAAAAPMAAAAAAAAAAAAAAADzAAAAAAAAAAAAAAAA8wAAAAAAAAAAAAAAAPMAAAAA
AAAAAAAAAADzAAAAAAAAAAAAAAAA8wAAAAAAAAAAAAAAAPMAAAAAAAAAAAAAAADzAAAAAAAAAAAA
AAAA8wAAAAAAAAAAAAAAAPMAAAAAAAAAAAAAAADzAAAAAAAAAAAAAAAA8wAAAAAAAAAAAAAAAPMA
AAAAAAAAAAAAAADzAAAAAAAAAAAAAAAA8wAAAAAAAAAAAAAAAPMAAAAAAAAAAAAAAADzAAAAAAAA
AAAAAAAA8wAAAAAAAAAAAAAAAPMAAAAAAAAAAAAAAADzAAAAAAAAAAAAAAAA8wAAAAAAAAAAAAAA
APMAAAAAAAAAAAAAAAAAAAAAAAAFDwANxgQBdiUABw8AD4TQAg3GBAF2JQAAHAAEAAAtBAAALgQA
AC8EAABaBAAAjwQAAMEEAAAFBQAAJgUAAFYFAACGBQAAmwUAAJwFAADHBQAA/AUAAC4GAAB0BgAA
lQYAALYGAAC3BgAA4gYAABcHAABJBwAAjwcAALAHAAC8BwAAvQcAAOgHAAAdCAAATwgAAJUIAAC2
CAAA5ggAAOwIAADtCAAAGAkAAE0JAAB/CQAAxQkAAOYJAADvCQAA8QkAAAMLAAB6CwAAewsAAHwL
AAAIDAAA/f39/f39/f39/f39/f39/f39/f39/f39/f39/f39/f39/f39/f39/f0AAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAwIPAAAuHQgAAE8IAACVCAAA
tggAAOYIAADsCAAA7QgAABgJAABNCQAAfwkAAMUJAADmCQAA7wkAAPEJAAADCwAAegsAAHsLAAB8
CwAACAwAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD3AAAAAAAAAAAAAAAA9wAAAAAAAAAAAAAAAPUAAAAAAAAAAAAAAAD1AAAAAAAAAAAAAAAA
9QAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAADAAADJAMFDwANxgQBdiUAABIrABIwABxQAQAfsNAv
ILDgPSGwoAUisKAFI5CgBSSQoAUlsAAAF7CgBRiwoAUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABIAEAAKAAEAWwAPAAIA
AAAAAAAAJAAAQPH/AgAkAAAABgBOAG8AcgBtAGEAbAAAAAIAAAAEAG1ICQQAAAAAAAAAAAAAAAAA
AAAAAAA8AEFA8v+hADwAAAAWAEQAZQBmAGEAdQBsAHQAIABQAGEAcgBhAGcAcgBhAHAAaAAgAEYA
bwBuAHQAAAAAAAAAAAAAAAAAYgD+bwEA8gBiAAAADABQAHIAZQBmAG8AcgBtAGEAdAB0AGUAZAAA
ACgADwANxiMACwAAvwN+Bz0L/A67EnoWORr4HbchdiUAAAAAAAAAAAAAAA8AT0oEAFFKBABoCABu
SAkEAAAAAAAICAAACAAAGAAABgD/////AAQAAAgMAAAIAAAAAAQAAB0IAAAIDAAACQAAAAsAAAAA
BAAACAwAAAoAAAAAAAAAlQAAAKEAAADfAAAA5wAAAAICAAAOAgAANgIAADwCAAAdAwAAKQMAAFED
AABXAwAAIwQAAC8EAABXBAAAXQQAAFMFAABfBQAAhwUAAI0FAAAKCAAABwAaAAcAGgAHABoABwAa
AAcAGgAHABoABwAaAAcAGgAHABoABwAaAAcA//8EAAAAAwBJAE0ARwAdAEMAOgBcAE0AeQAgAEQA
bwBjAHUAbQBlAG4AdABzAFwASQBTAFUAUABfAE0AUwBHAFMALgBkAG8AYwADAEkATQBHADIAQwA6
AFwAVwBJAE4ARABPAFcAUwBcAFQARQBNAFAAXABBAHUAdABvAFIAZQBjAG8AdgBlAHIAeQAgAHMA
YQB2AGUAIABvAGYAIABJAFMAVQBQAF8ATQBTAEcAUwAuAGEAcwBkAP9AA4ABAAcIAAAHCAAAeKZ0
AAEAAQAHCAAAAAAAAHsHAAAAAAAAAhAAAAAAAAAACAgAAIAAAAgAQAAABQAAAEcWkAEAAAICBgMF
BAUCAwQDAAAAAAAAAAAAAAAAAAAAAQAAAAAAAABUAGkAbQBlAHMAIABOAGUAdwAgAFIAbwBtAGEA
bgAAADUWkAECAAUFAQIBBwYCBQcAAAAAAAAAEAAAAAAAAAAAAAAAgAAAAABTAHkAbQBiAG8AbAAA
ADMmkAEAAAILBgQCAgICAgQDAAAAAAAAAAAAAAAAAAAAAQAAAAAAAABBAHIAaQBhAGwAAAA3JpAB
AAACCwYEAwUEBAIEhwIAAAAAAAAAAAAAAAAAAJ8AAAAAAAAAVgBlAHIAZABhAG4AYQAAAD81kAEA
AAIHAwkCAgUCBAQDAAAAAAAAAAAAAAAAAAAAAQAAAAAAAABDAG8AdQByAGkAZQByACAATgBlAHcA
AAAiAAQAMQiIGAAA0AIAAGgBAAAAAEJ6cWZRenFmAAAAAAYABgAAACkBAACfBgAAAQADAAAABAAD
EA4AAAAAAAAAAAAAAAEAAQAAAAEAAAAAAAAAIQMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAApQbAB7QAtACAADIwAAAAAAAAAAAAAAAAAAAhCAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAP//EgAAAAAAAAA7
ADIANQAwAEYAIAAgACAAIAAgAEMANwBUAFUAMQAwADEAIABKAFUATgAxADkAIAAxADUAOgA0ADIA
OgA1ADQAIAAwADQAMAAxACAASQBOAEYATwAgAEkATgBDAE8ATQBJAE4ARwAgAEwASQBOAEsAIABN
AFMARwAAAAAAAAADAEkATQBHAAMASQBNAEcAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD+/wAABAoCAAAAAAAAAAAAAAAAAAAA
AAABAAAA4IWf8vlPaBCrkQgAKyez2TAAAACEAQAAEAAAAAEAAACIAAAAAgAAAJAAAAADAAAA1AAA
AAQAAADgAAAABQAAAOwAAAAHAAAA+AAAAAgAAAAMAQAACQAAABgBAAASAAAAJAEAAAoAAABAAQAA
DAAAAEwBAAANAAAAWAEAAA4AAABkAQAADwAAAGwBAAAQAAAAdAEAABMAAAB8AQAAAgAAAOQEAAAe
AAAAPAAAADI1MEYgICAgIEM3VFUxMDEgSlVOMTkgMTU6NDI6NTQgMDQwMSBJTkZPIElOQ09NSU5H
IExJTksgTVNHAB4AAAABAAAAADUwRh4AAAAEAAAASU1HAB4AAAABAAAAAE1HAB4AAAALAAAATm9y
bWFsLmRvdABUHgAAAAQAAABJTUcAHgAAAAIAAAA2AEcAHgAAABMAAABNaWNyb3NvZnQgV29yZCA4
LjAATkAAAAAApJPWAAAAAEAAAAAAuKmpRrzCAUAAAAAA0hrCSLzCAQMAAAABAAAAAwAAACkBAAAD
AAAAnwYAAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/v8AAAQKAgAAAAAAAAAAAAAAAAAAAAAAAgAAAALV
zdWcLhsQk5cIACss+a5EAAAABdXN1ZwuGxCTlwgAKyz5rmwBAAAoAQAADAAAAAEAAABoAAAADwAA
AHAAAAAFAAAAgAAAAAYAAACIAAAAEQAAAJAAAAAXAAAAmAAAAAsAAACgAAAAEAAAAKgAAAATAAAA
sAAAABYAAAC4AAAADQAAAMAAAAAMAAAACAEAAAIAAADkBAAAHgAAAAYAAAB3aXBybwAgAAMAAAAO
AAAAAwAAAAMAAAADAAAAIQgAAAMAAABqEAgACwAAAAAAAAALAAAAAAAAAAsAAAAAAAAACwAAAAAA
AAAeEAAAAQAAADwAAAAyNTBGICAgICBDN1RVMTAxIEpVTjE5IDE1OjQyOjU0IDA0MDEgSU5GTyBJ
TkNPTUlORyBMSU5LIE1TRwAMEAAAAgAAAB4AAAAGAAAAVGl0bGUAAwAAAAEAAAAAAJgAAAADAAAA
AAAAACAAAAABAAAANgAAAAIAAAA+AAAAAQAAAAIAAAAKAAAAX1BJRF9HVUlEAAIAAADkBAAAQQAA
AE4AAAB7ADYAMwA2ADUAMQBFADAANgAtADIAOAA2ADgALQAxADEARAA3AC0AOABDAEIARAAtADAA
MAAwADAARQAyADAARABDADcARgAzAH0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAEAAAACAAAAAwAAAAQAAAAFAAAABgAAAAcAAAAIAAAACQAAAAoA
AAALAAAADAAAAP7///8OAAAADwAAABAAAAARAAAAEgAAABMAAAAUAAAA/v///xYAAAAXAAAAGAAA
ABkAAAAaAAAAGwAAABwAAAD+////HgAAAB8AAAAgAAAAIQAAACIAAAAjAAAAJAAAAP7////9////
JwAAAP7////+/////v//////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////UgBvAG8AdAAgAEUAbgB0AHIAeQAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABYABQH//////////wMAAAAGCQIAAAAAAMAAAAAAAABG
AAAAACDMrgtHvMIB4A4Y0Ei8wgEpAAAAgAAAAAAAAAAxAFQAYQBiAGwAZQAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADgACAP///////////////wAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA0AAAAAEAAAAAAAAFcAbwByAGQARABv
AGMAdQBtAGUAbgB0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAaAAIB
BQAAAP//////////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAC0YAAAA
AAAABQBTAHUAbQBtAGEAcgB5AEkAbgBmAG8AcgBtAGEAdABpAG8AbgAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAACgAAgECAAAABAAAAP////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAVAAAAABAAAAAAAAAFAEQAbwBjAHUAbQBlAG4AdABTAHUAbQBtAGEAcgB5AEkAbgBmAG8A
cgBtAGEAdABpAG8AbgAAAAAAAAAAAAAAOAACAf///////////////wAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAB0AAAAAEAAAAAAAAAEAQwBvAG0AcABPAGIAagAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAASAAIBAQAAAAYAAAD/////AAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGoAAAAAAAAATwBiAGoAZQBjAHQA
UABvAG8AbAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABYAAQD/
//////////////8AAAAAAAAAAAAAAAAAAAAAAAAAAOAOGNBIvMIB4A4Y0Ei8wgEAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAP///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAJCeQAA6AQDwBwAAAAEAAAD+////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////AQD+/wMKAAD/////BgkCAAAAAADAAAAAAAAARhgAAABNaWNyb3NvZnQg
V29yZCBEb2N1bWVudAAKAAAATVNXb3JkRG9jABAAAABXb3JkLkRvY3VtZW50LjgA9DmycQAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAA=

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



From mailnull@www1.ietf.org  Thu Jan 16 04:10: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 EAA05102
	for <sigtran-archive@odin.ietf.org>; Thu, 16 Jan 2003 04:10:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0G9P9u03903
	for sigtran-archive@odin.ietf.org; Thu, 16 Jan 2003 04:25:09 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G9OMJ03855;
	Thu, 16 Jan 2003 04:24:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G9KjJ03729
	for <sigtran@optimus.ietf.org>; Thu, 16 Jan 2003 04:20:45 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05063
	for <sigtran@ietf.org>; Thu, 16 Jan 2003 04:05:12 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:mV6K/+GJ5ghbzs+n6IAywPEnxekw1xj/@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0G981D11080;
	Thu, 16 Jan 2003 02:08:01 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0G981F30079;
	Thu, 16 Jan 2003 02:08:01 -0700
Date: Thu, 16 Jan 2003 02:08:00 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Somesh <somesh@indts.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>, Vasudeva <vasudeva@indts.com>
Message-ID: <20030116020800.A29760@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Somesh <somesh@indts.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>,
	Vasudeva <vasudeva@indts.com>
References: <F73B646FCC01D5118F530002B32C3372DEE3EC@INDTS_FS>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <F73B646FCC01D5118F530002B32C3372DEE3EC@INDTS_FS>; from somesh@indts.com on Thu, Jan 16, 2003 at 02:19:11PM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: setup message after disconnect
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>

Somesh,

What protocol are you talking about?  Q.931?

--brian

Somesh wrote:                                                                       (Thu, 16 Jan 2003 14:19:11)
> Hi,
> we have a doubt regarding the setup message sent from <MGC> to the
> originator <SG> immediately after receiving disconnect from the originator
> <SG>.
> 
> Description:-
> 
>  In an end to end call <sg1> calls <sg2> through <mgc>.After succesful
> completion of resart sequence and call creation sequence SG1 sends a
> disconnect message with cause value "normal call clearing" ,if at this point
> if an MGC sends Setup message with the same call reference to SG1 should the
> message be ignored or should <SG1> repond with Alerting or should it be
> treated as unexpected message and the call should be torn down.
> 
> Somesh
> 

-- 
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 Jan 16 09: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 JAA11441
	for <sigtran-archive@odin.ietf.org>; Thu, 16 Jan 2003 09:07:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0GEN1924990
	for sigtran-archive@odin.ietf.org; Thu, 16 Jan 2003 09:23:01 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GEMFJ24959;
	Thu, 16 Jan 2003 09:22:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GELlJ24923
	for <sigtran@optimus.ietf.org>; Thu, 16 Jan 2003 09:21:47 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11419
	for <sigtran@ietf.org>; Thu, 16 Jan 2003 09:06:08 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0GE9Nbg015028;
	Thu, 16 Jan 2003 08:09:24 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id SAA05661; Thu, 16 Jan 2003 18:38:31 -0500 (GMT)
Message-ID: <3E26BD52.E852AC71@axes-mach01.usa.alcatel.com>
Date: Thu, 16 Jan 2003 19:40:28 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: sigtran@ietf.org
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] [M3UA] ASP Auditing
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

Brian,

In Section 4.5.3 ASP Auditing,

..... The SGP SHOULD respond to a DAUD message with the MTP3
availability/congested status of the routeset associated with each
Destination Point Code(s) in the DAUD message.....


Does it mean that Destination Point Code(s) status be maintained by M3UA
of SGP?.


--Srini

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



From mailnull@www1.ietf.org  Thu Jan 16 09:19: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 JAA11726
	for <sigtran-archive@odin.ietf.org>; Thu, 16 Jan 2003 09:19:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0GEYm025557
	for sigtran-archive@odin.ietf.org; Thu, 16 Jan 2003 09:34:48 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GEYAJ25510;
	Thu, 16 Jan 2003 09:34:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GEXwJ25453
	for <sigtran@optimus.ietf.org>; Thu, 16 Jan 2003 09:33:58 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11701
	for <sigtran@ietf.org>; Thu, 16 Jan 2003 09:18:19 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:BomgQ2b39br0/AkqwmNh6kPj2tI6R1xG@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0GELfD15760;
	Thu, 16 Jan 2003 07:21:41 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0GELeM04454;
	Thu, 16 Jan 2003 07:21:40 -0700
Date: Thu, 16 Jan 2003 07:21:40 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Message-ID: <20030116072140.A4231@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <3E26BD52.E852AC71@axes-mach01.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: <3E26BD52.E852AC71@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Thu, Jan 16, 2003 at 07:40:28PM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: [M3UA] ASP Auditing
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>

Srini,

ksrinivas wrote:                                                                 (Thu, 16 Jan 2003 19:40:28)
> Brian,
> 
> In Section 4.5.3 ASP Auditing,
> 
> ..... The SGP SHOULD respond to a DAUD message with the MTP3
> availability/congested status of the routeset associated with each
> Destination Point Code(s) in the DAUD message.....
> 
> 
> Does it mean that Destination Point Code(s) status be maintained by M3UA
> of SGP?.

Pretty much.

--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  Thu Jan 16 09:25: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 JAA11869
	for <sigtran-archive@odin.ietf.org>; Thu, 16 Jan 2003 09:25:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0GEerM26562
	for sigtran-archive@odin.ietf.org; Thu, 16 Jan 2003 09:40:53 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GEe6J26454;
	Thu, 16 Jan 2003 09:40:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GEd3J26381
	for <sigtran@optimus.ietf.org>; Thu, 16 Jan 2003 09:39:03 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11800
	for <sigtran@ietf.org>; Thu, 16 Jan 2003 09:23:24 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0GEQhbg017741;
	Thu, 16 Jan 2003 08:26:44 -0600 (CST)
Received: from axsppc67 by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id SAA05950; Thu, 16 Jan 2003 18:55:31 -0500 (GMT)
Message-ID: <00fe01c2bd6b$589a4210$7501ff0a@axsppc67>
From: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
To: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>, <bidulock@openss7.org>
Cc: <sigtran@ietf.org>
References: <3E26BD52.E852AC71@axes-mach01.usa.alcatel.com>
Subject: Re: [Sigtran] [M3UA] ASP Auditing
Date: Thu, 16 Jan 2003 19:56:50 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="x-user-defined"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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

Srini,

At SGP MTP3 layer should maintain status of all destinations.  M3UA shall
get the status of a destination from NIF and send to ASP.  But I am not
finding any primitive to request destination status from NIF.

IMO, M3UA should not maintain destination status as it will be redundant.

Thanks
Chak

----- Original Message -----
From: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
To: <bidulock@openss7.org>
Cc: <sigtran@ietf.org>
Sent: Thursday, January 16, 2003 7:40 PM
Subject: [Sigtran] [M3UA] ASP Auditing


> Brian,
>
> In Section 4.5.3 ASP Auditing,
>
> ..... The SGP SHOULD respond to a DAUD message with the MTP3
> availability/congested status of the routeset associated with each
> Destination Point Code(s) in the DAUD message.....
>
>
> Does it mean that Destination Point Code(s) status be maintained by M3UA
> of SGP?.
>
>
> --Srini
>
> _______________________________________________
> 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 Jan 16 17:13: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 RAA25259
	for <sigtran-archive@odin.ietf.org>; Thu, 16 Jan 2003 17:13:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0GMSlP28592
	for sigtran-archive@odin.ietf.org; Thu, 16 Jan 2003 17:28:47 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GMS4J28571;
	Thu, 16 Jan 2003 17:28:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G92YJ02414
	for <sigtran@optimus.ietf.org>; Thu, 16 Jan 2003 04:02:34 -0500
Received: from telesoft.indts.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04936
	for <sigtran@ietf.org>; Thu, 16 Jan 2003 03:46:56 -0500 (EST)
Received: from indts_fs.indts.com (indts_fs.indts.com [201.64.64.29])
	by telesoft.indts.com (8.11.6/8.11.6) with ESMTP id h0G8gVm26952;
	Thu, 16 Jan 2003 14:12:42 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <CZBA6K3B>; Thu, 16 Jan 2003 14:19:12 +0530
Message-ID: <F73B646FCC01D5118F530002B32C3372DEE3EC@INDTS_FS>
From: Somesh <somesh@indts.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>,
        "'sigtran@ietf.org'"
	 <sigtran@ietf.org>
Cc: Vasudeva <vasudeva@indts.com>
Date: Thu, 16 Jan 2003 14:19:11 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] setup message after disconnect
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,
we have a doubt regarding the setup message sent from <MGC> to the
originator <SG> immediately after receiving disconnect from the originator
<SG>.

Description:-

 In an end to end call <sg1> calls <sg2> through <mgc>.After succesful
completion of resart sequence and call creation sequence SG1 sends a
disconnect message with cause value "normal call clearing" ,if at this point
if an MGC sends Setup message with the same call reference to SG1 should the
message be ignored or should <SG1> repond with Alerting or should it be
treated as unexpected message and the call should be torn down.

Somesh


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



From mailnull@www1.ietf.org  Thu Jan 16 18:06: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 SAA26186
	for <sigtran-archive@odin.ietf.org>; Thu, 16 Jan 2003 18:06:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0GNLqH32011
	for sigtran-archive@odin.ietf.org; Thu, 16 Jan 2003 18:21:52 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GNLAJ31987;
	Thu, 16 Jan 2003 18:21:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GNKYJ31961
	for <sigtran@optimus.ietf.org>; Thu, 16 Jan 2003 18:20:34 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26162
	for <sigtran@ietf.org>; Thu, 16 Jan 2003 18:04:45 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0GN85BS011139;
	Thu, 16 Jan 2003 17:08:05 -0600 (CST)
Message-ID: <3E273B55.ED673C7A@alcatel.com>
Date: Thu, 16 Jan 2003 17:08:05 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: sigtran@ietf.org
CC: bidulock@openss7.org
Subject: Re: [Sigtran] Re: Suggested New Test Cases for 
 draft-bidulock-sigtran-m2pa-test-02.ps
References: <OFDF94CA83.3F3A9FF3-ON85256C39.00461160@nc.tekelec.com> <20020919072404.A17957@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

Brian,

I think there was a concern about what would happen if only one message
was sent, and it got lost. 

Do you think we should not send these messages periodically?

   LS Ready
   LS Busy
   LS PO

tomG.


"Brian F. G. Bidulock" wrote long ago on 09/19/02:
> 
> Jeffrey,
> 
> I don't enjoy burning timers for nothing.  It is easy enough
> (even trivial) for an implementation to ignore the repetition,
> but generating and interval requires a timer and introduces
> additional fodder for race conditions and barriers to scale.
> Unless someone can come up with a good reason, the intervals
> should be struck.
> 
> Can you remember why they were added, Tom?
> 
> --brian
> 
> jeffrey.craig@tekelec.com wrote:               (Thu, 19 Sep 2002 08:47:34)
> >
> > Hello Brian,
> >
> > >My preference is that they are struck.  The reason for striking
> > >is that sending these at an interval serves no purpose whatsoever
> > >that I can think of.  Can you think of a reason to send any of
> > >these periodically?  This is SCTP after all and not a lossy link.
> >
> > I can think of no reason to periodically send these messages.
> > My preference for keeping them has to with the fact that I've
> > implemented them. (Yes, I know, not a good reason.... I'm human).
> >
> > Regards,
> >
> > Jeff
> >
> 
> --
> 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 USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 16 18:43: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 SAA26696
	for <sigtran-archive@odin.ietf.org>; Thu, 16 Jan 2003 18:43:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0GNwUf01492
	for sigtran-archive@odin.ietf.org; Thu, 16 Jan 2003 18:58:30 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GNvpJ01465;
	Thu, 16 Jan 2003 18:57:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GNupJ01417
	for <sigtran@optimus.ietf.org>; Thu, 16 Jan 2003 18:56:51 -0500
Received: from revere.sonusnet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26627
	for <sigtran@ietf.org>; Thu, 16 Jan 2003 18:41:02 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3.sonusnet.com [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h0GNhl129687
	for <sigtran@ietf.org>; Thu, 16 Jan 2003 18:43:47 -0500 (EST)
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19)
	id <Y68HT1NC>; Thu, 16 Jan 2003 18:44:22 -0500
Message-ID: <4CF48720B6E9D4118D040060CF2074E9072F6BE6@sonusdc3.sonusnet.com>
From: "Wung, Joseph" <JWung@sonusnet.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA default AS
Date: Thu, 16 Jan 2003 18:44:21 -0500
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>

All,

> M3UA section 1.4.2.4 says
> 
> 	"When there is no matching Routing Key entry for an
> 	incoming SS7 message, a default treatment MAY be
> 	specified.  Possible solutions are to provide a default
> 	AS at the SGP that directs all unallocated traffic to a
> 	(set of) default ASP(s), or to drop the message and
> 	provide a notification to layer management."
> 

Can someone tell me how this default AS is provided in the
system where dynamic registrations are used?  Normally,
an AS is tied to an SCTP association over which the ASP
registers with the AS.  Without a procedure, how could this
coupling between the default AS and the "default"
SCTP association be established?

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



From mailnull@www1.ietf.org  Thu Jan 16 21:28: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 VAA29903
	for <sigtran-archive@odin.ietf.org>; Thu, 16 Jan 2003 21:28:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0H2iAc12064
	for sigtran-archive@odin.ietf.org; Thu, 16 Jan 2003 21:44:10 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0H2hSJ12040;
	Thu, 16 Jan 2003 21:43:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0H2goJ12010
	for <sigtran@optimus.ietf.org>; Thu, 16 Jan 2003 21:42:50 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29897
	for <sigtran@ietf.org>; Thu, 16 Jan 2003 21:26:55 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:uX+7t3H+yaHF8L1leQIQsL4fRxltm9k8@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0H2UHD26392;
	Thu, 16 Jan 2003 19:30:17 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0H2UH022869;
	Thu, 16 Jan 2003 19:30:17 -0700
Date: Thu, 16 Jan 2003 19:30:17 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Wung, Joseph" <JWung@sonusnet.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA default AS
Message-ID: <20030116193017.C22477@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Wung, Joseph" <JWung@sonusnet.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <4CF48720B6E9D4118D040060CF2074E9072F6BE6@sonusdc3.sonusnet.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: <4CF48720B6E9D4118D040060CF2074E9072F6BE6@sonusdc3.sonusnet.com>; from JWung@sonusnet.com on Thu, Jan 16, 2003 at 06:44:21PM -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>

Wung,,

Wung, Joseph wrote:                                                                  (Thu, 16 Jan 2003 18:44:21)
> All,
> 
> > M3UA section 1.4.2.4 says
> > 
> > 	"When there is no matching Routing Key entry for an
> > 	incoming SS7 message, a default treatment MAY be
> > 	specified.  Possible solutions are to provide a default
> > 	AS at the SGP that directs all unallocated traffic to a
> > 	(set of) default ASP(s), or to drop the message and
> > 	provide a notification to layer management."
> > 
> 
> Can someone tell me how this default AS is provided in the
> system where dynamic registrations are used?  Normally,
> an AS is tied to an SCTP association over which the ASP
> registers with the AS.  Without a procedure, how could this
> coupling between the default AS and the "default"
> SCTP association be established?

ASP Id ?

--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  Thu Jan 16 23:18: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 XAA02034
	for <sigtran-archive@odin.ietf.org>; Thu, 16 Jan 2003 23:18:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0H4XV617377
	for sigtran-archive@odin.ietf.org; Thu, 16 Jan 2003 23:33:31 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0H4WiJ17352;
	Thu, 16 Jan 2003 23:32:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0H4V8J17289
	for <sigtran@optimus.ietf.org>; Thu, 16 Jan 2003 23:31:08 -0500
Received: from india.mercurykr.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01978
	for <sigtran@ietf.org>; Thu, 16 Jan 2003 23:15:07 -0500 (EST)
Received: from srivatsp (mercury-225-143-del.mercurykr.com [203.196.143.225] (may be forged))
	by india.mercurykr.com (8.11.2/8.11.2) with SMTP id h0H9Oit01996
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 14:54:47 +0530
Message-Id: <200301170924.h0H9Oit01996@india.mercurykr.com>
Date: Fri, 17 Jan 2003 9:47:2 +0500
From: "Srivats P." <srivats@india.mercurykr.com>
Reply-To: srivatsp@email.com
To: sigtran <sigtran@ietf.org>
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
Subject: [Sigtran] SCTP checksum
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,

What is the status of the checksum issue for SCTP ?
Is it Adler32 or CRC32 ? It is Adler32 in the RFC,
and the IG doesn't mention it. Does it remain Adler32
in that case ?

I realize this is not the correct list for this question,
but I don't know which working group is incharge of SCTP these
days (I recall it having moved from tsvwg to some place else).

Regards,
Srivats P.

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



From mailnull@www1.ietf.org  Thu Jan 16 23:45: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 XAA02458
	for <sigtran-archive@odin.ietf.org>; Thu, 16 Jan 2003 23:45:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0H510b19100
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 00:01:00 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0H50BJ19054;
	Fri, 17 Jan 2003 00:00:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0H4xDJ18959
	for <sigtran@optimus.ietf.org>; Thu, 16 Jan 2003 23:59:13 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02375
	for <sigtran@ietf.org>; Thu, 16 Jan 2003 23:43:15 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:PVs8dq1/J/EqyfKUKzHGu9YIzq2mKD4N@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0H4kcD28028;
	Thu, 16 Jan 2003 21:46:38 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0H4kcY25035;
	Thu, 16 Jan 2003 21:46:38 -0700
Date: Thu, 16 Jan 2003 21:46:38 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Srivats P." <srivats@india.mercurykr.com>
Cc: sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] SCTP checksum
Message-ID: <20030116214638.A24922@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Srivats P." <srivats@india.mercurykr.com>,
	sigtran <sigtran@ietf.org>
References: <200301170924.h0H9Oit01996@india.mercurykr.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: <200301170924.h0H9Oit01996@india.mercurykr.com>; from srivats@india.mercurykr.com on Fri, Jan 17, 2003 at 09:47:02AM +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>

Srivats,

RFC3309 updates the checksum to CRC32.  Adler32 is deprecated.

--brian

Srivats P. wrote:                                                                  (Fri, 17 Jan 2003 09:47:02)
> Hi,
> 
> What is the status of the checksum issue for SCTP ?
> Is it Adler32 or CRC32 ? It is Adler32 in the RFC,
> and the IG doesn't mention it. Does it remain Adler32
> in that case ?
> 
> I realize this is not the correct list for this question,
> but I don't know which working group is incharge of SCTP these
> days (I recall it having moved from tsvwg to some place else).
> 
> Regards,
> Srivats P.
> 
> _______________________________________________
> 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 Jan 17 01:12: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 BAA03418
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 01:12:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0H6RmX23756
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 01:27:48 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0H6RbJ23735;
	Fri, 17 Jan 2003 01:27:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0H6MTJ23534
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 01:22:29 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03332
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 01:06:30 -0500 (EST)
Subject: Re: [Sigtran] M3UA default AS
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFC7A51F6B.18E337C6-ONC2256CB1.0020C446@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 17 Jan 2003 08:06:28 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/17/2003
 08:06:33 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>


Joe,



Wung,,

Wung, Joseph wrote:
(Thu, 16 Jan 2003 18:44:21)
> All,
>
> > M3UA section 1.4.2.4 says
> >
> >        "When there is no matching Routing Key entry for an
> >        incoming SS7 message, a default treatment MAY be
> >        specified.  Possible solutions are to provide a default
> >        AS at the SGP that directs all unallocated traffic to a
> >        (set of) default ASP(s), or to drop the message and
> >        provide a notification to layer management."
> >
>
> Can someone tell me how this default AS is provided in the
> system where dynamic registrations are used?  Normally,
> an AS is tied to an SCTP association over which the ASP
> registers with the AS.  Without a procedure, how could this
> coupling between the default AS and the "default"
> SCTP association be established?

ASP Id ?
[TOLGA]If the goal is also to provide dynamic behaviour for addressing of
ASPs I also think AspId should be used. But for the case where dynamic
behaviour is required only for traffic ranges, one can also use static
addressing for default ASP.






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



From mailnull@www1.ietf.org  Fri Jan 17 01:20: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 BAA03561
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 01:20:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0H6ZlT24074
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 01:35:47 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0H6ZFJ24041;
	Fri, 17 Jan 2003 01:35:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0H6YCJ23985
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 01:34:12 -0500
Received: from telesoft.indts.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03534
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 01:18:07 -0500 (EST)
Received: from indts_fs.indts.com (indts_fs.indts.com [201.64.64.29])
	by telesoft.indts.com (8.11.6/8.11.6) with ESMTP id h0H6E5m09445
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 11:44:28 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <CZBA6LX8>; Fri, 17 Jan 2003 11:50:52 +0530
Message-ID: <F73B646FCC01D5118F530002B32C3372DB306F@INDTS_FS>
From: Latha <latha@indts.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Date: Fri, 17 Jan 2003 11:50:51 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] Release Complete Cause Indicators in ISUP
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 am not sure if this is the forum to discuss any clarifications on ISUP,
please let me know if my question is more relevant on any other mailing
lists. 
Anyways, here;s the concern:
Looking at the standard Q.763- Table 33, the Release message has a mandatory
variable length parameter Cause Indicators
(referred in 3.12 in the same doc) with length defined as 3-?
But when it comes to Release Complete Message (Table 34), the Cause
Indicators are
optional and with length defined as 5-6. Whenever Cause Indicators occurs as
Optional the length is shown to be 4 - ? (Call Progress and Address
Complete)
because it includes the parameter tag and length and the cause indicators
has
mandatory 2 bytes. So how is it defined as 5-6 bytes for Release Complete?
Is this right or an error? If this is right, what is the explanation for the
same?
thanks for your response
latha
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jan 17 07:30: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 HAA19678
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 07:30:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HCkWr26775
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 07:46:32 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HCjkJ26694;
	Fri, 17 Jan 2003 07:45:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HCe8J26441
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 07:40:09 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19525;
	Fri, 17 Jan 2003 07:24:03 -0500 (EST)
Message-Id: <200301171224.HAA19525@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: Fri, 17 Jan 2003 07:24:03 -0500
Subject: [Sigtran] I-D ACTION:draft-ietf-sigtran-dua-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		: DPNSS/DASS 2 extensions to the IUA protocol
	Author(s)	: A. Vydyam, K. Morneault
	Filename	: draft-ietf-sigtran-dua-05.txt
	Pages		: 10
	Date		: 2003-1-16
	
This document defines a mechanism for backhauling Digital Private 
Network Signaling System 1 (DPNSS 1) and Digital Access Signaling
System 2 (DASS 2) messages over IP by extending the ISDN User 
Adaptation (IUA) Layer Protocol defined in RFC 3057.  DPNSS 1, 
specified in BTNR 188, is used to interconnect Private Branch 
Exchanges (PBX) in a private network and DASS 2, specified in 
BTNR 190, is used to connect PBXs to the PSTN.  This document aims 
to become an Appendix to IUA and to be the base for a DPNSS 1/
DASS 2 User Adaptation (DUA) implementation.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sigtran-dua-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-dua-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-dua-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-1-16145729.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--


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



From mailnull@www1.ietf.org  Fri Jan 17 07:32: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 HAA19757
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 07:32:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HCmIr26901
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 07:48:18 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HCm4J26888;
	Fri, 17 Jan 2003 07:48:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HClrJ26869
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 07:47:53 -0500
Received: from india.mercurykr.com (mercury-251-143-del.mercurykr.com [203.196.143.251] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19732
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 07:31:46 -0500 (EST)
Received: from srivatsp (mercury-225-143-del.mercurykr.com [203.196.143.225] (may be forged))
	by india.mercurykr.com (8.11.2/8.11.2) with SMTP id h0HHcot08422
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 23:08:53 +0530
Message-Id: <200301171738.h0HHcot08422@india.mercurykr.com>
Date: Fri, 17 Jan 2003 18:1:1 +0500
From: "Srivats P." <srivats@india.mercurykr.com>
Reply-To: srivatsp@email.com
To: sigtran <sigtran@ietf.org>
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
Subject: [Sigtran] OPC List renamed as DPC List
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,

I need a clarification regarding the "OPC List in Registration
Request Message" issue in the M3UA IG.

<quote>
    ---------
    New text: (Section 3.6.1)
    ---------

    DPC List:

    The Destination Point Code List parameter contains one or more SS7
    DPC entries, and its format is the same as the Destination Point Code
    parameter. Multiple DPC values will only be valid in the case of
    Alias Point Code configuration. The absence of the DPC List parameter
    in the Routing Key indicates the use of the DPC value as the only
    posible DPC for the AS.

 3.8.3 Solution description

    Including the scenario where this parameter is used (Alias point code
    configurations), the problem is solved. The parameter name has also
    be changed to "Destination" since it is the way that the SG sees it.

</quote>

the OPC List has been renamed as DPC List. So now we have a DPC Parameter
(the point code of the AS which is being registered) and a DPC List (
earlier OPC List) which is a list of SS7 Point Codes from which the AS
can receive messages. Right ?

Say, SP A in the SS7 network has alias point codes 1-1-1 and 1-1-2.
ASP X registers an AS (DPC = 3-3-3 and DPC List = 1-1-1, 1-1-2). Now if the
SG receives any message with the DPC value as 3-3-3 in the Routing Label,
it will check the OPC value in the Routing Label to see if it is either
1-1-1 or 1-1-2, before sending the message to the AS. Right ?

What happens if the DPC List (1-1-1, 1-1-2) was not included in the RK ?
According to the IG -

"The absence of the DPC List parameter in the Routing Key indicates the 
use of the DPC value as the only posible DPC for the AS."
          ^^^^^^^^^^^

Which "DPC value" is being referred to here ? 3-3-3 ? But wasn't it the
same case even when the "DPC List (formerly OPC List)" was included ?
The ONLY point code of the AS was still 3-3-3. What am I misreading here ?

Regards,
Srivats

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



From mailnull@www1.ietf.org  Fri Jan 17 07:46: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 HAA20574
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 07:46:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HD1e827744
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 08:01:40 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HD18J27703;
	Fri, 17 Jan 2003 08:01:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HD0WJ27656
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 08:00:32 -0500
Received: from domino2.nc.tekelec.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20440
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 07:44:25 -0500 (EST)
From: jeffrey.craig@tekelec.com
Received: from domino4.nc.tekelec.com ([198.89.40.9])
          by domino2.nc.tekelec.com (Lotus Domino Release 5.0.7)
          with ESMTP id 2003011707414418:21867 ;
          Fri, 17 Jan 2003 07:41:44 -0500 
Subject: Re: [Sigtran] Re: Suggested New Test Cases for draft-bidulock-sigtran-m2pa-test-02.ps
To: Tom George <Tom.George@alcatel.com>
Cc: sigtran@ietf.org, bidulock@openss7.org
X-Mailer: Lotus Notes Release 5.0.7  March 21, 2001
Message-ID: <OF1C115F4D.F53C0160-ON85256CB1.00451C6F@nc.tekelec.com>
Date: Fri, 17 Jan 2003 07:43:35 -0500
MIME-Version: 1.0
X-MIMETrack: Serialize by Router on Domino4/Raleigh/TEKELEC(Release 5.0.10 |March 22, 2002) at
 01/17/2003 07:43:35 AM,
	Itemize by SMTP Server on Domino2/Raleigh/TEKELEC(Release 5.0.7 |March 21, 2001) at
 01/17/2003 07:41:44 AM,
	Serialize by Router on Domino2/Raleigh/TEKELEC(Release 5.0.7 |March 21, 2001) at
 01/17/2003 07:41:52 AM,
	Serialize complete at 01/17/2003 07:41:52 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,

After further consideration of the issue, I have concluded that the
repeated
sending of LSR, LSB, LSPO is useful for diagnostics and measurements.
I don't see how these messages could be lost if the association remains
established, but nevertheless, I now think that the repetition is useful.

Regards,

Jeff





Tom George <Tom.George@alcatel.com>@ietf.org on 01/16/2003 06:08:05 PM

Sent by:    sigtran-admin@ietf.org


To:    sigtran@ietf.org
cc:    bidulock@openss7.org
Subject:    Re: [Sigtran] Re: Suggested New Test Cases for
       draft-bidulock-sigtran-m2pa-test-02.ps


Brian,

I think there was a concern about what would happen if only one message
was sent, and it got lost.

Do you think we should not send these messages periodically?

   LS Ready
   LS Busy
   LS PO

tomG.


"Brian F. G. Bidulock" wrote long ago on 09/19/02:
>
> Jeffrey,
>
> I don't enjoy burning timers for nothing.  It is easy enough
> (even trivial) for an implementation to ignore the repetition,
> but generating and interval requires a timer and introduces
> additional fodder for race conditions and barriers to scale.
> Unless someone can come up with a good reason, the intervals
> should be struck.
>
> Can you remember why they were added, Tom?
>
> --brian
>
> jeffrey.craig@tekelec.com wrote:               (Thu, 19 Sep 2002
08:47:34)
> >
> > Hello Brian,
> >
> > >My preference is that they are struck.  The reason for striking
> > >is that sending these at an interval serves no purpose whatsoever
> > >that I can think of.  Can you think of a reason to send any of
> > >these periodically?  This is SCTP after all and not a lossy link.
> >
> > I can think of no reason to periodically send these messages.
> > My preference for keeping them has to with the fact that I've
> > implemented them. (Yes, I know, not a good reason.... I'm human).
> >
> > Regards,
> >
> > Jeff
> >
>
> --
> 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 USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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  Fri Jan 17 07: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 HAA20653
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 07:46:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HD2Ep27815
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 08:02:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HD23J27789;
	Fri, 17 Jan 2003 08:02:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HD1KJ27720
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 08:01:20 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20483
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 07:45:14 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:fPO2mtRXK3z8n29Kor1gnJfyeJfg2H77@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0HClmD01731;
	Fri, 17 Jan 2003 05:47:48 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0HClmD02059;
	Fri, 17 Jan 2003 05:47:48 -0700
Date: Fri, 17 Jan 2003 05:47:47 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: sigtran@ietf.org, Ken Morneault <kmorneau@cisco.com>
Subject: Re: [Sigtran] I-D ACTION:draft-ietf-sigtran-dua-05.txt
Message-ID: <20030117054747.A1767@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: sigtran@ietf.org, Ken Morneault <kmorneau@cisco.com>
References: <200301171224.HAA19525@ietf.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: <200301171224.HAA19525@ietf.org>; from Internet-Drafts@ietf.org on Fri, Jan 17, 2003 at 07:24:03AM -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>

Ken,

Nit:

In changing the date on the document, you inadvertently changed the
data on referece [4].

--brian

@@ -546,7 +580,7 @@
    Digital Access Signaling System No 2
 
    [4]  IUA (RFC3057) Implementors Guide, draft-ietf-sigtran-iua-imp-
-    guide-01.txt, Oct 2002
+    guide-01.txt, Jan 2003
 
 7.2  Informative References
 

-- 
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 Jan 17 07:50: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 HAA20762
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 07:50:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HD5fJ27998
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 08:05:41 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HD54J27961;
	Fri, 17 Jan 2003 08:05:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HD4gJ27921
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 08:04:42 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20719
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 07:48:35 -0500 (EST)
Subject: Re: [Sigtran] OPC List renamed as DPC List
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF5FF49888.9010AAC9-ONC2256CB1.0045D832@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Fri, 17 Jan 2003 14:48:32 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/17/2003
 02:48:38 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>


Srivats,
--- "Srivats P." <srivats@india.mercurykr.com> wrote:
> Hi,
>
> I need a clarification regarding the "OPC List in
> Registration
> Request Message" issue in the M3UA IG.
>
> <quote>
>     ---------
>     New text: (Section 3.6.1)
>     ---------
>
>     DPC List:
>
>     The Destination Point Code List parameter
> contains one or more SS7
>     DPC entries, and its format is the same as the
> Destination Point Code
>     parameter. Multiple DPC values will only be
> valid in the case of
>     Alias Point Code configuration. The absence of
> the DPC List parameter
>     in the Routing Key indicates the use of the DPC
> value as the only
>     posible DPC for the AS.
>
>  3.8.3 Solution description
>
>     Including the scenario where this parameter is
> used (Alias point code
>     configurations), the problem is solved. The
> parameter name has also
>     be changed to "Destination" since it is the way
> that the SG sees it.
>
> </quote>
>
> the OPC List has been renamed as DPC List. So now we
> have a DPC Parameter
> (the point code of the AS which is being registered)
> and a DPC List (
> earlier OPC List) which is a list of SS7 Point Codes
> from which the AS
> can receive messages. Right ?
[TOLGA] No, OPC list is not renamed. It is still there. There were
questions why multiple DPCs are allowed for a RK, and for that a
clarification has been added to IG. But the initial version had a typo
where it was referring to OPC instead of DPC. Still it seems a correction
is necessary. I think it should refer to multiple DPC values instead of a
DPC list, because this is the structure of RK parameter.
>
> Say, SP A in the SS7 network has alias point codes
> 1-1-1 and 1-1-2.
> ASP X registers an AS (DPC = 3-3-3 and DPC List =
> 1-1-1, 1-1-2). Now if the
> SG receives any message with the DPC value as 3-3-3
> in the Routing Label,
> it will check the OPC value in the Routing Label to
> see if it is either
> 1-1-1 or 1-1-2, before sending the message to the
> AS. Right ?
>
> What happens if the DPC List (1-1-1, 1-1-2) was not
> included in the RK ?
> According to the IG -
>
> "The absence of the DPC List parameter in the
> Routing Key indicates the
> use of the DPC value as the only posible DPC for the
> AS."
>           ^^^^^^^^^^^
>
> Which "DPC value" is being referred to here ? 3-3-3
> ? But wasn't it the
> same case even when the "DPC List (formerly OPC
> List)" was included ?
> The ONLY point code of the AS was still 3-3-3. What
> am I misreading here ?

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



From mailnull@www1.ietf.org  Fri Jan 17 07:54:02 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 HAA20868
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 07:54:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HD9b328875
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 08:09:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HD95J28849;
	Fri, 17 Jan 2003 08:09:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HD8jJ28826
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 08:08:45 -0500
Received: from india.mercurykr.com (mercury-251-143-del.mercurykr.com [203.196.143.251] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20824
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 07:52:37 -0500 (EST)
Received: from srivatsp (mercury-225-143-del.mercurykr.com [203.196.143.225] (may be forged))
	by india.mercurykr.com (8.11.2/8.11.2) with SMTP id h0HHxVt08542
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 23:29:38 +0530
Message-Id: <200301171759.h0HHxVt08542@india.mercurykr.com>
Date: Fri, 17 Jan 2003 18:21:41 +0500
From: "Srivats P." <srivats@india.mercurykr.com>
Reply-To: srivatsp@email.com
To: sigtran <sigtran@ietf.org>
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
Subject: [Sigtran] M3UA IG: Response to an ASPIA msg
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,

The "Response to an ASPIA message" issue in the M3UA IG
states that -

<quote>
    ---------
    New text: (Section 4.5.3)
    ---------

    When an ASP wishes to withdraw from receiving traffic within an AS,or
    the ASP wants to initiate the process of activation, the ASP sends an
    ASP Inactive message to the SGP or IPSP.

    An ASP Inactive message MUST be always responded by the peer
    (although other messages may be sent in the middle):
       - If the corresponding RK is registered (statically or
          dynamically), the peer should respond with an ASP Inactive Ack
          message.
       -           If the RK is not registered, or the RC information is not valid,
          the peer must respond with an ERROR message with Error Code =
          "Invalid Routing Context".
       - If the RC is missing and its specification is needed according
          to the used configuration, the peer must respond with an ERROR
          message with Error Code = "No Configured AS for ASP".
</quote>

I couldn't quite understand what is meant by "If the RC is missing and its
specification is needed according to the used configuration" - does it mean
that the missing RC indicates "all AS served by ASP" and if there is no
such AS for the said ASP, it sends ERROR("No configured AS for ASP") ?

Regards,
Srivats P.

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



From mailnull@www1.ietf.org  Fri Jan 17 07:56: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 HAA20964
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 07:56:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HDCNv29014
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 08:12:23 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HDC9J28982;
	Fri, 17 Jan 2003 08:12:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HDBOJ28947
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 08:11:24 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20915
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 07:55:18 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:dIrBKVNUY4UlXvRSHdjUAlhFHNkqRnaG@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0HCweD01859;
	Fri, 17 Jan 2003 05:58:40 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0HCweV02269;
	Fri, 17 Jan 2003 05:58:40 -0700
Date: Fri, 17 Jan 2003 05:58:39 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Srivats P." <srivats@india.mercurykr.com>
Cc: sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] OPC List renamed as DPC List
Message-ID: <20030117055839.B1767@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Srivats P." <srivats@india.mercurykr.com>,
	sigtran <sigtran@ietf.org>
References: <200301171738.h0HHcot08422@india.mercurykr.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: <200301171738.h0HHcot08422@india.mercurykr.com>; from srivats@india.mercurykr.com on Fri, Jan 17, 2003 at 06:01:01PM +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>

Srivats,

Section 3.8 of the IG is absurd.

It is impossible to specify the OPC without the OPC List parameter.

Alias point codes are handled by repeating the DPC and associated
routing key parameters again in the list per:

      Note: The Destination Point Code, Service Indicators, Originating
      Point Code List and Circuit Range List parameters MAY be repeated
      as a grouping within the Routing Key parameter, in the structure
      shown above.

Section 3.8 of the IG should be struck.

--brian


Srivats P. wrote:                                                                  (Fri, 17 Jan 2003 18:01:01)
> Hi,
> 
> I need a clarification regarding the "OPC List in Registration
> Request Message" issue in the M3UA IG.
> 
> <quote>
>     ---------
>     New text: (Section 3.6.1)
>     ---------
> 
>     DPC List:
> 
>     The Destination Point Code List parameter contains one or more SS7
>     DPC entries, and its format is the same as the Destination Point Code
>     parameter. Multiple DPC values will only be valid in the case of
>     Alias Point Code configuration. The absence of the DPC List parameter
>     in the Routing Key indicates the use of the DPC value as the only
>     posible DPC for the AS.
> 
>  3.8.3 Solution description
> 
>     Including the scenario where this parameter is used (Alias point code
>     configurations), the problem is solved. The parameter name has also
>     be changed to "Destination" since it is the way that the SG sees it.
> 
> </quote>
> 
> the OPC List has been renamed as DPC List. So now we have a DPC Parameter
> (the point code of the AS which is being registered) and a DPC List (
> earlier OPC List) which is a list of SS7 Point Codes from which the AS
> can receive messages. Right ?
> 
> Say, SP A in the SS7 network has alias point codes 1-1-1 and 1-1-2.
> ASP X registers an AS (DPC = 3-3-3 and DPC List = 1-1-1, 1-1-2). Now if the
> SG receives any message with the DPC value as 3-3-3 in the Routing Label,
> it will check the OPC value in the Routing Label to see if it is either
> 1-1-1 or 1-1-2, before sending the message to the AS. Right ?
> 
> What happens if the DPC List (1-1-1, 1-1-2) was not included in the RK ?
> According to the IG -
> 
> "The absence of the DPC List parameter in the Routing Key indicates the 
> use of the DPC value as the only posible DPC for the AS."
>           ^^^^^^^^^^^
> 
> Which "DPC value" is being referred to here ? 3-3-3 ? But wasn't it the
> same case even when the "DPC List (formerly OPC List)" was included ?
> The ONLY point code of the AS was still 3-3-3. What am I misreading here ?
> 
> Regards,
> Srivats
> 
> _______________________________________________
> 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 Jan 17 08:02: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 IAA21088
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 08:02:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HDHk529275
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 08:17:46 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HDH8J29250;
	Fri, 17 Jan 2003 08:17:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HDGRJ29219
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 08:16:27 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21048
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 08:00:20 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Z7OLpXjKpzck5SG9pTL/jTBA9RnLUweF@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0HD3fD02100;
	Fri, 17 Jan 2003 06:03:41 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0HD3fE02482;
	Fri, 17 Jan 2003 06:03:41 -0700
Date: Fri, 17 Jan 2003 06:03:41 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] OPC List renamed as DPC List
Message-ID: <20030117060341.C1767@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF5FF49888.9010AAC9-ONC2256CB1.0045D832@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF5FF49888.9010AAC9-ONC2256CB1.0045D832@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Fri, Jan 17, 2003 at 02:48:32PM +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>

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Fri, 17 Jan 2003 14:48:32)
> 
> Srivats,
> --- "Srivats P." <srivats@india.mercurykr.com> wrote:
> > Hi,
> >
> > I need a clarification regarding the "OPC List in
> > Registration
> > Request Message" issue in the M3UA IG.
> >
> > <quote>
> >     ---------
> >     New text: (Section 3.6.1)
> >     ---------
> >
> >     DPC List:
> >
> >     The Destination Point Code List parameter
> > contains one or more SS7
> >     DPC entries, and its format is the same as the
> > Destination Point Code
> >     parameter. Multiple DPC values will only be
> > valid in the case of
> >     Alias Point Code configuration. The absence of
> > the DPC List parameter
> >     in the Routing Key indicates the use of the DPC
> > value as the only
> >     posible DPC for the AS.
> >
> >  3.8.3 Solution description
> >
> >     Including the scenario where this parameter is
> > used (Alias point code
> >     configurations), the problem is solved. The
> > parameter name has also
> >     be changed to "Destination" since it is the way
> > that the SG sees it.
> >
> > </quote>
> >
> > the OPC List has been renamed as DPC List. So now we
> > have a DPC Parameter
> > (the point code of the AS which is being registered)
> > and a DPC List (
> > earlier OPC List) which is a list of SS7 Point Codes
> > from which the AS
> > can receive messages. Right ?
> [TOLGA] No, OPC list is not renamed. It is still there. There were
> questions why multiple DPCs are allowed for a RK, and for that a
> clarification has been added to IG. But the initial version had a typo
> where it was referring to OPC instead of DPC. Still it seems a correction
> is necessary. I think it should refer to multiple DPC values instead of a
> DPC list, because this is the structure of RK parameter.

It is foolish to use the terms DPC and OPC at all.  DPC only has meaning
in SS7 for a direction of message flow.  Local and Remote would be better
terms that are used throughout the SS7 specifications.

Nevertheless, the IG describes the "DPC List" as  for "alias" point codes
and replaces the OPC List text.  This is absurd.  The section should read
as follows:

 ----------
  Old Text (section 3.6.1)
 ----------

      Note: The Destination Point Code, Service Indicators, Originating
      Point Code List and Circuit Range List parameters MAY be repeated
      as a grouping within the Routing Key parameter, in the structure
      shown above.

 ----------
  New Text (section 3.6.1)
 ----------

      Note: The Destination Point Code, Service Indicators, Originating
      Point Code List and Circuit Range List parameters MAY be repeated
      as a grouping within the Routing Key parameter, in the structure
      shown above.  This could be used where the RK represends multiple
      alias point codes.

--brian

> >
> > Say, SP A in the SS7 network has alias point codes
> > 1-1-1 and 1-1-2.
> > ASP X registers an AS (DPC = 3-3-3 and DPC List =
> > 1-1-1, 1-1-2). Now if the
> > SG receives any message with the DPC value as 3-3-3
> > in the Routing Label,
> > it will check the OPC value in the Routing Label to
> > see if it is either
> > 1-1-1 or 1-1-2, before sending the message to the
> > AS. Right ?
> >
> > What happens if the DPC List (1-1-1, 1-1-2) was not
> > included in the RK ?
> > According to the IG -
> >
> > "The absence of the DPC List parameter in the
> > Routing Key indicates the
> > use of the DPC value as the only posible DPC for the
> > AS."
> >           ^^^^^^^^^^^
> >
> > Which "DPC value" is being referred to here ? 3-3-3
> > ? But wasn't it the
> > same case even when the "DPC List (formerly OPC
> > List)" was included ?
> > The ONLY point code of the AS was still 3-3-3. What
> > am I misreading here ?
> 
> _______________________________________________
> 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 Jan 17 08:06: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 IAA21297
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 08:06:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HDMS629600
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 08:22:28 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HDM8J29585;
	Fri, 17 Jan 2003 08:22:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HDKdJ29474
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 08:20:39 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21137
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 08:04:32 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:sYiUBhKDB5YoVnYb6VyARoJo0tUvCeUR@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0HD7sD02161;
	Fri, 17 Jan 2003 06:07:54 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0HD7s702578;
	Fri, 17 Jan 2003 06:07:54 -0700
Date: Fri, 17 Jan 2003 06:07:53 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: jeffrey.craig@tekelec.com
Cc: Tom George <Tom.George@alcatel.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: Suggested New Test Cases for draft-bidulock-sigtran-m2pa-test-02.ps
Message-ID: <20030117060753.D1767@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: jeffrey.craig@tekelec.com,
	Tom George <Tom.George@alcatel.com>, sigtran@ietf.org
References: <OF1C115F4D.F53C0160-ON85256CB1.00451C6F@nc.tekelec.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: <OF1C115F4D.F53C0160-ON85256CB1.00451C6F@nc.tekelec.com>; from jeffrey.craig@tekelec.com on Fri, Jan 17, 2003 at 07:43:35AM -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>

Jeffrey,

Sure, so allow them to be repeated, but don' require or recommend it.
Use the words MAY or OPTIONAL.

--brian

jeffrey.craig@tekelec.com wrote:                                             (Fri, 17 Jan 2003 07:43:35)
> 
> Hello Tom,
> 
> After further consideration of the issue, I have concluded that the
> repeated
> sending of LSR, LSB, LSPO is useful for diagnostics and measurements.
> I don't see how these messages could be lost if the association remains
> established, but nevertheless, I now think that the repetition is useful.
> 
> Regards,
> 
> Jeff
> 
> 
> 
> 
> 
> Tom George <Tom.George@alcatel.com>@ietf.org on 01/16/2003 06:08:05 PM
> 
> Sent by:    sigtran-admin@ietf.org
> 
> 
> To:    sigtran@ietf.org
> cc:    bidulock@openss7.org
> Subject:    Re: [Sigtran] Re: Suggested New Test Cases for
>        draft-bidulock-sigtran-m2pa-test-02.ps
> 
> 
> Brian,
> 
> I think there was a concern about what would happen if only one message
> was sent, and it got lost.
> 
> Do you think we should not send these messages periodically?
> 
>    LS Ready
>    LS Busy
>    LS PO
> 
> tomG.
> 
> 
> "Brian F. G. Bidulock" wrote long ago on 09/19/02:
> >
> > Jeffrey,
> >
> > I don't enjoy burning timers for nothing.  It is easy enough
> > (even trivial) for an implementation to ignore the repetition,
> > but generating and interval requires a timer and introduces
> > additional fodder for race conditions and barriers to scale.
> > Unless someone can come up with a good reason, the intervals
> > should be struck.
> >
> > Can you remember why they were added, Tom?
> >
> > --brian
> >
> > jeffrey.craig@tekelec.com wrote:               (Thu, 19 Sep 2002
> 08:47:34)
> > >
> > > Hello Brian,
> > >
> > > >My preference is that they are struck.  The reason for striking
> > > >is that sending these at an interval serves no purpose whatsoever
> > > >that I can think of.  Can you think of a reason to send any of
> > > >these periodically?  This is SCTP after all and not a lossy link.
> > >
> > > I can think of no reason to periodically send these messages.
> > > My preference for keeping them has to with the fact that I've
> > > implemented them. (Yes, I know, not a good reason.... I'm human).
> > >
> > > Regards,
> > >
> > > Jeff
> > >
> >
> > --
> > 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 USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
> * 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  Fri Jan 17 08:07: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 IAA21317
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 08:07:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HDNJY29694
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 08:23:19 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HDN5J29679;
	Fri, 17 Jan 2003 08:23:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HDMdJ29629
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 08:22:39 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21287
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 08:06:33 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:3/2uraEop8XIzrY5qeq2v3ouXHCCMUJ8@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0HD9tD02182;
	Fri, 17 Jan 2003 06:09:55 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0HD9tN02605;
	Fri, 17 Jan 2003 06:09:55 -0700
Date: Fri, 17 Jan 2003 06:09:55 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Srivats P." <srivats@india.mercurykr.com>
Cc: sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA IG: Response to an ASPIA msg
Message-ID: <20030117060955.E1767@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Srivats P." <srivats@india.mercurykr.com>,
	sigtran <sigtran@ietf.org>
References: <200301171759.h0HHxVt08542@india.mercurykr.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: <200301171759.h0HHxVt08542@india.mercurykr.com>; from srivats@india.mercurykr.com on Fri, Jan 17, 2003 at 06:21:41PM +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>

Srivats,

Srivats P. wrote:                                                                  (Fri, 17 Jan 2003 18:21:41)
> Hi,
> 
> The "Response to an ASPIA message" issue in the M3UA IG
> states that -
> 
> <quote>
>     ---------
>     New text: (Section 4.5.3)
>     ---------
> 
>     When an ASP wishes to withdraw from receiving traffic within an AS,or
>     the ASP wants to initiate the process of activation, the ASP sends an
>     ASP Inactive message to the SGP or IPSP.
> 
>     An ASP Inactive message MUST be always responded by the peer
>     (although other messages may be sent in the middle):
>        - If the corresponding RK is registered (statically or
>           dynamically), the peer should respond with an ASP Inactive Ack
>           message.
>        -           If the RK is not registered, or the RC information is not valid,
>           the peer must respond with an ERROR message with Error Code =
>           "Invalid Routing Context".
>        - If the RC is missing and its specification is needed according
>           to the used configuration, the peer must respond with an ERROR
>           message with Error Code = "No Configured AS for ASP".
> </quote>
> 
> I couldn't quite understand what is meant by "If the RC is missing and its
> specification is needed according to the used configuration" - does it mean
> that the missing RC indicates "all AS served by ASP" and if there is no
> such AS for the said ASP, it sends ERROR("No configured AS for ASP") ?

RC is optional when an assocation serves a single AS.  If RC is missing and
there is no single AS that the association serves, then it is missing in
error.

--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  Fri Jan 17 08:11: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 IAA21393
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 08:11:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HDQe829864
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 08:26:40 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HDQ4J29833;
	Fri, 17 Jan 2003 08:26:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HDPwJ29810
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 08:25:58 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21345
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 08:09:50 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:x4CWatXzVgirHAMX8prHhMq6QftV25Rb@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0HDDCD02232;
	Fri, 17 Jan 2003 06:13:12 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0HDDCY02692;
	Fri, 17 Jan 2003 06:13:12 -0700
Date: Fri, 17 Jan 2003 06:13:12 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] I-D ACTION:draft-ietf-sigtran-m3ua-implementors-gui de-02.txt
Message-ID: <20030117061312.F1767@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
	TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <1AB3D30B989BF141BBD5C70057B2EF7C475A1F@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: <1AB3D30B989BF141BBD5C70057B2EF7C475A1F@EESTQNT105.es.eu.ericsson.se>; from javier.pastor-balbas@ece.ericsson.se on Wed, Jan 15, 2003 at 03:22:44PM +0100
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, 15 Jan 2003 15:22:44)
> Brian, 
> 
> IMHO an implementation supports or not the registration procedures.
> Supporting some of the messages means increasing the coding without getting
> any practical advantage. I agree with Tolga on this point: it is not a vital
> decission, but it makes sense to choose the message class error.

If it is not vital, the word "MUST" must go.

> 
> The inclusion of 40 bytes of the message was decided in order to find what
> message you sent. If you don't do that way you may not find what was the
> origin of the failure. Since the source of the failure could have been a
> software bug, you may have produced a lot of messages with the erroneous
> message class/type and can not find which one was the faulty one. I might
> help in the debugging process...

The statement that all error messages SHOULD include the offending message
(and not just the first 40 bytes) should suffice.  The IG decleares a "MUST"
include 40 bytes in contradiction to the SHOULD include the message.  Again,
since it is no more vital than any other error case, the statement should be
struct and the "SHOULD contain the offending message" will apply.

--brian

> 
> Cheers // Javier. 
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Wednesday, January 15, 2003 1:11 PM
> > To: TOLGA ASVEREN
> > Cc: sigtran@ietf.org
> > Subject: Re: [Sigtran] I-D
> > ACTION:draft-ietf-sigtran-m3ua-implementors-guide-02.txt
> > 
> > 
> > TOLGA,
> > 
> > TOLGA ASVEREN wrote:                                          
> >                        (Wed, 15 Jan 2003 13:35:13)
> > > 
> > > Brian,
> > > > Resend...
> > > >
> > > > Ken Morneault wrote:
> > > > (Thu, 02 Jan 2003 09:05:39)
> > > > >
> > > > >
> > > > > Brian,
> > > > >
> > > > > Please address your concerns to the entire group
> > > > as your proposed
> > > > > change is something for all to discuss.
> > > > >
> > > > > Regards,
> > > > >
> > > > > Ken
> > > >
> > > >
> > > > SIGTRAN,
> > > >
> > > > Section 3.2.
> > > >
> > > > What does it matter if the SGP sends "Unsupported
> > > > Message Type" or
> > > > "Unsupported Message Class"?  Acutally, if we ever
> > > > add a message to the class,
> > > > "Unsupport Message Class" might no longer be
> > > > correct, whereas "Unsupported
> > > > Message Type" survives the addition of new message
> > > > types to the class.
> > > [TOLGA]Although IMO not very important to send which one 
> > still just my 2
> > > cents: Personally I would prefer "Unsupported Message 
> > Class" because it
> > > suits better for the case, where registration procedure and 
> > so all of the
> > > related messages in the message class is not supported.
> > 
> > Well, the ASP didn't send every message type in the class, it just
> > sent one message type.  It is easy to conceiver that an implementation
> > could support DEREG REQ without supporting REG REQ.  When an ASP sends
> > DEREG REQ, it is responded to with a DEREG RSP with a Deregistration
> > Result indicating "Error - Not Registered".  So it is possible that
> > an implementation supports DEREG REQ without supporting REG REQ.
> > 
> > In fact, an SGP not supporting dynamic registration could easily
> > send REG RSP with Registration Result "Error - Unsupported RK 
> > parameter
> > field" or some such.  Just because an SGP "does not suppor the
> > registration procedure" does not mean that it cannot respond to
> > any message in the class.
> > 
> > At best, section 3.2 of the IG needs to be reworked in light of the
> > above.
> > 
> > Comments?
> > 
> > --brian
> > 
> > 
> > > >
> > > > Also, as the only necessary piece of information
> > > > given in the Error message
> > > > is the Message Class and Type, why force an
> > > > implementation to include the
> > > > first 40 bytes of the message?  That's ridiculous.
> > > > All that needs to be
> > > > included a couple bytes of the message header.
> > > [TOLGA] For that I agree. For those error types, reporting 
> > message class
> > > and type should be enough.
> > > >
> > > > Also, there is no more need to correlate this error
> > > > than others.  The
> > > > ASP is obviously misconfigured (it figures it can
> > > > register with an SGP
> > > > that does not even supoprt registration), so it
> > > > really doesn't matter
> > > > what happens to it: there are many ways to
> > > > misconfigure an ASP so that
> > > > it will not be caught by the protocol.
> > > >
> > > > Please strike section 3.2.
> > > >
> > > > Also note that M2UA and SUA also use the same text.
> > > > It makes no sense to
> > > > have M3UA act differently in this regard than M2UA
> > > > and SUA.
> > > 
> > > _______________________________________________
> > > 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 mailnull@www1.ietf.org  Fri Jan 17 08:43: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 IAA22220
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 08:43:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HDxT232686
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 08:59:29 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HDwYJ32654;
	Fri, 17 Jan 2003 08:58:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HDvmJ32609
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 08:57:48 -0500
Received: from domino2.nc.tekelec.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22172
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 08:41:41 -0500 (EST)
From: jeffrey.craig@tekelec.com
Received: from domino4.nc.tekelec.com ([198.89.40.9])
          by domino2.nc.tekelec.com (Lotus Domino Release 5.0.7)
          with ESMTP id 2003011708390568:21933 ;
          Fri, 17 Jan 2003 08:39:05 -0500 
Subject: Re: [Sigtran] Re: Suggested New Test Cases for draft-bidulock-sigtran-m2pa-test-02.ps
To: bidulock@openss7.org
Cc: jTom George <Tom.George@alcatel.com>, sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.7  March 21, 2001
Message-ID: <OF50D34C54.B6BE7B32-ON85256CB1.004B0FD0@nc.tekelec.com>
Date: Fri, 17 Jan 2003 08:40:56 -0500
MIME-Version: 1.0
X-MIMETrack: Serialize by Router on Domino4/Raleigh/TEKELEC(Release 5.0.10 |March 22, 2002) at
 01/17/2003 08:40:57 AM,
	Itemize by SMTP Server on Domino2/Raleigh/TEKELEC(Release 5.0.7 |March 21, 2001) at
 01/17/2003 08:39:05 AM,
	Serialize by Router on Domino2/Raleigh/TEKELEC(Release 5.0.7 |March 21, 2001) at
 01/17/2003 08:39:07 AM,
	Serialize complete at 01/17/2003 08:39:07 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 Brian,

>Sure, so allow them to be repeated, but don' require or recommend it.
>Use the words MAY or OPTIONAL.

Good recommendation. I agree with this.

Regards,

Jeff





"Brian F. G. Bidulock" <bidulock@openss7.org> on 01/17/2003 08:07:53 AM

Please respond to bidulock@openss7.org

To:    jeffrey.craig@tekelec.com
cc:    Tom George <Tom.George@alcatel.com>, sigtran@ietf.org
Subject:    Re: [Sigtran] Re: Suggested New Test Cases for
       draft-bidulock-sigtran-m2pa-test-02.ps


Jeffrey,

Sure, so allow them to be repeated, but don' require or recommend it.
Use the words MAY or OPTIONAL.

--brian

jeffrey.craig@tekelec.com wrote:
(Fri, 17 Jan 2003 07:43:35)
>
> Hello Tom,
>
> After further consideration of the issue, I have concluded that the
> repeated
> sending of LSR, LSB, LSPO is useful for diagnostics and measurements.
> I don't see how these messages could be lost if the association remains
> established, but nevertheless, I now think that the repetition is useful.
>
> Regards,
>
> Jeff
>
>
>
>
>
> Tom George <Tom.George@alcatel.com>@ietf.org on 01/16/2003 06:08:05 PM
>
> Sent by:    sigtran-admin@ietf.org
>
>
> To:    sigtran@ietf.org
> cc:    bidulock@openss7.org
> Subject:    Re: [Sigtran] Re: Suggested New Test Cases for
>        draft-bidulock-sigtran-m2pa-test-02.ps
>
>
> Brian,
>
> I think there was a concern about what would happen if only one message
> was sent, and it got lost.
>
> Do you think we should not send these messages periodically?
>
>    LS Ready
>    LS Busy
>    LS PO
>
> tomG.
>
>
> "Brian F. G. Bidulock" wrote long ago on 09/19/02:
> >
> > Jeffrey,
> >
> > I don't enjoy burning timers for nothing.  It is easy enough
> > (even trivial) for an implementation to ignore the repetition,
> > but generating and interval requires a timer and introduces
> > additional fodder for race conditions and barriers to scale.
> > Unless someone can come up with a good reason, the intervals
> > should be struck.
> >
> > Can you remember why they were added, Tom?
> >
> > --brian
> >
> > jeffrey.craig@tekelec.com wrote:               (Thu, 19 Sep 2002
> 08:47:34)
> > >
> > > Hello Brian,
> > >
> > > >My preference is that they are struck.  The reason for striking
> > > >is that sending these at an interval serves no purpose whatsoever
> > > >that I can think of.  Can you think of a reason to send any of
> > > >these periodically?  This is SCTP after all and not a lossy link.
> > >
> > > I can think of no reason to periodically send these messages.
> > > My preference for keeping them has to with the fact that I've
> > > implemented them. (Yes, I know, not a good reason.... I'm human).
> > >
> > > Regards,
> > >
> > > Jeff
> > >
> >
> > --
> > 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 USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
> * 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  Fri Jan 17 09: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 JAA22870
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 09:15:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HEV6P02393
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 09:31:06 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HEUQJ02313;
	Fri, 17 Jan 2003 09:30:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HET9J02268
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 09:29:09 -0500
Received: from rtp-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22804
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 09:13:00 -0500 (EST)
Received: from cia.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0HEGuZg010896;
	Fri, 17 Jan 2003 09:16:56 -0500 (EST)
Received: from kmorneau-w2k.cisco.com (rtp-vpn2-822.cisco.com [10.82.243.54])
	by cia.cisco.com (Mirapoint)
	with ESMTP id ABM95273;
	Fri, 17 Jan 2003 09:06:07 -0500 (EST)
Message-Id: <4.3.2.7.2.20030117091442.04465070@cia.cisco.com>
X-Sender: kmorneau@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 17 Jan 2003 09:16:08 -0500
To: bidulock@openss7.org, TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
From: Ken Morneault <kmorneau@cisco.com>
Subject: Re: [Sigtran] OPC List renamed as DPC List
Cc: sigtran@ietf.org
In-Reply-To: <20030117060341.C1767@openss7.org>
References: <OF5FF49888.9010AAC9-ONC2256CB1.0045D832@LocalDomain>
 <OF5FF49888.9010AAC9-ONC2256CB1.0045D832@LocalDomain>
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>



All:

It was previously noted that Section 3.8 was incorrect and
that it would be fixed in the next release of the I-G.  

Regards,

Ken

At 06:03 AM 1/17/2003 -0700, Brian F. G. Bidulock wrote:
>TOLGA,
>
>TOLGA ASVEREN wrote:                                                                 (Fri, 17 Jan 2003 14:48:32)
>> 
>> Srivats,
>> --- "Srivats P." <srivats@india.mercurykr.com> wrote:
>> > Hi,
>> >
>> > I need a clarification regarding the "OPC List in
>> > Registration
>> > Request Message" issue in the M3UA IG.
>> >
>> > <quote>
>> >     ---------
>> >     New text: (Section 3.6.1)
>> >     ---------
>> >
>> >     DPC List:
>> >
>> >     The Destination Point Code List parameter
>> > contains one or more SS7
>> >     DPC entries, and its format is the same as the
>> > Destination Point Code
>> >     parameter. Multiple DPC values will only be
>> > valid in the case of
>> >     Alias Point Code configuration. The absence of
>> > the DPC List parameter
>> >     in the Routing Key indicates the use of the DPC
>> > value as the only
>> >     posible DPC for the AS.
>> >
>> >  3.8.3 Solution description
>> >
>> >     Including the scenario where this parameter is
>> > used (Alias point code
>> >     configurations), the problem is solved. The
>> > parameter name has also
>> >     be changed to "Destination" since it is the way
>> > that the SG sees it.
>> >
>> > </quote>
>> >
>> > the OPC List has been renamed as DPC List. So now we
>> > have a DPC Parameter
>> > (the point code of the AS which is being registered)
>> > and a DPC List (
>> > earlier OPC List) which is a list of SS7 Point Codes
>> > from which the AS
>> > can receive messages. Right ?
>> [TOLGA] No, OPC list is not renamed. It is still there. There were
>> questions why multiple DPCs are allowed for a RK, and for that a
>> clarification has been added to IG. But the initial version had a typo
>> where it was referring to OPC instead of DPC. Still it seems a correction
>> is necessary. I think it should refer to multiple DPC values instead of a
>> DPC list, because this is the structure of RK parameter.
>
>It is foolish to use the terms DPC and OPC at all.  DPC only has meaning
>in SS7 for a direction of message flow.  Local and Remote would be better
>terms that are used throughout the SS7 specifications.
>
>Nevertheless, the IG describes the "DPC List" as  for "alias" point codes
>and replaces the OPC List text.  This is absurd.  The section should read
>as follows:
>
> ----------
>  Old Text (section 3.6.1)
> ----------
>
>      Note: The Destination Point Code, Service Indicators, Originating
>      Point Code List and Circuit Range List parameters MAY be repeated
>      as a grouping within the Routing Key parameter, in the structure
>      shown above.
>
> ----------
>  New Text (section 3.6.1)
> ----------
>
>      Note: The Destination Point Code, Service Indicators, Originating
>      Point Code List and Circuit Range List parameters MAY be repeated
>      as a grouping within the Routing Key parameter, in the structure
>      shown above.  This could be used where the RK represends multiple
>      alias point codes.
>
>--brian
>
>> >
>> > Say, SP A in the SS7 network has alias point codes
>> > 1-1-1 and 1-1-2.
>> > ASP X registers an AS (DPC = 3-3-3 and DPC List =
>> > 1-1-1, 1-1-2). Now if the
>> > SG receives any message with the DPC value as 3-3-3
>> > in the Routing Label,
>> > it will check the OPC value in the Routing Label to
>> > see if it is either
>> > 1-1-1 or 1-1-2, before sending the message to the
>> > AS. Right ?
>> >
>> > What happens if the DPC List (1-1-1, 1-1-2) was not
>> > included in the RK ?
>> > According to the IG -
>> >
>> > "The absence of the DPC List parameter in the
>> > Routing Key indicates the
>> > use of the DPC value as the only posible DPC for the
>> > AS."
>> >           ^^^^^^^^^^^
>> >
>> > Which "DPC value" is being referred to here ? 3-3-3
>> > ? But wasn't it the
>> > same case even when the "DPC List (formerly OPC
>> > List)" was included ?
>> > The ONLY point code of the AS was still 3-3-3. What
>> > am I misreading here ?
>> 
>> _______________________________________________
>> 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 mailnull@www1.ietf.org  Fri Jan 17 09:15: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 JAA22883
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 09:15:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HEV8w02405
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 09:31:08 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HEUfJ02344;
	Fri, 17 Jan 2003 09:30:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HETMJ02280
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 09:29:22 -0500
Received: from rtp-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22812
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 09:13:14 -0500 (EST)
Received: from cia.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0HEHLcL010946;
	Fri, 17 Jan 2003 09:17:21 -0500 (EST)
Received: from kmorneau-w2k.cisco.com (rtp-vpn2-822.cisco.com [10.82.243.54])
	by cia.cisco.com (Mirapoint)
	with ESMTP id ABM95281;
	Fri, 17 Jan 2003 09:06:33 -0500 (EST)
Message-Id: <4.3.2.7.2.20030117091629.045c6ef0@cia.cisco.com>
X-Sender: kmorneau@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 17 Jan 2003 09:16:34 -0500
To: bidulock@openss7.org, sigtran@ietf.org
From: Ken Morneault <kmorneau@cisco.com>
Subject: Re: [Sigtran] I-D ACTION:draft-ietf-sigtran-dua-05.txt
In-Reply-To: <20030117054747.A1767@openss7.org>
References: <200301171224.HAA19525@ietf.org>
 <200301171224.HAA19525@ietf.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>



thanks.

Ken

At 05:47 AM 1/17/2003 -0700, Brian F. G. Bidulock wrote:
>Ken,
>
>Nit:
>
>In changing the date on the document, you inadvertently changed the
>data on referece [4].
>
>--brian
>
>@@ -546,7 +580,7 @@
>    Digital Access Signaling System No 2
> 
>    [4]  IUA (RFC3057) Implementors Guide, draft-ietf-sigtran-iua-imp-
>-    guide-01.txt, Oct 2002
>+    guide-01.txt, Jan 2003
> 
> 7.2  Informative References
> 
>
>-- 
>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 Jan 17 10:07: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 KAA24833
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 10:07:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HFN0Z06605
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 10:23:00 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HFMiJ06558;
	Fri, 17 Jan 2003 10:22:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HFKXJ06415
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 10:20:33 -0500
Received: from web8206.mail.in.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA24652
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 10:04:23 -0500 (EST)
Message-ID: <20030117150745.19805.qmail@web8206.mail.in.yahoo.com>
Received: from [203.123.167.157] by web8206.mail.in.yahoo.com via HTTP; Fri, 17 Jan 2003 15:07:45 GMT
Date: Fri, 17 Jan 2003 15:07:45 +0000 (GMT)
From: =?iso-8859-1?q?amit=20somani?= <amitksomani@yahoo.co.in>
To: Sigtran <sigtran@ietf.org>, tsvwg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Sigtran] (no subject)
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 all!
  we r a group of student from pune institute of
computer technology,pune,india. we r working on ss7 as
our final year project.
 i've some basic questions
1. is it possible to have ss7 signal on a EPABX? does
telephone exchange provides it?
2. if possible then will it be possible that we can
get those ss7 signals on computer by inserting some
kind of card in ISA slot.
3. are such kind of cards available ?
4. how much such card will cost?
5. what kind of hardware is used at exchange to deal
with ss7 signals?
6. is there any kind of software tool available which
will simulate/
    generate ss7 signals as actual.
  if u've any material available will u please mail
it.
  thank u.
         anup   
 

________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
       visit http://in.tv.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jan 17 10:09:19 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 KAA25020
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 10:09:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HFOvr06771
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 10:24:57 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HFOiJ06725;
	Fri, 17 Jan 2003 10:24:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HFMIJ06529
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 10:22:18 -0500
Received: from web8204.mail.in.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA24739
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 10:06:08 -0500 (EST)
Message-ID: <20030117150930.28891.qmail@web8204.mail.in.yahoo.com>
Received: from [203.123.167.157] by web8204.mail.in.yahoo.com via HTTP; Fri, 17 Jan 2003 15:09:30 GMT
Date: Fri, 17 Jan 2003 15:09:30 +0000 (GMT)
From: =?iso-8859-1?q?amit=20somani?= <amitksomani@yahoo.co.in>
To: Sigtran <sigtran@ietf.org>, tsvwg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Sigtran] (no subject)
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 all!
  we r a group of student from pune institute of
computer technology,pune,india. we r working on ss7 as
our final year project.
 i've some basic questions
1. is it possible to have ss7 signal on a EPABX? does
telephone exchange provides it?
2. if possible then will it be possible that we can
get those ss7 signals on computer by inserting some
kind of card in ISA slot.
3. are such kind of cards available ?
4. how much such card will cost?
5. what kind of hardware is used at exchange to deal
with ss7 signals?
6. is there any kind of software tool available which
will simulate/
    generate ss7 signals as actual.
  if u've any material available will u please mail
it.
  thank u.
         amit
 

________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
       visit http://in.tv.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jan 17 10:09: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 KAA25133
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 10:09:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HFPLP06871
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 10:25:21 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HFP7J06828;
	Fri, 17 Jan 2003 10:25:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HFNNJ06648
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 10:23:23 -0500
Received: from web8201.mail.in.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA24794
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 10:07:12 -0500 (EST)
Message-ID: <20030117151034.50999.qmail@web8201.mail.in.yahoo.com>
Received: from [203.123.167.157] by web8201.mail.in.yahoo.com via HTTP; Fri, 17 Jan 2003 15:10:34 GMT
Date: Fri, 17 Jan 2003 15:10:34 +0000 (GMT)
From: =?iso-8859-1?q?amit=20somani?= <amitksomani@yahoo.co.in>
To: Sigtran <sigtran@ietf.org>, tsvwg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Sigtran] (no subject)
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 all!
  we r a group of student from pune institute of
computer technology,pune,india. we r working on ss7 as
our final year project.
 i've some basic questions
1. is it possible to have ss7 signal on a EPABX? does
telephone exchange provides it?
2. if possible then will it be possible that we can
get those ss7 signals on computer by inserting some
kind of card in ISA slot.
3. are such kind of cards available ?
4. how much such card will cost?
5. what kind of hardware is used at exchange to deal
with ss7 signals?
6. is there any kind of software tool available which
will simulate/
    generate ss7 signals as actual.
  if u've any material available will u please mail
it.
  thank u.
         amit
 

________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
       visit http://in.tv.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jan 17 10:32: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 KAA26099
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 10:32:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HFlm108680
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 10:47:48 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HFlZJ08624;
	Fri, 17 Jan 2003 10:47:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HFj0J08395
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 10:45:00 -0500
Received: from web8206.mail.in.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA25844
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 10:28:46 -0500 (EST)
Message-ID: <20030117153207.5184.qmail@web8206.mail.in.yahoo.com>
Received: from [203.123.167.157] by web8206.mail.in.yahoo.com via HTTP; Fri, 17 Jan 2003 15:32:07 GMT
Date: Fri, 17 Jan 2003 15:32:07 +0000 (GMT)
From: =?iso-8859-1?q?amit=20somani?= <amitksomani@yahoo.co.in>
To: Sigtran <sigtran@ietf.org>, tsvwg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Sigtran] query regarding ss7
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 all!
  we r a group of student from pune institute of
computer technology,pune,india. we r working on ss7 as
our final year project.
 i've some basic questions
1. is it possible to have ss7 signal on a EPABX? does
telephone exchange provides it?
2. if possible then will it be possible that we can
get those ss7 signals on computer by inserting some
kind of card in ISA slot.
3. are such kind of cards available ?
4. how much such card will cost?
5. what kind of hardware is used at exchange to deal
with ss7 signals?
6. is there any kind of software tool available which
will simulate/
    generate ss7 signals as actual.
  if u've any material available will u please mail
it.
  thank u.
         amit


________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
       visit http://in.tv.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jan 17 10:35: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 KAA26196
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 10:35:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HFodo08881
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 10:50:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HFo6J08860;
	Fri, 17 Jan 2003 10:50:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HFnjJ08818
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 10:49:45 -0500
Received: from revere.sonusnet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26166
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 10:33:34 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3.sonusnet.com [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h0HFaJ111486
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 10:36:20 -0500 (EST)
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19)
	id <Y68HTGXZ>; Fri, 17 Jan 2003 10:36:56 -0500
Message-ID: <4CF48720B6E9D4118D040060CF2074E9072F6BE7@sonusdc3.sonusnet.com>
From: "Wung, Joseph" <JWung@sonusnet.com>
To: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA default AS
Date: Fri, 17 Jan 2003 10:36:52 -0500
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,
Tolga,

Are you suggesting the following steps in creating
a default AS?

1) Configure the SG with ASP IDs that are to be used
   as default ASPs.
2) A default ASP establishes its own SCTP associations.
3) The default ASP sends an ASP Up message with an ASP Id
   that SG has configured.
4) SG responds with ASP Up Ack.
5) Other default ASPs can repeat step 2 thru 4.
6) From now on, any incoming SS7 message that cannot find a 
   matching routing key entry will be routed over to one of 
   default ASPs.
  
How does the SGP know what traffic mode they are running in,
i.e., loadshare, broadcast, or override?

Joe

> > > M3UA section 1.4.2.4 says
> > >
> > >        "When there is no matching Routing Key entry for an
> > >        incoming SS7 message, a default treatment MAY be
> > >        specified.  Possible solutions are to provide a default
> > >        AS at the SGP that directs all unallocated traffic to a
> > >        (set of) default ASP(s), or to drop the message and
> > >        provide a notification to layer management."
> > >
> >
> > Can someone tell me how this default AS is provided in the
> > system where dynamic registrations are used?  Normally,
> > an AS is tied to an SCTP association over which the ASP
> > registers with the AS.  Without a procedure, how could this
> > coupling between the default AS and the "default"
> > SCTP association be established?
> 
> ASP Id ?
> [TOLGA]If the goal is also to provide dynamic behaviour for 
> addressing of
> ASPs I also think AspId should be used. But for the case where dynamic
> behaviour is required only for traffic ranges, one can also use static
> addressing for default ASP.
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 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 Jan 17 11:17: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 LAA27433
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 11:17:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HGXFW11640
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 11:33:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HGWpJ11605;
	Fri, 17 Jan 2003 11:32:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HGV0J11534
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 11:31:00 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27314
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 11:14:48 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:CiygGqEq9qBL0lod0RCmdfUVbSQuiaUY@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0HGIBD05050;
	Fri, 17 Jan 2003 09:18:11 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0HGIBq07529;
	Fri, 17 Jan 2003 09:18:11 -0700
Date: Fri, 17 Jan 2003 09:18:11 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Wung, Joseph" <JWung@sonusnet.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA default AS
Message-ID: <20030117091811.B5295@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Wung, Joseph" <JWung@sonusnet.com>, sigtran@ietf.org
References: <4CF48720B6E9D4118D040060CF2074E9072F6BE7@sonusdc3.sonusnet.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: <4CF48720B6E9D4118D040060CF2074E9072F6BE7@sonusdc3.sonusnet.com>; from JWung@sonusnet.com on Fri, Jan 17, 2003 at 10:36:52AM -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>

Joseph,

I would think that it is a good idea to have the ASPs
activate for the "default" AS.  I thought it would be
a good idea to use, say, RC=0, to indicate the default
AS to the SG.  Then the traffic mode is the traffic mode
of the AS.

--brian

Wung, Joseph wrote:                                                                  (Fri, 17 Jan 2003 10:36:52)
> Brian,
> Tolga,
> 
> Are you suggesting the following steps in creating
> a default AS?
> 
> 1) Configure the SG with ASP IDs that are to be used
>    as default ASPs.
> 2) A default ASP establishes its own SCTP associations.
> 3) The default ASP sends an ASP Up message with an ASP Id
>    that SG has configured.
> 4) SG responds with ASP Up Ack.
> 5) Other default ASPs can repeat step 2 thru 4.
> 6) From now on, any incoming SS7 message that cannot find a 
>    matching routing key entry will be routed over to one of 
>    default ASPs.
>   
> How does the SGP know what traffic mode they are running in,
> i.e., loadshare, broadcast, or override?
> 
> Joe
> 
> > > > M3UA section 1.4.2.4 says
> > > >
> > > >        "When there is no matching Routing Key entry for an
> > > >        incoming SS7 message, a default treatment MAY be
> > > >        specified.  Possible solutions are to provide a default
> > > >        AS at the SGP that directs all unallocated traffic to a
> > > >        (set of) default ASP(s), or to drop the message and
> > > >        provide a notification to layer management."
> > > >
> > >
> > > Can someone tell me how this default AS is provided in the
> > > system where dynamic registrations are used?  Normally,
> > > an AS is tied to an SCTP association over which the ASP
> > > registers with the AS.  Without a procedure, how could this
> > > coupling between the default AS and the "default"
> > > SCTP association be established?
> > 
> > ASP Id ?
> > [TOLGA]If the goal is also to provide dynamic behaviour for 
> > addressing of
> > ASPs I also think AspId should be used. But for the case where dynamic
> > behaviour is required only for traffic ranges, one can also use static
> > addressing for default ASP.
> > 
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > 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 Jan 17 11:37: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 LAA28034
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 11:37:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HGqkC13344
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 11:52:46 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HGqFJ13285;
	Fri, 17 Jan 2003 11:52:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HGpHJ13234
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 11:51:17 -0500
Received: from revere.sonusnet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27941
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 11:35:06 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3.sonusnet.com [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h0HGbj117813;
	Fri, 17 Jan 2003 11:37:45 -0500 (EST)
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19)
	id <Y68HTH1R>; Fri, 17 Jan 2003 11:38:21 -0500
Message-ID: <4CF48720B6E9D4118D040060CF2074E9072F6BE8@sonusdc3.sonusnet.com>
From: "Wung, Joseph" <JWung@sonusnet.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA default AS
Date: Fri, 17 Jan 2003 11:38:16 -0500
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,

Good idea. So the procedures are like:
1) Default ASPs each establish an SCTP associations
2) Default ASPs each send a ASP Up message.
3) Default ASPs each send ASP Active message with RC=0,
   and a desired traffic mode.

I think this should work, but we need the procedures
specified in the IG, espcially RC=0 being used for 
default AS.

Joe
 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Friday, January 17, 2003 11:18 AM
> To: Wung, Joseph
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] M3UA default AS
> 
> 
> Joseph,
> 
> I would think that it is a good idea to have the ASPs
> activate for the "default" AS.  I thought it would be
> a good idea to use, say, RC=0, to indicate the default
> AS to the SG.  Then the traffic mode is the traffic mode
> of the AS.
> 
> --brian
> 
> Wung, Joseph wrote:                                           
>                        (Fri, 17 Jan 2003 10:36:52)
> > Brian,
> > Tolga,
> > 
> > Are you suggesting the following steps in creating
> > a default AS?
> > 
> > 1) Configure the SG with ASP IDs that are to be used
> >    as default ASPs.
> > 2) A default ASP establishes its own SCTP associations.
> > 3) The default ASP sends an ASP Up message with an ASP Id
> >    that SG has configured.
> > 4) SG responds with ASP Up Ack.
> > 5) Other default ASPs can repeat step 2 thru 4.
> > 6) From now on, any incoming SS7 message that cannot find a 
> >    matching routing key entry will be routed over to one of 
> >    default ASPs.
> >   
> > How does the SGP know what traffic mode they are running in,
> > i.e., loadshare, broadcast, or override?
> > 
> > Joe
> > 
> > > > > M3UA section 1.4.2.4 says
> > > > >
> > > > >        "When there is no matching Routing Key entry for an
> > > > >        incoming SS7 message, a default treatment MAY be
> > > > >        specified.  Possible solutions are to provide a default
> > > > >        AS at the SGP that directs all unallocated traffic to a
> > > > >        (set of) default ASP(s), or to drop the message and
> > > > >        provide a notification to layer management."
> > > > >
> > > >
> > > > Can someone tell me how this default AS is provided in the
> > > > system where dynamic registrations are used?  Normally,
> > > > an AS is tied to an SCTP association over which the ASP
> > > > registers with the AS.  Without a procedure, how could this
> > > > coupling between the default AS and the "default"
> > > > SCTP association be established?
> > > 
> > > ASP Id ?
> > > [TOLGA]If the goal is also to provide dynamic behaviour for 
> > > addressing of
> > > ASPs I also think AspId should be used. But for the case 
> where dynamic
> > > behaviour is required only for traffic ranges, one can 
> also use static
> > > addressing for default ASP.
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > 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 Jan 17 11:56:52 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 LAA28577
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 11:56:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HHCXN15229
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 12:12:33 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HHC8J15198;
	Fri, 17 Jan 2003 12:12:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HHBFJ15173
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 12:11:15 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28514
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 11:55:02 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0HGwPVN000308;
	Fri, 17 Jan 2003 10:58:25 -0600 (CST)
Message-ID: <3E283631.30267CD4@alcatel.com>
Date: Fri, 17 Jan 2003 10:58:25 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: sigtran@ietf.org
Subject: Re: [Sigtran] Re: Suggested New Test Cases for 
 draft-bidulock-sigtran-m2pa-test-02.ps
References: <OF50D34C54.B6BE7B32-ON85256CB1.004B0FD0@nc.tekelec.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

Good idea. For example, I will change this in 4.1.3:

When the proving period timer T4 expires, M2PA changes to the Aligned
Ready state. M2PA SHALL start the timer T1 and send Link Status Ready
messages to its peer at interval Status_Interval. These messages are
used to verify that both ends have completed proving.

to this:

When the proving period timer T4 expires, M2PA changes to the Aligned
Ready state. M2PA SHALL start the timer T1 and send a Link Status
Ready message to its peer. These Link Status Ready message is used to
verify that both ends have completed proving. M2PA MAY send additional
Link Status Ready messages while timer T1 is running.

And I will remove the Status_Interval.


While I am in the neighborhood: Proving_Rate is really an interval, not
a rate. So I was thinking of changing its name to Proving_Interval. 

tomG.

jeffrey.craig@tekelec.com wrote:
> 
> Hello Brian,
> 
> >Sure, so allow them to be repeated, but don' require or recommend it.
> >Use the words MAY or OPTIONAL.
> 
> Good recommendation. I agree with this.
> 
> Regards,
> 
> Jeff
> 
> "Brian F. G. Bidulock" <bidulock@openss7.org> on 01/17/2003 08:07:53 AM
> 
> Please respond to bidulock@openss7.org
> 
> To:    jeffrey.craig@tekelec.com
> cc:    Tom George <Tom.George@alcatel.com>, sigtran@ietf.org
> Subject:    Re: [Sigtran] Re: Suggested New Test Cases for
>        draft-bidulock-sigtran-m2pa-test-02.ps
> 
> Jeffrey,
> 
> Sure, so allow them to be repeated, but don' require or recommend it.
> Use the words MAY or OPTIONAL.
> 
> --brian
> 
> jeffrey.craig@tekelec.com wrote:
> (Fri, 17 Jan 2003 07:43:35)
> >
> > Hello Tom,
> >
> > After further consideration of the issue, I have concluded that the
> > repeated
> > sending of LSR, LSB, LSPO is useful for diagnostics and measurements.
> > I don't see how these messages could be lost if the association remains
> > established, but nevertheless, I now think that the repetition is useful.
> >
> > Regards,
> >
> > Jeff
> >
> >
> >
> >
> >
> > Tom George <Tom.George@alcatel.com>@ietf.org on 01/16/2003 06:08:05 PM
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    sigtran@ietf.org
> > cc:    bidulock@openss7.org
> > Subject:    Re: [Sigtran] Re: Suggested New Test Cases for
> >        draft-bidulock-sigtran-m2pa-test-02.ps
> >
> >
> > Brian,
> >
> > I think there was a concern about what would happen if only one message
> > was sent, and it got lost.
> >
> > Do you think we should not send these messages periodically?
> >
> >    LS Ready
> >    LS Busy
> >    LS PO
> >
> > tomG.
> >
> >
> > "Brian F. G. Bidulock" wrote long ago on 09/19/02:
> > >
> > > Jeffrey,
> > >
> > > I don't enjoy burning timers for nothing.  It is easy enough
> > > (even trivial) for an implementation to ignore the repetition,
> > > but generating and interval requires a timer and introduces
> > > additional fodder for race conditions and barriers to scale.
> > > Unless someone can come up with a good reason, the intervals
> > > should be struck.
> > >
> > > Can you remember why they were added, Tom?
> > >
> > > --brian
> > >
> > > jeffrey.craig@tekelec.com wrote:               (Thu, 19 Sep 2002
> > 08:47:34)
> > > >
> > > > Hello Brian,
> > > >
> > > > >My preference is that they are struck.  The reason for striking
> > > > >is that sending these at an interval serves no purpose whatsoever
> > > > >that I can think of.  Can you think of a reason to send any of
> > > > >these periodically?  This is SCTP after all and not a lossy link.
> > > >
> > > > I can think of no reason to periodically send these messages.
> > > > My preference for keeping them has to with the fact that I've
> > > > implemented them. (Yes, I know, not a good reason.... I'm human).
> > > >
> > > > Regards,
> > > >
> > > > Jeff
> > > >
> > >
> > > --
> > > 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 USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
> > * 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/

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 17 11:58: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 LAA28622
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 11:58:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HHEIU15300
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 12:14:18 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HHE4J15285;
	Fri, 17 Jan 2003 12:14:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HHD4J15249
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 12:13:04 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28576
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 11:56:51 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:K6QF30y0IvxExyLvH4kJXWymqBJl7APa@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0HH0ED05866;
	Fri, 17 Jan 2003 10:00:14 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0HH0Ec09316;
	Fri, 17 Jan 2003 10:00:14 -0700
Date: Fri, 17 Jan 2003 10:00:13 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Wung, Joseph" <JWung@sonusnet.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA default AS
Message-ID: <20030117100013.B8748@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Wung, Joseph" <JWung@sonusnet.com>, sigtran@ietf.org
References: <4CF48720B6E9D4118D040060CF2074E9072F6BE8@sonusdc3.sonusnet.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: <4CF48720B6E9D4118D040060CF2074E9072F6BE8@sonusdc3.sonusnet.com>; from JWung@sonusnet.com on Fri, Jan 17, 2003 at 11:38:16AM -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>

Joe,

Wung, Joseph wrote:                                                                  (Fri, 17 Jan 2003 11:38:16)
> Brian,
> 
> Good idea. So the procedures are like:
> 1) Default ASPs each establish an SCTP associations
> 2) Default ASPs each send a ASP Up message.
> 3) Default ASPs each send ASP Active message with RC=0,
>    and a desired traffic mode.
> 
> I think this should work, but we need the procedures
> specified in the IG, espcially RC=0 being used for 
> default AS.
> 

Doesn't need to be defined in the IG.  ASPs and SGs can
agree to a statically defined RK (default) and RC anytime
they like.

--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  Fri Jan 17 11:59: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 LAA28665
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 11:59:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HHFIi15370
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 12:15:18 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HHF4J15337;
	Fri, 17 Jan 2003 12:15:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HHEEJ15296
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 12:14:14 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28612
	for <sigtran@ietf.org>; Fri, 17 Jan 2003 11:57:59 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:RrptnHOE2FMJ26J2JuipqFj7iW/4B501@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0HH1JD05943;
	Fri, 17 Jan 2003 10:01:19 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0HH1JL09522;
	Fri, 17 Jan 2003 10:01:19 -0700
Date: Fri, 17 Jan 2003 10:01:19 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tom George <Tom.George@alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: Suggested New Test Cases for draft-bidulock-sigtran-m2pa-test-02.ps
Message-ID: <20030117100119.C8748@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tom George <Tom.George@alcatel.com>, sigtran@ietf.org
References: <OF50D34C54.B6BE7B32-ON85256CB1.004B0FD0@nc.tekelec.com> <3E283631.30267CD4@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: <3E283631.30267CD4@alcatel.com>; from Tom.George@alcatel.com on Fri, Jan 17, 2003 at 10:58:25AM -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>

Tom,

Works for me.

--brian

Tom George wrote:                                                                      (Fri, 17 Jan 2003 10:58:25)
> Good idea. For example, I will change this in 4.1.3:
> 
> When the proving period timer T4 expires, M2PA changes to the Aligned
> Ready state. M2PA SHALL start the timer T1 and send Link Status Ready
> messages to its peer at interval Status_Interval. These messages are
> used to verify that both ends have completed proving.
> 
> to this:
> 
> When the proving period timer T4 expires, M2PA changes to the Aligned
> Ready state. M2PA SHALL start the timer T1 and send a Link Status
> Ready message to its peer. These Link Status Ready message is used to
> verify that both ends have completed proving. M2PA MAY send additional
> Link Status Ready messages while timer T1 is running.
> 
> And I will remove the Status_Interval.
> 
> 
> While I am in the neighborhood: Proving_Rate is really an interval, not
> a rate. So I was thinking of changing its name to Proving_Interval. 
> 
> tomG.
> 

-- 
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 Jan 17 13:38:23 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 NAA01180
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 13:38:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HIs4l21554
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 13:54:04 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HIrkJ21503;
	Fri, 17 Jan 2003 13:53:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HIqdJ21457
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 13:52:39 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01138
	for <SIGTRAN@IETF.org>; Fri, 17 Jan 2003 13:36:26 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0HIdkBS029137;
	Fri, 17 Jan 2003 12:39:46 -0600 (CST)
Message-ID: <3E284DF1.77D19100@alcatel.com>
Date: Fri, 17 Jan 2003 12:39:45 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: SIGTRAN e-mail list <SIGTRAN@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M2PA: LS Alignment after proving
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

Right now I have in section 4.1.3:

   Anomalous messages received during alignment SHOULD be
   discarded. Examples include:

      (a) User Data received before proving begins.

      (b) Link Status Alignment received before or during proving.

Jeff Craig (11/04/02 subject "[Sigtran] M2PA Plugtest Comments - Day 1")
asked if LS Alignment received during ALIGNED READY should cause a
transition to OOS. 

I think it will work either way (discarding it or going to OOS). 

If the other end is trying to restart alignment, it should have sent LS
OOS first. Maybe the LS OOS got delayed. If so, the other end's (newly
renamed) T2 will expire and it will send another LS OOS. 

OTOH, it could be argued that receipt of LS Alignment during ALIGNED
READY shows that the ends are out of step and it would be best just to
go to OOS and start over. 

I am inclined toward going to OOS. Opinions?

tomG.

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 17 14:50: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 OAA02952
	for <sigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 14:50:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0HK6Rb25634
	for sigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 15:06:27 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HK5oJ25608;
	Fri, 17 Jan 2003 15:05:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HK3PJ25439
	for <sigtran@optimus.ietf.org>; Fri, 17 Jan 2003 15:03:25 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02884
	for <SIGTRAN@ietf.org>; Fri, 17 Jan 2003 14:47:10 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:peD1OsYWHWqQk6D1hhgzz2/M/dpk5d2K@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0HJoWD08605;
	Fri, 17 Jan 2003 12:50:32 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0HJoVW14113;
	Fri, 17 Jan 2003 12:50:31 -0700
Date: Fri, 17 Jan 2003 12:50:31 -0700
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: LS Alignment after proving
Message-ID: <20030117125031.A13581@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tom George <Tom.George@alcatel.com>,
	SIGTRAN e-mail list <SIGTRAN@ietf.org>
References: <3E284DF1.77D19100@alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <3E284DF1.77D19100@alcatel.com>; from Tom.George@alcatel.com on Fri, Jan 17, 2003 at 12:39:45PM -0600
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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,

Q.703 ignores SIO during proving, however, SIO puts the link out of
service in Aligned Ready state.  Also, SIO puts the link out of service
in In Service state.  IMO stick with the Q.703 behavior and say that
"Alignment" causes OOS in either the "Aligned Ready" or "In Service"
states.  (It also should put the link out of service in the "Aligned
Not Ready" state, per Q.703).

--brian

On Fri, 17 Jan 2003, Tom George wrote:

> Right now I have in section 4.1.3:
> 
>    Anomalous messages received during alignment SHOULD be
>    discarded. Examples include:
> 
>       (a) User Data received before proving begins.
> 
>       (b) Link Status Alignment received before or during proving.
> 
> Jeff Craig (11/04/02 subject "[Sigtran] M2PA Plugtest Comments - Day 1")
> asked if LS Alignment received during ALIGNED READY should cause a
> transition to OOS. 
> 
> I think it will work either way (discarding it or going to OOS). 
> 
> If the other end is trying to restart alignment, it should have sent LS
> OOS first. Maybe the LS OOS got delayed. If so, the other end's (newly
> renamed) T2 will expire and it will send another LS OOS. 
> 
> OTOH, it could be argued that receipt of LS Alignment during ALIGNED
> READY shows that the ends are out of step and it would be best just to
> go to OOS and start over. 
> 
> I am inclined toward going to OOS. Opinions?
> 
> tomG.
> 
> -- 
> * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> * Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
> * 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 Jan 20 01:21: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 BAA02271
	for <sigtran-archive@odin.ietf.org>; Mon, 20 Jan 2003 01:21:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0K6c4U15995
	for sigtran-archive@odin.ietf.org; Mon, 20 Jan 2003 01:38:04 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K6bJJ15890;
	Mon, 20 Jan 2003 01:37:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K6UxJ15140
	for <sigtran@optimus.ietf.org>; Mon, 20 Jan 2003 01:30:59 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02198
	for <sigtran@ietf.org>; Mon, 20 Jan 2003 01:13:27 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:VAuKs1R56eA3zi1iAsUAugz9wRR4zBKn@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0K6GpD27580;
	Sun, 19 Jan 2003 23:16:51 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0K6Gp113827;
	Sun, 19 Jan 2003 23:16:51 -0700
Date: Sun, 19 Jan 2003 23:16:51 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Srivats P." <srivats@india.mercurykr.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] OPC List renamed as DPC List
Message-ID: <20030119231651.A13799@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Srivats P." <srivats@india.mercurykr.com>,
	sigtran@ietf.org
References: <200301171846.h0HIkit08959@india.mercurykr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <200301171846.h0HIkit08959@india.mercurykr.com>; from srivats@india.mercurykr.com on Fri, Jan 17, 2003 at 07:08:53PM +0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

Srivats,

No.  The entire RFC stays as it stands.  DPC can already be repeated
in the RK.  It is the explanation of the repetition which is missing:
i.e., that one might want to repeat DPC (and associated optional
RK parameters) where the additional DPCs are "alias" point codes for,
say, the first DPC.

But there are other uses for this as well.  For example, the same effect
as cluster routing at the SG could be accomplished by placing all the
DPCs in a cluster in the RK.  Of course, the entire cluster will be
accessible or inaccessible, but that's how cluster routing works.

--brian

On Fri, 17 Jan 2003, Srivats P. wrote:

> Brian,
> 
> In effect, what you are saying is that the OPC List stands as it is
> in the RFC. What has changed is that instead of a single DPC in the
> DPC Parameter, we can have DPC List for an AS which uses Alias Point
> Codes ?
> 
> Srivats
> 
> At 1/17/03 5:58:00 AM, you wrote:
> >Srivats,
> >
> >Section 3.8 of the IG is absurd.
> >
> >It is impossible to specify the OPC without the OPC List parameter.
> >
> >Alias point codes are handled by repeating the DPC and associated
> >routing key parameters again in the list per:
> >
> >      Note: The Destination Point Code, Service Indicators, Originating
> >      Point Code List and Circuit Range List parameters MAY be repeated
> >      as a grouping within the Routing Key parameter, in the structure
> >      shown above.
> >
> >Section 3.8 of the IG should be struck.
> >
> >--brian
> >
> >
> >Srivats P. wrote:                                                                  (Fri, 17 Jan 2003 18:01:01)
> >> Hi,
> >> 
> >> I need a clarification regarding the "OPC List in Registration
> >> Request Message" issue in the M3UA IG.
> >> 
> >> <quote>
> >>     ---------
> >>     New text: (Section 3.6.1)
> >>     ---------
> >> 
> >>     DPC List:
> >> 
> >>     The Destination Point Code List parameter contains one or more SS7
> >>     DPC entries, and its format is the same as the Destination Point Code
> >>     parameter. Multiple DPC values will only be valid in the case of
> >>     Alias Point Code configuration. The absence of the DPC List parameter
> >>     in the Routing Key indicates the use of the DPC value as the only
> >>     posible DPC for the AS.
> >> 
> >>  3.8.3 Solution description
> >> 
> >>     Including the scenario where this parameter is used (Alias point code
> >>     configurations), the problem is solved. The parameter name has also
> >>     be changed to "Destination" since it is the way that the SG sees it.
> >> 
> >> </quote>
> >> 
> >> the OPC List has been renamed as DPC List. So now we have a DPC Parameter
> >> (the point code of the AS which is being registered) and a DPC List (
> >> earlier OPC List) which is a list of SS7 Point Codes from which the AS
> >> can receive messages. Right ?
> >> 
> >> Say, SP A in the SS7 network has alias point codes 1-1-1 and 1-1-2.
> >> ASP X registers an AS (DPC = 3-3-3 and DPC List = 1-1-1, 1-1-2). Now if the
> >> SG receives any message with the DPC value as 3-3-3 in the Routing Label,
> >> it will check the OPC value in the Routing Label to see if it is either
> >> 1-1-1 or 1-1-2, before sending the message to the AS. Right ?
> >> 
> >> What happens if the DPC List (1-1-1, 1-1-2) was not included in the RK ?
> >> According to the IG -
> >> 
> >> "The absence of the DPC List parameter in the Routing Key indicates the 
> >> use of the DPC value as the only posible DPC for the AS."
> >>           ^^^^^^^^^^^
> >> 
> >> Which "DPC value" is being referred to here ? 3-3-3 ? But wasn't it the
> >> same case even when the "DPC List (formerly OPC List)" was included ?
> >> The ONLY point code of the AS was still 3-3-3. What am I misreading here ?
> >> 
> >> Regards,
> >> Srivats
> >> 
> >> _______________________________________________
> >> 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    ¦ 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 Jan 20 02:11: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 CAA12746
	for <sigtran-archive@odin.ietf.org>; Mon, 20 Jan 2003 02:11:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0K7SQn28606
	for sigtran-archive@odin.ietf.org; Mon, 20 Jan 2003 02:28:26 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K7QoJ28569;
	Mon, 20 Jan 2003 02:26:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K7NxJ28056
	for <sigtran@optimus.ietf.org>; Mon, 20 Jan 2003 02:23:59 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11465
	for <sigtran@ietf.org>; Mon, 20 Jan 2003 02:06:31 -0500 (EST)
Subject: Re: [Sigtran] OPC List renamed as DPC List
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF050FAA11.707AD2BA-ONC2256CB4.0026B4C5@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Mon, 20 Jan 2003 09:06:32 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/20/2003
 09:06:35 AM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0K7NxJ28057
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


Brian,
> Srivats,
>
> No.  The entire RFC stays as it stands.  DPC can
> already be repeated
> in the RK.  It is the explanation of the repetition
> which is missing:
> i.e., that one might want to repeat DPC (and
> associated optional
> RK parameters) where the additional DPCs are "alias"
> point codes for,
> say, the first DPC.
>
> But there are other uses for this as well.  For
> example, the same effect
> as cluster routing at the SG could be accomplished
> by placing all the
> DPCs in a cluster in the RK.  Of course, the entire
> cluster will be
> accessible or inaccessible, but that's how cluster
> routing works.
[TOLGA] IMO, this might be problematic. This violates the principle that
one RK should not span SPMC boundaries. For example for DUPU, a cluster RK
wouldn´t be inline with SS7 UPU semantics. UPU from SS7 is received as
response for a specific PC but it would map to a DUPU for the whole
cluster.

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



From mailnull@www1.ietf.org  Mon Jan 20 02:21: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 CAA12868
	for <sigtran-archive@odin.ietf.org>; Mon, 20 Jan 2003 02:21:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0K7cq429829
	for sigtran-archive@odin.ietf.org; Mon, 20 Jan 2003 02:38:52 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K7bQJ29583;
	Mon, 20 Jan 2003 02:37:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K7XsJ29032
	for <sigtran@optimus.ietf.org>; Mon, 20 Jan 2003 02:33:54 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12825
	for <sigtran@ietf.org>; Mon, 20 Jan 2003 02:16:25 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:IlcVCU+gyChBW1dwyDnpDdiEF3/H/XaZ@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0K7JoD28311;
	Mon, 20 Jan 2003 00:19:50 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0K7Joo14757;
	Mon, 20 Jan 2003 00:19:50 -0700
Date: Mon, 20 Jan 2003 00:19:50 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] OPC List renamed as DPC List
Message-ID: <20030120001950.A14737@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF050FAA11.707AD2BA-ONC2256CB4.0026B4C5@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF050FAA11.707AD2BA-ONC2256CB4.0026B4C5@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Mon, Jan 20, 2003 at 09:06:32AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Mon, 20 Jan 2003 09:06:32)
> 
> Brian,
> > Srivats,
> >
> > No.  The entire RFC stays as it stands.  DPC can
> > already be repeated
> > in the RK.  It is the explanation of the repetition
> > which is missing:
> > i.e., that one might want to repeat DPC (and
> > associated optional
> > RK parameters) where the additional DPCs are "alias"
> > point codes for,
> > say, the first DPC.
> >
> > But there are other uses for this as well.  For
> > example, the same effect
> > as cluster routing at the SG could be accomplished
> > by placing all the
> > DPCs in a cluster in the RK.  Of course, the entire
> > cluster will be
> > accessible or inaccessible, but that's how cluster
> > routing works.
> [TOLGA] IMO, this might be problematic. This violates the principle that
> one RK should not span SPMC boundaries. For example for DUPU, a cluster RK
> wouldn´t be inline with SS7 UPU semantics. UPU from SS7 is received as
> response for a specific PC but it would map to a DUPU for the whole
> cluster.

It doesn't cause a problem.  In this case the entire cluster is an SPMC.
It is no different than if all the point codes except one are aliases.

And there is no problem with UPU, if you understand how UPU works.  Each
PC in the cluster would receive UPU if it sent a message to the affected
destination, so there is no problem with them all receiving it.  This is
also the case for "alias" point codes.

--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 Jan 20 02: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 CAA13174
	for <sigtran-archive@odin.ietf.org>; Mon, 20 Jan 2003 02:45:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0K82ki30707
	for sigtran-archive@odin.ietf.org; Mon, 20 Jan 2003 03:02:46 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K80aJ30630;
	Mon, 20 Jan 2003 03:00:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K7u0J30501
	for <sigtran@optimus.ietf.org>; Mon, 20 Jan 2003 02:56:00 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13088
	for <sigtran@ietf.org>; Mon, 20 Jan 2003 02:38:31 -0500 (EST)
Subject: Re: [Sigtran] OPC List renamed as DPC List
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF2EE66947.E3C65648-ONC2256CB4.0028DB1C@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Mon, 20 Jan 2003 09:38:34 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/20/2003
 09:38:37 AM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0K7u0J30502
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


Brian,
> TOLGA,
>
> TOLGA ASVEREN wrote:
>                                 (Mon, 20 Jan 2003
> 09:06:32)
> >
> > Brian,
> > > Srivats,
> > >
> > > No.  The entire RFC stays as it stands.  DPC can
> > > already be repeated
> > > in the RK.  It is the explanation of the
> repetition
> > > which is missing:
> > > i.e., that one might want to repeat DPC (and
> > > associated optional
> > > RK parameters) where the additional DPCs are
> "alias"
> > > point codes for,
> > > say, the first DPC.
> > >
> > > But there are other uses for this as well.  For
> > > example, the same effect
> > > as cluster routing at the SG could be
> accomplished
> > > by placing all the
> > > DPCs in a cluster in the RK.  Of course, the
> entire
> > > cluster will be
> > > accessible or inaccessible, but that's how
> cluster
> > > routing works.
> > [TOLGA] IMO, this might be problematic. This
> violates the principle that
> > one RK should not span SPMC boundaries. For
> example for DUPU, a cluster RK
> > wouldn´t be inline with SS7 UPU semantics. UPU
> from SS7 is received as
> > response for a specific PC but it would map to a
> DUPU for the whole
> > cluster.
>
> It doesn't cause a problem.  In this case the entire
> cluster is an SPMC.
> It is no different than if all the point codes
> except one are aliases.
[TOLGA]IMO a cluster RK and a RK with multiple alias point codes are
different things. With cluster RKs, we have PCs, whose user parts are
totally independent from functional point of view. IMO cluster RKs are
violation of the key principle that RKs shouldn´t span SPMC.
>
> And there is no problem with UPU, if you understand
> how UPU works.  Each
> PC in the cluster would receive UPU if it sent a
> message to the affected
> destination, so there is no problem with them all
> receiving it.  This is
> also the case for "alias" point codes.
[TOLGA] What happens if only one PC in the cluster sends a message to the
affected destination? Because DUPU would be sent for the whole RK, I would
consider this a violation of the UPU semantic of SS7.

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



From mailnull@www1.ietf.org  Mon Jan 20 03:04: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 DAA13474
	for <sigtran-archive@odin.ietf.org>; Mon, 20 Jan 2003 03:04:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0K8LAc32055
	for sigtran-archive@odin.ietf.org; Mon, 20 Jan 2003 03:21:10 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K8JnJ31919;
	Mon, 20 Jan 2003 03:19:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K859J30878
	for <sigtran@optimus.ietf.org>; Mon, 20 Jan 2003 03:05:09 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13193
	for <sigtran@ietf.org>; Mon, 20 Jan 2003 02:47:42 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0K7p5BS008151;
	Mon, 20 Jan 2003 01:51:05 -0600 (CST)
Received: from sun3271.ssd.usa.alcatel.com (sun3271.ssd.usa.alcatel.com [143.209.151.211])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0K7n6M18260;
	Mon, 20 Jan 2003 01:49:07 -0600 (CST)
Date: Mon, 20 Jan 2003 01:49:06 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: "Srivats P." <srivats@india.mercurykr.com>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA IG: Response to an ASPIA msg
In-Reply-To: <20030117060955.E1767@openss7.org>
Message-ID: <Pine.SOL.4.10.10301200139540.12888-100000@sun3271.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,

So RC is mantatory in ASPIA when ASP1 serves more than one AS over a
single association. If it is not a mantatory field then one always
will receive Error Code = "No Configured AS for ASP"(if he has not
understood the below sentence properly

 3.10.2 (IG)
       - If the RC is missing and its specification is needed according
          to the used configuration, the peer must respond with an ERROR
          message with Error Code = "No Configured AS for ASP".


--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, 17 Jan 2003, Brian F. G. Bidulock wrote:

> Srivats,
> 
> Srivats P. wrote:                                                                  (Fri, 17 Jan 2003 18:21:41)
> > Hi,
> > 
> > The "Response to an ASPIA message" issue in the M3UA IG
> > states that -
> > 
> > <quote>
> >     ---------
> >     New text: (Section 4.5.3)
> >     ---------
> > 
> >     When an ASP wishes to withdraw from receiving traffic within an AS,or
> >     the ASP wants to initiate the process of activation, the ASP sends an
> >     ASP Inactive message to the SGP or IPSP.
> > 
> >     An ASP Inactive message MUST be always responded by the peer
> >     (although other messages may be sent in the middle):
> >        - If the corresponding RK is registered (statically or
> >           dynamically), the peer should respond with an ASP Inactive Ack
> >           message.
> >        -           If the RK is not registered, or the RC information is not valid,
> >           the peer must respond with an ERROR message with Error Code =
> >           "Invalid Routing Context".
> >        - If the RC is missing and its specification is needed according
> >           to the used configuration, the peer must respond with an ERROR
> >           message with Error Code = "No Configured AS for ASP".
> > </quote>
> > 
> > I couldn't quite understand what is meant by "If the RC is missing and its
> > specification is needed according to the used configuration" - does it mean
> > that the missing RC indicates "all AS served by ASP" and if there is no
> > such AS for the said ASP, it sends ERROR("No configured AS for ASP") ?
> 
> RC is optional when an assocation serves a single AS.  If RC is missing and
> there is no single AS that the association serves, then it is missing in
> error.
> 
> --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 mailnull@www1.ietf.org  Mon Jan 20 03:07: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 DAA13514
	for <sigtran-archive@odin.ietf.org>; Mon, 20 Jan 2003 03:07:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0K8Nvf32199
	for sigtran-archive@odin.ietf.org; Mon, 20 Jan 2003 03:23:57 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K8NkJ32171;
	Mon, 20 Jan 2003 03:23:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K8KYJ32020
	for <sigtran@optimus.ietf.org>; Mon, 20 Jan 2003 03:20:34 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13457
	for <sigtran@ietf.org>; Mon, 20 Jan 2003 03:03:06 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:lHB4V+ukkIQr0qBQ7Ar4ZWkn29brxT0t@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0K86UD28890;
	Mon, 20 Jan 2003 01:06:30 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0K86UQ15457;
	Mon, 20 Jan 2003 01:06:30 -0700
Date: Mon, 20 Jan 2003 01:06:29 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: "Srivats P." <srivats@india.mercurykr.com>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA IG: Response to an ASPIA msg
Message-ID: <20030120010629.B15126@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	"Srivats P." <srivats@india.mercurykr.com>,
	sigtran <sigtran@ietf.org>
References: <20030117060955.E1767@openss7.org> <Pine.SOL.4.10.10301200139540.12888-100000@sun3271.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.10301200139540.12888-100000@sun3271.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Mon, Jan 20, 2003 at 01:49:06AM -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,

See my comments on the IG for this section: it is redundant in places,
wrong in places, and more confusing that it is worth.  I proposed that
Section 3.10 be struck.

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Mon, 20 Jan 2003 01:49:06)
> 
> Brian,
> 
> So RC is mantatory in ASPIA when ASP1 serves more than one AS over a
> single association. If it is not a mantatory field then one always
> will receive Error Code = "No Configured AS for ASP"(if he has not
> understood the below sentence properly
> 
>  3.10.2 (IG)
>        - If the RC is missing and its specification is needed according
>           to the used configuration, the peer must respond with an ERROR
>           message with Error Code = "No Configured AS for ASP".
> 
> 
> --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, 17 Jan 2003, Brian F. G. Bidulock wrote:
> 
> > Srivats,
> > 
> > Srivats P. wrote:                                                                  (Fri, 17 Jan 2003 18:21:41)
> > > Hi,
> > > 
> > > The "Response to an ASPIA message" issue in the M3UA IG
> > > states that -
> > > 
> > > <quote>
> > >     ---------
> > >     New text: (Section 4.5.3)
> > >     ---------
> > > 
> > >     When an ASP wishes to withdraw from receiving traffic within an AS,or
> > >     the ASP wants to initiate the process of activation, the ASP sends an
> > >     ASP Inactive message to the SGP or IPSP.
> > > 
> > >     An ASP Inactive message MUST be always responded by the peer
> > >     (although other messages may be sent in the middle):
> > >        - If the corresponding RK is registered (statically or
> > >           dynamically), the peer should respond with an ASP Inactive Ack
> > >           message.
> > >        -           If the RK is not registered, or the RC information is not valid,
> > >           the peer must respond with an ERROR message with Error Code =
> > >           "Invalid Routing Context".
> > >        - If the RC is missing and its specification is needed according
> > >           to the used configuration, the peer must respond with an ERROR
> > >           message with Error Code = "No Configured AS for ASP".
> > > </quote>
> > > 
> > > I couldn't quite understand what is meant by "If the RC is missing and its
> > > specification is needed according to the used configuration" - does it mean
> > > that the missing RC indicates "all AS served by ASP" and if there is no
> > > such AS for the said ASP, it sends ERROR("No configured AS for ASP") ?
> > 
> > RC is optional when an assocation serves a single AS.  If RC is missing and
> > there is no single AS that the association serves, then it is missing in
> > error.
> > 
> > --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 mailnull@www1.ietf.org  Mon Jan 20 03:11: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 DAA13621
	for <sigtran-archive@odin.ietf.org>; Mon, 20 Jan 2003 03:11:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0K8S1W32380
	for sigtran-archive@odin.ietf.org; Mon, 20 Jan 2003 03:28:01 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K8QUJ32310;
	Mon, 20 Jan 2003 03:26:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K8J1J31892
	for <sigtran@optimus.ietf.org>; Mon, 20 Jan 2003 03:19:01 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13432
	for <sigtran@ietf.org>; Mon, 20 Jan 2003 03:01:34 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:9Qx7p6iGRskOorySMMLI4Sk312oJU7T8@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0K84wD28866;
	Mon, 20 Jan 2003 01:04:58 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0K84vr15440;
	Mon, 20 Jan 2003 01:04:57 -0700
Date: Mon, 20 Jan 2003 01:04:57 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] OPC List renamed as DPC List
Message-ID: <20030120010457.A15126@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF2EE66947.E3C65648-ONC2256CB4.0028DB1C@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF2EE66947.E3C65648-ONC2256CB4.0028DB1C@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Mon, Jan 20, 2003 at 09:38:34AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Mon, 20 Jan 2003 09:38:34)
> 
> Brian,
> > TOLGA,
> >
> > TOLGA ASVEREN wrote:
> >                                 (Mon, 20 Jan 2003
> > 09:06:32)
> > >
> > > Brian,
> > > > Srivats,
> > > >
> > > > No.  The entire RFC stays as it stands.  DPC can
> > > > already be repeated
> > > > in the RK.  It is the explanation of the
> > repetition
> > > > which is missing:
> > > > i.e., that one might want to repeat DPC (and
> > > > associated optional
> > > > RK parameters) where the additional DPCs are
> > "alias"
> > > > point codes for,
> > > > say, the first DPC.
> > > >
> > > > But there are other uses for this as well.  For
> > > > example, the same effect
> > > > as cluster routing at the SG could be
> > accomplished
> > > > by placing all the
> > > > DPCs in a cluster in the RK.  Of course, the
> > entire
> > > > cluster will be
> > > > accessible or inaccessible, but that's how
> > cluster
> > > > routing works.
> > > [TOLGA] IMO, this might be problematic. This
> > violates the principle that
> > > one RK should not span SPMC boundaries. For
> > example for DUPU, a cluster RK
> > > wouldn´t be inline with SS7 UPU semantics. UPU
> > from SS7 is received as
> > > response for a specific PC but it would map to a
> > DUPU for the whole
> > > cluster.
> >
> > It doesn't cause a problem.  In this case the entire
> > cluster is an SPMC.
> > It is no different than if all the point codes
> > except one are aliases.
> [TOLGA]IMO a cluster RK and a RK with multiple alias point codes are
> different things. With cluster RKs, we have PCs, whose user parts are
> totally independent from functional point of view.

Not necessarily.

> IMO cluster RKs are violation of the key principle that RKs shouldn´t span
> SPMC.

They don't span the SPMC if the *are* the SPMC.

> >
> > And there is no problem with UPU, if you understand
> > how UPU works.  Each
> > PC in the cluster would receive UPU if it sent a
> > message to the affected
> > destination, so there is no problem with them all
> > receiving it.  This is
> > also the case for "alias" point codes.
> [TOLGA] What happens if only one PC in the cluster sends a message to the
> affected destination? Because DUPU would be sent for the whole RK, I would
> consider this a violation of the UPU semantic of SS7.

Then you don't understand UPU semantics:  See Clause 11/Q.704.  In this
case, the entire cluster has one "local user."  So, the MTP-STATUS is always
delivered to the correct user and there is no problem.

--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 Jan 20 03:27: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 DAA13855
	for <sigtran-archive@odin.ietf.org>; Mon, 20 Jan 2003 03:27:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0K8ieh01359
	for sigtran-archive@odin.ietf.org; Mon, 20 Jan 2003 03:44:40 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K8hGJ01269;
	Mon, 20 Jan 2003 03:43:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K8djJ01076
	for <sigtran@optimus.ietf.org>; Mon, 20 Jan 2003 03:39:45 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13743
	for <sigtran@ietf.org>; Mon, 20 Jan 2003 03:22:16 -0500 (EST)
Subject: Re: [Sigtran] OPC List renamed as DPC List
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFD8F77FB8.CAB6FD3E-ONC2256CB4.002D6763@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Mon, 20 Jan 2003 10:22:18 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/20/2003
 10:22:19 AM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0K8djJ01077
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


Brian,
> TOLGA,
>
> TOLGA ASVEREN wrote:
>                                 (Mon, 20 Jan 2003
> 09:38:34)
> >
> > Brian,
> > > TOLGA,
> > >
> > > TOLGA ASVEREN wrote:
> > >                                 (Mon, 20 Jan
> 2003
> > > 09:06:32)
> > > >
> > > > Brian,
> > > > > Srivats,
> > > > >
> > > > > No.  The entire RFC stays as it stands.  DPC
> can
> > > > > already be repeated
> > > > > in the RK.  It is the explanation of the
> > > repetition
> > > > > which is missing:
> > > > > i.e., that one might want to repeat DPC (and
> > > > > associated optional
> > > > > RK parameters) where the additional DPCs are
> > > "alias"
> > > > > point codes for,
> > > > > say, the first DPC.
> > > > >
> > > > > But there are other uses for this as well.
> For
> > > > > example, the same effect
> > > > > as cluster routing at the SG could be
> > > accomplished
> > > > > by placing all the
> > > > > DPCs in a cluster in the RK.  Of course, the
> > > entire
> > > > > cluster will be
> > > > > accessible or inaccessible, but that's how
> > > cluster
> > > > > routing works.
> > > > [TOLGA] IMO, this might be problematic. This
> > > violates the principle that
> > > > one RK should not span SPMC boundaries. For
> > > example for DUPU, a cluster RK
> > > > wouldn´t be inline with SS7 UPU semantics. UPU
> > > from SS7 is received as
> > > > response for a specific PC but it would map to
> a
> > > DUPU for the whole
> > > > cluster.
> > >
> > > It doesn't cause a problem.  In this case the
> entire
> > > cluster is an SPMC.
> > > It is no different than if all the point codes
> > > except one are aliases.
> > [TOLGA]IMO a cluster RK and a RK with multiple
> alias point codes are
> > different things. With cluster RKs, we have PCs,
> whose user parts are
> > totally independent from functional point of view.
>
> Not necessarily.
>
> > IMO cluster RKs are violation of the key principle
> that RKs shouldn´t span
> > SPMC.
>
> They don't span the SPMC if the *are* the SPMC.
[TOLGA] IMO, it is not correct to think all of the cluster PCs as one SPMC.
>
> > >
> > > And there is no problem with UPU, if you
> understand
> > > how UPU works.  Each
> > > PC in the cluster would receive UPU if it sent a
> > > message to the affected
> > > destination, so there is no problem with them
> all
> > > receiving it.  This is
> > > also the case for "alias" point codes.
> > [TOLGA] What happens if only one PC in the cluster
> sends a message to the
> > affected destination? Because DUPU would be sent
> for the whole RK, I would
> > consider this a violation of the UPU semantic of
> SS7.
>
> Then you don't understand UPU semantics:  See Clause
> 11/Q.704.  In this
> case, the entire cluster has one "local user."  So,
> the MTP-STATUS is always
> delivered to the correct user and there is no
> problem.
[TOLGA]I disagree that user parts of cluster PCs can be seen as "one local
user". They are separate entities for the general case. So, I would expect
that only the user part of the PC, which sent the message to the affected
PC should be informed with MTP-STATUS. DUPU does not contain (correctly)
any additional info than RC to distribute the message on ASP side.

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



From mailnull@www1.ietf.org  Mon Jan 20 03: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 DAA14282
	for <sigtran-archive@odin.ietf.org>; Mon, 20 Jan 2003 03:50:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0K97RU03051
	for sigtran-archive@odin.ietf.org; Mon, 20 Jan 2003 04:07:27 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K95tJ02576;
	Mon, 20 Jan 2003 04:05:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K8uNJ01866
	for <sigtran@optimus.ietf.org>; Mon, 20 Jan 2003 03:56:23 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14091
	for <sigtran@ietf.org>; Mon, 20 Jan 2003 03:38:54 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:sdeAANW9dCQt4mXFBriWgZz3F4pvpROu@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0K8gID29397;
	Mon, 20 Jan 2003 01:42:18 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0K8gIX15953;
	Mon, 20 Jan 2003 01:42:18 -0700
Date: Mon, 20 Jan 2003 01:42:17 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] OPC List renamed as DPC List
Message-ID: <20030120014217.A15938@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OFD8F77FB8.CAB6FD3E-ONC2256CB4.002D6763@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OFD8F77FB8.CAB6FD3E-ONC2256CB4.002D6763@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Mon, Jan 20, 2003 at 10:22:18AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Mon, 20 Jan 2003 10:22:18)
> 
> Brian,
> > TOLGA,
> >
> > TOLGA ASVEREN wrote:
> >                                 (Mon, 20 Jan 2003
> > 09:38:34)
> > >
> > > Brian,
> > > > TOLGA,
> > > >
> > > > TOLGA ASVEREN wrote:
> > > >                                 (Mon, 20 Jan
> > 2003
> > > > 09:06:32)
> > > > >
> > > > > Brian,
> > > > > > Srivats,
> > > > > >
> > > > > > No.  The entire RFC stays as it stands.  DPC
> > can
> > > > > > already be repeated
> > > > > > in the RK.  It is the explanation of the
> > > > repetition
> > > > > > which is missing:
> > > > > > i.e., that one might want to repeat DPC (and
> > > > > > associated optional
> > > > > > RK parameters) where the additional DPCs are
> > > > "alias"
> > > > > > point codes for,
> > > > > > say, the first DPC.
> > > > > >
> > > > > > But there are other uses for this as well.
> > For
> > > > > > example, the same effect
> > > > > > as cluster routing at the SG could be
> > > > accomplished
> > > > > > by placing all the
> > > > > > DPCs in a cluster in the RK.  Of course, the
> > > > entire
> > > > > > cluster will be
> > > > > > accessible or inaccessible, but that's how
> > > > cluster
> > > > > > routing works.
> > > > > [TOLGA] IMO, this might be problematic. This
> > > > violates the principle that
> > > > > one RK should not span SPMC boundaries. For
> > > > example for DUPU, a cluster RK
> > > > > wouldn´t be inline with SS7 UPU semantics. UPU
> > > > from SS7 is received as
> > > > > response for a specific PC but it would map to
> > a
> > > > DUPU for the whole
> > > > > cluster.
> > > >
> > > > It doesn't cause a problem.  In this case the
> > entire
> > > > cluster is an SPMC.
> > > > It is no different than if all the point codes
> > > > except one are aliases.
> > > [TOLGA]IMO a cluster RK and a RK with multiple
> > alias point codes are
> > > different things. With cluster RKs, we have PCs,
> > whose user parts are
> > > totally independent from functional point of view.
> >
> > Not necessarily.
> >
> > > IMO cluster RKs are violation of the key principle
> > that RKs shouldn´t span
> > > SPMC.
> >
> > They don't span the SPMC if the *are* the SPMC.
> [TOLGA] IMO, it is not correct to think all of the cluster PCs as one SPMC.

It can be.

> >
> > > >
> > > > And there is no problem with UPU, if you
> > understand
> > > > how UPU works.  Each
> > > > PC in the cluster would receive UPU if it sent a
> > > > message to the affected
> > > > destination, so there is no problem with them
> > all
> > > > receiving it.  This is
> > > > also the case for "alias" point codes.
> > > [TOLGA] What happens if only one PC in the cluster
> > sends a message to the
> > > affected destination? Because DUPU would be sent
> > for the whole RK, I would
> > > consider this a violation of the UPU semantic of
> > SS7.
> >
> > Then you don't understand UPU semantics:  See Clause
> > 11/Q.704.  In this
> > case, the entire cluster has one "local user."  So,
> > the MTP-STATUS is always
> > delivered to the correct user and there is no
> > problem.
> [TOLGA]I disagree that user parts of cluster PCs can be seen as "one local
> user". They are separate entities for the general case. So, I would expect
> that only the user part of the PC, which sent the message to the affected
> PC should be informed with MTP-STATUS. DUPU does not contain (correctly)
> any additional info than RC to distribute the message on ASP side.

You are making assumptions.  It can be one user part.

--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 Jan 20 04:03: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 EAA14428
	for <sigtran-archive@odin.ietf.org>; Mon, 20 Jan 2003 04:03:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0K9KTF03870
	for sigtran-archive@odin.ietf.org; Mon, 20 Jan 2003 04:20:29 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K9IsJ03774;
	Mon, 20 Jan 2003 04:18:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0K9F4J03663
	for <sigtran@optimus.ietf.org>; Mon, 20 Jan 2003 04:15:04 -0500
Received: from ganesh.ctd.hctech.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14343
	for <sigtran@ietf.org>; Mon, 20 Jan 2003 03:57:34 -0500 (EST)
Received: by GANESH with Internet Mail Service (5.5.2653.19)
	id <DBDMXVHH>; Mon, 20 Jan 2003 14:32:15 +0530
Message-ID: <55E277B99171E041ABF5F4B1C6DDCA06011DEDB1@haritha.hclt.com>
From: "Vishwanatham Mallik - CTD, Chennai." <pvmallik@ctd.hcltech.com>
To: sigtran@ietf.org
Subject:  [Sigtran] pls. UNSUBSCRIBE me from the mailing list.
Date: Mon, 20 Jan 2003 14:33:17 +0530
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>

Could somebody here UNSUBSCRIBE me from SIGTRAN mailing list pls.

Thanks in advance,
Mallik

-----Original Message-----
From: Vishwanatham Mallik - CTD, Chennai.
[mailto:pvmallik@ctd.hcltech.com]
Sent: 14 January 2003 12:52 PM
To: sigtran@ietf.org
Subject: [Sigtran] pls. UNSUBSCRIBE me from the mailing list.


Can somebody here unsubscribe me from the SIGTRAN mailing list.

Regards,
Mallik
_______________________________________________
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 Jan 20 09:06: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 JAA20512
	for <sigtran-archive@odin.ietf.org>; Mon, 20 Jan 2003 09:06:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0KEN8422102
	for sigtran-archive@odin.ietf.org; Mon, 20 Jan 2003 09:23:08 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0KEMhJ22080;
	Mon, 20 Jan 2003 09:22:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0KELtJ22030
	for <sigtran@optimus.ietf.org>; Mon, 20 Jan 2003 09:21:55 -0500
Received: from hindon.hss.co.in (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20464
	for <sigtran@ietf.org>; Mon, 20 Jan 2003 09:04:15 -0500 (EST)
From: kakaul@hss.hns.com
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 h0KE6Nj23270
	for <sigtran@ietf.org>; Mon, 20 Jan 2003 19:36:23 +0530 (IST)
Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h0KE6LM23264
	for <sigtran@ietf.org>; Mon, 20 Jan 2003 19:36:21 +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 SMTP id h0KE8Zw29384
	for <sigtran@ietf.org>; Mon, 20 Jan 2003 19:38:35 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256CB4.004CECA7 ; Mon, 20 Jan 2003 19:30:13 +0530
X-Lotus-FromDomain: HSS
To: sigtran@ietf.org
Message-ID: <65256CB4.004CEAD4.00@sandesh.hss.hns.com>
Date: Mon, 20 Jan 2003 19:33:01 +0530
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Sigtran] I-D ACTION:draft-kamesh-m3ua-congestion-procedures-00.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>





A New Internet-Draft is available from the on-line Internet-Drafts directories.


     Title          : M3UA Congestion procedures
     Author(s) : K. Kaul
     Filename  : draft-kamesh-m3ua-congestion-procedures-00.txt
     Pages          : 17
     Date      : 2003-1-15

This Internet-Draft describes congestion procedures applicable for both
M3UA ASP and SG nodes. Draft explains all the procedures needed by
M3UA ASP and SG to handle local and network congestion communicated
between M3UA SG and ASP through SSNM messages. Congestion
procedures proposed are in line with MTP3 Q.704 with some alteration to
suit sigtran architecture.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-kamesh-m3ua-congestion-procedures-00.txt













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  Tue Jan 21 07:57: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 HAA27902
	for <sigtran-archive@odin.ietf.org>; Tue, 21 Jan 2003 07:57:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0LDFHE15279
	for sigtran-archive@odin.ietf.org; Tue, 21 Jan 2003 08:15:17 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LDCwJ15125;
	Tue, 21 Jan 2003 08:14:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LDAsJ14945
	for <sigtran@optimus.ietf.org>; Tue, 21 Jan 2003 08:10:54 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27713;
	Tue, 21 Jan 2003 07:52:50 -0500 (EST)
Message-Id: <200301211252.HAA27713@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: Tue, 21 Jan 2003 07:52:50 -0500
Subject: [Sigtran] I-D ACTION:draft-ietf-sigtran-m2pa-07.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 MTP2-User Peer-to-Peer Adaptation Layer
	Author(s)	: T. George et al.
	Filename	: draft-ietf-sigtran-m2pa-07.txt
	Pages		: 55
	Date		: 2003-1-20
	
This Internet Draft defines a protocol supporting the transport of
Signaling System Number 7 (SS7) Message Transfer Part (MTP) Layer 3
signaling messages over Internet Protocol (IP) using the services of
the Stream Control Transmission Protocol (SCTP).  This protocol would
be used between SS7 Signaling Points employing the MTP Level 3
protocol. The SS7 Signaling Points may also employ standard SS7 links
using the SS7 MTP Layer 2 to provide transport of MTP Layer 3
signaling messages.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m2pa-07.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-m2pa-07.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-m2pa-07.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-1-20131807.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sigtran-m2pa-07.txt

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

Content-Type: text/plain
Content-ID:	<2003-1-20131807.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 Jan 21 10:49: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 KAA03065
	for <sigtran-archive@odin.ietf.org>; Tue, 21 Jan 2003 10:49:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0LG7Cs27076
	for sigtran-archive@odin.ietf.org; Tue, 21 Jan 2003 11:07:12 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LG6dJ26820;
	Tue, 21 Jan 2003 11:06:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LFqNJ25951
	for <sigtran@optimus.ietf.org>; Tue, 21 Jan 2003 10:52:23 -0500
Received: from mx1.etsi.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02626
	for <sigtran@ietf.org>; Tue, 21 Jan 2003 10:34:15 -0500 (EST)
Received: from email10.etsihq.org ([172.27.1.62]) by mx1.etsi.org with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 21 Jan 2003 16:38:35 +0100
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="Windows-1252"
Date: Tue, 21 Jan 2003 16:38:34 +0100
Message-ID: <4091553999CBE4409CC2B562152B5A33EDDF4C@email10.etsihq.org>
Thread-Topic: SUA 14 editorial suggestions
Thread-Index: AcLBYyh/KUPp+q/ySw6iZQLbZ6jGDw==
From: "Richard Adams" <Richard.Adams@etsi.org>
To: <john.loughney@nokia.com>
Cc: <sigtran@ietf.org>
X-OriginalArrivalTime: 21 Jan 2003 15:38:35.0171 (UTC) FILETIME=[28E36730:01C2C163]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0LFqNJ25952
Subject: [Sigtran] SUA 14 editorial suggestions
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

John,
If I repeat editorial suggestions already made, then I apologise! If there is still time, here are the editorials I found.

Section 1 Introduction
 Replace one of the [ANSI SCCP] references with [ITU SCCP].
 Replace i.e. with e.g. in the parentheses, since the list isn't complete.
 And SCCP user _messages_ are transported between two signalling endpoints.

Old text:
This draft defines a protocol for the transport SS7 SCCP [ANSI SCCP]
   [ANSI SCCP] Users (i.e. TCAP, RANAP, etc.) signalling messages over
   IP using the Stream Control Transmission Protocol (SCTP) [2960].
   This protocol would be used between a Signalling Gateway (SG) and
   Signaling Endpoint located in an IP network.  Additionally, the
   protocol can be used to transport SS7 SCCP users between two
   signaling endpoints located within an IP network.

New text:
This draft defines a protocol for the transport SS7 SCCP [ANSI SCCP]
   [ITU SCCP] Users (e.g. TCAP, RANAP, etc.) signalling messages over
   IP using the Stream Control Transmission Protocol (SCTP) [2960].
   This protocol would be used between a Signalling Gateway (SG) and
   Signaling Endpoint located in an IP network.  Additionally, the
   protocol can be used to transport SS7 SCCP user messages between two
   signaling endpoints located within an IP network.

Subsection 1.2 Terminology
Need to add a definition of Network Appearance. I suggest a modified form of
M3UA's.

Old text:
None.

New Text:
Network Appearance - The Network Appearance is an SUA local reference
(typically an integer) shared by SG and AS that together with a Signalling
Point Code or global title uniquely identifies an SS7 node by indicating the
specific SS7 network it belongs to.

Subsection 1.3.1.2 SG as relay-point
Global Title Translation in SCCP yields an "entity set", not an "entity".

Old text:
A Global Title translation is executed at the SG, before the
   destination of the message can be determined.  The actual location
   of the SCCP-user is irrelevant to the SS7 network.  GT Translation
   yields an "SCCP entity", from an AS can be derived.  Selection of
   the AS is thus based on the SCCP called party address  (and possibly
   other SS7 parameters depending on the implementation).

New text:
A Global Title translation is executed at the SG, before the
   destination of the message can be determined.  The actual location
   of the SCCP-user is irrelevant to the SS7 network.  GT Translation
   yields an "SCCP entity set", from which an AS can be derived.
   Selection of the AS is thus based on the SCCP called party address
   (and possibly other SS7 parameters depending on the implementation).

Subsection 1.4.4 Interworking with SCCP Network Management Functions
The latest ITU Q.711 is for 2001, and since the references don't mention the
date, this is the one implied, I think.
N-STATE is defined in ITU Q.711 clause 6.3.2.3.2 Table 16/Q.711.
N-PCSTATE is defined in ITU Q.711 clause 6.3.2.3.3 Table 17/Q.711.
N-COORD is defined in ITU Q.711 clause 6.3.2.3.1 Table 15/Q.711.
I haven't looked at the ANSI references.
Old text:

   Generic   |Specific   |
   Name      |Name       |ANSI/ITU Reference
      ----------+-----------+---------------------------------------------
   N-State   |Request    |ITU-Q.711   Chap 6.3.2.3.2 (Tab 14/Q.711)
             |Indication |ANSI-T1.112 Chap 2.3.2.3.2 (Tab 8E/T1.112.1)
   ----------+-----------+---------------------------------------------
   N-Pcstate |Indication |ITU-Q.711   Chap 6.3.2.3.3 (Tab 15/Q.711)
             |           |ANSI-T1.112 Chap 2.3.2.3.4 (Tab 8G/T1.112.1)
   N-Coord   |Request    |ITU-Q.711   Chap 6.3.2.3.1 (Tab 13/Q.711)
             |Indication |ANSI-T1.112 Chap 2.3.2.3.3 (Tab 8F/T1.112.1)
             |Response   |
             |Confirm    |
New text:

   Generic   |Specific   |
   Name      |Name       |ANSI/ITU Reference
   ----------+-----------+---------------------------------------------
   N-STATE   |Request    |ITU-Q.711   Chap 6.3.2.3.2 (Tab 16/Q.711)
             |Indication |ANSI-T1.112 Chap 2.3.2.3.2 (Tab 8E/T1.112.1)
   ----------+-----------+---------------------------------------------
   N-PCSTATE |Indication |ITU-Q.711   Chap 6.3.2.3.3 (Tab 17/Q.711)
             |           |ANSI-T1.112 Chap 2.3.2.3.4 (Tab 8G/T1.112.1)
   ----------+-----------+---------------------------------------------
   N-COORD   |Request    |ITU-Q.711   Chap 6.3.2.3.1 (Tab 15/Q.711)
             |Indication |ANSI-T1.112 Chap 2.3.2.3.3 (Tab 8F/T1.112.1)
             |Response   |
             |Confirm    |

Subsection 1.5.1 Address Mapping at the SG
Replace occurrences of "t(r)""by "T(r)" to make this consistent with other
UAs and section 4.3.4.4.

Old text:
   Normally, one or more ASPs are active in the AS (i.e., currently
   processing traffic) but in certain failure and transition cases it
   is possible that there may not be an active ASP available. The SGP
   will buffer the message destined for this AS for a time t(r) or
   until an ASP becomes available. When no ASP becomes available before
   expiry of t(r), the SGP will flush the buffered messages and
   initiate the appropriate return or refusal procedures.


New text:
   Normally, one or more ASPs are active in the AS (i.e., currently
   processing traffic) but in certain failure and transition cases it
   is possible that there may not be an active ASP available. The SGP
   will buffer the message destined for this AS for a time T(r) or
   until an ASP becomes available. When no ASP becomes available before
   expiry of T(r), the SGP will flush the buffered messages and
   initiate the appropriate return or refusal procedures.

Subsection 1.6.1 Definition of the upper boundary
N-INFORM is defined in [ITU Q711] clause 6.1.1.3.2 Table 8/Q.711.
N-UNIT DATA is defined in [ITU Q711] clause 6.2.2.3.1 Table 12/Q.711.
N-NOTICE is defined in [ITU Q711] clause 6.2.2.3.2 Table 13/Q.711.
I haven't checked the ANSI references, and don't have them with me.
Also, the User at the ASP needs to be informed of SS7 network
availability/unavailability and congestion, so that it can modify the
traffic it offers, and give permission or not for subsystem state changes.
That is why the N-COORD, N-STATE and N-PCSTATE primitives are defined in
ITU - they are between the SCCP and its Users. ITU Q.711 clause 6.3.2 Tables
14/Q.711, 15/Q.711, 16/Q.711 and 17/Q.711. So they need to be added here.

Old text:
   The following primitives are supported between the SUA and an SCCP-
   user (a reference to ITU and ANSI sections where these primitives
   and corresponding parameters are described, is also given):

   Generic     |Specific  |
   Name        |Name      |ANSI/ITU Reference
   ------------+----------+-------------------------------------------
   N-Connect   |Request   |ITU-Q.711   Chap 6.1.1.2.2 (Tab 2/Q.711)
               |Indication|ANSI-T1.112 Chap 2.1.1.2.2 (Tab 2/T1.112.1)
               |Response  |
               |Confirm   |
   ------------+----------+-------------------------------------------
   N-Data      |Request   |ITU-Q.711   Chap 6.1.1.2.3 (Tab 3/Q.711)
               |Indication|ANSI-T1.112 Chap 2.1.1.2.3 (Tab 3/T1.112.1)
   ------------+----------+-------------------------------------------
   N-Expedited |Request   |ITU-Q.711   Chap 6.1.1.2.3 (Tab 4/Q.711)
   Data        |Indication|ANSI-T1.112 Chap 2.1.1.2.3 (Tab 4/T1.112.1)
   ------------+----------+-------------------------------------------
   N-Reset     |Request   |ITU-Q.711   Chap 6.1.1.2.3 (Tab 5/Q.711)
               |Indication|ANSI-T1.112 Chap 2.1.1.2.3 (Tab 5/T1.112.1)
               |Response  |
               |Confirm   |
   ------------+----------+-------------------------------------------
   N-Disconnect|Request   |ITU-Q.711   Chap 6.1.1.2.4 (Tab 6/Q.711)
               |Indication|ANSI-T1.112 Chap 2.1.1.2.4 (Tab 6/T1.112.1)
   ------------+----------+-------------------------------------------
   N-Inform    |Request   |ITU-Q.711   Chap 6.1.1.3.1 (Tab 7/Q.711)
               |Indication|ANSI-T1.112 Chap 2.1.1.2.5 (Tab 6A/T1.112.1)
   ------------+----------+-------------------------------------------
   N-Unit Data |Request   |ITU-Q.711   Chap 6.2.2.3.1 (Tab 10/Q.711)
               |Indication|ANSI-T1.112 Chap 2.2.2.3.1 (Tab 8A/T1.112.1)
   ------------+----------+-------------------------------------------
   N-Notice    |Indication|ITU-Q.711   Chap 6.2.2.3.2 (Tab 11/Q.711)
               |          |ANSI-T1.112 Chap 2.2.2.3.2 (Tab 8B/T1.112.1)

New text:
   The following primitives are supported between the SUA and an SCCP-
   user (a reference to ITU and ANSI sections where these primitives
   and corresponding parameters are described, is also given):

   Generic     |Specific  |
   Name        |Name      |ANSI/ITU Reference
   ------------+----------+-------------------------------------------
   N-CONNECT   |Request   |ITU-Q.711   Chap 6.1.1.2.2 (Tab 2/Q.711)
               |Indication|ANSI-T1.112 Chap 2.1.1.2.2 (Tab 2/T1.112.1)
               |Response  |
               |Confirm   |
   ------------+----------+-------------------------------------------
   N-DATA      |Request   |ITU-Q.711   Chap 6.1.1.2.3 (Tab 3/Q.711)
               |Indication|ANSI-T1.112 Chap 2.1.1.2.3 (Tab 3/T1.112.1)
   ------------+----------+-------------------------------------------
   N-EXPEDITED |Request   |ITU-Q.711   Chap 6.1.1.2.3 (Tab 4/Q.711)
   DATA        |Indication|ANSI-T1.112 Chap 2.1.1.2.3 (Tab 4/T1.112.1)
   ------------+----------+-------------------------------------------
   N-RESET     |Request   |ITU-Q.711   Chap 6.1.1.2.3 (Tab 5/Q.711)
               |Indication|ANSI-T1.112 Chap 2.1.1.2.3 (Tab 5/T1.112.1)
               |Response  |
               |Confirm   |
   ------------+----------+-------------------------------------------
   N-DISCONNECT|Request   |ITU-Q.711   Chap 6.1.1.2.4 (Tab 6/Q.711)
               |Indication|ANSI-T1.112 Chap 2.1.1.2.4 (Tab 6/T1.112.1)
   ------------+----------+-------------------------------------------
   N-INFORM    |Request   |ITU-Q.711   Chap 6.1.1.3.2 (Tab 8/Q.711)
               |Indication|ANSI-T1.112 Chap 2.1.1.2.5 (Tab 6A/T1.112.1)
   ------------+----------+-------------------------------------------
   N-UNITDATA  |Request   |ITU-Q.711   Chap 6.2.2.3.1 (Tab 12/Q.711)
               |Indication|ANSI-T1.112 Chap 2.2.2.3.1 (Tab 8A/T1.112.1)
   ------------+----------+-------------------------------------------
   N-NOTICE    |Indication|ITU-Q.711   Chap 6.2.2.3.2 (Tab 13/Q.711)
               |          |ANSI-T1.112 Chap 2.2.2.3.2 (Tab 8B/T1.112.1)
   ------------+----------+--------------------------------------------
   N-STATE     |Request   |ITU-Q.711   Chap 6.3.2.3.2 (Tab 16/Q.711)
               |Indication|ANSI-T1.112 Chap 2.3.2.3.2 (Tab 8E/T1.112.1)
   ------------+----------+--------------------------------------------
   N-PCSTATE   |Indication|ITU-Q.711   Chap 6.3.2.3.3 (Tab 17/Q.711)
               |          |ANSI-T1.112 Chap 2.3.2.3.4 (Tab 8G/T1.112.1)
   ------------+----------+--------------------------------------------
   N-COORD     |Request   |ITU-Q.711   Chap 6.3.2.3.1 (Tab 15/Q.711)
               |Indication|ANSI-T1.112 Chap 2.3.2.3.3 (Tab 8F/T1.112.1)
               |Response  |
               |Confirm   |

Subsection 3.1 Common Message Header
Need to state what the reserved field is set to.

Old text:
   Note that the 'data' portion of SUA messages SHALL contain SCCP-User
   data, not the encapsulated SCCP message.

   Optional parameters can only occur at most once in an SUA message.

New text:
   Note that the 'data' portion of SUA messages SHALL contain SCCP-User
   data, not the encapsulated SCCP message.

   Optional parameters can only occur at most once in an SUA message.

   The Reserved field shall be set to 0 in messages sent, and shall not be
   examined on reception.

Subsection 3.2.1 Connectionless Data Transfer (CLDT)
The sequence control parameter is not supplied for class 0 from SCCP User to
SCCP. It is mandatory here. So what value is it ? I suggest 0.

Old text:
   Implementation note: This message covers the following SCCP
   messages: unitdata (UDT), extended unitdata (XUDT), long unitdata
   (LUDT).

New text:
   Implementation note: This message covers the following SCCP
   messages: unitdata (UDT), extended unitdata (XUDT), long unitdata
   (LUDT). Sequence Control shall be set to 0 for class 0 messages.

Subsection 3.4.1 Destination Unavailable (DUNA)
How many point codes can be in the Affected Point Code parameter of a DUNA
message containing an SSN? I suggest just 1, that of the destination
containing the unavailable subsystem.

Old text:
Note 1:    When the SSN is included, the DUNA message corresponds to
              the SCCP N-STATE primitive. When SSN is not, the DUNA
              message corresponds to the SCCP N-PCSTATE primitive.
New text:
Note 1:    When the SSN is included, the DUNA message corresponds to
           the SCCP N-STATE primitive, and contains just one point code
           in the Affected Point Code parameter. When the SSN is not
           included, the DUNA message corresponds to the SCCP
           N-PCSTATE primitive.

Subsection 3.4.4 Network Congestion (SCON)
The N-STATE primitive between SCCP and SCCP User only indicates User In
Service (UIS for the User status parameter), or User out of Service (UOS).
It does not indicate congestion. The congestion status of a subsystem other
than SCCP is not reported directly. The SSC message is for SCCP/subsystem
congested, and always has its affected SSN parameter set to 1 (section
5.2.7.1 in my 2001 version of Q.714). So the SCON with SSN must have SSN =
1, and it corresponds with the N-PCSTATE indication containing both Remote
SCCP status and Restricted importance level parameters (see 6.3.2.2.6 and
table 17 of Q.711 of 2001. N-STATE User status is defined in 6.3.2.2.2 of
Q.711).
You might want to use N-STATE to report subsystem congestion for SUA, but
the congestion procedures in Q.714 handle only MTP (network and signalling
point) congestion, and SCCP and nodal congestion. If there is more than 1
SCCP user at an ASP sending messages to a destination at or towards which
there is SCCP/subsystem congestion, then both have to use the same RIL for
that destination.
I have another problem with SCON and SSC mapping, but for now I think Note 1
should provisionally change.

Old text:
Note 1:    When the SSN is included, the SCON message corresponds to
              the SCCP N-STATE primitive. When SSN is not included, the
              SCON message corresponds to the SCCP N-PCSTATE primitive.
New text:
Note 1: When the SSN is included it must be equal to 1. If the SSN is
        included the SCON corresponds to the N-PCSTATE primitive used to
        convey the Restricted Importance Level (RIL) to the SCCP user.
        When the SSN is not included, the SCON message corresponds to
        the SCCP N-PCSTATE primitive reporting signalling point or
        network congestion status.

Subsection 3.4.5 Destination User Part Unavailable (DUPU)
This should contain just one point code in the Affected Point Code field.

Old text:
 Note 1:    The DUPU corresponds to the SCCP N-PCSTATE primitive.

New text:
 Note 1:    The DUPU corresponds to the SCCP N-PCSTATE primitive, and
            contains in the Affected Point Code parameter just one point
            code.

Subsection 3.7.1 Error (ERR)
This might have already been caught, the value of the Tag for the Network
Appearance parameter should be 0x010D.
Old text:
       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 = 0x000C         |             Length            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                          Error Code                           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Tag = 0x0006          |            Length             |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      /                       Routing Context                         /
      \                                                               \
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Tag = 0x0012          |             Length            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |      Mask     |                 Affected PC 1                 |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      /                              ...                              /
      \                                                               \
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |      Mask     |                 Affected PC n                 |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Tag = 0x010D          |         Length = 8            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Network Appearance                        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |          Tag = 0x0007         |            Length             |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      /                        Diagnostic Info                        /
      \                                                               \
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Parameters
     Error Code                    Mandatory
     Routing Context               Mandatory *1
     Network Appearance            Mandatory *1
     Affected Point Code           Mandatory *1
     Diagnostic Information        Optional

   Note 1: Only mandatory for specific error codes.

Subsection 3.9.17 ASP Identifier
Delete the last paragraph (it is an incorrect version of the paragraph
before it):
" The optional ASP Identifier parameter would contain a unique value that is
locally significant among the ASPs that support an AS. The SGP shall save
the ASP Identifier to be used, if necessary, with the Notify message (see
Section 3.3.3.2)."

Subsection 3.10 SUA-Specific parameters
Note that the parameter SSN used in SNM messages is the same as Subsystem
Number defined in subsection 3.10.2.5.
Note that in subsection 3.10.12 defining the User/Cause parameter, it is
named "Cause/User".
Subsection 3.10.12 Cause / User
Note that in messages using this parameter, and in subsection 3.10 listing
the SUA-Specific parameters, this is referred to as "User/Cause".
The value of the Length of the User/Cause parameter should be 8.

Old text:
      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 = 0x010c          |             Length = 32       |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |             Cause             |            User               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

New text:
      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 = 0x010c          |             Length = 8        |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |             Cause             |            User               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Subsection 3.10.13 Network Appearance
The value of the Length of the Network Appearance parameter should be 8.

Old text:
      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 = 0x010D          |             Length = 32       |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                      Network Appearance                       |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

New text:
      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 = 0x010D          |             Length = 8        |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                      Network Appearance                       |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Subsection 3.10.22 Sequence Control
Replace the reference with ITU Q.711 section 6.2.2.2.2.

Old text:
   Sequence Control (1.1.2/Q.714)

   The field is coded with the value of the sequence control parameter
   associated with a group of messages and are chosen so as to ensure
   proper loadsharing of message groups over SLS values while ensuring
   that sequence control values within message groups have the sequence
   control value coded with the same value as the initial message of
   the message group.

New text:
   Sequence Control (6.2.2.2.2/Q.711)

   The field is coded with the value of the sequence control parameter
   associated with a group of messages and are chosen so as to ensure
   proper loadsharing of message groups over SLS values while ensuring
   that sequence control values within message groups have the sequence
   control value coded with the same value as the initial message of
   the message group.

Subsection 4.2 Receipt of Primitives from the Layer Management
NOTE:   Third paragraph, the ASP (not the SGP) or IPSP initiate the
establishment of the SCTP association.

Old text:
   When an SCTP association has been successfully established, the SCTP
   will send an SCTP-COMMUNICATION_UP notification primitive to the
   local SUA layer.  At the SGP or IPSP that initiated the request, the
   SUA layer will send an M-SCTP_ESTABLISH confirm primitive to Layer
   Management when the association setup is complete.  At the peer SUA
   layer, an M-SCTP_ESTABLISH indication primitive is sent to Layer
   Management upon successful completion of an incoming SCTP association
   setup.

New text:

   When an SCTP association has been successfully established, the SCTP
   will send an SCTP-COMMUNICATION_UP notification primitive to the
   local SUA layer.  At the ASP or IPSP that initiated the request, the
   SUA layer will send an M-SCTP_ESTABLISH confirm primitive to Layer
   Management when the association setup is complete.  At the peer SUA
   layer, an M-SCTP_ESTABLISH indication primitive is sent to Layer
   Management upon successful completion of an incoming SCTP association
   setup.

Subsection 4.3.4.2 ASP Down Procedures
In the first paragraph, replace "DATA" with "Connectionless or Connection -
Oriented".
Replace "SSNM" with "SNM".

Old text:
   The ASP will send an ASP Down message to an SGP when the ASP wishes
   to be removed from service in all Application Servers that it is a
   member and no longer receive any DATA, SSNM or ASPTM messages.  This
   action MAY be initiated at the ASP by an M-ASP_DOWN request primitive
   from Layer Management or MAY be initiated automatically by an SUA
   management function.

New text:
   The ASP will send an ASP Down message to an SGP when the ASP wishes
   to be removed from service in all Application Servers that it is a
   member and no longer receive any Connectionless or
   Connection - Oriented, SNM or ASPTM messages.  This
   action MAY be initiated at the ASP by an M-ASP_DOWN request primitive
   from Layer Management or MAY be initiated automatically by an SUA
   management function.

Subsection 4.5.1 At an SGP
Replace "SSNM" with "SNM" in the first paragraph.

Old text:
   On receiving a N-STATE, N-PCSTATE and N-INFORM indication primitive
   from the nodal inter-working function at an SGP, the SGP SUA layer
   will send a corresponding SS7 Signalling Network Management (SSNM)
   DUNA, DAVA, SCON, or DUPU message (see Section 3.4) to the SUA peers
   at concerned ASPs.  The SUA layer must fill in various fields of the
   SSNM messages consistently with the information received in the
   primitives.

New text:
   On receiving a N-STATE, N-PCSTATE and N-INFORM indication primitive
   from the nodal inter-working function at an SGP, the SGP SUA layer
   will send a corresponding SS7 Signalling Network Management (SNM)
   DUNA, DAVA, SCON, or DUPU message (see Section 3.4) to the SUA peers
   at concerned ASPs.  The SUA layer must fill in various fields of the
   SNM messages consistently with the information received in the
   primitives.

The following paragraphs are inconsistent in SCTP stream useage:

   DUNA, DAVA, SCON, and DRST messages are sent sequentially and
   processed at the receiver in the order sent.  SCTP stream 0 **SHOULD
   NOT** be used. The Unordered bit in the SCTP DATA chunk MAY be used for
   the SCON message.

   Sequencing is not required for the DUPU or DAUD messages, which MAY
   be sent un-sequenced.  **Again, SCTP stream 0 is used**, with optional
   use of the Unordered bit in the SCTP DATA chunk.

I think the new text of the first of these paras should be:

   DUNA, DAVA, SCON, and DRST messages are sent sequentially and
   processed at the receiver in the order sent.  SCTP stream 0 SHOULD
   be used. The Unordered bit in the SCTP DATA chunk MAY be used for
   the SCON message.

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



From mailnull@www1.ietf.org  Tue Jan 21 11:08: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 LAA03782
	for <sigtran-archive@odin.ietf.org>; Tue, 21 Jan 2003 11:08:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0LGPpu28711
	for sigtran-archive@odin.ietf.org; Tue, 21 Jan 2003 11:25:51 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LGPKJ28673;
	Tue, 21 Jan 2003 11:25:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LGOKJ28548
	for <sigtran@optimus.ietf.org>; Tue, 21 Jan 2003 11:24:20 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03679
	for <sigtran@ietf.org>; Tue, 21 Jan 2003 11:06:12 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:2KUW9ZSXh1B13pKEP9tu9F9DpEizr/sU@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0LG9bD04870;
	Tue, 21 Jan 2003 09:09:37 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0LG9a227389;
	Tue, 21 Jan 2003 09:09:36 -0700
Date: Tue, 21 Jan 2003 09:09:35 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Richard Adams <Richard.Adams@etsi.org>
Cc: john.loughney@nokia.com, sigtran@ietf.org
Subject: Re: [Sigtran] SUA 14 editorial suggestions
Message-ID: <20030121090935.B26661@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Richard Adams <Richard.Adams@etsi.org>,
	john.loughney@nokia.com, sigtran@ietf.org
References: <4091553999CBE4409CC2B562152B5A33EDDF4C@email10.etsihq.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: <4091553999CBE4409CC2B562152B5A33EDDF4C@email10.etsihq.org>; from Richard.Adams@etsi.org on Tue, Jan 21, 2003 at 04:38:34PM +0100
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>

Richard,

Richard Adams wrote:                                                               (Tue, 21 Jan 2003 16:38:34)

--X---[snip]---X--

I don't think that we should replace references with 2001 specs.
Let's just put the correct date of the document under "References".

> 
> Subsection 3.2.1 Connectionless Data Transfer (CLDT)
> The sequence control parameter is not supplied for class 0 from SCCP User to
> SCCP. It is mandatory here. So what value is it ? I suggest 0.
> 
> Old text:
>    Implementation note: This message covers the following SCCP
>    messages: unitdata (UDT), extended unitdata (XUDT), long unitdata
>    (LUDT).
> 
> New text:
>    Implementation note: This message covers the following SCCP
>    messages: unitdata (UDT), extended unitdata (XUDT), long unitdata
>    (LUDT). Sequence Control shall be set to 0 for class 0 messages.

It was intended to be mandatory for class 0 a well.  The SUA user should
set this value to a value that will ensure equal loadsharing.

> 
> Subsection 3.4.1 Destination Unavailable (DUNA)
> How many point codes can be in the Affected Point Code parameter of a DUNA
> message containing an SSN? I suggest just 1, that of the destination
> containing the unavailable subsystem.
> 
> Old text:
> Note 1:    When the SSN is included, the DUNA message corresponds to
>               the SCCP N-STATE primitive. When SSN is not, the DUNA
>               message corresponds to the SCCP N-PCSTATE primitive.
> New text:
> Note 1:    When the SSN is included, the DUNA message corresponds to
>            the SCCP N-STATE primitive, and contains just one point code
>            in the Affected Point Code parameter. When the SSN is not
>            included, the DUNA message corresponds to the SCCP
>            N-PCSTATE primitive.

It could contain mutliple affected point code parameters.

> 
> Subsection 3.4.4 Network Congestion (SCON)
> The N-STATE primitive between SCCP and SCCP User only indicates User In
> Service (UIS for the User status parameter), or User out of Service (UOS).
> It does not indicate congestion. The congestion status of a subsystem other
> than SCCP is not reported directly. The SSC message is for SCCP/subsystem
> congested, and always has its affected SSN parameter set to 1 (section
> 5.2.7.1 in my 2001 version of Q.714). So the SCON with SSN must have SSN =
> 1, and it corresponds with the N-PCSTATE indication containing both Remote
> SCCP status and Restricted importance level parameters (see 6.3.2.2.6 and
> table 17 of Q.711 of 2001. N-STATE User status is defined in 6.3.2.2.2 of
> Q.711).
> You might want to use N-STATE to report subsystem congestion for SUA, but
> the congestion procedures in Q.714 handle only MTP (network and signalling
> point) congestion, and SCCP and nodal congestion. If there is more than 1
> SCCP user at an ASP sending messages to a destination at or towards which
> there is SCCP/subsystem congestion, then both have to use the same RIL for
> that destination.
> I have another problem with SCON and SSC mapping, but for now I think Note 1
> should provisionally change.
> 
> Old text:
> Note 1:    When the SSN is included, the SCON message corresponds to
>               the SCCP N-STATE primitive. When SSN is not included, the
>               SCON message corresponds to the SCCP N-PCSTATE primitive.
> New text:
> Note 1: When the SSN is included it must be equal to 1. If the SSN is
>         included the SCON corresponds to the N-PCSTATE primitive used to
>         convey the Restricted Importance Level (RIL) to the SCCP user.
>         When the SSN is not included, the SCON message corresponds to
>         the SCCP N-PCSTATE primitive reporting signalling point or
>         network congestion status.
> 
> Subsection 3.4.5 Destination User Part Unavailable (DUPU)
> This should contain just one point code in the Affected Point Code field.
> 
> Old text:
>  Note 1:    The DUPU corresponds to the SCCP N-PCSTATE primitive.
> 
> New text:
>  Note 1:    The DUPU corresponds to the SCCP N-PCSTATE primitive, and
>             contains in the Affected Point Code parameter just one point
>             code.

It could be multiple.

> Subsection 4.3.4.2 ASP Down Procedures
> In the first paragraph, replace "DATA" with "Connectionless or Connection -
> Oriented".
> Replace "SSNM" with "SNM".
> 
> Old text:
>    The ASP will send an ASP Down message to an SGP when the ASP wishes
>    to be removed from service in all Application Servers that it is a
>    member and no longer receive any DATA, SSNM or ASPTM messages.  This
>    action MAY be initiated at the ASP by an M-ASP_DOWN request primitive
>    from Layer Management or MAY be initiated automatically by an SUA
>    management function.
> 
> New text:
>    The ASP will send an ASP Down message to an SGP when the ASP wishes
>    to be removed from service in all Application Servers that it is a
>    member and no longer receive any Connectionless or
>    Connection - Oriented, SNM or ASPTM messages.  This
>    action MAY be initiated at the ASP by an M-ASP_DOWN request primitive
>    from Layer Management or MAY be initiated automatically by an SUA
>    management function.

SSNM is correct.

> 
> Subsection 4.5.1 At an SGP
> Replace "SSNM" with "SNM" in the first paragraph.
> 
> Old text:
>    On receiving a N-STATE, N-PCSTATE and N-INFORM indication primitive
>    from the nodal inter-working function at an SGP, the SGP SUA layer
>    will send a corresponding SS7 Signalling Network Management (SSNM)
>    DUNA, DAVA, SCON, or DUPU message (see Section 3.4) to the SUA peers
>    at concerned ASPs.  The SUA layer must fill in various fields of the
>    SSNM messages consistently with the information received in the
>    primitives.
> 
> New text:
>    On receiving a N-STATE, N-PCSTATE and N-INFORM indication primitive
>    from the nodal inter-working function at an SGP, the SGP SUA layer
>    will send a corresponding SS7 Signalling Network Management (SNM)
>    DUNA, DAVA, SCON, or DUPU message (see Section 3.4) to the SUA peers
>    at concerned ASPs.  The SUA layer must fill in various fields of the
>    SNM messages consistently with the information received in the
>    primitives.
> 
SSNM is correct.


> The following paragraphs are inconsistent in SCTP stream useage:
> 
>    DUNA, DAVA, SCON, and DRST messages are sent sequentially and
>    processed at the receiver in the order sent.  SCTP stream 0 **SHOULD
>    NOT** be used. The Unordered bit in the SCTP DATA chunk MAY be used for
>    the SCON message.
> 
>    Sequencing is not required for the DUPU or DAUD messages, which MAY
>    be sent un-sequenced.  **Again, SCTP stream 0 is used**, with optional
>    use of the Unordered bit in the SCTP DATA chunk.
> 
> I think the new text of the first of these paras should be:
> 
>    DUNA, DAVA, SCON, and DRST messages are sent sequentially and
>    processed at the receiver in the order sent.  SCTP stream 0 SHOULD
>    be used. The Unordered bit in the SCTP DATA chunk MAY be used for
>    the SCON message.

DUNA, DAVA, SCON and DRST - not on stream 0
DUPU, DAUD - use stream 0

There is no inconsistency.

--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  Tue Jan 21 11:46: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 LAA04764
	for <sigtran-archive@odin.ietf.org>; Tue, 21 Jan 2003 11:46:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0LH48431181
	for sigtran-archive@odin.ietf.org; Tue, 21 Jan 2003 12:04:08 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LH3XJ31146;
	Tue, 21 Jan 2003 12:03:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LGsjJ30720
	for <sigtran@optimus.ietf.org>; Tue, 21 Jan 2003 11:54:45 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04479
	for <sigtran@ietf.org>; Tue, 21 Jan 2003 11:36:37 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0LGe1VN013333;
	Tue, 21 Jan 2003 10:40:01 -0600 (CST)
Message-ID: <3E2D77E1.A0A53F9D@alcatel.com>
Date: Tue, 21 Jan 2003 10:40:01 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: sigtran@ietf.org
References: <200301211252.HAA27713@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M2PA version 7 changes
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 is a list of changes made in M2PAv7 arranged by threads. I am
working on a more detailed list of changes and should be able to post
that tomorrow.


List of comments on M2PA draft version 6. 
01/21/2003

Here is my list of comments on M2PA draft version 6 and how they were
incorporated into version 7. For the most part, they are arranged by
the thread from the SIGTRAN list. The date/name/subject identify the
beginning of the thread.

If anyone wants to study the changes in detail, I have a "diff" file I
can send.


01. 09/02/02 Howard May, Ming Lin "[Sigtran] M2PA - Retrieval
    State". Is this state needed?

    11/21/02 Jeff Craig suggested more changes.

    A: Retrieval state is not needed. It is eliminated in Figure 7 and
    elsewhere.

    AIP is changed to INITIAL ALIGNMENT.

    ALIGNED NOT READY and PROCESSOR OUTAGE states were added. 

02. 09/04/02 Andrew Booth "[Sigtran] M2PA 6: message acknowledgement"
    and 
    09/12/02 anssharma "[Sigtran] M2PA : FSN value in Zero Data Acks"

    Incrementing FSN on ack-only message causes endless cycle of acking
    empty messages.

    A: Do not increment FSN on empty User Data message. Section 4.2.1
    is updated.

03. 09/17/02 Jeff Craig "(M2PA) link status messages should be received
    and processed during LPO".

    M2PA should not ack User Data messages, but it is OK to receive
    them. And M2PA should receive Link Status messages.

    A: Changed 4.1.4, 2nd paragraph.

04. 09/18/02 Jeff Craig "[Sigtran] (M2PA) Receipt of User Data during
    AIP, PROVING should cause transition to OOS".

    A: Discard message as in MTP2. Text already says this. See Brian
    Bidulock message 09/19.

05. 09/18/02 Jeff Craig "[Sigtran] (M2PA) Does an ACK (0-byte User
    Data) received in ALIGNED-READY cause transition to INS?"

    A: Yes. The text says "User Data message". That would include the
    ones with 0-byte data.

06. 09/19/02 Jeff Craig "[Sigtran] Re: Comments on
    draft-bidulock-sigtran-m2pa-test-02.ps".

    Rename timer T1 to T2, and others as well.

    A: T1 is renamed to T2. 
       T3 is renamed to T1.
       New timer T3 is added.
    New names should correspond more closely to MTP2 timer names. 

07. 09/19/02 Jeff Craig "[Sigtran] Suggested New Test Cases for
    draft-bidulock-sigtran-m2pa-test-02.ps".

    Should we eliminate the interval timers?

    A: The LS Busy, LS PO, and LS Ready MAY be sent periodically. But
    it should not be a requirement.  

    Requirement for periodic LS Ready was removed from
    4.1.3. Status_Interval was removed.

    Diagram in 5.1 was changed to show only one LS Ready, but text
    notes that more may be sent.

    Also in 4.1.3, Proving_Rate was changed to Proving_Interval.

    Requirement for periodic LS PO was removed from 4.1.4.

    Requirement for periodic LS Busy was removed from 4.1.5.

08. 09/27/02 Anshoo "[Sigtran] M2PA v6: Two Out of Three Valid BSN".

    A: I left this as is, since it makes it easier to convert M2PA to
    MTP2.

09. 09/26/02 Howard May "[Sigtran] M2PA V6: T7". Should T7 timer be
    per-message? 

    A: Yes. Updated section 4.2.1 Sending and receiving messages.

10. 10/10/02 Howard May "RE: [Sigtran] M2PA V6: LS Busy".

    Is it OK to be sending LS Busy and LS PO at the same time?

    A: There is no harm in this. No change needed to the draft.

11. 10/11/02 Richard Knowles "[Sigtran] M2PA testing at Plugtest".

    Change timer names: T1 to T2, T3 to T1. 

    T3 in Q.703 has no analog in M2PA. It should exist.

    A: Done. See previous item (6) on this.

12. 10/31/02 Barry Nagelberg "[Sigtran] m2pa v6: Recovering from a
    processor outage".

    11/05/02 Rohan. "[Sigtran] Clarification regarding Processor
    Outage". In section 4.2.4, do we need Continue before sending
    messages?

    Move last paragraph of 4.2.4 to 4.1.4. Change the statement to
    remove requirement that M2PA receive Flush Buffers or Continue.

    A: The last paragraph of 4.2.4 was moved to 4.1.4. The wording in
    4.1.4 was changed to refer to the MTP2 standards for the use of
    Flush Buffers and Continue. 

13. 10/31/02 Barry Nagelberg "[Sigtran] m2pa v6: Notifying MTP3 about
    end of PO".

    If peer receives LS PO Ended during Alignment, it should not
    notify MTP3 with the Remote Processor Recovered Indication.

    A: The last paragraph of 4.1.4 is changed to say that the Remote
    Processor Recovered Indication is given only in the IN SERVICE
    state.

14. 10/31/02 Barry Nagelberg "[Sigtran] M2pa v6: Timer T7 timeout
    during PO".

    M2PA should not fail a link because of T7 expiry if there is a
    Processor Outage condition.

    A: Correct. Section 4.1.4 is modified accordingly.

15. 11/04/02 Jeffrey Craig "[Sigtran] M2PA Plugtest Comments - Day
    1". Several comments.

    1. T7 should be disabled during Remote PO.

       A: Yes. See previous item about this.

    2. During ALIGNED-READY with local processor outage in-effect, is
       received User Data an event that should trigger a transition
       to INS state? (Currently M2PA should not receive user data from
       SCTP when LPO is in effect.)

       A: M2PA should not receive user data from SCTP when LPO is in
       effect because it cannot be processed by MTP3 (or one of the
       higher layers). 

    3. Should M2PA support the PO outage procedure as in Q.703, or
       should it take the link OOS when it detects LPO?

       A: I put the PO procedure in M2PA because it seemed better to
       keep the link up when possible, rather than failing it and
       going through alignment again.

    4. Should LSA received during ALIGNED-READY cause a transition to
       OOS (to match Q.703)?

       01/17/03 Tom George "[Sigtran] M2PA: LS Alignment after
       proving".

       A: LS Alignment causes OOS in either the "Aligned Ready" or "In
       Service" states. It also should put the link out of service in
       the "Aligned Not Ready" state.

       I updated the state diagram accordingly. 


16. 11/06/02 Michael Tuexen. "[Sigtran] M2PA discussions on M2PA".

    The handling of Alignment messages in 'unexpected' state needs
    to be clarified in the ID.

    A: Done. See the paragraph "Anomalous messages..." at the end of
    4.1.3.

17. 01/01/03 S Magesh. "[Sigtran] Contradiction between M2PA RFC Draft
    Version 6 and M2PA RFC Test Specification Draft Version 02".

    Timer names in M2PA draft do not match the M2PA test spec.

    A: Brian Bidulock suggests changing timer names. 

    Done. See previous item about this (6).

18. 01/03/03 Srini "[Sigtran] M2PA two out of three". Is the statement
    worded accurately?

    A: Yes, though it is a bit hard to read. Leave it as in Q.703.

19. 01/14/03 Jeffrey Craig "[Sigtran] (M2PA) Any word on when we can
    expect a M2PA v7?".

    Brian Bidulock suggested some stylistic changes.

    A: I made some stylistic changes suggested by Brian Bidulock:

       - I changed the reference format.
       - I added dots to the diagrams in section 5. 
       - I added figure numbers to the diagrams in section 5. 


==================================================================



-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 21 12:24: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 MAA05875
	for <sigtran-archive@odin.ietf.org>; Tue, 21 Jan 2003 12:24:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0LHg2c02190
	for sigtran-archive@odin.ietf.org; Tue, 21 Jan 2003 12:42:02 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LHfIJ02154;
	Tue, 21 Jan 2003 12:41:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LHZFJ01220
	for <sigtran@optimus.ietf.org>; Tue, 21 Jan 2003 12:35:15 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05649
	for <sigtran@ietf.org>; Tue, 21 Jan 2003 12:17:05 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:QidBVmE91CE8Ocacw+4/K8nyDzEFVPrR@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0LHKUD06557;
	Tue, 21 Jan 2003 10:20:30 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0LHKTx29746;
	Tue, 21 Jan 2003 10:20:29 -0700
Date: Tue, 21 Jan 2003 10:20:29 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tom George <Tom.George@alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA version 7 changes
Message-ID: <20030121102029.B29414@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tom George <Tom.George@alcatel.com>, sigtran@ietf.org
References: <200301211252.HAA27713@ietf.org> <3E2D77E1.A0A53F9D@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: <3E2D77E1.A0A53F9D@alcatel.com>; from Tom.George@alcatel.com on Tue, Jan 21, 2003 at 10:40:01AM -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>

Tom,

Good job!

--brian

Tom George wrote:                                                                      (Tue, 21 Jan 2003 10:40:01)
> Here is a list of changes made in M2PAv7 arranged by threads. I am
> working on a more detailed list of changes and should be able to post
> that tomorrow.
> 
> 
> List of comments on M2PA draft version 6. 
> 01/21/2003
> 
> Here is my list of comments on M2PA draft version 6 and how they were
> incorporated into version 7. For the most part, they are arranged by
> the thread from the SIGTRAN list. The date/name/subject identify the
> beginning of the thread.
> 
> If anyone wants to study the changes in detail, I have a "diff" file I
> can send.
> 
> 
> 01. 09/02/02 Howard May, Ming Lin "[Sigtran] M2PA - Retrieval
>     State". Is this state needed?
> 
>     11/21/02 Jeff Craig suggested more changes.
> 
>     A: Retrieval state is not needed. It is eliminated in Figure 7 and
>     elsewhere.
> 
>     AIP is changed to INITIAL ALIGNMENT.
> 
>     ALIGNED NOT READY and PROCESSOR OUTAGE states were added. 
> 
> 02. 09/04/02 Andrew Booth "[Sigtran] M2PA 6: message acknowledgement"
>     and 
>     09/12/02 anssharma "[Sigtran] M2PA : FSN value in Zero Data Acks"
> 
>     Incrementing FSN on ack-only message causes endless cycle of acking
>     empty messages.
> 
>     A: Do not increment FSN on empty User Data message. Section 4.2.1
>     is updated.
> 
> 03. 09/17/02 Jeff Craig "(M2PA) link status messages should be received
>     and processed during LPO".
> 
>     M2PA should not ack User Data messages, but it is OK to receive
>     them. And M2PA should receive Link Status messages.
> 
>     A: Changed 4.1.4, 2nd paragraph.
> 
> 04. 09/18/02 Jeff Craig "[Sigtran] (M2PA) Receipt of User Data during
>     AIP, PROVING should cause transition to OOS".
> 
>     A: Discard message as in MTP2. Text already says this. See Brian
>     Bidulock message 09/19.
> 
> 05. 09/18/02 Jeff Craig "[Sigtran] (M2PA) Does an ACK (0-byte User
>     Data) received in ALIGNED-READY cause transition to INS?"
> 
>     A: Yes. The text says "User Data message". That would include the
>     ones with 0-byte data.
> 
> 06. 09/19/02 Jeff Craig "[Sigtran] Re: Comments on
>     draft-bidulock-sigtran-m2pa-test-02.ps".
> 
>     Rename timer T1 to T2, and others as well.
> 
>     A: T1 is renamed to T2. 
>        T3 is renamed to T1.
>        New timer T3 is added.
>     New names should correspond more closely to MTP2 timer names. 
> 
> 07. 09/19/02 Jeff Craig "[Sigtran] Suggested New Test Cases for
>     draft-bidulock-sigtran-m2pa-test-02.ps".
> 
>     Should we eliminate the interval timers?
> 
>     A: The LS Busy, LS PO, and LS Ready MAY be sent periodically. But
>     it should not be a requirement.  
> 
>     Requirement for periodic LS Ready was removed from
>     4.1.3. Status_Interval was removed.
> 
>     Diagram in 5.1 was changed to show only one LS Ready, but text
>     notes that more may be sent.
> 
>     Also in 4.1.3, Proving_Rate was changed to Proving_Interval.
> 
>     Requirement for periodic LS PO was removed from 4.1.4.
> 
>     Requirement for periodic LS Busy was removed from 4.1.5.
> 
> 08. 09/27/02 Anshoo "[Sigtran] M2PA v6: Two Out of Three Valid BSN".
> 
>     A: I left this as is, since it makes it easier to convert M2PA to
>     MTP2.
> 
> 09. 09/26/02 Howard May "[Sigtran] M2PA V6: T7". Should T7 timer be
>     per-message? 
> 
>     A: Yes. Updated section 4.2.1 Sending and receiving messages.
> 
> 10. 10/10/02 Howard May "RE: [Sigtran] M2PA V6: LS Busy".
> 
>     Is it OK to be sending LS Busy and LS PO at the same time?
> 
>     A: There is no harm in this. No change needed to the draft.
> 
> 11. 10/11/02 Richard Knowles "[Sigtran] M2PA testing at Plugtest".
> 
>     Change timer names: T1 to T2, T3 to T1. 
> 
>     T3 in Q.703 has no analog in M2PA. It should exist.
> 
>     A: Done. See previous item (6) on this.
> 
> 12. 10/31/02 Barry Nagelberg "[Sigtran] m2pa v6: Recovering from a
>     processor outage".
> 
>     11/05/02 Rohan. "[Sigtran] Clarification regarding Processor
>     Outage". In section 4.2.4, do we need Continue before sending
>     messages?
> 
>     Move last paragraph of 4.2.4 to 4.1.4. Change the statement to
>     remove requirement that M2PA receive Flush Buffers or Continue.
> 
>     A: The last paragraph of 4.2.4 was moved to 4.1.4. The wording in
>     4.1.4 was changed to refer to the MTP2 standards for the use of
>     Flush Buffers and Continue. 
> 
> 13. 10/31/02 Barry Nagelberg "[Sigtran] m2pa v6: Notifying MTP3 about
>     end of PO".
> 
>     If peer receives LS PO Ended during Alignment, it should not
>     notify MTP3 with the Remote Processor Recovered Indication.
> 
>     A: The last paragraph of 4.1.4 is changed to say that the Remote
>     Processor Recovered Indication is given only in the IN SERVICE
>     state.
> 
> 14. 10/31/02 Barry Nagelberg "[Sigtran] M2pa v6: Timer T7 timeout
>     during PO".
> 
>     M2PA should not fail a link because of T7 expiry if there is a
>     Processor Outage condition.
> 
>     A: Correct. Section 4.1.4 is modified accordingly.
> 
> 15. 11/04/02 Jeffrey Craig "[Sigtran] M2PA Plugtest Comments - Day
>     1". Several comments.
> 
>     1. T7 should be disabled during Remote PO.
> 
>        A: Yes. See previous item about this.
> 
>     2. During ALIGNED-READY with local processor outage in-effect, is
>        received User Data an event that should trigger a transition
>        to INS state? (Currently M2PA should not receive user data from
>        SCTP when LPO is in effect.)
> 
>        A: M2PA should not receive user data from SCTP when LPO is in
>        effect because it cannot be processed by MTP3 (or one of the
>        higher layers). 
> 
>     3. Should M2PA support the PO outage procedure as in Q.703, or
>        should it take the link OOS when it detects LPO?
> 
>        A: I put the PO procedure in M2PA because it seemed better to
>        keep the link up when possible, rather than failing it and
>        going through alignment again.
> 
>     4. Should LSA received during ALIGNED-READY cause a transition to
>        OOS (to match Q.703)?
> 
>        01/17/03 Tom George "[Sigtran] M2PA: LS Alignment after
>        proving".
> 
>        A: LS Alignment causes OOS in either the "Aligned Ready" or "In
>        Service" states. It also should put the link out of service in
>        the "Aligned Not Ready" state.
> 
>        I updated the state diagram accordingly. 
> 
> 
> 16. 11/06/02 Michael Tuexen. "[Sigtran] M2PA discussions on M2PA".
> 
>     The handling of Alignment messages in 'unexpected' state needs
>     to be clarified in the ID.
> 
>     A: Done. See the paragraph "Anomalous messages..." at the end of
>     4.1.3.
> 
> 17. 01/01/03 S Magesh. "[Sigtran] Contradiction between M2PA RFC Draft
>     Version 6 and M2PA RFC Test Specification Draft Version 02".
> 
>     Timer names in M2PA draft do not match the M2PA test spec.
> 
>     A: Brian Bidulock suggests changing timer names. 
> 
>     Done. See previous item about this (6).
> 
> 18. 01/03/03 Srini "[Sigtran] M2PA two out of three". Is the statement
>     worded accurately?
> 
>     A: Yes, though it is a bit hard to read. Leave it as in Q.703.
> 
> 19. 01/14/03 Jeffrey Craig "[Sigtran] (M2PA) Any word on when we can
>     expect a M2PA v7?".
> 
>     Brian Bidulock suggested some stylistic changes.
> 
>     A: I made some stylistic changes suggested by Brian Bidulock:
> 
>        - I changed the reference format.
>        - I added dots to the diagrams in section 5. 
>        - I added figure numbers to the diagrams in section 5. 
> 
> 
> ==================================================================
> 
> 
> 
> -- 
> * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> * Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
> * 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  Tue Jan 21 12:25: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 MAA05933
	for <sigtran-archive@odin.ietf.org>; Tue, 21 Jan 2003 12:25:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0LHhDa02354
	for sigtran-archive@odin.ietf.org; Tue, 21 Jan 2003 12:43:13 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LHh0J02307;
	Tue, 21 Jan 2003 12:43:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LHdKJ02026
	for <sigtran@optimus.ietf.org>; Tue, 21 Jan 2003 12:39:20 -0500
Received: from web8207.mail.in.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA05789
	for <sigtran@ietf.org>; Tue, 21 Jan 2003 12:21:11 -0500 (EST)
Message-ID: <20030121172436.63900.qmail@web8207.mail.in.yahoo.com>
Received: from [210.214.67.91] by web8207.mail.in.yahoo.com via HTTP; Tue, 21 Jan 2003 17:24:36 GMT
Date: Tue, 21 Jan 2003 17:24:36 +0000 (GMT)
From: =?iso-8859-1?q?amit=20somani?= <amitksomani@yahoo.co.in>
To: Sigtran <sigtran@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Sigtran] (no subject)
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 all!
        Is there any code availabel on openss7 or
anywhere else which will directly genaerete ss7
traffic  as actual. We do not have direct access to
ss7 links. we r plannig to simulate Glbole Title
Translation (GTT).
                       amit

________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
       visit http://in.tv.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Tue Jan 21 17:11: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 RAA13559
	for <sigtran-archive@odin.ietf.org>; Tue, 21 Jan 2003 17:11:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0LMSrR21533
	for sigtran-archive@odin.ietf.org; Tue, 21 Jan 2003 17:28:53 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LMSLJ21509;
	Tue, 21 Jan 2003 17:28:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LMRSJ21486
	for <sigtran@optimus.ietf.org>; Tue, 21 Jan 2003 17:27:28 -0500
Received: from w2ksjexg01.ciena.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13511
	for <sigtran@ietf.org>; Tue, 21 Jan 2003 17:09:14 -0500 (EST)
Received: from wntcsdexg01.csd.ciena.com ([10.34.31.31]) by w2ksjexg01.ciena.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id C2BQMZTR; Tue, 21 Jan 2003 14:12:25 -0800
Received: by webdev-llnt.oni.com with Internet Mail Service (5.5.2653.19)
	id <Y5W9MC2F>; Tue, 21 Jan 2003 14:12:38 -0800
Message-ID: <2135200C183FD5119588009027DE572302836BE1@webdev-owa.oni.com>
From: "Ong, Lyndon" <LyOng@ciena.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Date: Tue, 21 Jan 2003 14:12:35 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] m2pa v7 Last Call
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,

Now that M2PA v7 is out and the reviews seem to be good, I would
like to initiate WG Last Call on the specification.  If there are no
objections, let's initiate Last Call as of Wednesday, Jan. 22,
ending on Wednesday, Feb. 5th.


Cheers,

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



From mailnull@www1.ietf.org  Tue Jan 21 23:38: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 XAA21372
	for <sigtran-archive@odin.ietf.org>; Tue, 21 Jan 2003 23:38:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0M4uiK11443
	for sigtran-archive@odin.ietf.org; Tue, 21 Jan 2003 23:56:44 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0M4uEJ11405;
	Tue, 21 Jan 2003 23:56:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0M4sdJ11332
	for <sigtran@optimus.ietf.org>; Tue, 21 Jan 2003 23:54:39 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21258
	for <sigtran@ietf.org>; Tue, 21 Jan 2003 23:36:16 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0M4dbBS005898;
	Tue, 21 Jan 2003 22:39:38 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id JAA22214; Wed, 22 Jan 2003 09:08:50 -0500 (GMT)
Message-ID: <3E2E20D8.F28141F1@axes-mach01.usa.alcatel.com>
Date: Wed, 22 Jan 2003 10:10:57 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: sigtran@ietf.org
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] [M3UA] Heartbeat procedures
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

Brian,

In Section, 4.3.4.6 Heartbeat Procedures of M3UA RFC, the following is
mentioned.

[...Either M3UA peer may optionally send Heartbeat messages
periodically, subject to a provisionable timer T(beat).  Upon receiving
a Heartbeat message, the M3UA peer MUST respond with a Heartbeat Ack
message...]

The following are understood from the above para:

1. Heartbeat messages are periodically sent subject to a provisionable
timer T(beat).

Once in every T(beat) interval, a Heartbeat message is sent.

2. Upon receiving a Heartbeat message, the M3UA peer MUST respond with a
Heartbeat Ack message.

Since Heartbeat message is sent Once in every T(beat) interval, the
Heartbeat Ack message should also be received Once in every T(beat)
interval if everything is proper.

Is my understanding proper?.

[...If no Heartbeat Ack message (or any other M3UA message) is received
from the M3UA peer within 2*T(beat), the remote M3UA peer is considered
unavailable.  Transmission of Heartbeat messages is stopped and the
signalling process SHOULD attempt to re-establish communication if it is
configured as the client for the disconnected M3UA peer...]

Can you please clarify my following doubts from the above para:

1. In response to Heartbeat message sent, should the M3UA expect either
the Heartbeat Ack message or any other M3UA message?

2. What should happen if the Heartbeat Ack message is not received
within the first T(beat) interval.?
    Should we wait for one more T(beat) interval for the Heartbeat Ack
message?.

--Srini

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



From mailnull@www1.ietf.org  Wed Jan 22 00:21: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 AAA21873
	for <sigtran-archive@odin.ietf.org>; Wed, 22 Jan 2003 00:21:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0M5dT714388
	for sigtran-archive@odin.ietf.org; Wed, 22 Jan 2003 00:39:29 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0M5dGJ14381;
	Wed, 22 Jan 2003 00:39:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0M5cvJ14349
	for <sigtran@optimus.ietf.org>; Wed, 22 Jan 2003 00:38:57 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21863
	for <sigtran@ietf.org>; Wed, 22 Jan 2003 00:20:34 -0500 (EST)
Subject: Re: [Sigtran] M2PA version 7 changes
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF602FCCBB.9172BC42-ONC2256CB6.001D3A69@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Wed, 22 Jan 2003 07:20:36 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/22/2003
 07:20:40 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>


Tom,
Is there also a decision about what to do while flushing buffers?

   Tolga

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



From mailnull@www1.ietf.org  Wed Jan 22 01:51: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 BAA23256
	for <sigtran-archive@odin.ietf.org>; Wed, 22 Jan 2003 01:51:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0M793j23021
	for sigtran-archive@odin.ietf.org; Wed, 22 Jan 2003 02:09:03 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0M78eJ22952;
	Wed, 22 Jan 2003 02:08:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0M77gJ22348
	for <sigtran@optimus.ietf.org>; Wed, 22 Jan 2003 02:07:42 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23249
	for <sigtran@ietf.org>; Wed, 22 Jan 2003 01:49:16 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0M6qWbg024473;
	Wed, 22 Jan 2003 00:52:32 -0600 (CST)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id h0M6pqM04432;
	Wed, 22 Jan 2003 00:51:52 -0600 (CST)
Date: Wed, 22 Jan 2003 00:51:52 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: kakaul@hss.hns.com
cc: sigtran@ietf.org
Subject: Re: [Sigtran] I-D ACTION:draft-kamesh-m3ua-congestion-procedures-00.txt
In-Reply-To: <65256CB4.004CEAD4.00@sandesh.hss.hns.com>
Message-ID: <Pine.SOL.4.10.10301220023160.7548-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>


Kaul,

Section 2.1
       ...
       Now if "association a" undergoes congestion, congestion status of point
       code X-Y-Z maintained at ASP gets updated. If after some time
       "association b" undergoes congestion. Congestion status of point code
       X-Y-Z is updated if "association b" undergoes more congestion than
       "association a".


Here the overall X-Y-Z PC congestion status is updated based on a single
association congestion status.    

Does it not conflict with RFC 3332 section 1.3.2.5?

IMO overall congestion status of  X-Y-Z PC
is obtained from the congestion status of the individual ROUTES but not
based on a single route.
 


--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 mailnull@www1.ietf.org  Wed Jan 22 05:08: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 FAA20934
	for <sigtran-archive@odin.ietf.org>; Wed, 22 Jan 2003 05:08:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0MAQgv09750
	for sigtran-archive@odin.ietf.org; Wed, 22 Jan 2003 05:26:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0MAQOJ09736;
	Wed, 22 Jan 2003 05:26:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0MAOEJ09619
	for <sigtran@optimus.ietf.org>; Wed, 22 Jan 2003 05:24:14 -0500
Received: from hindon.hss.co.in (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20879
	for <sigtran@ietf.org>; Wed, 22 Jan 2003 05:05:44 -0500 (EST)
From: kakaul@hss.hns.com
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 h0MA7rj14275
	for <sigtran@ietf.org>; Wed, 22 Jan 2003 15:37:53 +0530 (IST)
Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h0MA7oM14264;
	Wed, 22 Jan 2003 15:37:51 +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 SMTP id h0MAA4O01690;
	Wed, 22 Jan 2003 15:40:04 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256CB6.003716FA ; Wed, 22 Jan 2003 15:31:43 +0530
X-Lotus-FromDomain: HSS
To: sigtran@ietf.org
cc: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Message-ID: <65256CB6.003715D0.00@sandesh.hss.hns.com>
Date: Wed, 22 Jan 2003 15:34:26 +0530
Subject: Re: [Sigtran] I-D ACTION:draft-kamesh-m3ua-congestion-procedures
	-00.txt
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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
     You are write that congestion status of PC X-Y-Z is obtained from the
overall congestion status of the individual routes. In the example given in
section 2.1 it is shown that PC X-Y-Z can be reached via SG1 and SG2 . So from
ASP perspective there are only two routes (via assoc a and assoc b). Congestion
status of PC X-Y-Z in the given section 2.1 is also derived from congestion
status of two routes i.e assoc a  and assoc b.  In other words congestion status
of PC X-Y-Z is equal to congestion status of more congested route (which is
nothing but the overall congestion status).

Regards
Kamesh




"Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com> on 01/22/2003 12:21:52
PM

To:   Kamesh Kaul/HSS@HSS
cc:   sigtran@ietf.org

Subject:  Re: [Sigtran] I-D
      ACTION:draft-kamesh-m3ua-congestion-procedures-00.txt





Kaul,

Section 2.1
       ...
       Now if "association a" undergoes congestion, congestion status of point
       code X-Y-Z maintained at ASP gets updated. If after some time
       "association b" undergoes congestion. Congestion status of point code
       X-Y-Z is updated if "association b" undergoes more congestion than
       "association a".


Here the overall X-Y-Z PC congestion status is updated based on a single
association congestion status.

Does it not conflict with RFC 3332 section 1.3.2.5?

IMO overall congestion status of  X-Y-Z PC
is obtained from the congestion status of the individual ROUTES but not
based on a single route.



--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 mailnull@www1.ietf.org  Wed Jan 22 09:13: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 JAA25305
	for <sigtran-archive@odin.ietf.org>; Wed, 22 Jan 2003 09:13:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0MEVvc24649
	for sigtran-archive@odin.ietf.org; Wed, 22 Jan 2003 09:31:57 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0MEVYJ24635;
	Wed, 22 Jan 2003 09:31:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0METwJ24526
	for <sigtran@optimus.ietf.org>; Wed, 22 Jan 2003 09:29:58 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25276
	for <sigtran@ietf.org>; Wed, 22 Jan 2003 09:11:23 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:tflNCfxHqZA+nRSHsUsnHWO3CZPC5ZVm@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0MEEoD28689;
	Wed, 22 Jan 2003 07:14:50 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0MEEot16671;
	Wed, 22 Jan 2003 07:14:50 -0700
Date: Wed, 22 Jan 2003 07:14:49 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Message-ID: <20030122071449.A12004@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <3E2E20D8.F28141F1@axes-mach01.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: <3E2E20D8.F28141F1@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Wed, Jan 22, 2003 at 10:10:57AM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: [M3UA] Heartbeat procedures
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>

Srini,

An M3UA peer must respond to a BEAT with a BEAT ACK.  If it doesn't
the M3UA sending the DEAT can assume that the peer is dead.  Its
that simple.

--brian

ksrinivas wrote:                               (Wed, 22 Jan 2003 10:10:57)
> Brian,
> 
> In Section, 4.3.4.6 Heartbeat Procedures of M3UA RFC, the following is
> mentioned.
> 
> [...Either M3UA peer may optionally send Heartbeat messages
> periodically, subject to a provisionable timer T(beat).  Upon receiving
> a Heartbeat message, the M3UA peer MUST respond with a Heartbeat Ack
> message...]
> 
> The following are understood from the above para:
> 
> 1. Heartbeat messages are periodically sent subject to a provisionable
> timer T(beat).
> 
> Once in every T(beat) interval, a Heartbeat message is sent.
> 
> 2. Upon receiving a Heartbeat message, the M3UA peer MUST respond with a
> Heartbeat Ack message.
> 
> Since Heartbeat message is sent Once in every T(beat) interval, the
> Heartbeat Ack message should also be received Once in every T(beat)
> interval if everything is proper.
> 
> Is my understanding proper?.
> 
> [...If no Heartbeat Ack message (or any other M3UA message) is received
> from the M3UA peer within 2*T(beat), the remote M3UA peer is considered
> unavailable.  Transmission of Heartbeat messages is stopped and the
> signalling process SHOULD attempt to re-establish communication if it is
> configured as the client for the disconnected M3UA peer...]
> 
> Can you please clarify my following doubts from the above para:
> 
> 1. In response to Heartbeat message sent, should the M3UA expect either
> the Heartbeat Ack message or any other M3UA message?
> 
> 2. What should happen if the Heartbeat Ack message is not received
> within the first T(beat) interval.?
>     Should we wait for one more T(beat) interval for the Heartbeat Ack
> message?.
> 
> --Srini

-- 
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 Jan 22 15:17: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 PAA05829
	for <sigtran-archive@odin.ietf.org>; Wed, 22 Jan 2003 15:17:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0MKZXI16946
	for sigtran-archive@odin.ietf.org; Wed, 22 Jan 2003 15:35:33 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0MKZBJ16930;
	Wed, 22 Jan 2003 15:35:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0MKXUJ16872
	for <sigtran@optimus.ietf.org>; Wed, 22 Jan 2003 15:33:30 -0500
Received: from mail.wrs.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05739
	for <sigtran@ietf.org>; Wed, 22 Jan 2003 15:14:48 -0500 (EST)
Received: from stskchen2 ([147.11.239.25])
	by mail.wrs.com (8.9.3/8.9.1) with SMTP id MAA27731
	for <sigtran@ietf.org>; Wed, 22 Jan 2003 12:17:17 -0800 (PST)
From: "Kevin Chen" <Kevin.Chen@windriver.com>
To: <sigtran@ietf.org>
Subject: [Sigtran] unsubscribe
Date: Wed, 22 Jan 2003 12:17:35 -0800
Message-ID: <000801c2c253$50363880$19ef0b93@wrs.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 CWS, Build 9.0.2416 (9.0.2910.0)
x-mimeole: Produced By Microsoft MimeOLE V5.50.4522.1200
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




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



From mailnull@www1.ietf.org  Wed Jan 22 16:01:23 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 QAA07037
	for <sigtran-archive@odin.ietf.org>; Wed, 22 Jan 2003 16:01:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0MLJZC20094
	for sigtran-archive@odin.ietf.org; Wed, 22 Jan 2003 16:19:35 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0MLJBJ20073;
	Wed, 22 Jan 2003 16:19:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0MLIZJ20045
	for <sigtran@optimus.ietf.org>; Wed, 22 Jan 2003 16:18:35 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06932
	for <sigtran@ietf.org>; Wed, 22 Jan 2003 15:59:52 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0ML3IBS018815;
	Wed, 22 Jan 2003 15:03:18 -0600 (CST)
Message-ID: <3E2F0716.10D17513@alcatel.com>
Date: Wed, 22 Jan 2003 15:03:18 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: sigtran@ietf.org
References: <200301211252.HAA27713@ietf.org> <3E2D77E1.A0A53F9D@alcatel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M2PA version 7 detailed list of changes
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

This is a more detailed list of changes. It is arranged according to
the order of the document. 

This list does not include minor changes to wording, formatting, etc.

General changes:

   Changed the reference format. E.g., [Q.703] instead of [2].

   Changed some requirement words to capital letters: SHOULD, MUST,
   etc. I MAY have missed some. Let me know if any SHOULD or MUST be
   changed. 

1.6.2 Support for peer-to-peer communication

   In last paragraph, removed "Link Status messages" since they are
   not used to carry acknowledgement. 

2.3.1 User Data 

   Added: "The User Data is an optional field. It need not be included
   in an acknowlegement-only message."

3.  M2PA Link State Control

   State IDLE changed to POWER OFF. 

   State AIP changed to INITIAL ALIGNMENT.

   Added states ALIGNED NOT READY and PROCESSOR OUTAGE.

   Removed state RETRIEVAL.

   Updated state diagram (Figure 7). Changes include:

      IDLE renamed POWER OFF. 

      AIP changed to INITIAL ALIGNMENT.

      Added arrow to OUT OF SERVICE: "Flush Buffers or Retrieval",
      since Retrieval state was removed. 

      Added "OR Receive LS OOS" to arrow INITIAL ALIGNMENT -> OOS.

      Added "OR T3 Expiry" (new timer T3) to arrow PROVING -> OOS.

      Added "Send LS Ready" to arrow PROVING -> ALIGNED READY. 

      Added "OR Receive LS Align" to arrow ALIGNED READY -> OOS.

      Added "OR Receive LS Align" to arrow IN SERVICE -> OOS.

      Added states ALIGNED NOT READY and PROCESSOR OUTAGE, and arrows
      in/out.

4.1.2 MTP and SCTP Entities

   Table 2 - Changed "IPSP Y" to "IPSP Y/Z" since same info applies to
   both.

4.1.3  Link Alignment

   Timer T1 is renamed to T2.

   Timer T3 is renamed to T1.

   Added new timer T3. Added statements about when T3 is started,
   stopped, and what happens if it expires.

      Paragraph "When M2PA has both...": Added "M2PA starts the
      aligned timer T3 and moves to the proving state."

      Added paragraphs:

         "M2PA stops timer T3 when it receives a Proving Normal or
	 Proving Emergency message and starts proving period timer
	 T4."

         "If timer T3 expires, then M2PA reports to MTP3 that the link
is out of
	 service.  M2PA sends Link Status Out of Service to its peer.
	 M2PA SHOULD leave the association established.  M2PA waits
	 for MTP3 to initiate the alignment procedure again."

   Paragraph "During the proving period...": Proving_Rate is changed
   to Proving_Interval, since that is a better description.

   Paragraph "When the proving period timer T4...": Added that M2PA
   goes to ALIGNED READY state. It is no longer required to send LS
   Ready periodically. It is allowed. Changed 

         "send Link Status Ready messages to its peer at interval
	 Status_Interval. These messages are used to verify that both
	 ends have completed proving."
      to
         "send a Link Status Ready message to its peer. These [oops - 
	 should be "the"] Link Status Ready message is used to verify
	 that both ends have completed proving. M2PA MAY send
	 additional Link Status Ready messages while timer T1 is
	 running."

   In paragraph "If M2PA receives a Stop command...", clarified that
   M2PA goes to OOS state.  

   In paragraph "Anomalous messages..." item (b) has added "before
   or" during proving.

   Recommended values: Changed these to be more consistent with Q.703.

   Recommended values: Removed Status_Interval.

   Recommended values: Changed Proving_Rate to Proving_Interval.

4.1.4 Processor Outage

   Paragraph "When M2PA detects ...": Changed "M2PA shall stop
   receiving incoming messages from SCTP" to "M2PA SHALL stop
   acknowledging received User Data messages."

   Paragraph "M2PA MAY send additional ...": It is no longer required
   to send LS PO periodically. It is allowed. Changed "M2PA should
   periodically send a Link Status Processor Outage message" to "M2PA
   MAY send additional Link Status Processor Outage messages".

   Paragraph "The peer M2PA ...": Timer T7 is disabled during
   PO. Added to end of paragraph, "and timer T7, if it is running."

   Paragraph "MTP3 may send a Flush Buffers...": Added sentence to
   point to Q.703, "The use of Flush Buffers and Continue is specified
   in Q.703 [Q.703] and T1.111.3 [T1.111]."

   Paragraph "When the processor outage ceases...": Moved sentence
   here from 4.2.4, "The local M2PA SHALL resume receiving and
   transmitting messages."

   Paragraph "If the peer is in the IN SERVICE...": Qualified that
   Indication is used only when in IN SERVICE. Changed "The peer uses
   the Remote Processor Recovered Indication" to "If the peer is in
   the IN SERVICE state, it uses the Remote Processor Recovered
   Indication".

4.1.5 Level 2 Flow Control

   Paragraph "M2PA MAY send additional..": It is no longer required to
   send the LS Busy messages periodically. It is allowed. Changed
   "M2PA should periodically send a Link Status Busy message" to "M2PA
   MAY send additional Link Status Busy messages".

   Paragraph "When the peer M2PA receives...": Since there can be more
   than one LS Busy message, this clarifies that the T6 timer is
   started only on the FIRST message. It is not restarted every time
   M2PA receives LS Busy. Added "first" and the sentence, "Additional
   Link Status Busy messages received while T6 is running do not cause
   T6 to be reset."

   Paragraph "If timer T6 expires...": Retrieval state was removed, so
   changed "Retrieval" to "Out of Service".

   Paragraph "Recommended values": Added T6 default 4.5 sec.

4.2.1  Sending and receiving messages

   Paragraph "The Forward Sequence Number ...": FSN is not incremented
   for the empty User Data messages. Added "(provided that the message
   contains a data payload)".

   Paragraph "If there is no other...": FSN is not incremented for the
   empty User Data messages. Changed "is incremented as with any other
   User Data message" to "is not incremented. It MUST contain the same
   FSN as the most recently sent User Data message containing Data."

   Added paragraphs:

      "If M2PA receives an empty User Data message, it SHALL NOT send
      an acknowledgement of that message."

      "Note that there is no reason to place empty User Data messages
      in the M2PA retransmit buffer, since the empty messages are not
      retransmitted and timer T7 (below) does not apply to them."


   Paragraph "Timer T7 provides...": 

      In (a), used clearer language. Changed "in the M2PA transmit
      buffer that has been sent" to "in the M2PA retransmit buffer".

      In (b), added for clarity, "(i.e., the local timer T6 is not
      running)".

      In (c), made T7 a per-message timer. Changed 
         "M2PA has not received an acknowledgement in the span of T7." 
      to 
         "There is a message in the M2PA retransmit buffer that has not
	 received an acknowledgement in the span of T7 since its last
	 transmission."

   Paragraph "Recommended values": Added T7 default 1.0 sec.

4.2.4  Flush Buffers and Continue

   Paragraph was deleted: "If M2PA receives either a Flush Buffers or
   Continue command from MTP3, and the processor outage condition
   ceases, M2PA shall resume receiving and transmitting messages." The
   information was moved to 4.1.4.

5.  Examples of M2PA Procedures

   Throughout this section: 

      Added Figure numbers for the diagrams.

      Added dots to improve readability.

5.1  Link Initialization (Alignment)

   Figures 12 and 13: Renamed timers as in the text. 

   Figure 13: Changed to show only one LS Alignment sent. Changed text
   in the figure from "Send Link Status Ready until" to "Send Link
   Status Ready (one or more)".

7.1 SCTP Payload Protocol Identifier

   Paragraph "The SCTP...": Added UDP. Oops. This should not have been
   added. M2PA has a registered port for SCTP and TCP, not UDP.

9.  References 

   Changed the reference format and updated some of the references. 

10.  Author's Addresses

   Updated some of the authors' information.


================================================================



-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 23 00:20: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 AAA17641
	for <sigtran-archive@odin.ietf.org>; Thu, 23 Jan 2003 00:20:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0N5ckT17021
	for sigtran-archive@odin.ietf.org; Thu, 23 Jan 2003 00:38:46 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0N5cUJ17010;
	Thu, 23 Jan 2003 00:38:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0N5bYJ16978
	for <sigtran@optimus.ietf.org>; Thu, 23 Jan 2003 00:37:34 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17619
	for <sigtran@ietf.org>; Thu, 23 Jan 2003 00:18:41 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0N5M1bg003564;
	Wed, 22 Jan 2003 23:22:02 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id JAA23426; Thu, 23 Jan 2003 09:51:16 -0500 (GMT)
Message-ID: <3E2F7C19.EAC8641@axes-mach01.usa.alcatel.com>
Date: Thu, 23 Jan 2003 10:52:34 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: sigtran@ietf.org
References: <3E2E20D8.F28141F1@axes-mach01.usa.alcatel.com> <20030122071449.A12004@openss7.org>
Content-Type: multipart/alternative;
 boundary="------------EEC081EAECB01740CBCEFCAD"
Subject: [Sigtran] Re: [M3UA] Heartbeat procedures
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>


--------------EEC081EAECB01740CBCEFCAD
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 7bit

Brian,

    In Section, 4.3.4.6 Heartbeat Procedures of M3UA RFC, Why are the
following things mentioned?.

 [...If no Heartbeat Ack message (or any other M3UA message) is received from
the M3UA peer within 2*T(beat), the remote M3UA peer is considered
unavailable...]

  1. Why "or any other M3UA message" is mentioned?.
  2. What is 2*T(beat)?. Does it mean that we have to send Heartbeat message
once in every 2*T(beat) interval?.

--Srini

"Brian F. G. Bidulock" wrote:

> Srini,
>
> An M3UA peer must respond to a BEAT with a BEAT ACK.  If it doesn't
> the M3UA sending the DEAT can assume that the peer is dead.  Its
> that simple.
>
> --brian
>
> ksrinivas wrote:                               (Wed, 22 Jan 2003 10:10:57)
> > Brian,
> >
> > In Section, 4.3.4.6 Heartbeat Procedures of M3UA RFC, the following is
> > mentioned.
> >
> > [...Either M3UA peer may optionally send Heartbeat messages
> > periodically, subject to a provisionable timer T(beat).  Upon receiving
> > a Heartbeat message, the M3UA peer MUST respond with a Heartbeat Ack
> > message...]
> >
> > The following are understood from the above para:
> >
> > 1. Heartbeat messages are periodically sent subject to a provisionable
> > timer T(beat).
> >
> > Once in every T(beat) interval, a Heartbeat message is sent.
> >
> > 2. Upon receiving a Heartbeat message, the M3UA peer MUST respond with a
> > Heartbeat Ack message.
> >
> > Since Heartbeat message is sent Once in every T(beat) interval, the
> > Heartbeat Ack message should also be received Once in every T(beat)
> > interval if everything is proper.
> >
> > Is my understanding proper?.
> >
> > [...If no Heartbeat Ack message (or any other M3UA message) is received
> > from the M3UA peer within 2*T(beat), the remote M3UA peer is considered
> > unavailable.  Transmission of Heartbeat messages is stopped and the
> > signalling process SHOULD attempt to re-establish communication if it is
> > configured as the client for the disconnected M3UA peer...]
> >
> > Can you please clarify my following doubts from the above para:
> >
> > 1. In response to Heartbeat message sent, should the M3UA expect either
> > the Heartbeat Ack message or any other M3UA message?
> >
> > 2. What should happen if the Heartbeat Ack message is not received
> > within the first T(beat) interval.?
> >     Should we wait for one more T(beat) interval for the Heartbeat Ack
> > message?.
> >
> > --Srini
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/

--------------EEC081EAECB01740CBCEFCAD
Content-Type: text/html; charset=x-user-defined
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Brian,
<p>&nbsp;&nbsp;&nbsp; In Section, 4.3.4.6 Heartbeat Procedures of M3UA
RFC, Why are the following things mentioned?.
<p>&nbsp;[...If no Heartbeat Ack message (<b>or any other M3UA message</b>)
is received from the M3UA peer within 2*T(beat), the remote M3UA peer is
considered unavailable...]
<p>&nbsp; 1. Why "or any other M3UA message" is mentioned?.
<br>&nbsp; 2. What is 2*T(beat)?. Does it mean that we have to send Heartbeat
message once in every 2*T(beat) interval?.
<p>--Srini
<p>"Brian F. G. Bidulock" wrote:
<blockquote TYPE=CITE>Srini,
<p>An M3UA peer must respond to a BEAT with a BEAT ACK.&nbsp; If it doesn't
<br>the M3UA sending the DEAT can assume that the peer is dead.&nbsp; Its
<br>that simple.
<p>--brian
<p>ksrinivas wrote:&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;
(Wed, 22 Jan 2003 10:10:57)
<br>> Brian,
<br>>
<br>> In Section, 4.3.4.6 Heartbeat Procedures of M3UA RFC, the following
is
<br>> mentioned.
<br>>
<br>> [...Either M3UA peer may optionally send Heartbeat messages
<br>> periodically, subject to a provisionable timer T(beat).&nbsp; Upon
receiving
<br>> a Heartbeat message, the M3UA peer MUST respond with a Heartbeat
Ack
<br>> message...]
<br>>
<br>> The following are understood from the above para:
<br>>
<br>> 1. Heartbeat messages are periodically sent subject to a provisionable
<br>> timer T(beat).
<br>>
<br>> Once in every T(beat) interval, a Heartbeat message is sent.
<br>>
<br>> 2. Upon receiving a Heartbeat message, the M3UA peer MUST respond
with a
<br>> Heartbeat Ack message.
<br>>
<br>> Since Heartbeat message is sent Once in every T(beat) interval, the
<br>> Heartbeat Ack message should also be received Once in every T(beat)
<br>> interval if everything is proper.
<br>>
<br>> Is my understanding proper?.
<br>>
<br>> [...If no Heartbeat Ack message (or any other M3UA message) is received
<br>> from the M3UA peer within 2*T(beat), the remote M3UA peer is considered
<br>> unavailable.&nbsp; Transmission of Heartbeat messages is stopped
and the
<br>> signalling process SHOULD attempt to re-establish communication if
it is
<br>> configured as the client for the disconnected M3UA peer...]
<br>>
<br>> Can you please clarify my following doubts from the above para:
<br>>
<br>> 1. In response to Heartbeat message sent, should the M3UA expect
either
<br>> the Heartbeat Ack message or any other M3UA message?
<br>>
<br>> 2. What should happen if the Heartbeat Ack message is not received
<br>> within the first T(beat) interval.?
<br>>&nbsp;&nbsp;&nbsp;&nbsp; Should we wait for one more T(beat) interval
for the Heartbeat Ack
<br>> message?.
<br>>
<br>> --Srini
<p>--
<br>Brian F. G. Bidulock
<br>bidulock@openss7.org
<br><a href="http://www.openss7.org/">http://www.openss7.org/</a></blockquote>
</html>

--------------EEC081EAECB01740CBCEFCAD--

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



From mailnull@www1.ietf.org  Thu Jan 23 00:23:08 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 AAA17708
	for <sigtran-archive@odin.ietf.org>; Thu, 23 Jan 2003 00:23:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0N5fT817176
	for sigtran-archive@odin.ietf.org; Thu, 23 Jan 2003 00:41:29 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0N5f5J17128;
	Thu, 23 Jan 2003 00:41:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0N5eNJ17100
	for <sigtran@optimus.ietf.org>; Thu, 23 Jan 2003 00:40:23 -0500
Received: from hermes.fm.intel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17656
	for <sigtran@ietf.org>; Thu, 23 Jan 2003 00:21:30 -0500 (EST)
Received: from talaria.fm.intel.com (talaria.fm.intel.com [10.1.192.39])
	by hermes.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id h0N5MEj11033
	for <sigtran@ietf.org>; Thu, 23 Jan 2003 05:22:14 GMT
Received: from fmsmsxvs042.fm.intel.com (fmsmsxvs042.fm.intel.com [132.233.42.128])
	by talaria.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.28 2003/01/13 19:44:39 dmccart Exp $) with SMTP id h0N5Qr802393
	for <sigtran@ietf.org>; Thu, 23 Jan 2003 05:26:53 GMT
Received: from fmsmsx29.FM.INTEL.COM ([132.233.42.29])
 by fmsmsxvs042.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2003012221264724553
 for <sigtran@ietf.org>; Wed, 22 Jan 2003 21:26:47 -0800
Received: by fmsmsx29.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <XTSR3R4Z>; Wed, 22 Jan 2003 21:24:56 -0800
Message-ID: <12B638FEE763F74696D8544752E72048028E8478@bgsmsx101.iind.intel.com>
From: "Saxena, Anoop" <anoop.saxena@intel.com>
To: sigtran@ietf.org
Date: Wed, 22 Jan 2003 21:20:06 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2C29F.177BC090"
Subject: [Sigtran] unsubscribe
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 message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C2C29F.177BC090
Content-Type: text/plain

 


------_=_NextPart_001_01C2C29F.177BC090
Content-Type: text/html

<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">


<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C2C29F.177BC090--
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jan 23 00:34: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 AAA17909
	for <sigtran-archive@odin.ietf.org>; Thu, 23 Jan 2003 00:34:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0N5qUd17631
	for sigtran-archive@odin.ietf.org; Thu, 23 Jan 2003 00:52:30 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0N5q7J17619;
	Thu, 23 Jan 2003 00:52:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0N5pHJ17595
	for <sigtran@optimus.ietf.org>; Thu, 23 Jan 2003 00:51:17 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17894
	for <sigtran@ietf.org>; Thu, 23 Jan 2003 00:32:24 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:PXUjrWGu/LMonatLkqs3742sGxkoIGBP@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0N5ZoD13576;
	Wed, 22 Jan 2003 22:35:50 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0N5ZoZ13937;
	Wed, 22 Jan 2003 22:35:50 -0700
Date: Wed, 22 Jan 2003 22:35:50 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Message-ID: <20030122223550.A13852@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <3E2E20D8.F28141F1@axes-mach01.usa.alcatel.com> <20030122071449.A12004@openss7.org> <3E2F7C19.EAC8641@axes-mach01.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: <3E2F7C19.EAC8641@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Thu, Jan 23, 2003 at 10:52:34AM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: [M3UA] Heartbeat procedures
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>

ksrinivas,

ksrinivas wrote:                                                                 (Thu, 23 Jan 2003 10:52:34)
> 
>    Brian,
> 
>         In Section, 4.3.4.6 Heartbeat Procedures of M3UA RFC, Why are the
>    following things mentioned?.
> 
>     [...If  no  Heartbeat  Ack  message  (or  any  other M3UA message) is
>    received  from the M3UA peer within 2*T(beat), the remote M3UA peer is
>    considered unavailable...]
> 
>      1. Why "or any other M3UA message" is mentioned?.

The M3UA peer is hardly "dead" if it is sending messages.

>       2.  What is 2*T(beat)?. Does it mean that we have to send Heartbeat
>    message once in every 2*T(beat) interval?.

Sounds like a reasonable time to wait, doesn't it?

--brian

> 
>    --Srini
> 
>    "Brian F. G. Bidulock" wrote:
> 
>      Srini,
> 
>      An M3UA peer must respond to a BEAT with a BEAT ACK.  If it doesn't
>      the M3UA sending the DEAT can assume that the peer is dead.  Its
>      that simple.
> 
>      --brian
> 
>      ksrinivas  wrote:                                (Wed,  22 Jan 2003
>      10:10:57)
>      > Brian,
>      >
>      >  In  Section,  4.3.4.6  Heartbeat  Procedures  of  M3UA  RFC, the
>      following is
>      > mentioned.
>      >
>      > [...Either M3UA peer may optionally send Heartbeat messages
>      >  periodically,  subject  to  a provisionable timer T(beat).  Upon
>      receiving
>      >  a Heartbeat message, the M3UA peer MUST respond with a Heartbeat
>      Ack
>      > message...]
>      >
>      > The following are understood from the above para:
>      >
>      >  1.  Heartbeat  messages  are  periodically  sent  subject  to  a
>      provisionable
>      > timer T(beat).
>      >
>      > Once in every T(beat) interval, a Heartbeat message is sent.
>      >
>      > 2. Upon receiving a Heartbeat message, the M3UA peer MUST respond
>      with a
>      > Heartbeat Ack message.
>      >
>      >  Since  Heartbeat message is sent Once in every T(beat) interval,
>      the
>      >  Heartbeat  Ack  message  should  also  be received Once in every
>      T(beat)
>      > interval if everything is proper.
>      >
>      > Is my understanding proper?.
>      >
>      >  [...If  no  Heartbeat Ack message (or any other M3UA message) is
>      received
>      >  from  the  M3UA  peer  within 2*T(beat), the remote M3UA peer is
>      considered
>      >  unavailable.   Transmission of Heartbeat messages is stopped and
>      the
>      >  signalling  process SHOULD attempt to re-establish communication
>      if it is
>      > configured as the client for the disconnected M3UA peer...]
>      >
>      > Can you please clarify my following doubts from the above para:
>      >
>      >  1. In response to Heartbeat message sent, should the M3UA expect
>      either
>      > the Heartbeat Ack message or any other M3UA message?
>      >
>      >  2.  What  should  happen  if  the  Heartbeat  Ack message is not
>      received
>      > within the first T(beat) interval.?
>      >      Should  we  wait  for  one  more  T(beat)  interval  for the
>      Heartbeat Ack
>      > message?.
>      >
>      > --Srini
> 
>      --
>      Brian F. G. Bidulock
>      bidulock@openss7.org
>      [1]http://www.openss7.org/
> 
> References
> 
>    1. 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 mailnull@www1.ietf.org  Thu Jan 23 06:37: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 GAA03310
	for <sigtran-archive@odin.ietf.org>; Thu, 23 Jan 2003 06:37:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0NBtYq18013
	for sigtran-archive@odin.ietf.org; Thu, 23 Jan 2003 06:55:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0NBsrJ17984;
	Thu, 23 Jan 2003 06:54:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0NBqGJ17924
	for <sigtran@optimus.ietf.org>; Thu, 23 Jan 2003 06:52:16 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03176
	for <sigtran@ietf.org>; Thu, 23 Jan 2003 06:33:16 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0NBadVN024094;
	Thu, 23 Jan 2003 05:36:41 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id QAA02529; Thu, 23 Jan 2003 16:05:54 -0500 (GMT)
Message-ID: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com>
Date: Thu, 23 Jan 2003 17:07:16 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: sigtran@ietf.org
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M3UA Routing Keys partial match
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

Brian,

  Let us assume that the following two RKs are registered with an SGP

  REG REQ (RK1, DPC X, SI = Y)
  REG REQ (RK2, DPC X, SI = Z)

and from SS7 network, say a MSU with DPC X and SI = Z is received.

When M3UA at SGP tries to match DPC X and SI = Z with the first(DPC X,
SI = Y) Routing Key, Does it not treat it as a partial match?.(as DPC
matches).

--Srini

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



From mailnull@www1.ietf.org  Thu Jan 23 07:10: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 HAA03792
	for <sigtran-archive@odin.ietf.org>; Thu, 23 Jan 2003 07:10:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0NCSiW19965
	for sigtran-archive@odin.ietf.org; Thu, 23 Jan 2003 07:28:44 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0NCSGJ19941;
	Thu, 23 Jan 2003 07:28:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0NCR0J19894
	for <sigtran@optimus.ietf.org>; Thu, 23 Jan 2003 07:27:00 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03751
	for <sigtran@ietf.org>; Thu, 23 Jan 2003 07:07:59 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:iLYK78ob3ObBr3Cy/qXZdezeXAxgxrZA@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0NCBPD21230;
	Thu, 23 Jan 2003 05:11:25 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0NCBPx20834;
	Thu, 23 Jan 2003 05:11:25 -0700
Date: Thu, 23 Jan 2003 05:11:25 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Message-ID: <20030123051125.C20273@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <3E2FD3EB.91B957CD@axes-mach01.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: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Thu, Jan 23, 2003 at 05:07:16PM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: M3UA Routing Keys partial match
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>

Srini,

Here are the two same routing keys:

  RK1, OPC * DPC X SI Y
  RK1, OPC * DPC X SI Z

A message arrives with OPC A and DPC Q and SI W.  Does it not
partially match the first routing key because OPC A matches
the wildcard on OPC?

No.  When the RFC say partial match it is referring to the
message OPC A, DPC X, SI Y having a partial match to RK1.
(It does not match in OPC because OPC is "wildcarded".)

--brian


ksrinivas wrote:                                                                 (Thu, 23 Jan 2003 17:07:16)
> Brian,
> 
>   Let us assume that the following two RKs are registered with an SGP
> 
>   REG REQ (RK1, DPC X, SI = Y)
>   REG REQ (RK2, DPC X, SI = Z)
> 
> and from SS7 network, say a MSU with DPC X and SI = Z is received.
> 
> When M3UA at SGP tries to match DPC X and SI = Z with the first(DPC X,
> SI = Y) Routing Key, Does it not treat it as a partial match?.(as DPC
> matches).
> 
> --Srini

-- 
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 Jan 23 07:50: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 HAA05007
	for <sigtran-archive@odin.ietf.org>; Thu, 23 Jan 2003 07:50:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ND8lp23016
	for sigtran-archive@odin.ietf.org; Thu, 23 Jan 2003 08:08:47 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ND8XJ22987;
	Thu, 23 Jan 2003 08:08:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ND5sJ22161
	for <sigtran@optimus.ietf.org>; Thu, 23 Jan 2003 08:05:54 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04805;
	Thu, 23 Jan 2003 07:46:53 -0500 (EST)
Message-Id: <200301231246.HAA04805@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: Thu, 23 Jan 2003 07:46:53 -0500
Subject: [Sigtran] I-D ACTION:draft-ietf-sigtran-signalling-over-sctp-applic-07.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		: Telephony Signalling Transport over SCTP applicability
                          statement
	Author(s)	: L. Coene, J. Pastor
	Filename	: draft-ietf-sigtran-signalling-over-sctp-applic-07.txt
	Pages		: 23
	Date		: 2003-1-22
	
This document describes the applicability of the new protocols
developed under the signaling transport framework[RFC2719]. A
description of the main issues regarding the use of the Stream
Control Transmission Protocol (SCTP)[RFC2960] and each adaptation
layer for transport of telephony signalling information over IP
infrastructure is explained.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sigtran-signalling-over-sctp-applic-07.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-signalling-over-sctp-applic-07.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-signalling-over-sctp-applic-07.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-1-22111514.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sigtran-signalling-over-sctp-applic-07.txt

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

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

--OtherAccess--

--NextPart--


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



From mailnull@www1.ietf.org  Thu Jan 23 10:20: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 KAA09927
	for <sigtran-archive@odin.ietf.org>; Thu, 23 Jan 2003 10:20:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0NFdI901108
	for sigtran-archive@odin.ietf.org; Thu, 23 Jan 2003 10:39:18 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0NFcUJ01075;
	Thu, 23 Jan 2003 10:38:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0NFF5J31981
	for <sigtran@optimus.ietf.org>; Thu, 23 Jan 2003 10:15:05 -0500
Received: from beamer.mchh.siemens.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09424
	for <sigtran@ietf.org>; Thu, 23 Jan 2003 09:56:00 -0500 (EST)
Received: from blues.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.227])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id PAA18936
	for <sigtran@ietf.org>; Thu, 23 Jan 2003 15:59:27 +0100 (MET)
Received: from mchh274e.demchh201e.icn.siemens.de ([139.21.200.84])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id PAA27701
	for <sigtran@ietf.org>; Thu, 23 Jan 2003 15:59:10 +0100 (MET)
Received: by MCHH274E with Internet Mail Service (5.5.2656.59)
	id <D13JGYW8>; Thu, 23 Jan 2003 15:58:40 +0100
Message-ID: <3D72C18DF140D311A54F0008C7DBAC8D02917425@MCHH252E>
From: Gaiser Franz <franz.gaiser@siemens.com>
To: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA version 7 changes
Date: Thu, 23 Jan 2003 15:58:40 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
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>

Dear All,

some remarks to the new draft version 07:

1.)  Figure 7. M2PA Link State Transition Diagram:
Why is there an arrow from state INITIAL ALIGNMENT to state ALIGNED NOT READY  ? If the local side is in processor outage, the PROVING period should be passed before moving to ALIGNED NOT READY state.
2.) Figure 7. M2PA Link State Transition Diagram:
Missing the handling of receiving LS PO in state ALIGNED READY. Transition to PROCESSOR OUTAGE ? If so, the state PROCESSOR OUTAGE handles both local and remote processor outage and then there must be an arrow from PO to IN SERVICE in case of receiving LS PO Recovered (no local PO situation).
3.) Figure 7. M2PA Link State Transition Diagram:
Missing the handling of receiving User data in state ALIGNED NOT READY. Transition to PROCESSOR OUTAGE ? What is to do with this message then ?
4.) 4.2.1 Paragraph "If M2PA receives a User Data message with an FSN that is out of order, M2PA SHALL take the link out of service."
Does "take the link out of service"  mean also that the peer side is informed via sending LS OOS message.
5.) Figure 13. Example: Link Initialization - Proving
New Timer T3 "ALIGNED" is missing in the figure.


best regards, Franz 
  

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



From mailnull@www1.ietf.org  Thu Jan 23 11:33: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 LAA12410
	for <sigtran-archive@odin.ietf.org>; Thu, 23 Jan 2003 11:33:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0NGpn106478
	for sigtran-archive@odin.ietf.org; Thu, 23 Jan 2003 11:51:49 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0NGp1J06415;
	Thu, 23 Jan 2003 11:51:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0NGnrJ06340
	for <sigtran@optimus.ietf.org>; Thu, 23 Jan 2003 11:49:53 -0500
Received: from web11408.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA12329
	for <sigtran@ietf.org>; Thu, 23 Jan 2003 11:30:46 -0500 (EST)
Message-ID: <20030123163413.53592.qmail@web11408.mail.yahoo.com>
Received: from [208.255.120.2] by web11408.mail.yahoo.com via HTTP; Thu, 23 Jan 2003 08:34:13 PST
Date: Thu, 23 Jan 2003 08:34:13 -0800 (PST)
From: V K <vlakshmi70@yahoo.com>
To: sigtran@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Sigtran] query 3331
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,

It says in the RFC 3331, section 1.5.4.1
that "an implementation can choose to split
the SS7 link across several streams based on
SLS".

what does this mean.

thanks.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jan 23 11:37:15 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 LAA12593
	for <sigtran-archive@odin.ietf.org>; Thu, 23 Jan 2003 11:37:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0NGtpo06732
	for sigtran-archive@odin.ietf.org; Thu, 23 Jan 2003 11:55:51 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0NGt6J06707;
	Thu, 23 Jan 2003 11:55:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0NGrxJ06586
	for <sigtran@optimus.ietf.org>; Thu, 23 Jan 2003 11:53:59 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12444
	for <sigtran@ietf.org>; Thu, 23 Jan 2003 11:34:50 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Na6Q6VPAB/KaF+jX5quWj1Bk0bbtnQsD@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0NGcID26170;
	Thu, 23 Jan 2003 09:38:18 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0NGcH026857;
	Thu, 23 Jan 2003 09:38:17 -0700
Date: Thu, 23 Jan 2003 09:38:17 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: V K <vlakshmi70@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] query 3331
Message-ID: <20030123093817.A26800@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: V K <vlakshmi70@yahoo.com>, sigtran@ietf.org
References: <20030123163413.53592.qmail@web11408.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: <20030123163413.53592.qmail@web11408.mail.yahoo.com>; from vlakshmi70@yahoo.com on Thu, Jan 23, 2003 at 08:34:13AM -0800
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>

V,

It means send messages with one SLS value on one
stream and messages with another SLS value on
another stream.

--brian

V K wrote:                                                                               (Thu, 23 Jan 2003 08:34:13)
> Hi,
> 
> It says in the RFC 3331, section 1.5.4.1
> that "an implementation can choose to split
> the SS7 link across several streams based on
> SLS".
> 
> what does this mean.
> 
> thanks.
> 
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.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 Jan 23 23:34: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 XAA00090
	for <sigtran-archive@odin.ietf.org>; Thu, 23 Jan 2003 23:34:13 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0O4r3Q20822
	for sigtran-archive@odin.ietf.org; Thu, 23 Jan 2003 23:53:03 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0O4qmJ20804;
	Thu, 23 Jan 2003 23:52:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0O4l0J20651
	for <sigtran@optimus.ietf.org>; Thu, 23 Jan 2003 23:47:00 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00016
	for <sigtran@ietf.org>; Thu, 23 Jan 2003 23:27:39 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0O4UTBS001396;
	Thu, 23 Jan 2003 22:30:40 -0600 (CST)
Received: from axsppc67 by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id IAA16652; Fri, 24 Jan 2003 08:58:51 -0500 (GMT)
Message-ID: <013701c2c361$78dd0570$7501ff0a@axsppc67>
From: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
To: <bidulock@openss7.org>, "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
Cc: <sigtran@ietf.org>
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org>
Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
Date: Fri, 24 Jan 2003 10:01:20 +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.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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

Brian,

What about the following routing keys? Are they valid?

RK1, DPC X
RK2, DPC X, SIO Y
RK3, DPC X, SIO Y, OPC A
RK4, DPC X, SIO Y, OPC B
RK5, DPC X, SIO Y, OPC *

thanks
Chak

----- Original Message -----
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
Cc: <sigtran@ietf.org>
Sent: Thursday, January 23, 2003 5:41 PM
Subject: [Sigtran] Re: M3UA Routing Keys partial match


> Srini,
>
> Here are the two same routing keys:
>
>   RK1, OPC * DPC X SI Y
>   RK1, OPC * DPC X SI Z
>
> A message arrives with OPC A and DPC Q and SI W.  Does it not
> partially match the first routing key because OPC A matches
> the wildcard on OPC?
>
> No.  When the RFC say partial match it is referring to the
> message OPC A, DPC X, SI Y having a partial match to RK1.
> (It does not match in OPC because OPC is "wildcarded".)
>
> --brian
>
>
> ksrinivas wrote:
(Thu, 23 Jan 2003 17:07:16)
> > Brian,
> >
> >   Let us assume that the following two RKs are registered with an SGP
> >
> >   REG REQ (RK1, DPC X, SI = Y)
> >   REG REQ (RK2, DPC X, SI = Z)
> >
> > and from SS7 network, say a MSU with DPC X and SI = Z is received.
> >
> > When M3UA at SGP tries to match DPC X and SI = Z with the first(DPC X,
> > SI = Y) Routing Key, Does it not treat it as a partial match?.(as DPC
> > matches).
> >
> > --Srini
>
> --
> 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 mailnull@www1.ietf.org  Fri Jan 24 00:08: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 AAA00622
	for <sigtran-archive@odin.ietf.org>; Fri, 24 Jan 2003 00:08:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0O5RXX22509
	for sigtran-archive@odin.ietf.org; Fri, 24 Jan 2003 00:27:33 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0O5RAJ22490;
	Fri, 24 Jan 2003 00:27:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0O5QrJ22474
	for <sigtran@optimus.ietf.org>; Fri, 24 Jan 2003 00:26:53 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00598
	for <sigtran@ietf.org>; Fri, 24 Jan 2003 00:07:31 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:XnwWbFyRxxCdVIWFJ2/ByfeaNPwNmH0k@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0O5AxD06588;
	Thu, 23 Jan 2003 22:10:59 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0O5Axw14384;
	Thu, 23 Jan 2003 22:10:59 -0700
Date: Thu, 23 Jan 2003 22:10:58 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>
Cc: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
Message-ID: <20030123221058.A14261@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>,
	ksrinivas <ksrini@axes-mach01.usa.alcatel.com>, sigtran@ietf.org
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org> <013701c2c361$78dd0570$7501ff0a@axsppc67>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <013701c2c361$78dd0570$7501ff0a@axsppc67>; from chak@axes-mach01.usa.alcatel.com on Fri, Jan 24, 2003 at 10:01:20AM +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>

PSK,

Depends on the SG.

--brian

PSK Chakravarthi wrote:                                                                (Fri, 24 Jan 2003 10:01:20)
> Brian,
> 
> What about the following routing keys? Are they valid?
> 
> RK1, DPC X
> RK2, DPC X, SIO Y
> RK3, DPC X, SIO Y, OPC A
> RK4, DPC X, SIO Y, OPC B
> RK5, DPC X, SIO Y, OPC *
> 
> thanks
> Chak
> 
> ----- Original Message -----
> From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> To: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
> Cc: <sigtran@ietf.org>
> Sent: Thursday, January 23, 2003 5:41 PM
> Subject: [Sigtran] Re: M3UA Routing Keys partial match
> 
> 
> > Srini,
> >
> > Here are the two same routing keys:
> >
> >   RK1, OPC * DPC X SI Y
> >   RK1, OPC * DPC X SI Z
> >
> > A message arrives with OPC A and DPC Q and SI W.  Does it not
> > partially match the first routing key because OPC A matches
> > the wildcard on OPC?
> >
> > No.  When the RFC say partial match it is referring to the
> > message OPC A, DPC X, SI Y having a partial match to RK1.
> > (It does not match in OPC because OPC is "wildcarded".)
> >
> > --brian
> >
> >
> > ksrinivas wrote:
> (Thu, 23 Jan 2003 17:07:16)
> > > Brian,
> > >
> > >   Let us assume that the following two RKs are registered with an SGP
> > >
> > >   REG REQ (RK1, DPC X, SI = Y)
> > >   REG REQ (RK2, DPC X, SI = Z)
> > >
> > > and from SS7 network, say a MSU with DPC X and SI = Z is received.
> > >
> > > When M3UA at SGP tries to match DPC X and SI = Z with the first(DPC X,
> > > SI = Y) Routing Key, Does it not treat it as a partial match?.(as DPC
> > > matches).
> > >
> > > --Srini
> >
> > --
> > 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 mailnull@www1.ietf.org  Fri Jan 24 01:02: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 BAA01285
	for <sigtran-archive@odin.ietf.org>; Fri, 24 Jan 2003 01:02:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0O6LSm25492
	for sigtran-archive@odin.ietf.org; Fri, 24 Jan 2003 01:21:28 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0O6KvJ25460;
	Fri, 24 Jan 2003 01:20:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0O6IOJ25373
	for <sigtran@optimus.ietf.org>; Fri, 24 Jan 2003 01:18:24 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01199
	for <sigtran@ietf.org>; Fri, 24 Jan 2003 00:59:02 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0O61fVN009311;
	Fri, 24 Jan 2003 00:01:47 -0600 (CST)
Received: from axsppc67 by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id KAA18939; Fri, 24 Jan 2003 10:30:54 -0500 (GMT)
Message-ID: <015c01c2c36e$55254540$7501ff0a@axsppc67>
From: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
To: <bidulock@openss7.org>
Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>, <sigtran@ietf.org>
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org> <013701c2c361$78dd0570$7501ff0a@axsppc67> <20030123221058.A14261@openss7.org>
Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
Date: Fri, 24 Jan 2003 11:33:23 +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.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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

Brian,

Why I asked is, MSU with DPC X, SIO Y, OPC A will give three full matches,
RK1, RK3 and RK5.  As per RFC we should design RKs such that we will get
only one full/partial match.

[Section 1.4.2.2 says
   Routing Keys SHOULD be unique in the sense that each received SS7
   signalling message SHOULD have a full or partial match to a single
   routing result.]

Similarly when we receive an MSU with DPC X, SIO Y we will have two full
matches, RK1 and RK2. We can derive many cases which will give more than one
full match.  To which AS SGP will route when it finds more than one full
match in the routing key list.

IMO, Routing keys should be designed in such a manner that there will be
only one full match.

I am not getting what is a partial match. Can you please explain what is a
partial match with an example?

thanks
Chak

----- Original Message -----
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>; <sigtran@ietf.org>
Sent: Friday, January 24, 2003 10:40 AM
Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match


> PSK,
>
> Depends on the SG.
>
> --brian
>
> PSK Chakravarthi wrote:
(Fri, 24 Jan 2003 10:01:20)
> > Brian,
> >
> > What about the following routing keys? Are they valid?
> >
> > RK1, DPC X
> > RK2, DPC X, SIO Y
> > RK3, DPC X, SIO Y, OPC A
> > RK4, DPC X, SIO Y, OPC B
> > RK5, DPC X, SIO Y, OPC *
> >
> > thanks
> > Chak
> >
> > ----- Original Message -----
> > From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > To: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
> > Cc: <sigtran@ietf.org>
> > Sent: Thursday, January 23, 2003 5:41 PM
> > Subject: [Sigtran] Re: M3UA Routing Keys partial match
> >
> >
> > > Srini,
> > >
> > > Here are the two same routing keys:
> > >
> > >   RK1, OPC * DPC X SI Y
> > >   RK1, OPC * DPC X SI Z
> > >
> > > A message arrives with OPC A and DPC Q and SI W.  Does it not
> > > partially match the first routing key because OPC A matches
> > > the wildcard on OPC?
> > >
> > > No.  When the RFC say partial match it is referring to the
> > > message OPC A, DPC X, SI Y having a partial match to RK1.
> > > (It does not match in OPC because OPC is "wildcarded".)
> > >
> > > --brian
> > >
> > >
> > > ksrinivas wrote:
> > (Thu, 23 Jan 2003 17:07:16)
> > > > Brian,
> > > >
> > > >   Let us assume that the following two RKs are registered with an
SGP
> > > >
> > > >   REG REQ (RK1, DPC X, SI = Y)
> > > >   REG REQ (RK2, DPC X, SI = Z)
> > > >
> > > > and from SS7 network, say a MSU with DPC X and SI = Z is received.
> > > >
> > > > When M3UA at SGP tries to match DPC X and SI = Z with the first(DPC
X,
> > > > SI = Y) Routing Key, Does it not treat it as a partial match?.(as
DPC
> > > > matches).
> > > >
> > > > --Srini
> > >
> > > --
> > > 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 mailnull@www1.ietf.org  Fri Jan 24 01:18: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 BAA01469
	for <sigtran-archive@odin.ietf.org>; Fri, 24 Jan 2003 01:18:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0O6bbx26648
	for sigtran-archive@odin.ietf.org; Fri, 24 Jan 2003 01:37:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0O6bBJ26334;
	Fri, 24 Jan 2003 01:37:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0O6asJ25958
	for <sigtran@optimus.ietf.org>; Fri, 24 Jan 2003 01:36:54 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01456
	for <sigtran@ietf.org>; Fri, 24 Jan 2003 01:17:31 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:EaQC47xzBfppODcL3Ac9yNFAWbq9sGEe@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0O6KwD07623;
	Thu, 23 Jan 2003 23:20:58 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0O6KvA15613;
	Thu, 23 Jan 2003 23:20:57 -0700
Date: Thu, 23 Jan 2003 23:20:57 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>
Cc: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
Message-ID: <20030123232057.A15212@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>,
	ksrinivas <ksrini@axes-mach01.usa.alcatel.com>, sigtran@ietf.org
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org> <013701c2c361$78dd0570$7501ff0a@axsppc67> <20030123221058.A14261@openss7.org> <015c01c2c36e$55254540$7501ff0a@axsppc67>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <015c01c2c36e$55254540$7501ff0a@axsppc67>; from chak@axes-mach01.usa.alcatel.com on Fri, Jan 24, 2003 at 11:33:23AM +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>

PSK,

PSK Chakravarthi wrote:                                                                (Fri, 24 Jan 2003 11:33:23)
> Brian,
> 
> Why I asked is, MSU with DPC X, SIO Y, OPC A will give three full matches,
> RK1, RK3 and RK5.  As per RFC we should design RKs such that we will get
> only one full/partial match.

One could think of RK5 as a partial match.

One could also think of RK5 as an overlapping routing key with RK3 and RK4
which does not have to be permitted by an SG.

> 
> [Section 1.4.2.2 says
>    Routing Keys SHOULD be unique in the sense that each received SS7
>    signalling message SHOULD have a full or partial match to a single
>    routing result.]
> 
> Similarly when we receive an MSU with DPC X, SIO Y we will have two full
> matches, RK1 and RK2. We can derive many cases which will give more than one
> full match.  To which AS SGP will route when it finds more than one full
> match in the routing key list.

Again, that sounds like a partial match to me.

> 
> IMO, Routing keys should be designed in such a manner that there will be
> only one full match.

What about RK: DPC X OPC A SIO 4 SSN 3?

There can be partial matches here for messages that do not contain SSN.

> 
> I am not getting what is a partial match. Can you please explain what is a
> partial match with an example?

It is the responsibility of the SG to refuse routing keys that it feels
are "overlapping" in the sense that multiple matches are possible.

--brian

> 
> thanks
> Chak
> 
> ----- Original Message -----
> From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> To: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
> Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>; <sigtran@ietf.org>
> Sent: Friday, January 24, 2003 10:40 AM
> Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
> 
> 
> > PSK,
> >
> > Depends on the SG.
> >
> > --brian
> >
> > PSK Chakravarthi wrote:
> (Fri, 24 Jan 2003 10:01:20)
> > > Brian,
> > >
> > > What about the following routing keys? Are they valid?
> > >
> > > RK1, DPC X
> > > RK2, DPC X, SIO Y
> > > RK3, DPC X, SIO Y, OPC A
> > > RK4, DPC X, SIO Y, OPC B
> > > RK5, DPC X, SIO Y, OPC *
> > >
> > > thanks
> > > Chak
> > >
> > > ----- Original Message -----
> > > From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > To: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
> > > Cc: <sigtran@ietf.org>
> > > Sent: Thursday, January 23, 2003 5:41 PM
> > > Subject: [Sigtran] Re: M3UA Routing Keys partial match
> > >
> > >
> > > > Srini,
> > > >
> > > > Here are the two same routing keys:
> > > >
> > > >   RK1, OPC * DPC X SI Y
> > > >   RK1, OPC * DPC X SI Z
> > > >
> > > > A message arrives with OPC A and DPC Q and SI W.  Does it not
> > > > partially match the first routing key because OPC A matches
> > > > the wildcard on OPC?
> > > >
> > > > No.  When the RFC say partial match it is referring to the
> > > > message OPC A, DPC X, SI Y having a partial match to RK1.
> > > > (It does not match in OPC because OPC is "wildcarded".)
> > > >
> > > > --brian
> > > >
> > > >
> > > > ksrinivas wrote:
> > > (Thu, 23 Jan 2003 17:07:16)
> > > > > Brian,
> > > > >
> > > > >   Let us assume that the following two RKs are registered with an
> SGP
> > > > >
> > > > >   REG REQ (RK1, DPC X, SI = Y)
> > > > >   REG REQ (RK2, DPC X, SI = Z)
> > > > >
> > > > > and from SS7 network, say a MSU with DPC X and SI = Z is received.
> > > > >
> > > > > When M3UA at SGP tries to match DPC X and SI = Z with the first(DPC
> X,
> > > > > SI = Y) Routing Key, Does it not treat it as a partial match?.(as
> DPC
> > > > > matches).
> > > > >
> > > > > --Srini
> > > >
> > > > --
> > > > 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/
> >

-- 
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 Jan 24 03:18:25 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 DAA12695
	for <sigtran-archive@odin.ietf.org>; Fri, 24 Jan 2003 03:18:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0O8bJl11280
	for sigtran-archive@odin.ietf.org; Fri, 24 Jan 2003 03:37:19 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0O8auJ10903;
	Fri, 24 Jan 2003 03:36:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0O8ZWJ10857
	for <sigtran@optimus.ietf.org>; Fri, 24 Jan 2003 03:35:32 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12685
	for <sigtran@ietf.org>; Fri, 24 Jan 2003 03:16:06 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0O8JVVN021130;
	Fri, 24 Jan 2003 02:19:32 -0600 (CST)
Received: from axsppc67 by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id MAA22301; Fri, 24 Jan 2003 12:48:44 -0500 (GMT)
Message-ID: <017a01c2c381$95c3a660$7501ff0a@axsppc67>
From: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
To: <bidulock@openss7.org>
Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>, <sigtran@ietf.org>
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org> <013701c2c361$78dd0570$7501ff0a@axsppc67> <20030123221058.A14261@openss7.org> <015c01c2c36e$55254540$7501ff0a@axsppc67> <20030123232057.A15212@openss7.org>
Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
Date: Fri, 24 Jan 2003 13:51:12 +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.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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

Brian,

 > What about RK: DPC X OPC A SIO 4 SSN 3?
 >
 > There can be partial matches here for messages that do not contain SSN.

Why you are giving an example with SSN?  This is not possible with M3UA.

Anyway as per RFC if the search results only in a partial match then the
message will be routed to default ASP.

There can be many partial matches but search should yield a single full
match unless the overlapping routing keys are permitted.

thanks
Chak

----- Original Message -----
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>; <sigtran@ietf.org>
Sent: Friday, January 24, 2003 11:50 AM
Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match


> PSK,
>
> PSK Chakravarthi wrote:
(Fri, 24 Jan 2003 11:33:23)
> > Brian,
> >
> > Why I asked is, MSU with DPC X, SIO Y, OPC A will give three full
matches,
> > RK1, RK3 and RK5.  As per RFC we should design RKs such that we will get
> > only one full/partial match.
>
> One could think of RK5 as a partial match.
>
> One could also think of RK5 as an overlapping routing key with RK3 and RK4
> which does not have to be permitted by an SG.
>
> >
> > [Section 1.4.2.2 says
> >    Routing Keys SHOULD be unique in the sense that each received SS7
> >    signalling message SHOULD have a full or partial match to a single
> >    routing result.]
> >
> > Similarly when we receive an MSU with DPC X, SIO Y we will have two full
> > matches, RK1 and RK2. We can derive many cases which will give more than
one
> > full match.  To which AS SGP will route when it finds more than one full
> > match in the routing key list.
>
> Again, that sounds like a partial match to me.
>
> >
> > IMO, Routing keys should be designed in such a manner that there will be
> > only one full match.
>
> What about RK: DPC X OPC A SIO 4 SSN 3?
>
> There can be partial matches here for messages that do not contain SSN.
>
> >
> > I am not getting what is a partial match. Can you please explain what is
a
> > partial match with an example?
>
> It is the responsibility of the SG to refuse routing keys that it feels
> are "overlapping" in the sense that multiple matches are possible.
>
> --brian
>
> >
> > thanks
> > Chak
> >
> > ----- Original Message -----
> > From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > To: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
> > Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>; <sigtran@ietf.org>
> > Sent: Friday, January 24, 2003 10:40 AM
> > Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
> >
> >
> > > PSK,
> > >
> > > Depends on the SG.
> > >
> > > --brian
> > >
> > > PSK Chakravarthi wrote:
> > (Fri, 24 Jan 2003 10:01:20)
> > > > Brian,
> > > >
> > > > What about the following routing keys? Are they valid?
> > > >
> > > > RK1, DPC X
> > > > RK2, DPC X, SIO Y
> > > > RK3, DPC X, SIO Y, OPC A
> > > > RK4, DPC X, SIO Y, OPC B
> > > > RK5, DPC X, SIO Y, OPC *
> > > >
> > > > thanks
> > > > Chak
> > > >
> > > > ----- Original Message -----
> > > > From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > To: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
> > > > Cc: <sigtran@ietf.org>
> > > > Sent: Thursday, January 23, 2003 5:41 PM
> > > > Subject: [Sigtran] Re: M3UA Routing Keys partial match
> > > >
> > > >
> > > > > Srini,
> > > > >
> > > > > Here are the two same routing keys:
> > > > >
> > > > >   RK1, OPC * DPC X SI Y
> > > > >   RK1, OPC * DPC X SI Z
> > > > >
> > > > > A message arrives with OPC A and DPC Q and SI W.  Does it not
> > > > > partially match the first routing key because OPC A matches
> > > > > the wildcard on OPC?
> > > > >
> > > > > No.  When the RFC say partial match it is referring to the
> > > > > message OPC A, DPC X, SI Y having a partial match to RK1.
> > > > > (It does not match in OPC because OPC is "wildcarded".)
> > > > >
> > > > > --brian
> > > > >
> > > > >
> > > > > ksrinivas wrote:
> > > > (Thu, 23 Jan 2003 17:07:16)
> > > > > > Brian,
> > > > > >
> > > > > >   Let us assume that the following two RKs are registered with
an
> > SGP
> > > > > >
> > > > > >   REG REQ (RK1, DPC X, SI = Y)
> > > > > >   REG REQ (RK2, DPC X, SI = Z)
> > > > > >
> > > > > > and from SS7 network, say a MSU with DPC X and SI = Z is
received.
> > > > > >
> > > > > > When M3UA at SGP tries to match DPC X and SI = Z with the
first(DPC
> > X,
> > > > > > SI = Y) Routing Key, Does it not treat it as a partial
match?.(as
> > DPC
> > > > > > matches).
> > > > > >
> > > > > > --Srini
> > > > >
> > > > > --
> > > > > 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/
> > >
>
> --
> 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 Jan 24 03:32:25 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 DAA12867
	for <sigtran-archive@odin.ietf.org>; Fri, 24 Jan 2003 03:32:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0O8pKN12172
	for sigtran-archive@odin.ietf.org; Fri, 24 Jan 2003 03:51:20 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0O8p7J12153;
	Fri, 24 Jan 2003 03:51:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0O8mTJ12029
	for <sigtran@optimus.ietf.org>; Fri, 24 Jan 2003 03:48:29 -0500
Received: from web8204.mail.in.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA12829
	for <sigtran@ietf.org>; Fri, 24 Jan 2003 03:29:03 -0500 (EST)
Message-ID: <20030124083230.950.qmail@web8204.mail.in.yahoo.com>
Received: from [203.90.82.135] by web8204.mail.in.yahoo.com via HTTP; Fri, 24 Jan 2003 08:32:30 GMT
Date: Fri, 24 Jan 2003 08:32:30 +0000 (GMT)
From: =?iso-8859-1?q?amit=20somani?= <amitksomani@yahoo.co.in>
To: Sigtran <sigtran@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Sigtran] POINT CODES
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

hello everyone!

i`m working on gtt i.e. global title translation.
i could not understand the significance of PC-point
code in calling & called party fields?
can some one tell to which node these PC refer to?

if these r the PC to which the query message is to be
sent then what is the significance of DPC-destination
point code.

can someone plz lemme know what r the significances of
various point codes.

also let me know whether called part field carries
actually dialled number and calling party the phone
number of the dialler?

thank you.

________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
       visit http://in.tv.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jan 24 06:02: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 GAA15555
	for <sigtran-archive@odin.ietf.org>; Fri, 24 Jan 2003 06:02:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0OBKwK22429
	for sigtran-archive@odin.ietf.org; Fri, 24 Jan 2003 06:20:58 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0OBIqJ22325;
	Fri, 24 Jan 2003 06:18:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0OBHiJ22273
	for <sigtran@optimus.ietf.org>; Fri, 24 Jan 2003 06:17:44 -0500
Received: from hrtades9.atea.be (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15483
	for <sigtran@ietf.org>; Fri, 24 Jan 2003 05:58:13 -0500 (EST)
Received: from hrtades10.atea.be (siemens.atea.be [139.10.143.141]) by hrtades9.atea.be with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id X463RYGR; Fri, 24 Jan 2003 11:58:01 +0100
Received: by siemens.atea.be with Internet Mail Service (5.5.2653.19)
	id <DN10Q3KS>; Fri, 24 Jan 2003 11:56:41 +0100
Message-ID: <E76F715C0429D5118F2100508BB9EDEE037F5B5F@hrtades7.atea.be>
From: Coene Lode <Lode.Coene@siemens.atea.be>
To: "'amit somani'" <amitksomani@yahoo.co.in>, Sigtran <sigtran@ietf.org>
Subject: RE: [Sigtran] POINT CODES
Date: Fri, 24 Jan 2003 11:49:52 +0100
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>

> -----Original Message-----
> From: amit somani [mailto:amitksomani@yahoo.co.in]
> Sent: Friday, January 24, 2003 9:33 AM
> To: Sigtran
> Subject: [Sigtran] POINT CODES
> 
> 
> hello everyone!
> 
> i`m working on gtt i.e. global title translation.
> i could not understand the significance of PC-point
> code in calling & called party fields?
> can some one tell to which node these PC refer to?

I assume that you will do a GTT in the initiating endpoint. 

the pointcode in the Called party fields(=CLD) refers to the node which will
be a intermediate relay node(SRP) or the terminating endpoint node(SEP). 
the pointcode in the calling party fields(=CLG) refers to the node which
will be a intermediate relay node or the the initiating endpoint.
the pointcode in the CLG/CLD has the same significance as the OPC/DPC in the
MTP/M3UA routing label, they are only valid within that same network. 
The way in which the msg is routed is based on the routing indicator:
- route on GT: the msg may pass through intermediate SRP nodes(which will
yield different pointcodes for each translation)
- route on SSN: the msg is supposed to go directly to the final terminating
endpoint. It may pass SRP nodes but the GTT function must not be involved(as
it could possibly change Pointcodes AND the routing indicator). If invoking
GTT would happen then there is a strong possibility that the the response
msg going back would not be routable in the network.(none of us is
interested in blackholing traffic, I think)

> 
> if these r the PC to which the query message is to be
> sent then what is the significance of DPC-destination
> point code.
the DPC in the MTP routing label and the PC in the CLD should be the same
and the same is true for the OPC and the PC in the CLG.
it looks like redundant information but that is the way it is done. 
This way supports network architectures where the initiating endpoint does a
GTT which yield the final endpoint immediatly, so the endpoint can route
directly on PC alone(routing indicator set to route-on-SSN).(which should be
faster)
The drawback is that the msg cannot cross network borders. 

> 
> can someone plz lemme know what r the significances of
> various point codes.

Another network architecture  might be to put the GTT capability not in the
endpoint but distributed throughout the network and then the CLG and CLD
consists of a GT (PC may or may not be present). The DPC in the MTP routing
label could be the PC of the intermediate SCCP node doing GTT or the final
endpoint. The OPC would be the PC of the node which was the initiating
endnode or the node which did a intermediate GTT.
This methods allows for network border crossings and should be the one used
in all wireless networks.

> 
> also let me know whether called part field carries
> actually dialled number and calling party the phone
> number of the dialler?

Depends on the application:
- supplementary services such as CCBS: CLD = the dialled number, CLG= number
of the dialler
- wireless: mobility managment: CLD= dialled number, CLG= number of the
MSC/SGSN to which the subscriber is presently attached.
- wireless: MO-SMS( mobile origniating SMS): CLD= SMS service center number,
CLG = number of the MSC/SGSN to which the subscriber is presently attached.
- wireless: MT-SMS(mobile terminating SMS): CLD= number of the MSC/SGSN to
which the subscriber is presently attached, CLG = SMS service center number
....

as you can see there are a lot of possibilities...
> 
> thank you.
> 

Hope this helps...

yours sincerly,
Lode Coene

Siemens atea
atealaan 34          2200 Herentals, Belgium
E-mail: lode.coene@siemens.atea.be
Tel: +32-14-252081
Fax: +32-14-253212
 
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jan 24 06:44:23 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 GAA16105
	for <sigtran-archive@odin.ietf.org>; Fri, 24 Jan 2003 06:44:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0OC3KQ24665
	for sigtran-archive@odin.ietf.org; Fri, 24 Jan 2003 07:03:20 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0OC2dJ24589;
	Fri, 24 Jan 2003 07:02:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0OBwUJ24349
	for <sigtran@optimus.ietf.org>; Fri, 24 Jan 2003 06:58:30 -0500
Received: from corp.tatatel.co.in (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15990
	for <sigtran@ietf.org>; Fri, 24 Jan 2003 06:38:59 -0500 (EST)
Received: by MAIL with Internet Mail Service (5.5.2650.21)
	id <CHKQ9005>; Fri, 24 Jan 2003 17:08:46 +0530
Message-ID: <889BA89F68ACD511B13F0002A5750FCD08B0FA48@MAIL>
From: Kasiraju Srinivasa Raju <ksraju@tatatel.co.in>
To: Coene Lode <Lode.Coene@siemens.atea.be>,
        "'amit somani'"
	 <amitksomani@yahoo.co.in>,
        Sigtran <sigtran@ietf.org>
Subject: RE: [Sigtran] POINT CODES
Date: Fri, 24 Jan 2003 17:08:46 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
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,
thanks for the explainatory answer provided.
Could anyone help me for designing an ss7 overlay network with following
details/rules :
1.	Link load capability for A, B, C, D, E links for Sigtran and TDM
links.
2.	Since IP overhead is realtively high assuming LSL links of 64kbps
where is the point of Trade-off arriving between SCTP and TDM links.
3.	General Gateway screening rules for efficient network.
4.	Can the load-sharing capability of an STP overcome a network
element's in capability to do so.
5.	Global Title translation rules for efficient network.

::      Thanks and Regards,     :: 
        K.Srinivasa Raju, 
        Adv. Services,TTL- Hyd 
        Tatatel ] +91-40-55554064 
        Mobitel ] +91-40-56109064 
        email * ksraju@tatatel.co.in 



-----Original Message-----
From: Coene Lode [mailto:Lode.Coene@siemens.atea.be]
Sent: Friday, January 24, 2003 4:20 PM
To: 'amit somani'; Sigtran
Subject: RE: [Sigtran] POINT CODES


> -----Original Message-----
> From: amit somani [mailto:amitksomani@yahoo.co.in]
> Sent: Friday, January 24, 2003 9:33 AM
> To: Sigtran
> Subject: [Sigtran] POINT CODES
> 
> 
> hello everyone!
> 
> i`m working on gtt i.e. global title translation.
> i could not understand the significance of PC-point
> code in calling & called party fields?
> can some one tell to which node these PC refer to?

I assume that you will do a GTT in the initiating endpoint. 

the pointcode in the Called party fields(=CLD) refers to the node which will
be a intermediate relay node(SRP) or the terminating endpoint node(SEP). 
the pointcode in the calling party fields(=CLG) refers to the node which
will be a intermediate relay node or the the initiating endpoint.
the pointcode in the CLG/CLD has the same significance as the OPC/DPC in the
MTP/M3UA routing label, they are only valid within that same network. 
The way in which the msg is routed is based on the routing indicator:
- route on GT: the msg may pass through intermediate SRP nodes(which will
yield different pointcodes for each translation)
- route on SSN: the msg is supposed to go directly to the final terminating
endpoint. It may pass SRP nodes but the GTT function must not be involved(as
it could possibly change Pointcodes AND the routing indicator). If invoking
GTT would happen then there is a strong possibility that the the response
msg going back would not be routable in the network.(none of us is
interested in blackholing traffic, I think)

> 
> if these r the PC to which the query message is to be
> sent then what is the significance of DPC-destination
> point code.
the DPC in the MTP routing label and the PC in the CLD should be the same
and the same is true for the OPC and the PC in the CLG.
it looks like redundant information but that is the way it is done. 
This way supports network architectures where the initiating endpoint does a
GTT which yield the final endpoint immediatly, so the endpoint can route
directly on PC alone(routing indicator set to route-on-SSN).(which should be
faster)
The drawback is that the msg cannot cross network borders. 

> 
> can someone plz lemme know what r the significances of
> various point codes.

Another network architecture  might be to put the GTT capability not in the
endpoint but distributed throughout the network and then the CLG and CLD
consists of a GT (PC may or may not be present). The DPC in the MTP routing
label could be the PC of the intermediate SCCP node doing GTT or the final
endpoint. The OPC would be the PC of the node which was the initiating
endnode or the node which did a intermediate GTT.
This methods allows for network border crossings and should be the one used
in all wireless networks.

> 
> also let me know whether called part field carries
> actually dialled number and calling party the phone
> number of the dialler?

Depends on the application:
- supplementary services such as CCBS: CLD = the dialled number, CLG= number
of the dialler
- wireless: mobility managment: CLD= dialled number, CLG= number of the
MSC/SGSN to which the subscriber is presently attached.
- wireless: MO-SMS( mobile origniating SMS): CLD= SMS service center number,
CLG = number of the MSC/SGSN to which the subscriber is presently attached.
- wireless: MT-SMS(mobile terminating SMS): CLD= number of the MSC/SGSN to
which the subscriber is presently attached, CLG = SMS service center number
....

as you can see there are a lot of possibilities...
> 
> thank you.
> 

Hope this helps...

yours sincerly,
Lode Coene

Siemens atea
atealaan 34          2200 Herentals, Belgium
E-mail: lode.coene@siemens.atea.be
Tel: +32-14-252081
Fax: +32-14-253212
 
_______________________________________________
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 Jan 24 09:14:15 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 JAA19901
	for <sigtran-archive@odin.ietf.org>; Fri, 24 Jan 2003 09:14:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0OEXH401533
	for sigtran-archive@odin.ietf.org; Fri, 24 Jan 2003 09:33:17 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0OEWaJ01489;
	Fri, 24 Jan 2003 09:32:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0OEVdJ01419
	for <sigtran@optimus.ietf.org>; Fri, 24 Jan 2003 09:31:39 -0500
Received: from cbibipnt08.hc.bt.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19821
	for <sigtran@ietf.org>; Fri, 24 Jan 2003 09:12:07 -0500 (EST)
From: karen.d.king@bt.com
Received: by cbibipnt08.hc.bt.com with Internet Mail Service (5.5.2654.89)
	id <DQH60YN2>; Fri, 24 Jan 2003 14:14:58 -0000
Message-ID: <B1F38D7B53615140BCEA6677DF9F2F8C5B1A29@i2km11-ukbr.domain1.systemhost.net>
To: sigtran@ietf.org
Date: Fri, 24 Jan 2003 14:10:33 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.89)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] M2PA Draft 7 comment
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 still have the comments, from draft 5, on the use of processor outage
(section 4.1.4).

When processor outage ceases, the buffers need to be flushed. Therefore
please can you move the paragraph "MTP3 may send Flush Buffers or
Continue......."  to after the paragraph starting, "When processor outage
ceases....".

Please could you also add a statement that processor outage should not be
used to cover the situations when MTP3 or user parts are encountering
congestion, or where the user part is unavailable.

Regards,

Karen

Karen King
BTexact Technologies
Orion Building MLB1/PP9
Adastral Park
Martlesham Heath
IPSWICH
Suffolk   IP5 3RE

Tel: (01473) 605389
karen.d.king@bt.com

BTexact Technologies is a trademark of British Telecommunications plc
Registered office: 81 Newgate Street London EC1A 7AJ
Registered in England no. 1800000

This electronic message contains information from British Telecommunications
plc which may be privileged or confidential. The information is intended to
be for the use of the individual(s) or entity named above. If you are not
the intended recipient be aware that any disclosure, copying, distribution
or use of the contents of this information is prohibited. If you have
received this electronic message in error, please notify us by telephone or
email (to the numbers or address above) immediately.
Activity and use of British Telecommunications plc E-mail system is
monitored to secure its effective operation and for other lawful business
purposes. Communications using this system will also be monitored and may be
recorded to secure effective operation and for other lawful business
purposes.

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



From mailnull@www1.ietf.org  Fri Jan 24 16:23: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 QAA02804
	for <sigtran-archive@odin.ietf.org>; Fri, 24 Jan 2003 16:23:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0OLgQL30866
	for sigtran-archive@odin.ietf.org; Fri, 24 Jan 2003 16:42:26 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0OLfbJ30824;
	Fri, 24 Jan 2003 16:41:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0OLeeJ30764
	for <sigtran@optimus.ietf.org>; Fri, 24 Jan 2003 16:40:40 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02760
	for <sigtran@ietf.org>; Fri, 24 Jan 2003 16:20:52 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:EqUbiZHsORzF35INf4bFYscC23jW1LnQ@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0OLOLD22933;
	Fri, 24 Jan 2003 14:24:21 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0OLOKU03370;
	Fri, 24 Jan 2003 14:24:20 -0700
Date: Fri, 24 Jan 2003 14:24:20 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>
Cc: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
Message-ID: <20030124142420.B30630@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>,
	ksrinivas <ksrini@axes-mach01.usa.alcatel.com>, sigtran@ietf.org
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org> <013701c2c361$78dd0570$7501ff0a@axsppc67> <20030123221058.A14261@openss7.org> <015c01c2c36e$55254540$7501ff0a@axsppc67> <20030123232057.A15212@openss7.org> <017a01c2c381$95c3a660$7501ff0a@axsppc67>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <017a01c2c381$95c3a660$7501ff0a@axsppc67>; from chak@axes-mach01.usa.alcatel.com on Fri, Jan 24, 2003 at 01:51:12PM +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>

PSK,

PSK Chakravarthi wrote:                                                                (Fri, 24 Jan 2003 13:51:12)
> Brian,
> 
>  > What about RK: DPC X OPC A SIO 4 SSN 3?
>  >
>  > There can be partial matches here for messages that do not contain SSN.
> 
> Why you are giving an example with SSN?  This is not possible with M3UA.

It is as the RFC stands.

> Anyway as per RFC if the search results only in a partial match then the
> message will be routed to default ASP.
> 
> There can be many partial matches but search should yield a single full
> match unless the overlapping routing keys are permitted.

Have you answered your own question?

--brian

> 
> thanks
> Chak
> 
> ----- Original Message -----
> From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> To: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
> Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>; <sigtran@ietf.org>
> Sent: Friday, January 24, 2003 11:50 AM
> Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
> 
> 
> > PSK,
> >
> > PSK Chakravarthi wrote:
> (Fri, 24 Jan 2003 11:33:23)
> > > Brian,
> > >
> > > Why I asked is, MSU with DPC X, SIO Y, OPC A will give three full
> matches,
> > > RK1, RK3 and RK5.  As per RFC we should design RKs such that we will get
> > > only one full/partial match.
> >
> > One could think of RK5 as a partial match.
> >
> > One could also think of RK5 as an overlapping routing key with RK3 and RK4
> > which does not have to be permitted by an SG.
> >
> > >
> > > [Section 1.4.2.2 says
> > >    Routing Keys SHOULD be unique in the sense that each received SS7
> > >    signalling message SHOULD have a full or partial match to a single
> > >    routing result.]
> > >
> > > Similarly when we receive an MSU with DPC X, SIO Y we will have two full
> > > matches, RK1 and RK2. We can derive many cases which will give more than
> one
> > > full match.  To which AS SGP will route when it finds more than one full
> > > match in the routing key list.
> >
> > Again, that sounds like a partial match to me.
> >
> > >
> > > IMO, Routing keys should be designed in such a manner that there will be
> > > only one full match.
> >
> > What about RK: DPC X OPC A SIO 4 SSN 3?
> >
> > There can be partial matches here for messages that do not contain SSN.
> >
> > >
> > > I am not getting what is a partial match. Can you please explain what is
> a
> > > partial match with an example?
> >
> > It is the responsibility of the SG to refuse routing keys that it feels
> > are "overlapping" in the sense that multiple matches are possible.
> >
> > --brian
> >
> > >
> > > thanks
> > > Chak
> > >
> > > ----- Original Message -----
> > > From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > To: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
> > > Cc: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>; <sigtran@ietf.org>
> > > Sent: Friday, January 24, 2003 10:40 AM
> > > Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
> > >
> > >
> > > > PSK,
> > > >
> > > > Depends on the SG.
> > > >
> > > > --brian
> > > >
> > > > PSK Chakravarthi wrote:
> > > (Fri, 24 Jan 2003 10:01:20)
> > > > > Brian,
> > > > >
> > > > > What about the following routing keys? Are they valid?
> > > > >
> > > > > RK1, DPC X
> > > > > RK2, DPC X, SIO Y
> > > > > RK3, DPC X, SIO Y, OPC A
> > > > > RK4, DPC X, SIO Y, OPC B
> > > > > RK5, DPC X, SIO Y, OPC *
> > > > >
> > > > > thanks
> > > > > Chak
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > To: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
> > > > > Cc: <sigtran@ietf.org>
> > > > > Sent: Thursday, January 23, 2003 5:41 PM
> > > > > Subject: [Sigtran] Re: M3UA Routing Keys partial match
> > > > >
> > > > >
> > > > > > Srini,
> > > > > >
> > > > > > Here are the two same routing keys:
> > > > > >
> > > > > >   RK1, OPC * DPC X SI Y
> > > > > >   RK1, OPC * DPC X SI Z
> > > > > >
> > > > > > A message arrives with OPC A and DPC Q and SI W.  Does it not
> > > > > > partially match the first routing key because OPC A matches
> > > > > > the wildcard on OPC?
> > > > > >
> > > > > > No.  When the RFC say partial match it is referring to the
> > > > > > message OPC A, DPC X, SI Y having a partial match to RK1.
> > > > > > (It does not match in OPC because OPC is "wildcarded".)
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > >
> > > > > > ksrinivas wrote:
> > > > > (Thu, 23 Jan 2003 17:07:16)
> > > > > > > Brian,
> > > > > > >
> > > > > > >   Let us assume that the following two RKs are registered with
> an
> > > SGP
> > > > > > >
> > > > > > >   REG REQ (RK1, DPC X, SI = Y)
> > > > > > >   REG REQ (RK2, DPC X, SI = Z)
> > > > > > >
> > > > > > > and from SS7 network, say a MSU with DPC X and SI = Z is
> received.
> > > > > > >
> > > > > > > When M3UA at SGP tries to match DPC X and SI = Z with the
> first(DPC
> > > X,
> > > > > > > SI = Y) Routing Key, Does it not treat it as a partial
> match?.(as
> > > DPC
> > > > > > > matches).
> > > > > > >
> > > > > > > --Srini
> > > > > >
> > > > > > --
> > > > > > 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/
> > > >
> >
> > --
> > 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 mailnull@www1.ietf.org  Fri Jan 24 16:26: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 QAA02894
	for <sigtran-archive@odin.ietf.org>; Fri, 24 Jan 2003 16:26:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0OLjGM31018
	for sigtran-archive@odin.ietf.org; Fri, 24 Jan 2003 16:45:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0OLj4J30993;
	Fri, 24 Jan 2003 16:45:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0OLi4J30918
	for <sigtran@optimus.ietf.org>; Fri, 24 Jan 2003 16:44:04 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02836
	for <sigtran@ietf.org>; Fri, 24 Jan 2003 16:24:22 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:mXpgj0Rce9R6OIVy2evQY/zQCtFN4m+M@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0OLRoD22981;
	Fri, 24 Jan 2003 14:27:51 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0OLRoq03478;
	Fri, 24 Jan 2003 14:27:50 -0700
Date: Fri, 24 Jan 2003 14:27:50 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: karen.d.king@bt.com
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA Draft 7 comment
Message-ID: <20030124142750.C30630@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: karen.d.king@bt.com, sigtran@ietf.org
References: <B1F38D7B53615140BCEA6677DF9F2F8C5B1A29@i2km11-ukbr.domain1.systemhost.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <B1F38D7B53615140BCEA6677DF9F2F8C5B1A29@i2km11-ukbr.domain1.systemhost.net>; from karen.d.king@bt.com on Fri, Jan 24, 2003 at 02:10:33PM -0000
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>

karen.d.king,

karen.d.king@bt.com wrote:                                                    (Fri, 24 Jan 2003 14:10:33)
> Hi,
> 
> I still have the comments, from draft 5, on the use of processor outage
> (section 4.1.4).
> 
> When processor outage ceases, the buffers need to be flushed. Therefore
> please can you move the paragraph "MTP3 may send Flush Buffers or
> Continue......."  to after the paragraph starting, "When processor outage
> ceases....".
> 
> Please could you also add a statement that processor outage should not be
> used to cover the situations when MTP3 or user parts are encountering
> congestion, or where the user part is unavailable.

Doesn't this last point go without saying?

--brian

> 
> Regards,
> 
> Karen
> 
> Karen King
> BTexact Technologies
> Orion Building MLB1/PP9
> Adastral Park
> Martlesham Heath
> IPSWICH
> Suffolk   IP5 3RE
> 
> Tel: (01473) 605389
> karen.d.king@bt.com
> 
> BTexact Technologies is a trademark of British Telecommunications plc
> Registered office: 81 Newgate Street London EC1A 7AJ
> Registered in England no. 1800000
> 
> This electronic message contains information from British Telecommunications
> plc which may be privileged or confidential. The information is intended to
> be for the use of the individual(s) or entity named above. If you are not
> the intended recipient be aware that any disclosure, copying, distribution
> or use of the contents of this information is prohibited. If you have
> received this electronic message in error, please notify us by telephone or
> email (to the numbers or address above) immediately.
> Activity and use of British Telecommunications plc E-mail system is
> monitored to secure its effective operation and for other lawful business
> purposes. Communications using this system will also be monitored and may be
> recorded to secure effective operation and for other lawful business
> purposes.
> 
> _______________________________________________
> 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 Jan 24 17:21: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 RAA04060
	for <sigtran-archive@odin.ietf.org>; Fri, 24 Jan 2003 17:21:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0OMewH02405
	for sigtran-archive@odin.ietf.org; Fri, 24 Jan 2003 17:40:58 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0OMeDJ02374;
	Fri, 24 Jan 2003 17:40:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0OAT3J18982
	for <sigtran@optimus.ietf.org>; Fri, 24 Jan 2003 05:29:03 -0500
Received: from rsys002a.roke.co.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14750;
	Fri, 24 Jan 2003 05:09:34 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <CN3C00BN>; Fri, 24 Jan 2003 10:13:01 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED41804A0F195@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'Lars-Erik Jonsson (EAB)'" <Lars-Erik.Jonsson@epl.ericsson.se>,
        "'rohc@ietf.org'" <rohc@ietf.org>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>,
        "'tsvwg@ietf.org'"
	 <tsvwg@ietf.org>,
        "Allison Mankin (E-mail)" <mankin@psg.com>
Date: Fri, 24 Jan 2003 10:13:01 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] RE: [rohc] Removing SCTP header compression from the ROHC charter
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>

> Trying to fulfill this work item during the last year, we have
> repeatedly asked for contributions to SCTP header compression, but
> we have not received a single response.

We published a first version of an SCTP compression profile in
draft-west-sctp-epic-00.txt. This draft is based on the formal header
compression notation (see draft-ietf-rohc-formal-notation-00.txt),
so we intend to update the SCTP draft once the formal notation draft
is finalised.

> Given that this work item was originally added without immediate
> market pull, and considering the lack of current interest in doing
> the work (or even having it done at all), we intend to remove SCTP
> header compression from the ROHC WG charter.  To keep it in the
> charter, justifications for developing SCTP header compression now
> would have to be presented, as well as industry support and
> commitments for doing the actual work.

This work item is important because, unlike for TCP, there is currently
no published scheme for SCTP compression. This will hinder the
deployment of SCTP, particularly in the mobile environment.

Regarding the industry support, we're currently working on SCTP
compression at the moment in the form of the notation draft. Once this
work is done we'll publish an updated version of our SCTP profile.

> Barring further input, we will send a request to the ADs by Jan 24,
> so please reply before this date if you believe SCTP header
> compression should be on the agenda now.

I believe that SCTP compression should remain on the ROHC charter.

Regards,

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



From mailnull@www1.ietf.org  Fri Jan 24 17:46: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 RAA04625
	for <sigtran-archive@odin.ietf.org>; Fri, 24 Jan 2003 17:46:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ON5uF03215
	for sigtran-archive@odin.ietf.org; Fri, 24 Jan 2003 18:05:56 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ON56J03181;
	Fri, 24 Jan 2003 18:05:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ON3hJ03136
	for <sigtran@optimus.ietf.org>; Fri, 24 Jan 2003 18:03:43 -0500
Received: from revere.sonusnet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04566
	for <sigtran@ietf.org>; Fri, 24 Jan 2003 17:43:59 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3.sonusnet.com [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h0OMlR728123
	for <sigtran@ietf.org>; Fri, 24 Jan 2003 17:47:27 -0500 (EST)
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19)
	id <Y68H42PP>; Fri, 24 Jan 2003 17:47:27 -0500
Message-ID: <4CF48720B6E9D4118D040060CF2074E9072F6BFB@sonusdc3.sonusnet.com>
From: "Wung, Joseph" <JWung@sonusnet.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Date: Fri, 24 Jan 2003 17:47:17 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] SUA: Routing Key
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>

A Routing Key in SUA (draft 14) contains an Address Range 
parameter in addition to Source and Destination Address
parameters.  The Address Range parameter contains either pairs
of Source Address or Destination Address parameters.

Can someone explain what all these mean?

Thanks,
Joe

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



From mailnull@www1.ietf.org  Fri Jan 24 18:48: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 SAA05580
	for <sigtran-archive@odin.ietf.org>; Fri, 24 Jan 2003 18:48:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0P07tF07000
	for sigtran-archive@odin.ietf.org; Fri, 24 Jan 2003 19:07:55 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0P07NJ06926;
	Fri, 24 Jan 2003 19:07:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0P06KJ06303
	for <sigtran@optimus.ietf.org>; Fri, 24 Jan 2003 19:06:20 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05527
	for <sigtran@ietf.org>; Fri, 24 Jan 2003 18:46:34 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:jAiH2aa21kJI73YKgfNm7+Ig5AtB5Xt1@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0ONo3D25263;
	Fri, 24 Jan 2003 16:50:03 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0ONo2f07237;
	Fri, 24 Jan 2003 16:50:02 -0700
Date: Fri, 24 Jan 2003 16:50:01 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Wung, Joseph" <JWung@sonusnet.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA: Routing Key
Message-ID: <20030124165001.A6948@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Wung, Joseph" <JWung@sonusnet.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <4CF48720B6E9D4118D040060CF2074E9072F6BFB@sonusdc3.sonusnet.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: <4CF48720B6E9D4118D040060CF2074E9072F6BFB@sonusdc3.sonusnet.com>; from JWung@sonusnet.com on Fri, Jan 24, 2003 at 05:47:17PM -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>

Joe,

The Source and Desintation Address parameters are used to
specify a Source and Destination Address for an AMF entry
(or Routing Key).

The Address Range parameter can be used to specify a range
of Sources and range of Destinations Addresses for a set
of AMF entries.

In SUA, the registration process essentially associates an
Application Server and Routing Context with a (set of)
entries in the AMF.  This is essentially the GTT tables in
the SG.

So, for example, an Application Server could register as
an HLR (SSN=5) against a range of Addresses (MINs) using
the range parameters.

That's the idea, anyway.

--brian

Wung, Joseph wrote:                                       (Fri, 24 Jan 2003 17:47:17)
> A Routing Key in SUA (draft 14) contains an Address Range 
> parameter in addition to Source and Destination Address
> parameters.  The Address Range parameter contains either pairs
> of Source Address or Destination Address parameters.
> 
> Can someone explain what all these mean?
> 
> Thanks,
> Joe
> 
> _______________________________________________
> 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  Sat Jan 25 14:02: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 OAA27126
	for <sigtran-archive@odin.ietf.org>; Sat, 25 Jan 2003 14:02:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0PJM9n04652
	for sigtran-archive@odin.ietf.org; Sat, 25 Jan 2003 14:22:09 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0PJLgJ04630;
	Sat, 25 Jan 2003 14:21:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0PJGHJ04503
	for <sigtran@optimus.ietf.org>; Sat, 25 Jan 2003 14:16:17 -0500
Received: from web8204.mail.in.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA27020
	for <sigtran@ietf.org>; Sat, 25 Jan 2003 13:56:09 -0500 (EST)
Message-ID: <20030125185934.85718.qmail@web8204.mail.in.yahoo.com>
Received: from [61.1.106.210] by web8204.mail.in.yahoo.com via HTTP; Sat, 25 Jan 2003 18:59:34 GMT
Date: Sat, 25 Jan 2003 18:59:34 +0000 (GMT)
From: =?iso-8859-1?q?amit=20somani?= <amitksomani@yahoo.co.in>
To: Sigtran <sigtran@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Sigtran] query
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 everyone!
  i m working on ss7 right now. but i do not have
access to ss7 links. 
 i've got some of the ss7 message structures which are
output of a protocol anyalyser or directly from ss7
link. some of these are related to ANSI and some of
them are ITU....
  but my question is what standard is followed in
INDIA? and do someone in INDIA can sent me some of the
message stucture used in INDIA.
 
                          amit

________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
       visit http://in.tv.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Sun Jan 26 14:37: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 OAA21009
	for <sigtran-archive@odin.ietf.org>; Sun, 26 Jan 2003 14:37:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0QJvjb20313
	for sigtran-archive@odin.ietf.org; Sun, 26 Jan 2003 14:57:45 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0QJvHJ20276;
	Sun, 26 Jan 2003 14:57:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0QJtBJ20220
	for <sigtran@optimus.ietf.org>; Sun, 26 Jan 2003 14:55:11 -0500
Received: from w2ksjexg01.ciena.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20979
	for <sigtran@ietf.org>; Sun, 26 Jan 2003 14:34:34 -0500 (EST)
Received: from wntcsdexg01.csd.ciena.com ([10.34.31.31]) by w2ksjexg01.ciena.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id C2BQN71G; Sun, 26 Jan 2003 11:37:49 -0800
Received: by webdev-llnt.oni.com with Internet Mail Service (5.5.2653.19)
	id <Y5W9MGYG>; Sun, 26 Jan 2003 11:38:02 -0800
Message-ID: <2135200C183FD5119588009027DE572302836C0A@webdev-owa.oni.com>
From: "Ong, Lyndon" <LyOng@ciena.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Date: Sun, 26 Jan 2003 11:38:01 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] m2pa comment: author list
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,

One comment - the author's list is too long and will get it killed in IESG.
Suggest we drop at least 2 names, probably Mallesh Kalla and one or
two others (volunteers?).

Also, references need to be sorted into Normative and Non-normative,
in separate sections.

The security section probably needs to be updated based on the
security framework document (which should come out this week).

Cheers,

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



From mailnull@www1.ietf.org  Sun Jan 26 17:38: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 RAA23118
	for <sigtran-archive@odin.ietf.org>; Sun, 26 Jan 2003 17:38:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0QMwSG28951
	for sigtran-archive@odin.ietf.org; Sun, 26 Jan 2003 17:58:28 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0QMvnJ28926;
	Sun, 26 Jan 2003 17:57:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0QMqlJ28838
	for <sigtran@optimus.ietf.org>; Sun, 26 Jan 2003 17:52:47 -0500
Received: from fep04-mail.bloor.is.net.cable.rogers.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23047
	for <sigtran@ietf.org>; Sun, 26 Jan 2003 17:32:06 -0500 (EST)
Received: from cr389192a ([24.156.64.205])
          by fep04-mail.bloor.is.net.cable.rogers.com
          (InterMail vM.5.01.05.06 201-253-122-126-106-20020509) with ESMTP
          id <20030126223535.PYWP120822.fep04-mail.bloor.is.net.cable.rogers.com@cr389192a>;
          Sun, 26 Jan 2003 17:35:35 -0500
Message-ID: <000601c2c58b$3b75d820$cd409c18@lndn.phub.net.cable.rogers.com>
From: "Greg Sidebottom" <gregside@rogers.com>
To: "Ong, Lyndon" <LyOng@ciena.com>, <sigtran@ietf.org>
References: <2135200C183FD5119588009027DE572302836C0A@webdev-owa.oni.com>
Subject: Re: [Sigtran] m2pa comment: author list
Date: Sun, 26 Jan 2003 17:35:29 -0500
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 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep04-mail.bloor.is.net.cable.rogers.com from [24.156.64.205] using ID <gregside@rogers.com> at Sun, 26 Jan 2003 17:35:34 -0500
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 Lyndon,

  I'll volunteer  2;^)

Cheers,

    Greg

----- Original Message -----
From: "Ong, Lyndon" <LyOng@ciena.com>
To: <sigtran@ietf.org>
Sent: Sunday, January 26, 2003 2:38 PM
Subject: [Sigtran] m2pa comment: author list


> Folks,
>
> One comment - the author's list is too long and will get it killed in
IESG.
> Suggest we drop at least 2 names, probably Mallesh Kalla and one or
> two others (volunteers?).
>
> Also, references need to be sorted into Normative and Non-normative,
> in separate sections.
>
> The security section probably needs to be updated based on the
> security framework document (which should come out this week).
>
> Cheers,
>
> L. Ong
> _______________________________________________
> 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  Sun Jan 26 19:26: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 TAA23849
	for <sigtran-archive@odin.ietf.org>; Sun, 26 Jan 2003 19:26:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0R0kEb01133
	for sigtran-archive@odin.ietf.org; Sun, 26 Jan 2003 19:46:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R0jZJ01108;
	Sun, 26 Jan 2003 19:45:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R0dGJ00982
	for <sigtran@optimus.ietf.org>; Sun, 26 Jan 2003 19:39:16 -0500
Received: from w2ksjexg01.ciena.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23827
	for <sigtran@ietf.org>; Sun, 26 Jan 2003 19:18:32 -0500 (EST)
Received: from wntcsdexg01.csd.ciena.com ([10.34.31.31]) by w2ksjexg01.ciena.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id C2BQN7SW; Sun, 26 Jan 2003 16:21:48 -0800
Received: by webdev-llnt.oni.com with Internet Mail Service (5.5.2653.19)
	id <Y5W9MG5C>; Sun, 26 Jan 2003 16:22:01 -0800
Message-ID: <2135200C183FD5119588009027DE572302836C0C@webdev-owa.oni.com>
From: "Ong, Lyndon" <LyOng@ciena.com>
To: "'Greg Sidebottom'" <gregside@rogers.com>, sigtran@ietf.org
Subject: RE: [Sigtran] m2pa comment: author list
Date: Sun, 26 Jan 2003 16:22:00 -0800
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, Greg!

-----Original Message-----
From: Greg Sidebottom [mailto:gregside@rogers.com]
Sent: Sunday, January 26, 2003 2:35 PM
To: Ong, Lyndon; sigtran@ietf.org
Subject: Re: [Sigtran] m2pa comment: author list


Hi Lyndon,

  I'll volunteer  2;^)

Cheers,

    Greg

----- Original Message -----
From: "Ong, Lyndon" <LyOng@ciena.com>
To: <sigtran@ietf.org>
Sent: Sunday, January 26, 2003 2:38 PM
Subject: [Sigtran] m2pa comment: author list


> Folks,
>
> One comment - the author's list is too long and will get it killed in
IESG.
> Suggest we drop at least 2 names, probably Mallesh Kalla and one or
> two others (volunteers?).
>
> Also, references need to be sorted into Normative and Non-normative,
> in separate sections.
>
> The security section probably needs to be updated based on the
> security framework document (which should come out this week).
>
> Cheers,
>
> L. Ong
> _______________________________________________
> 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  Sun Jan 26 22:57: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 WAA26197
	for <sigtran-archive@odin.ietf.org>; Sun, 26 Jan 2003 22:57:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0R4I4X10758
	for sigtran-archive@odin.ietf.org; Sun, 26 Jan 2003 23:18:04 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R4HXJ10747;
	Sun, 26 Jan 2003 23:17:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R4FvJ10706
	for <sigtran@optimus.ietf.org>; Sun, 26 Jan 2003 23:15:57 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26187
	for <sigtran@ietf.org>; Sun, 26 Jan 2003 22:55:10 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0R3wabg013812;
	Sun, 26 Jan 2003 21:58:38 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id IAA11244; Mon, 27 Jan 2003 08:27:50 -0500 (GMT)
Message-ID: <3E34AEBD.CD390A33@axes-mach01.usa.alcatel.com>
Date: Mon, 27 Jan 2003 09:29:58 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: sigtran@ietf.org
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org>
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] Re: M3UA Routing Keys partial match
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

Brian,

     If a message arrives with OPC A and DPC X and SI W for the Routing Keys you have mentioned, Does it not
partially match with both the Routing Keys?. (Assuming that hierarchical RKs are not allowed by the SGP).

--Srini

"Brian F. G. Bidulock" wrote:

> Srini,
>
> Here are the two same routing keys:
>
>   RK1, OPC * DPC X SI Y
>   RK1, OPC * DPC X SI Z
>
> A message arrives with OPC A and DPC Q and SI W.  Does it not
> partially match the first routing key because OPC A matches
> the wildcard on OPC?
>
> No.  When the RFC say partial match it is referring to the
> message OPC A, DPC X, SI Y having a partial match to RK1.
> (It does not match in OPC because OPC is "wildcarded".)
>
> --brian
>
> ksrinivas wrote:                                                                 (Thu, 23 Jan 2003 17:07:16)
> > Brian,
> >
> >   Let us assume that the following two RKs are registered with an SGP
> >
> >   REG REQ (RK1, DPC X, SI = Y)
> >   REG REQ (RK2, DPC X, SI = Z)
> >
> > and from SS7 network, say a MSU with DPC X and SI = Z is received.
> >
> > When M3UA at SGP tries to match DPC X and SI = Z with the first(DPC X,
> > SI = Y) Routing Key, Does it not treat it as a partial match?.(as DPC
> > matches).
> >
> > --Srini
>
> --
> 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 Jan 27 00:06: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 AAA26909
	for <sigtran-archive@odin.ietf.org>; Mon, 27 Jan 2003 00:06:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0R5R3713773
	for sigtran-archive@odin.ietf.org; Mon, 27 Jan 2003 00:27:03 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R5P8J13722;
	Mon, 27 Jan 2003 00:26:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R5MpJ13651
	for <sigtran@optimus.ietf.org>; Mon, 27 Jan 2003 00:22:51 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26842
	for <sigtran@ietf.org>; Mon, 27 Jan 2003 00:02:02 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:zzAt3M1pNpt0z22iBgh//VqtttYza/ii@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0R55WD09928;
	Sun, 26 Jan 2003 22:05:32 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0R55VM01044;
	Sun, 26 Jan 2003 22:05:31 -0700
Date: Sun, 26 Jan 2003 22:05:31 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Message-ID: <20030126220531.A895@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org> <3E34AEBD.CD390A33@axes-mach01.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: <3E34AEBD.CD390A33@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Mon, Jan 27, 2003 at 09:29:58AM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: M3UA Routing Keys partial match
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>

Srini,

No, SI W does not match at all.

--brian

ksrinivas wrote:                                                                 (Mon, 27 Jan 2003 09:29:58)
> Brian,
> 
>      If a message arrives with OPC A and DPC X and SI W for the Routing Keys you have mentioned, Does it not
> partially match with both the Routing Keys?. (Assuming that hierarchical RKs are not allowed by the SGP).
> 
> --Srini
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Srini,
> >
> > Here are the two same routing keys:
> >
> >   RK1, OPC * DPC X SI Y
> >   RK1, OPC * DPC X SI Z
> >
> > A message arrives with OPC A and DPC Q and SI W.  Does it not
> > partially match the first routing key because OPC A matches
> > the wildcard on OPC?
> >
> > No.  When the RFC say partial match it is referring to the
> > message OPC A, DPC X, SI Y having a partial match to RK1.
> > (It does not match in OPC because OPC is "wildcarded".)
> >
> > --brian
> >
> > ksrinivas wrote:                                                                 (Thu, 23 Jan 2003 17:07:16)
> > > Brian,
> > >
> > >   Let us assume that the following two RKs are registered with an SGP
> > >
> > >   REG REQ (RK1, DPC X, SI = Y)
> > >   REG REQ (RK2, DPC X, SI = Z)
> > >
> > > and from SS7 network, say a MSU with DPC X and SI = Z is received.
> > >
> > > When M3UA at SGP tries to match DPC X and SI = Z with the first(DPC X,
> > > SI = Y) Routing Key, Does it not treat it as a partial match?.(as DPC
> > > matches).
> > >
> > > --Srini
> >
> > --
> > 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 mailnull@www1.ietf.org  Mon Jan 27 01:17:19 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 BAA28066
	for <sigtran-archive@odin.ietf.org>; Mon, 27 Jan 2003 01:17:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0R6bdN17990
	for sigtran-archive@odin.ietf.org; Mon, 27 Jan 2003 01:37:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R6aqJ17327;
	Mon, 27 Jan 2003 01:36:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R6XKJ17235
	for <sigtran@optimus.ietf.org>; Mon, 27 Jan 2003 01:33:20 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28029
	for <sigtran@ietf.org>; Mon, 27 Jan 2003 01:12:29 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0R6FsBS028065;
	Mon, 27 Jan 2003 00:15:56 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id KAA14819; Mon, 27 Jan 2003 10:45:09 -0500 (GMT)
Message-ID: <3E34CEED.B3006B46@axes-mach01.usa.alcatel.com>
Date: Mon, 27 Jan 2003 11:47:18 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

     If a message arrives with OPC A and DPC X and SI W for the Routing Keys
you have mentioned, Does it not partially match with both the Routing Keys?. (Assuming that hierarchical RKs are
not allowed by the SGP).

--Srini

"Brian F. G. Bidulock" wrote:

> Srini,
>
> Here are the two same routing keys:
>
>   RK1, OPC * DPC X SI Y
>   RK1, OPC * DPC X SI Z
>
> A message arrives with OPC A and DPC Q and SI W.  Does it not
> partially match the first routing key because OPC A matches
> the wildcard on OPC?
>
> No.  When the RFC say partial match it is referring to the
> message OPC A, DPC X, SI Y having a partial match to RK1.
> (It does not match in OPC because OPC is "wildcarded".)
>
> --brian
>
> ksrinivas wrote:                                                                 (Thu, 23 Jan 2003 17:07:16)
> > Brian,
> >
> >   Let us assume that the following two RKs are registered with an SGP
> >
> >   REG REQ (RK1, DPC X, SI = Y)
> >   REG REQ (RK2, DPC X, SI = Z)
> >
> > and from SS7 network, say a MSU with DPC X and SI = Z is received.
> >
> > When M3UA at SGP tries to match DPC X and SI = Z with the first(DPC X,
> > SI = Y) Routing Key, Does it not treat it as a partial match?.(as DPC
> > matches).
> >
> > --Srini
>
> --
> 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 mailnull@www1.ietf.org  Mon Jan 27 01:20: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 BAA28102
	for <sigtran-archive@odin.ietf.org>; Mon, 27 Jan 2003 01:20:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0R6eTH18111
	for sigtran-archive@odin.ietf.org; Mon, 27 Jan 2003 01:40:29 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R6eJJ18104;
	Mon, 27 Jan 2003 01:40:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R6d3J18033
	for <sigtran@optimus.ietf.org>; Mon, 27 Jan 2003 01:39:03 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28085
	for <sigtran@ietf.org>; Mon, 27 Jan 2003 01:18:12 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:5rUI3aqjKl3yQJ/2doy610/IJSGPl5Yc@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0R6LgD10875;
	Sun, 26 Jan 2003 23:21:42 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0R6LgE02312;
	Sun, 26 Jan 2003 23:21:42 -0700
Date: Sun, 26 Jan 2003 23:21:42 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
Message-ID: <20030126232141.A2194@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org> <3E34CEED.B3006B46@axes-mach01.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: <3E34CEED.B3006B46@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Mon, Jan 27, 2003 at 11:47:18AM +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>

Srini,

It is is a mismatch because W != Y && W != Z.

--brian

ksrinivas wrote:                                                                 (Mon, 27 Jan 2003 11:47:18)
> Brian,
> 
>      If a message arrives with OPC A and DPC X and SI W for the Routing Keys
> you have mentioned, Does it not partially match with both the Routing Keys?. (Assuming that hierarchical RKs are
> not allowed by the SGP).
> 
> --Srini
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Srini,
> >
> > Here are the two same routing keys:
> >
> >   RK1, OPC * DPC X SI Y
> >   RK1, OPC * DPC X SI Z
> >
> > A message arrives with OPC A and DPC Q and SI W.  Does it not
> > partially match the first routing key because OPC A matches
> > the wildcard on OPC?
> >
> > No.  When the RFC say partial match it is referring to the
> > message OPC A, DPC X, SI Y having a partial match to RK1.
> > (It does not match in OPC because OPC is "wildcarded".)
> >
> > --brian
> >
> > ksrinivas wrote:                                                                 (Thu, 23 Jan 2003 17:07:16)
> > > Brian,
> > >
> > >   Let us assume that the following two RKs are registered with an SGP
> > >
> > >   REG REQ (RK1, DPC X, SI = Y)
> > >   REG REQ (RK2, DPC X, SI = Z)
> > >
> > > and from SS7 network, say a MSU with DPC X and SI = Z is received.
> > >
> > > When M3UA at SGP tries to match DPC X and SI = Z with the first(DPC X,
> > > SI = Y) Routing Key, Does it not treat it as a partial match?.(as DPC
> > > matches).
> > >
> > > --Srini
> >
> > --
> > 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 mailnull@www1.ietf.org  Mon Jan 27 03:34:25 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 DAA09760
	for <sigtran-archive@odin.ietf.org>; Mon, 27 Jan 2003 03:34:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0R8skN03252
	for sigtran-archive@odin.ietf.org; Mon, 27 Jan 2003 03:54:46 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R8s4J03213;
	Mon, 27 Jan 2003 03:54:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R8qwJ03155
	for <sigtran@optimus.ietf.org>; Mon, 27 Jan 2003 03:52:58 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09719
	for <sigtran@ietf.org>; Mon, 27 Jan 2003 03:32:04 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0R8ZUVN007661;
	Mon, 27 Jan 2003 02:35:31 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id NAA18638; Mon, 27 Jan 2003 13:04:42 -0500 (GMT)
Message-ID: <3E34EFA4.5DFDBCC9@axes-mach01.usa.alcatel.com>
Date: Mon, 27 Jan 2003 14:06:52 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: sigtran@ietf.org
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org> <3E34AEBD.CD390A33@axes-mach01.usa.alcatel.com> <20030126220531.A895@openss7.org>
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] Re: M3UA Routing Keys partial match
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

Brian,

    But the DPC X matches. Is it not a partial match?. If not, What is a partial match?.

--Srini

"Brian F. G. Bidulock" wrote:

> Srini,
>
> No, SI W does not match at all.
>
> --brian
>
> ksrinivas wrote:                                                                 (Mon, 27 Jan 2003 09:29:58)
> > Brian,
> >
> >      If a message arrives with OPC A and DPC X and SI W for the Routing Keys you have mentioned, Does it not
> > partially match with both the Routing Keys?. (Assuming that hierarchical RKs are not allowed by the SGP).
> >
> > --Srini
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > Srini,
> > >
> > > Here are the two same routing keys:
> > >
> > >   RK1, OPC * DPC X SI Y
> > >   RK1, OPC * DPC X SI Z
> > >
> > > A message arrives with OPC A and DPC Q and SI W.  Does it not
> > > partially match the first routing key because OPC A matches
> > > the wildcard on OPC?
> > >
> > > No.  When the RFC say partial match it is referring to the
> > > message OPC A, DPC X, SI Y having a partial match to RK1.
> > > (It does not match in OPC because OPC is "wildcarded".)
> > >
> > > --brian
> > >
> > > ksrinivas wrote:                                                                 (Thu, 23 Jan 2003 17:07:16)
> > > > Brian,
> > > >
> > > >   Let us assume that the following two RKs are registered with an SGP
> > > >
> > > >   REG REQ (RK1, DPC X, SI = Y)
> > > >   REG REQ (RK2, DPC X, SI = Z)
> > > >
> > > > and from SS7 network, say a MSU with DPC X and SI = Z is received.
> > > >
> > > > When M3UA at SGP tries to match DPC X and SI = Z with the first(DPC X,
> > > > SI = Y) Routing Key, Does it not treat it as a partial match?.(as DPC
> > > > matches).
> > > >
> > > > --Srini
> > >
> > > --
> > > 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 mailnull@www1.ietf.org  Mon Jan 27 03:52: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 DAA10078
	for <sigtran-archive@odin.ietf.org>; Mon, 27 Jan 2003 03:52:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0R9CPK04951
	for sigtran-archive@odin.ietf.org; Mon, 27 Jan 2003 04:12:25 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R9CCJ04869;
	Mon, 27 Jan 2003 04:12:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R8v9J03340
	for <sigtran@optimus.ietf.org>; Mon, 27 Jan 2003 03:57:09 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09784
	for <sigtran@ietf.org>; Mon, 27 Jan 2003 03:36:16 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:CLV0R74PVrLyiCcLnI4W7MUvjHoMQPFc@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0R8djD12541;
	Mon, 27 Jan 2003 01:39:45 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0R8djW04127;
	Mon, 27 Jan 2003 01:39:45 -0700
Date: Mon, 27 Jan 2003 01:39:44 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Message-ID: <20030127013944.A4093@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org> <3E34AEBD.CD390A33@axes-mach01.usa.alcatel.com> <20030126220531.A895@openss7.org> <3E34EFA4.5DFDBCC9@axes-mach01.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: <3E34EFA4.5DFDBCC9@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Mon, Jan 27, 2003 at 02:06:52PM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: M3UA Routing Keys partial match
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>

Srini,

RK SSN = 5, Message with no SSN.

IMO, that's a partial match.

If one removes SSN from RK, one can remove the words "partial match".

--brian

ksrinivas wrote:                                                                 (Mon, 27 Jan 2003 14:06:52)
> Brian,
> 
>     But the DPC X matches. Is it not a partial match?. If not, What is a partial match?.
> 
> --Srini
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Srini,
> >
> > No, SI W does not match at all.
> >
> > --brian
> >
> > ksrinivas wrote:                                                                 (Mon, 27 Jan 2003 09:29:58)
> > > Brian,
> > >
> > >      If a message arrives with OPC A and DPC X and SI W for the Routing Keys you have mentioned, Does it not
> > > partially match with both the Routing Keys?. (Assuming that hierarchical RKs are not allowed by the SGP).
> > >
> > > --Srini
> > >
> > > "Brian F. G. Bidulock" wrote:
> > >
> > > > Srini,
> > > >
> > > > Here are the two same routing keys:
> > > >
> > > >   RK1, OPC * DPC X SI Y
> > > >   RK1, OPC * DPC X SI Z
> > > >
> > > > A message arrives with OPC A and DPC Q and SI W.  Does it not
> > > > partially match the first routing key because OPC A matches
> > > > the wildcard on OPC?
> > > >
> > > > No.  When the RFC say partial match it is referring to the
> > > > message OPC A, DPC X, SI Y having a partial match to RK1.
> > > > (It does not match in OPC because OPC is "wildcarded".)
> > > >
> > > > --brian
> > > >
> > > > ksrinivas wrote:                                                                 (Thu, 23 Jan 2003 17:07:16)
> > > > > Brian,
> > > > >
> > > > >   Let us assume that the following two RKs are registered with an SGP
> > > > >
> > > > >   REG REQ (RK1, DPC X, SI = Y)
> > > > >   REG REQ (RK2, DPC X, SI = Z)
> > > > >
> > > > > and from SS7 network, say a MSU with DPC X and SI = Z is received.
> > > > >
> > > > > When M3UA at SGP tries to match DPC X and SI = Z with the first(DPC X,
> > > > > SI = Y) Routing Key, Does it not treat it as a partial match?.(as DPC
> > > > > matches).
> > > > >
> > > > > --Srini
> > > >
> > > > --
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> >
> > --
> > 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 mailnull@www1.ietf.org  Mon Jan 27 03: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 DAA10094
	for <sigtran-archive@odin.ietf.org>; Mon, 27 Jan 2003 03:52:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0R9CgC04980
	for sigtran-archive@odin.ietf.org; Mon, 27 Jan 2003 04:12:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R9CKJ04920;
	Mon, 27 Jan 2003 04:12:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R93dJ03883
	for <sigtran@optimus.ietf.org>; Mon, 27 Jan 2003 04:03:39 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09849
	for <sigtran@ietf.org>; Mon, 27 Jan 2003 03:42:46 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0R8kBVN008131;
	Mon, 27 Jan 2003 02:46:13 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id NAA18941; Mon, 27 Jan 2003 13:15:24 -0500 (GMT)
Message-ID: <3E34F225.CEDA864F@axes-mach01.usa.alcatel.com>
Date: Mon, 27 Jan 2003 14:17:34 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org> <3E34CEED.B3006B46@axes-mach01.usa.alcatel.com> <20030126232141.A2194@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

   How is it different from partial match?.

--Srini

"Brian F. G. Bidulock" wrote:

> Srini,
>
> It is is a mismatch because W != Y && W != Z.
>
> --brian
>
> ksrinivas wrote:                                                                 (Mon, 27 Jan 2003 11:47:18)
> > Brian,
> >
> >      If a message arrives with OPC A and DPC X and SI W for the Routing Keys
> > you have mentioned, Does it not partially match with both the Routing Keys?. (Assuming that hierarchical RKs are
> > not allowed by the SGP).
> >
> > --Srini
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > Srini,
> > >
> > > Here are the two same routing keys:
> > >
> > >   RK1, OPC * DPC X SI Y
> > >   RK1, OPC * DPC X SI Z
> > >
> > > A message arrives with OPC A and DPC Q and SI W.  Does it not
> > > partially match the first routing key because OPC A matches
> > > the wildcard on OPC?
> > >
> > > No.  When the RFC say partial match it is referring to the
> > > message OPC A, DPC X, SI Y having a partial match to RK1.
> > > (It does not match in OPC because OPC is "wildcarded".)
> > >
> > > --brian
> > >
> > > ksrinivas wrote:                                                                 (Thu, 23 Jan 2003 17:07:16)
> > > > Brian,
> > > >
> > > >   Let us assume that the following two RKs are registered with an SGP
> > > >
> > > >   REG REQ (RK1, DPC X, SI = Y)
> > > >   REG REQ (RK2, DPC X, SI = Z)
> > > >
> > > > and from SS7 network, say a MSU with DPC X and SI = Z is received.
> > > >
> > > > When M3UA at SGP tries to match DPC X and SI = Z with the first(DPC X,
> > > > SI = Y) Routing Key, Does it not treat it as a partial match?.(as DPC
> > > > matches).
> > > >
> > > > --Srini
> > >
> > > --
> > > 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 mailnull@www1.ietf.org  Mon Jan 27 03:59:15 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 DAA10185
	for <sigtran-archive@odin.ietf.org>; Mon, 27 Jan 2003 03:59:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0R9JbF05302
	for sigtran-archive@odin.ietf.org; Mon, 27 Jan 2003 04:19:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R9JAJ05289;
	Mon, 27 Jan 2003 04:19:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R9IMJ05242
	for <sigtran@optimus.ietf.org>; Mon, 27 Jan 2003 04:18:22 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10153
	for <sigtran@ietf.org>; Mon, 27 Jan 2003 03:57:28 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:5R/tV9ZaGIDBf9jfDw7RvOGKvrc7f0W4@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0R90vD12843;
	Mon, 27 Jan 2003 02:00:57 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0R90vs04518;
	Mon, 27 Jan 2003 02:00:57 -0700
Date: Mon, 27 Jan 2003 02:00:57 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
Message-ID: <20030127020057.A4258@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	sigtran@ietf.org
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org> <3E34CEED.B3006B46@axes-mach01.usa.alcatel.com> <20030126232141.A2194@openss7.org> <3E34F225.CEDA864F@axes-mach01.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: <3E34F225.CEDA864F@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Mon, Jan 27, 2003 at 02:17:34PM +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>

Srini,

Because it is a mismatch.  A partial match matches on
the information available in the message but the routing
key has fields not specified in the message.  The only
case of this is SSN or TID.

--brian

ksrinivas wrote:                                                                 (Mon, 27 Jan 2003 14:17:34)
> Brian,
> 
>    How is it different from partial match?.
> 
> --Srini
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Srini,
> >
> > It is is a mismatch because W != Y && W != Z.
> >
> > --brian
> >
> > ksrinivas wrote:                                                                 (Mon, 27 Jan 2003 11:47:18)
> > > Brian,
> > >
> > >      If a message arrives with OPC A and DPC X and SI W for the Routing Keys
> > > you have mentioned, Does it not partially match with both the Routing Keys?. (Assuming that hierarchical RKs are
> > > not allowed by the SGP).
> > >
> > > --Srini
> > >
> > > "Brian F. G. Bidulock" wrote:
> > >
> > > > Srini,
> > > >
> > > > Here are the two same routing keys:
> > > >
> > > >   RK1, OPC * DPC X SI Y
> > > >   RK1, OPC * DPC X SI Z
> > > >
> > > > A message arrives with OPC A and DPC Q and SI W.  Does it not
> > > > partially match the first routing key because OPC A matches
> > > > the wildcard on OPC?
> > > >
> > > > No.  When the RFC say partial match it is referring to the
> > > > message OPC A, DPC X, SI Y having a partial match to RK1.
> > > > (It does not match in OPC because OPC is "wildcarded".)
> > > >
> > > > --brian
> > > >
> > > > ksrinivas wrote:                                                                 (Thu, 23 Jan 2003 17:07:16)
> > > > > Brian,
> > > > >
> > > > >   Let us assume that the following two RKs are registered with an SGP
> > > > >
> > > > >   REG REQ (RK1, DPC X, SI = Y)
> > > > >   REG REQ (RK2, DPC X, SI = Z)
> > > > >
> > > > > and from SS7 network, say a MSU with DPC X and SI = Z is received.
> > > > >
> > > > > When M3UA at SGP tries to match DPC X and SI = Z with the first(DPC X,
> > > > > SI = Y) Routing Key, Does it not treat it as a partial match?.(as DPC
> > > > > matches).
> > > > >
> > > > > --Srini
> > > >
> > > > --
> > > > 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 mailnull@www1.ietf.org  Mon Jan 27 04:06: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 EAA10321
	for <sigtran-archive@odin.ietf.org>; Mon, 27 Jan 2003 04:06:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0R9QxH05689
	for sigtran-archive@odin.ietf.org; Mon, 27 Jan 2003 04:26:59 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R9QGJ05663;
	Mon, 27 Jan 2003 04:26:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R9P5J05573
	for <sigtran@optimus.ietf.org>; Mon, 27 Jan 2003 04:25:05 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10283
	for <sigtran@ietf.org>; Mon, 27 Jan 2003 04:04:11 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0R97ZBS024755;
	Mon, 27 Jan 2003 03:07:37 -0600 (CST)
Received: from axsppc67 by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id NAA19624; Mon, 27 Jan 2003 13:36:47 -0500 (GMT)
Message-ID: <007201c2c5e3$de68e6a0$7501ff0a@axsppc67>
From: "PSK Chakravarthi" <chak@axes-mach01.usa.alcatel.com>
To: <bidulock@openss7.org>, "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
Cc: <sigtran@ietf.org>
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org> <3E34AEBD.CD390A33@axes-mach01.usa.alcatel.com> <20030126220531.A895@openss7.org> <3E34EFA4.5DFDBCC9@axes-mach01.usa.alcatel.com> <20030127013944.A4093@openss7.org>
Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
Date: Mon, 27 Jan 2003 14:39:46 +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.50.4133.2400
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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

Brian,

Thanks, now I got what is a partial match.
What about default ASP?  This was introduced for supporting partial RKs.

Thanks
Chak



----- Original Message -----
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
Cc: <sigtran@ietf.org>
Sent: Monday, January 27, 2003 2:09 PM
Subject: [Sigtran] Re: M3UA Routing Keys partial match


> Srini,
>
> RK SSN = 5, Message with no SSN.
>
> IMO, that's a partial match.
>
> If one removes SSN from RK, one can remove the words "partial match".
>
> --brian
>
> ksrinivas wrote:
(Mon, 27 Jan 2003 14:06:52)
> > Brian,
> >
> >     But the DPC X matches. Is it not a partial match?. If not, What is a
partial match?.
> >
> > --Srini
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > Srini,
> > >
> > > No, SI W does not match at all.
> > >
> > > --brian
> > >
> > > ksrinivas wrote:
(Mon, 27 Jan 2003 09:29:58)
> > > > Brian,
> > > >
> > > >      If a message arrives with OPC A and DPC X and SI W for the
Routing Keys you have mentioned, Does it not
> > > > partially match with both the Routing Keys?. (Assuming that
hierarchical RKs are not allowed by the SGP).
> > > >
> > > > --Srini
> > > >
> > > > "Brian F. G. Bidulock" wrote:
> > > >
> > > > > Srini,
> > > > >
> > > > > Here are the two same routing keys:
> > > > >
> > > > >   RK1, OPC * DPC X SI Y
> > > > >   RK1, OPC * DPC X SI Z
> > > > >
> > > > > A message arrives with OPC A and DPC Q and SI W.  Does it not
> > > > > partially match the first routing key because OPC A matches
> > > > > the wildcard on OPC?
> > > > >
> > > > > No.  When the RFC say partial match it is referring to the
> > > > > message OPC A, DPC X, SI Y having a partial match to RK1.
> > > > > (It does not match in OPC because OPC is "wildcarded".)
> > > > >
> > > > > --brian
> > > > >
> > > > > ksrinivas wrote:
(Thu, 23 Jan 2003 17:07:16)
> > > > > > Brian,
> > > > > >
> > > > > >   Let us assume that the following two RKs are registered with
an SGP
> > > > > >
> > > > > >   REG REQ (RK1, DPC X, SI = Y)
> > > > > >   REG REQ (RK2, DPC X, SI = Z)
> > > > > >
> > > > > > and from SS7 network, say a MSU with DPC X and SI = Z is
received.
> > > > > >
> > > > > > When M3UA at SGP tries to match DPC X and SI = Z with the
first(DPC X,
> > > > > > SI = Y) Routing Key, Does it not treat it as a partial
match?.(as DPC
> > > > > > matches).
> > > > > >
> > > > > > --Srini
> > > > >
> > > > > --
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > >
> > > --
> > > 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
>

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



From mailnull@www1.ietf.org  Mon Jan 27 04:08:57 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 EAA10380
	for <sigtran-archive@odin.ietf.org>; Mon, 27 Jan 2003 04:08:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0R9TKr05836
	for sigtran-archive@odin.ietf.org; Mon, 27 Jan 2003 04:29:20 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R9T7J05814;
	Mon, 27 Jan 2003 04:29:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0R9SUJ05778
	for <sigtran@optimus.ietf.org>; Mon, 27 Jan 2003 04:28:30 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10349
	for <sigtran@ietf.org>; Mon, 27 Jan 2003 04:07:36 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:KC64g9D61jkyHIkyG4kGVDLzF4NRyd3a@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0R9B5D12977;
	Mon, 27 Jan 2003 02:11:05 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0R9B5r04845;
	Mon, 27 Jan 2003 02:11:05 -0700
Date: Mon, 27 Jan 2003 02:11:05 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>
Cc: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Routing Keys partial match
Message-ID: <20030127021105.A4664@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: PSK Chakravarthi <chak@axes-mach01.usa.alcatel.com>,
	ksrinivas <ksrini@axes-mach01.usa.alcatel.com>, sigtran@ietf.org
References: <3E2FD3EB.91B957CD@axes-mach01.usa.alcatel.com> <20030123051125.C20273@openss7.org> <3E34AEBD.CD390A33@axes-mach01.usa.alcatel.com> <20030126220531.A895@openss7.org> <3E34EFA4.5DFDBCC9@axes-mach01.usa.alcatel.com> <20030127013944.A4093@openss7.org> <007201c2c5e3$de68e6a0$7501ff0a@axsppc67>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <007201c2c5e3$de68e6a0$7501ff0a@axsppc67>; from chak@axes-mach01.usa.alcatel.com on Mon, Jan 27, 2003 at 02:39:46PM +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>

Chak,

Default ASP is primarily for if there is no match.

--brian

PSK Chakravarthi wrote:                                                                (Mon, 27 Jan 2003 14:39:46)
> Brian,
> 
> Thanks, now I got what is a partial match.
> What about default ASP?  This was introduced for supporting partial RKs.
> 
> Thanks
> Chak
> 
> 
> 
> ----- Original Message -----
> From: "Brian F. G. Bidulock" <bidulock@openss7.org>
> To: "ksrinivas" <ksrini@axes-mach01.usa.alcatel.com>
> Cc: <sigtran@ietf.org>
> Sent: Monday, January 27, 2003 2:09 PM
> Subject: [Sigtran] Re: M3UA Routing Keys partial match
> 
> 
> > Srini,
> >
> > RK SSN = 5, Message with no SSN.
> >
> > IMO, that's a partial match.
> >
> > If one removes SSN from RK, one can remove the words "partial match".
> >
> > --brian
> >
> > ksrinivas wrote:
> (Mon, 27 Jan 2003 14:06:52)
> > > Brian,
> > >
> > >     But the DPC X matches. Is it not a partial match?. If not, What is a
> partial match?.
> > >
> > > --Srini
> > >
> > > "Brian F. G. Bidulock" wrote:
> > >
> > > > Srini,
> > > >
> > > > No, SI W does not match at all.
> > > >
> > > > --brian
> > > >
> > > > ksrinivas wrote:
> (Mon, 27 Jan 2003 09:29:58)
> > > > > Brian,
> > > > >
> > > > >      If a message arrives with OPC A and DPC X and SI W for the
> Routing Keys you have mentioned, Does it not
> > > > > partially match with both the Routing Keys?. (Assuming that
> hierarchical RKs are not allowed by the SGP).
> > > > >
> > > > > --Srini
> > > > >
> > > > > "Brian F. G. Bidulock" wrote:
> > > > >
> > > > > > Srini,
> > > > > >
> > > > > > Here are the two same routing keys:
> > > > > >
> > > > > >   RK1, OPC * DPC X SI Y
> > > > > >   RK1, OPC * DPC X SI Z
> > > > > >
> > > > > > A message arrives with OPC A and DPC Q and SI W.  Does it not
> > > > > > partially match the first routing key because OPC A matches
> > > > > > the wildcard on OPC?
> > > > > >
> > > > > > No.  When the RFC say partial match it is referring to the
> > > > > > message OPC A, DPC X, SI Y having a partial match to RK1.
> > > > > > (It does not match in OPC because OPC is "wildcarded".)
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > > ksrinivas wrote:
> (Thu, 23 Jan 2003 17:07:16)
> > > > > > > Brian,
> > > > > > >
> > > > > > >   Let us assume that the following two RKs are registered with
> an SGP
> > > > > > >
> > > > > > >   REG REQ (RK1, DPC X, SI = Y)
> > > > > > >   REG REQ (RK2, DPC X, SI = Z)
> > > > > > >
> > > > > > > and from SS7 network, say a MSU with DPC X and SI = Z is
> received.
> > > > > > >
> > > > > > > When M3UA at SGP tries to match DPC X and SI = Z with the
> first(DPC X,
> > > > > > > SI = Y) Routing Key, Does it not treat it as a partial
> match?.(as DPC
> > > > > > > matches).
> > > > > > >
> > > > > > > --Srini
> > > > > >
> > > > > > --
> > > > > > Brian F. G. Bidulock
> > > > > > bidulock@openss7.org
> > > > > > http://www.openss7.org/
> > > >
> > > > --
> > > > 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
> >

-- 
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 Jan 27 10:37: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 KAA17808
	for <sigtran-archive@odin.ietf.org>; Mon, 27 Jan 2003 10:37:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0RFwG929843
	for sigtran-archive@odin.ietf.org; Mon, 27 Jan 2003 10:58:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0RFvoJ29809;
	Mon, 27 Jan 2003 10:57:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0RFsGJ29673
	for <sigtran@optimus.ietf.org>; Mon, 27 Jan 2003 10:54:16 -0500
Received: from revere.sonusnet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17739
	for <sigtran@ietf.org>; Mon, 27 Jan 2003 10:33:14 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3.sonusnet.com [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h0RFaT705792;
	Mon, 27 Jan 2003 10:36:32 -0500 (EST)
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19)
	id <Y68H4MWW>; Mon, 27 Jan 2003 10:36:31 -0500
Message-ID: <4CF48720B6E9D4118D040060CF2074E9072F6BFD@sonusdc3.sonusnet.com>
From: "Wung, Joseph" <JWung@sonusnet.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: RE: [Sigtran] SUA: Routing Key
Date: Mon, 27 Jan 2003 10:36:30 -0500
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,

Section 3.10.17 Address Range of SUA (draft 14)

	"Note 1: The address field must contain pairs of
	Source addresses or pairs of Destination Addresses
	but MUST NOT mix Source Addrress with Destination
	Address in the same Address field."

Why are there pairs of either Source or Destination Addresses 
here?
Why is it that the Address field cannot contain Source AND
Destination Address pairs?

Thanks,
Joe

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Friday, January 24, 2003 6:50 PM
> To: Wung, Joseph
> Cc: 'sigtran@ietf.org'
> Subject: Re: [Sigtran] SUA: Routing Key
> 
> 
> Joe,
> 
> The Source and Desintation Address parameters are used to
> specify a Source and Destination Address for an AMF entry
> (or Routing Key).
> 
> The Address Range parameter can be used to specify a range
> of Sources and range of Destinations Addresses for a set
> of AMF entries.
> 
> In SUA, the registration process essentially associates an
> Application Server and Routing Context with a (set of)
> entries in the AMF.  This is essentially the GTT tables in
> the SG.
> 
> So, for example, an Application Server could register as
> an HLR (SSN=5) against a range of Addresses (MINs) using
> the range parameters.
> 
> That's the idea, anyway.
> 
> --brian
> 
> Wung, Joseph wrote:                                       
> (Fri, 24 Jan 2003 17:47:17)
> > A Routing Key in SUA (draft 14) contains an Address Range 
> > parameter in addition to Source and Destination Address
> > parameters.  The Address Range parameter contains either pairs
> > of Source Address or Destination Address parameters.
> > 
> > Can someone explain what all these mean?
> > 
> > Thanks,
> > Joe
> > 
> > _______________________________________________
> > 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  Mon Jan 27 12:53: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 MAA20842
	for <sigtran-archive@odin.ietf.org>; Mon, 27 Jan 2003 12:53:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0RIE1F06146
	for sigtran-archive@odin.ietf.org; Mon, 27 Jan 2003 13:14:01 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0RIDnJ06130;
	Mon, 27 Jan 2003 13:13:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0RIBZJ05998
	for <sigtran@optimus.ietf.org>; Mon, 27 Jan 2003 13:11:35 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20690
	for <sigtran@ietf.org>; Mon, 27 Jan 2003 12:50:29 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:OXLmGx4FfngwVmF7qrDJ6Qtn2cb5IDQt@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0RHrxD23802;
	Mon, 27 Jan 2003 10:53:59 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0RHrxI15910;
	Mon, 27 Jan 2003 10:53:59 -0700
Date: Mon, 27 Jan 2003 10:53:59 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Wung, Joseph" <JWung@sonusnet.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA: Routing Key
Message-ID: <20030127105359.A4904@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Wung, Joseph" <JWung@sonusnet.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <4CF48720B6E9D4118D040060CF2074E9072F6BFD@sonusdc3.sonusnet.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: <4CF48720B6E9D4118D040060CF2074E9072F6BFD@sonusdc3.sonusnet.com>; from JWung@sonusnet.com on Mon, Jan 27, 2003 at 10:36:30AM -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>

Joseph,

Because the Address Range must specify either a range of source
address or a range of destination address.  A mixture in the
same parameter has no meaning.

--brian

Wung, Joseph wrote:                                                                  (Mon, 27 Jan 2003 10:36:30)
> Brian,
> 
> Section 3.10.17 Address Range of SUA (draft 14)
> 
> 	"Note 1: The address field must contain pairs of
> 	Source addresses or pairs of Destination Addresses
> 	but MUST NOT mix Source Addrress with Destination
> 	Address in the same Address field."
> 
> Why are there pairs of either Source or Destination Addresses 
> here?
> Why is it that the Address field cannot contain Source AND
> Destination Address pairs?
> 
> Thanks,
> Joe
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Friday, January 24, 2003 6:50 PM
> > To: Wung, Joseph
> > Cc: 'sigtran@ietf.org'
> > Subject: Re: [Sigtran] SUA: Routing Key
> > 
> > 
> > Joe,
> > 
> > The Source and Desintation Address parameters are used to
> > specify a Source and Destination Address for an AMF entry
> > (or Routing Key).
> > 
> > The Address Range parameter can be used to specify a range
> > of Sources and range of Destinations Addresses for a set
> > of AMF entries.
> > 
> > In SUA, the registration process essentially associates an
> > Application Server and Routing Context with a (set of)
> > entries in the AMF.  This is essentially the GTT tables in
> > the SG.
> > 
> > So, for example, an Application Server could register as
> > an HLR (SSN=5) against a range of Addresses (MINs) using
> > the range parameters.
> > 
> > That's the idea, anyway.
> > 
> > --brian
> > 
> > Wung, Joseph wrote:                                       
> > (Fri, 24 Jan 2003 17:47:17)
> > > A Routing Key in SUA (draft 14) contains an Address Range 
> > > parameter in addition to Source and Destination Address
> > > parameters.  The Address Range parameter contains either pairs
> > > of Source Address or Destination Address parameters.
> > > 
> > > Can someone explain what all these mean?
> > > 
> > > Thanks,
> > > Joe
> > > 
> > > _______________________________________________
> > > 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 mailnull@www1.ietf.org  Mon Jan 27 13:09: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 NAA21436
	for <sigtran-archive@odin.ietf.org>; Mon, 27 Jan 2003 13:09:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0RITwP06991
	for sigtran-archive@odin.ietf.org; Mon, 27 Jan 2003 13:29:58 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0RITAJ06966;
	Mon, 27 Jan 2003 13:29:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0RISJJ06937
	for <sigtran@optimus.ietf.org>; Mon, 27 Jan 2003 13:28:19 -0500
Received: from revere.sonusnet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21369
	for <sigtran@ietf.org>; Mon, 27 Jan 2003 13:07:13 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3.sonusnet.com [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h0RIAZ720559;
	Mon, 27 Jan 2003 13:10:35 -0500 (EST)
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19)
	id <Y68H4NZX>; Mon, 27 Jan 2003 13:10:36 -0500
Message-ID: <4CF48720B6E9D4118D040060CF2074E9072F6BFE@sonusdc3.sonusnet.com>
From: "Wung, Joseph" <JWung@sonusnet.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: RE: [Sigtran] SUA: Routing Key
Date: Mon, 27 Jan 2003 13:10:35 -0500
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,

What makes Source addresses a pair of Source addresses?

Joe

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Monday, January 27, 2003 12:54 PM
> To: Wung, Joseph
> Cc: 'sigtran@ietf.org'
> Subject: Re: [Sigtran] SUA: Routing Key
> 
> 
> Joseph,
> 
> Because the Address Range must specify either a range of source
> address or a range of destination address.  A mixture in the
> same parameter has no meaning.
> 
> --brian
> 
> Wung, Joseph wrote:                                           
>                        (Mon, 27 Jan 2003 10:36:30)
> > Brian,
> > 
> > Section 3.10.17 Address Range of SUA (draft 14)
> > 
> > 	"Note 1: The address field must contain pairs of
> > 	Source addresses or pairs of Destination Addresses
> > 	but MUST NOT mix Source Addrress with Destination
> > 	Address in the same Address field."
> > 
> > Why are there pairs of either Source or Destination Addresses 
> > here?
> > Why is it that the Address field cannot contain Source AND
> > Destination Address pairs?
> > 
> > Thanks,
> > Joe
> > 
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: Friday, January 24, 2003 6:50 PM
> > > To: Wung, Joseph
> > > Cc: 'sigtran@ietf.org'
> > > Subject: Re: [Sigtran] SUA: Routing Key
> > > 
> > > 
> > > Joe,
> > > 
> > > The Source and Desintation Address parameters are used to
> > > specify a Source and Destination Address for an AMF entry
> > > (or Routing Key).
> > > 
> > > The Address Range parameter can be used to specify a range
> > > of Sources and range of Destinations Addresses for a set
> > > of AMF entries.
> > > 
> > > In SUA, the registration process essentially associates an
> > > Application Server and Routing Context with a (set of)
> > > entries in the AMF.  This is essentially the GTT tables in
> > > the SG.
> > > 
> > > So, for example, an Application Server could register as
> > > an HLR (SSN=5) against a range of Addresses (MINs) using
> > > the range parameters.
> > > 
> > > That's the idea, anyway.
> > > 
> > > --brian
> > > 
> > > Wung, Joseph wrote:                                       
> > > (Fri, 24 Jan 2003 17:47:17)
> > > > A Routing Key in SUA (draft 14) contains an Address Range 
> > > > parameter in addition to Source and Destination Address
> > > > parameters.  The Address Range parameter contains either pairs
> > > > of Source Address or Destination Address parameters.
> > > > 
> > > > Can someone explain what all these mean?
> > > > 
> > > > Thanks,
> > > > Joe
> > > > 
> > > > _______________________________________________
> > > > 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 mailnull@www1.ietf.org  Mon Jan 27 14:35: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 OAA23877
	for <sigtran-archive@odin.ietf.org>; Mon, 27 Jan 2003 14:35:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0RJuEe12590
	for sigtran-archive@odin.ietf.org; Mon, 27 Jan 2003 14:56:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0RJtVJ12561;
	Mon, 27 Jan 2003 14:55:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0RJslJ12511
	for <sigtran@optimus.ietf.org>; Mon, 27 Jan 2003 14:54:47 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23814
	for <sigtran@ietf.org>; Mon, 27 Jan 2003 14:33:38 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:7W6AJ3gczOfjasYM8b8PRN4PM+SWydUx@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0RJb9D25561;
	Mon, 27 Jan 2003 12:37:09 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0RJb8N19932;
	Mon, 27 Jan 2003 12:37:08 -0700
Date: Mon, 27 Jan 2003 12:37:08 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Wung, Joseph" <JWung@sonusnet.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA: Routing Key
Message-ID: <20030127123708.A17223@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Wung, Joseph" <JWung@sonusnet.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <4CF48720B6E9D4118D040060CF2074E9072F6BFE@sonusdc3.sonusnet.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: <4CF48720B6E9D4118D040060CF2074E9072F6BFE@sonusdc3.sonusnet.com>; from JWung@sonusnet.com on Mon, Jan 27, 2003 at 01:10:35PM -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>

Joe,

When they are both Source addresses and they are a pair. ;)

--brian

Wung, Joseph wrote:                                                                  (Mon, 27 Jan 2003 13:10:35)
> Brian,
> 
> What makes Source addresses a pair of Source addresses?
> 
> Joe
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Monday, January 27, 2003 12:54 PM
> > To: Wung, Joseph
> > Cc: 'sigtran@ietf.org'
> > Subject: Re: [Sigtran] SUA: Routing Key
> > 
> > 
> > Joseph,
> > 
> > Because the Address Range must specify either a range of source
> > address or a range of destination address.  A mixture in the
> > same parameter has no meaning.
> > 
> > --brian
> > 
> > Wung, Joseph wrote:                                           
> >                        (Mon, 27 Jan 2003 10:36:30)
> > > Brian,
> > > 
> > > Section 3.10.17 Address Range of SUA (draft 14)
> > > 
> > > 	"Note 1: The address field must contain pairs of
> > > 	Source addresses or pairs of Destination Addresses
> > > 	but MUST NOT mix Source Addrress with Destination
> > > 	Address in the same Address field."
> > > 
> > > Why are there pairs of either Source or Destination Addresses 
> > > here?
> > > Why is it that the Address field cannot contain Source AND
> > > Destination Address pairs?
> > > 
> > > Thanks,
> > > Joe
> > > 
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: Friday, January 24, 2003 6:50 PM
> > > > To: Wung, Joseph
> > > > Cc: 'sigtran@ietf.org'
> > > > Subject: Re: [Sigtran] SUA: Routing Key
> > > > 
> > > > 
> > > > Joe,
> > > > 
> > > > The Source and Desintation Address parameters are used to
> > > > specify a Source and Destination Address for an AMF entry
> > > > (or Routing Key).
> > > > 
> > > > The Address Range parameter can be used to specify a range
> > > > of Sources and range of Destinations Addresses for a set
> > > > of AMF entries.
> > > > 
> > > > In SUA, the registration process essentially associates an
> > > > Application Server and Routing Context with a (set of)
> > > > entries in the AMF.  This is essentially the GTT tables in
> > > > the SG.
> > > > 
> > > > So, for example, an Application Server could register as
> > > > an HLR (SSN=5) against a range of Addresses (MINs) using
> > > > the range parameters.
> > > > 
> > > > That's the idea, anyway.
> > > > 
> > > > --brian
> > > > 
> > > > Wung, Joseph wrote:                                       
> > > > (Fri, 24 Jan 2003 17:47:17)
> > > > > A Routing Key in SUA (draft 14) contains an Address Range 
> > > > > parameter in addition to Source and Destination Address
> > > > > parameters.  The Address Range parameter contains either pairs
> > > > > of Source Address or Destination Address parameters.
> > > > > 
> > > > > Can someone explain what all these mean?
> > > > > 
> > > > > Thanks,
> > > > > Joe
> > > > > 
> > > > > _______________________________________________
> > > > > 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/
> > 

-- 
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 Jan 27 17:43: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 RAA29638
	for <sigtran-archive@odin.ietf.org>; Mon, 27 Jan 2003 17:43:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0RN43c24000
	for sigtran-archive@odin.ietf.org; Mon, 27 Jan 2003 18:04:03 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0RN2oJ23955;
	Mon, 27 Jan 2003 18:02:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0RMxWJ23812
	for <sigtran@optimus.ietf.org>; Mon, 27 Jan 2003 17:59:32 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29570
	for <sigtran@ietf.org>; Mon, 27 Jan 2003 17:38:21 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0RMfoeW020912;
	Mon, 27 Jan 2003 16:41:50 -0600 (CST)
Message-ID: <3E35B5AE.E339F159@alcatel.com>
Date: Mon, 27 Jan 2003 16:41:50 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: sigtran@ietf.org
Subject: Re: [Sigtran] m2pa comment: author list
References: <2135200C183FD5119588009027DE572302836C0C@webdev-owa.oni.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

Lyndon,

I removed those 2 names from the author list and added them to the
Acknowledgements section.

tomG.

"Ong, Lyndon" wrote:
> 
> Thanks, Greg!
> 
> -----Original Message-----
> From: Greg Sidebottom [mailto:gregside@rogers.com]
> Sent: Sunday, January 26, 2003 2:35 PM
> To: Ong, Lyndon; sigtran@ietf.org
> Subject: Re: [Sigtran] m2pa comment: author list
> 
> Hi Lyndon,
> 
>   I'll volunteer  2;^)
> 
> Cheers,
> 
>     Greg
> 
> ----- Original Message -----
> From: "Ong, Lyndon" <LyOng@ciena.com>
> To: <sigtran@ietf.org>
> Sent: Sunday, January 26, 2003 2:38 PM
> Subject: [Sigtran] m2pa comment: author list
> 
> > Folks,
> >
> > One comment - the author's list is too long and will get it killed in
> IESG.
> > Suggest we drop at least 2 names, probably Mallesh Kalla and one or
> > two others (volunteers?).
> >
> > Also, references need to be sorted into Normative and Non-normative,
> > in separate sections.
> >
> > The security section probably needs to be updated based on the
> > security framework document (which should come out this week).
> >
> > Cheers,
> >
> > L. Ong
> > _______________________________________________
> > 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

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 28 03:03:52 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 DAA18939
	for <sigtran-archive@odin.ietf.org>; Tue, 28 Jan 2003 03:03:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0S8OiY32555
	for sigtran-archive@odin.ietf.org; Tue, 28 Jan 2003 03:24:44 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0S8O0J32517;
	Tue, 28 Jan 2003 03:24:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0S8MGJ32466
	for <sigtran@optimus.ietf.org>; Tue, 28 Jan 2003 03:22:16 -0500
Received: from envoy.ot.com.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA18876
	for <sigtran@ietf.org>; Tue, 28 Jan 2003 03:00:51 -0500 (EST)
Received: (qmail 62 invoked by uid 40); 28 Jan 2003 08:04:18 -0000
Received: from jolan.evans@opentelecommunications.com by envoy by uid 51 with qmail-scanner-1.12 (. Clear:. Processed in 0.24107 secs); 28 Jan 2003 08:04:18 -0000
X-Qmail-Scanner-Mail-From: jolan.evans@opentelecommunications.com via envoy
X-Qmail-Scanner: 1.12 (Clear:. Processed in 0.24107 secs)
Received: from unknown (HELO nobel.in.ot.com.au) (10.70.10.5)
  by envoy.ot.com.au with SMTP; 28 Jan 2003 08:04:17 -0000
Received: (qmail 12583 invoked from network); 28 Jan 2003 08:03:51 -0000
Received: from druid.in.ot.com.au (10.70.80.5)
  by nobel.syd.ot with SMTP; 28 Jan 2003 08:03:51 -0000
Received: (qmail 20879 invoked from network); 28 Jan 2003 08:03:44 -0000
Received: from unknown (HELO Mars) (10.70.12.144)
  by druid.in.ot.com.au with SMTP; 28 Jan 2003 08:03:43 -0000
From: "Jolan Evans" <jolan.evans@opentelecommunications.com>
To: "Sigtran" <sigtran@ietf.org>
Cc: <bidulock@openss7.org>
Subject: RE: [Sigtran] M3UA: ASP to SGP communication
Date: Tue, 28 Jan 2003 19:01:56 +1100
Organization: Open Telecommunications
Message-ID: <005801c2c6a3$8d1e3050$900c460a@Mars>
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, Build 10.0.2627
In-Reply-To: <20021008014725.A10013@openss7.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
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

I would like to raise a few issues regarding your procedures below for
ASP to SGP routing. I know this discussion took places a while ago, but
it has taken me some time to come up to speed with the RFC as I have
been busy on other things until recently.

Please note that I have inserted "M3UA" into the subject line of the
original email.



1. Nomenclature
AsPc: Point code of an AS. In defining routing keys, the RFC uses DPC
for this term as it takes the SG's frame of reference.
RemotePc: Point code of an SS7 MTP entity with which an AS communicates
via an SG, or directly in the case of IPSP-IPSP communication. In
defining routing keys, the RFC uses OPC for this term as it takes the
SG's frame of reference again.



2. Background Assumptions
As per Brian's introduction, we assume that zero or more MTP-User's are
bound to an MTP-SAP. The MTP-SAP exists in a particular MTP-Network,
which has a particular MTP protocol variant. An SG is associated with a
single MTP-Network. A RK is defined as in the RFC, but, for clarity, is
independent of any SG and associated with a single MTP-Network. An
SgRouteSet is uniquely defined by an RK, an SG and an MTP-SAP (the RK
and SG must be both associated with the same MTP-Network) and also
specifies the network appearance for the MTP-Network to be used with the
SG and the RC of each SGP in the SG. Therefore, an SgRouteSet is
implicitly associated with a single MTP-Network. An MTP-SAP is
associated with zero or more SgRouteSet's and therefore an MTP-SAP is
associated with zero or more RKs. In contrast, it appears that Brian
assumes that an MTP-SAP can only be associated with one RK. Given this
extension, we have the following requirement.



3. Routing Keys Requirements to Support Unique SS7 Destination Status
Let RemotePcSet(Rk) be the set of RemotePc's reachable via the SG from
the ASP where the RK is defined.
Consider any two SgRouteSet's SgRsA and SgRsA which are associated with
the same MTP-SAP.
Let the routing key of SgRsA and SgRsB be RkA and RkB respectively.
If the intersection of RemotePcSet(RkA) and RemotePcSet(RkB) is non-nil
then the routing keys MUST be identical in every respect apart from
their RemotePcSet.
If this wasn't the case, an ASP could never indicate an MTP-RESUME to an
MTP-USER because an MTP-RESUME can only specify a RemotePc and no other
SS7 element. I assume here for simplicity that every MTP-User of a
MTP-SAP must be given the same MTP status (i.e. different MTP-Users of
the same MTP-SAP cannot be given different MTP-Status indications
depending on what traffic they have requested).

Here's a concrete example of why this is so. Consider an ASP with the
following routing keys:
RkA: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={A}
RkB: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={B}
RkC: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={M}
RkD: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={N}

Assume that RkA and RkB were both active in SgpA and SgpB respectively
and are associated with the same MTP-SAP, but different SGs. Also assume
that a DAVA has been received for RemotePc=X from SgpA after a DUNA from
SgpB for the same RemotePc. We might consider generating an MTP-Resume
to all the MTP-Users of the MTP-SAP for RemotePc X. However, if an
MTP-User requests an MTP-Transfer with an AsPc of B then SgpB may not be
able to transfer it as indicated by the DUNA it sent the ASP.

The same explanation applies to RkC and RkD.

In practice this requirement probably won't cause too many headaches
because it is likely that there would be two different MTP-Users, one
using only RkA/RkC and the other using only RkB/RkD. In this case, we
can simply create two MTP-SAPs in the same MTP-Network and associate
each routing key with a different MTP-SAP. Of course, this would require
the M3UA implementation to support more than one MTP-SAP per
MTP-Network, which would be extra work obviously.



4. ASP-SGP Routing should use SS7 Destination Availability/Restricted
Status on a per-SGP rather than a per-SG basis.

I believe your ASP-SGP procedures should be amended (I only amend the
multiple SG case as the single SG case is a special case of the former)
as follows:

Change:
"This routing information is updated by collecting DUNA/DAVA/DRST
messages received from (any of the SGP in) the SG."
To:
"This routing information is updated by collecting DUNA/DAVA/DRST
information on a per-(SGP,destination) basis. An SG is considered to be
available and unrestricted for a particular destination if any SGP in it
is available and unrestricted for that destination. Otherwise if this is
not he case, then an SG is considered to be restricted for a particular
destination if there is at least one SGP in the SG restricted for that
destination. Otherwise if this is not the case, the SG is considered to
be prohibited for that destination."

The RFC is not particular clear on this point. In section 1.4.1 para 3
it states that "MTP3 routeset, SPMC and remote AS/ASP states of each SGP
SHOULD be coordinated across all the SGPs". However, this uses "SHOULD"
which implies it is only recommended and it also doesn't specifically
state that SS7 destination availability, restriction and congestion
status ("SS7 destination status" for short) should be coordinated across
all SGPs. I don't think that "MTP3 routeset" necessarily implies SS7
destination status. Also, in section 1.3.2.5 1.4.2.5 it suggests in
should be on a per-SGP basis. Section 4.5.2.2 uses the word "SG" but
also uses the term "affected route(s)". Section 1.3.2.5 and section
1.4.2.5 suggest the word "route" refers to an SGP and not an SG. Hence,
given the ambiguity of section 4.5.2.2 I think that route can be
considered to refer to an SGP.

A configuration where per-SGP SS7 destination status is necessary is as
follows. Consider an SEP SG which has two SGP's acting as a redundant
pair. Each SGP has it's own link set to a particular STP. While in
section 1.4.1 para 3 it states that "Rerouting of traffic between the
SGPs MAY also be supported", it uses "MAY" and hence this is optional.
If one link set fails but not the other, one SGP will be able to reach
the SS7 network but not the other if rerouting between SGPs is not
supported or the rerouting link has also failed. Hence, it would be
possible for one SGP to send a DUNA for a particular destination but not
the other.


Your feedback would be appreciated.

Jolan.


--
Jolan Evans
Open Telecommunications
jolan.evans@opentelecommunications.com


-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org] On Behalf
Of Brian F. G. Bidulock
Sent: Tuesday, 8 October 2002 17:47
To: Srikanth Yandapalli
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] ASP to SGP communication

Srikanth,

Srikanth Yandapalli wrote:               (Tue, 08 Oct 2002 12:03:52)
> 
>    I am late entrant to this group.I am quite sure all this should
have
>    been discussed and I am sorry about this.

Welcome.

> 
>    In the context of a single ASP in communication with multiple SGPs,
>    how should the routing of a MTP_DATA_REQ take place at the ASP?

I assume you are talking about M3UA?  As we are dealing with 5 or more
UAs
now, in the future it would be helpful to add M3UA (or whichever) to the
subject line.

> 
>    approach 1:
> 
>    We may find out the  RK and find out the SGP list that the RK is
>    active on and choose one SGP for sending the message based
>    on congestion level and also whether we have received any DRST
>    message from any of the SGPs.

This approach is applicable to multiple SGs, but not to multiple SGPs
within a
single SG.

>    approach 2:
> 
>    An SGP can also be viewed as providing route to a set of DPCs
>    and the routing can be based on the DPC for the message alone.
>    This approach is reduces the complexity but adds a situation
>    where the RK may not be active on that association. And also is
>    is mandatory to send RC on this association and if so what could
>    the SGP make out of the RC?

RC should be coordinated and the same across multiple SGPs within an SG.

> 
>    Is there a preferred approach to this issue?
> 

Typically, the logic can be something like this: (but there are several
other
schools of thought):

Single SG case: (multiple SGs is more complicated)

  MTP-TRANSFER request is issued by an MTP-User.  The MTP-User is bound
to an
  MTP-SAP.  The MTP-SAP is associated with an AS/RC/RK.  There is a pool
of
  SGPs on an SG for which the AS/RC/RK is active.  The AS may have
received
  MTP-PAUSE/RESUME/STATUS indications from the SG and may choose to
honor that
  information or not.  If the ASP chooses not to honor this information
it can
  blindly send messages to the SGP and rely upon a DUNA/SCON response
from the
  SGP later.

  Selection of an SGP within an SG is based on the traffic mode for the
SGP.
  This traffic mode is not managed by M3UA, however, M3UA provides for
  distribution of traffic over SGP based on any of the methods described
for
  ASPs (active/standby, load-share, broadcast).  A typical method is
  load-share based on SLS.  In this scheme, using the SLS in the
MTP-TRANSFER
  request, the ASP selects load-shares traffic over the available SGP.

Multiple SG case:

  In the more complicated multiple SG case, the ASP must first select an
SG
  before it selects an SGP within the SG.  The ASP must maintain some
  additional routing information to be able to properly select an SG.
This
  routing information is updated by collecting DUNA/DAVA/DRST messages
  received from (any of the SGP in) the SG.  To select the outgoing SG,
the
  ASP must examine the destination of the MTP-TRANSFER request.

  (If the SG has no SGP active for the AS/RC/RK, all destinations can be
  considered prohibited).

  If the destination is available and unrestricted for several SGs, the
ASP
  should select an SG on a load-sharing basis (based on SLS) and then
select
  an active SGP within the SG on the basis of the traffic mode for the
SG.

  If some SG are restricted for the specified destination (based on
received
  DRST messages from the SG), the ASP should load-share across the
available
  unrestricted SGs.  If all SGs are restricted for a given destination,
the
  ASP should load-share across the available SGs and ignore the
restricted
  status.
  
  If some SG are prohibited for the specified destination (based on
received
  DUNA messages from the SG), the ASP should load-share across the
available
  non-prohibited SGs.  If all SGs are prohibited for a given destination
(or
  no SGP is active for the AS/RC/RK in any SG), the ASP should respond
to the
  MTP-User with an MTP-PAUSE in accordance with the style of the
MTP-User
  interface (ITU-T and ANSI differ here).

Properly selecting SGs requires that the ASP maintain the DUNA/DAVA/DRST
information for each destination received from any SGP in an SG, on a
per-SG
basis.  This is the same as MTP Level 3 ROUTE status.  However, SCON
information should only be maintained on a per-destination basis (and
not
per-SG).  This is the same as MTP Level 3 ROUTESET status.

Note that, in general, it is a bad idea to consider congestion (SCON)
when
selecting an SG.  SCON does not necessarily indicate congestion at an SG
or on
a path to an SG, but indicates congestion at the affected destination or
somewhere (perhaps distant) in the SS7 network.  SCON is
ROUTESET-specific
(applies to the destination), whereas DUNA/DAVA/DRST is ROUTE-specific
(applies to the destination and path).  SCON should only be used to
determine
whether a message should be dropped completely and an MTP-STATUS
returned to
the MTP-User according to the style of the MTP-User interface (ITU-T and
ANSI
differ here again).

So, to summarize:  on behalf of the AS/RC/RK/MTP-User, the ASP
determines
whether to send a message based on SCON received for the specified
destination, then selects an SG based on DUNA/DAVA/DRST received for the
specified destination and load-shares based on SLS across the eligible
SGs.
Once an SG is selected, an active SGP (active for the AS/RC/RK) is
selected
within the SG based on the traffic mode of the SG (active/standby,
load-share,
broadcast: but typically load-share on SLS).

As I said, there are other schools of thought, but that is my
understanding.

--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 mailnull@www1.ietf.org  Tue Jan 28 03:51: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 DAA19339
	for <sigtran-archive@odin.ietf.org>; Tue, 28 Jan 2003 03:51:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0S9CSR03237
	for sigtran-archive@odin.ietf.org; Tue, 28 Jan 2003 04:12:28 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0S9BhJ03205;
	Tue, 28 Jan 2003 04:11:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0S9AsJ03173
	for <sigtran@optimus.ietf.org>; Tue, 28 Jan 2003 04:10:54 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19319
	for <sigtran@ietf.org>; Tue, 28 Jan 2003 03:49:30 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:CVyfPGQ0DfawqqnTpUSHvRMlwjou8TVg@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0S8qwD17045;
	Tue, 28 Jan 2003 01:52:58 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0S8qwK05993;
	Tue, 28 Jan 2003 01:52:58 -0700
Date: Tue, 28 Jan 2003 01:52:58 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Jolan Evans <jolan.evans@opentelecommunications.com>
Cc: Sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
Message-ID: <20030128015258.A5712@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Jolan Evans <jolan.evans@opentelecommunications.com>,
	Sigtran <sigtran@ietf.org>
References: <20021008014725.A10013@openss7.org> <005801c2c6a3$8d1e3050$900c460a@Mars>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <005801c2c6a3$8d1e3050$900c460a@Mars>; from jolan.evans@opentelecommunications.com on Tue, Jan 28, 2003 at 07:01:56PM +1100
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>

Jolan,

You are a litte of track: please see comments below...

Jolan Evans wrote:                                                                   (Tue, 28 Jan 2003 19:01:56)
> I would like to raise a few issues regarding your procedures below for
> ASP to SGP routing. I know this discussion took places a while ago, but
> it has taken me some time to come up to speed with the RFC as I have
> been busy on other things until recently.
> 
> Please note that I have inserted "M3UA" into the subject line of the
> original email.
> 
> 
> 
> 1. Nomenclature
> AsPc: Point code of an AS. In defining routing keys, the RFC uses DPC
> for this term as it takes the SG's frame of reference.
> RemotePc: Point code of an SS7 MTP entity with which an AS communicates
> via an SG, or directly in the case of IPSP-IPSP communication. In
> defining routing keys, the RFC uses OPC for this term as it takes the
> SG's frame of reference again.
> 
> 
> 
> 2. Background Assumptions
> As per Brian's introduction, we assume that zero or more MTP-User's are
> bound to an MTP-SAP. The MTP-SAP exists in a particular MTP-Network,
> which has a particular MTP protocol variant. An SG is associated with a
> single MTP-Network. A RK is defined as in the RFC, but, for clarity, is
> independent of any SG and associated with a single MTP-Network. An
> SgRouteSet is uniquely defined by an RK, an SG and an MTP-SAP (the RK
> and SG must be both associated with the same MTP-Network) and also
> specifies the network appearance for the MTP-Network to be used with the
> SG and the RC of each SGP in the SG. Therefore, an SgRouteSet is
> implicitly associated with a single MTP-Network. An MTP-SAP is
> associated with zero or more SgRouteSet's and therefore an MTP-SAP is
> associated with zero or more RKs.

Bad assumption.  An MTP-SAP is assocated with one RK.  This is the
1:1:1 rule between AS:RK:RC.

> In contrast, it appears that Brian
> assumes that an MTP-SAP can only be associated with one RK. Given this
> extension, we have the following requirement.
> 
> 
> 
> 3. Routing Keys Requirements to Support Unique SS7 Destination Status
> Let RemotePcSet(Rk) be the set of RemotePc's reachable via the SG from
> the ASP where the RK is defined.

RKs do not have to be defined at ASPs, just MTP-SAPs.

> Consider any two SgRouteSet's SgRsA and SgRsA which are associated with
> the same MTP-SAP.

I think you mean SgRsA and SgRsB <---.

> Let the routing key of SgRsA and SgRsB be RkA and RkB respectively.
> If the intersection of RemotePcSet(RkA) and RemotePcSet(RkB) is non-nil
> then the routing keys MUST be identical in every respect apart from
> their RemotePcSet.

RkA and RkB must be identical or they cannot be associated with the
same MTP-SAP.  See 1:1:1 rule above.

> If this wasn't the case, an ASP could never indicate an MTP-RESUME to an
> MTP-USER because an MTP-RESUME can only specify a RemotePc and no other
> SS7 element. I assume here for simplicity that every MTP-User of a
> MTP-SAP must be given the same MTP status (i.e. different MTP-Users of
> the same MTP-SAP cannot be given different MTP-Status indications
> depending on what traffic they have requested).

The AS can deliver whatever MTP-STATUS indications it cares to.  If
there are SI values represented by the MTP-SAP, it is normally the
MTP-User's responsibility to sort out the MTP-STATUS indications.

> 
> Here's a concrete example of why this is so. Consider an ASP with the
> following routing keys:
> RkA: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={A}
> RkB: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={B}
> RkC: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={M}
> RkD: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={N}
> 
> Assume that RkA and RkB were both active in SgpA and SgpB respectively
> and are associated with the same MTP-SAP, but different SGs.

To be associated with the same MTP-SAP, RkA and RkB must be identical,
which implies that AsPcSetA and AsPcSetB are also identical.

> Also assume that a DAVA has been received for RemotePc=X from SgpA after a
> DUNA from SgpB for the same RemotePc. We might consider generating an
> MTP-Resume to all the MTP-Users of the MTP-SAP for RemotePc X. However, if
> an MTP-User requests an MTP-Transfer with an AsPc of B then SgpB may not be
> able to transfer it as indicated by the DUNA it sent the ASP.

This is not a problem because AsPc A must be identical to AsPc B.  Also,
you do not seem to realize that DAVA and DUNA are specific to the SG.
A DUNA received from one SG does not indicate that the affected destination
is also unavailable via the other SG.  It takes a DUNA from both SGs
to indicate that the affected destination is inaccessible.

> 
> The same explanation applies to RkC and RkD.

For RkC and RkD to be associated with the same MTP-SAP requires that
they are identical according to the 1:1:1 rule above.

> 
> In practice this requirement probably won't cause too many headaches
> because it is likely that there would be two different MTP-Users, one
> using only RkA/RkC and the other using only RkB/RkD.

In fact there must be two different MTP-SAPs (and necessarily different
MTP-Users from the perspective of the SG) for RkA/RkC to tbe different
from RkB/RkD.

> In this case, we can simply create two MTP-SAPs in the same MTP-Network and
> associate each routing key with a different MTP-SAP. Of course, this would
> require the M3UA implementation to support more than one MTP-SAP per
> MTP-Network, which would be extra work obviously.

It is not extra work.  M3UA not only supports this but requires it.
An MTP-SAP is an AS.  Having multiple AS (whether in a single network
or not) is fundamental to the SIGTRAN model.

> 
> 4. ASP-SGP Routing should use SS7 Destination Availability/Restricted
> Status on a per-SGP rather than a per-SG basis.

Wrong.  ASPSM/ASPTM is per-SGP.  SSNM is per-SG.

> 
> I believe your ASP-SGP procedures should be amended (I only amend the
> multiple SG case as the single SG case is a special case of the former)
> as follows:
> 
> Change:
> "This routing information is updated by collecting DUNA/DAVA/DRST
> messages received from (any of the SGP in) the SG."
> To:
> "This routing information is updated by collecting DUNA/DAVA/DRST
> information on a per-(SGP,destination) basis. An SG is considered to be
> available and unrestricted for a particular destination if any SGP in it
> is available and unrestricted for that destination. Otherwise if this is
> not he case, then an SG is considered to be restricted for a particular
> destination if there is at least one SGP in the SG restricted for that
> destination. Otherwise if this is not the case, the SG is considered to
> be prohibited for that destination."
> 
> The RFC is not particular clear on this point. In section 1.4.1 para 3
> it states that "MTP3 routeset, SPMC and remote AS/ASP states of each SGP
> SHOULD be coordinated across all the SGPs". However, this uses "SHOULD"
> which implies it is only recommended and it also doesn't specifically
> state that SS7 destination availability, restriction and congestion
> status ("SS7 destination status" for short) should be coordinated across
> all SGPs. I don't think that "MTP3 routeset" necessarily implies SS7
> destination status. Also, in section 1.3.2.5 1.4.2.5 it suggests in
> should be on a per-SGP basis. Section 4.5.2.2 uses the word "SG" but
> also uses the term "affected route(s)". Section 1.3.2.5 and section
> 1.4.2.5 suggest the word "route" refers to an SGP and not an SG. Hence,
> given the ambiguity of section 4.5.2.2 I think that route can be
> considered to refer to an SGP.

Each SGP in an SG offers identical connectivity to the SS7 network.
This means that a destination which is inaccessible to one SGP is
inaccessible to all, congested, restricted, accessible, etc.

> 
> A configuration where per-SGP SS7 destination status is necessary is as
> follows. Consider an SEP SG which has two SGP's acting as a redundant
> pair. Each SGP has it's own link set to a particular STP. While in
> section 1.4.1 para 3 it states that "Rerouting of traffic between the
> SGPs MAY also be supported", it uses "MAY" and hence this is optional.
> If one link set fails but not the other, one SGP will be able to reach
> the SS7 network but not the other if rerouting between SGPs is not
> supported or the rerouting link has also failed. Hence, it would be
> possible for one SGP to send a DUNA for a particular destination but not
> the other.

This is addressed.  The SGP has suffered a complete failure (it is unable
to process traffic) and can simply drop its associations to the ASPs.
DUNA is incorrect here: the destination is still accessible from the SG.
One SGP has simply broken it's contract (providing identical connectivity
to the SS7 network as other SGP in the SG) and must be placed out of 
service.

--brian

> 
> 
> Your feedback would be appreciated.
> 
> Jolan.
> 
> 
> --
> Jolan Evans
> Open Telecommunications
> jolan.evans@opentelecommunications.com
> 
> 
> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org] On Behalf
> Of Brian F. G. Bidulock
> Sent: Tuesday, 8 October 2002 17:47
> To: Srikanth Yandapalli
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] ASP to SGP communication
> 
> Srikanth,
> 
> Srikanth Yandapalli wrote:               (Tue, 08 Oct 2002 12:03:52)
> > 
> >    I am late entrant to this group.I am quite sure all this should
> have
> >    been discussed and I am sorry about this.
> 
> Welcome.
> 
> > 
> >    In the context of a single ASP in communication with multiple SGPs,
> >    how should the routing of a MTP_DATA_REQ take place at the ASP?
> 
> I assume you are talking about M3UA?  As we are dealing with 5 or more
> UAs
> now, in the future it would be helpful to add M3UA (or whichever) to the
> subject line.
> 
> > 
> >    approach 1:
> > 
> >    We may find out the  RK and find out the SGP list that the RK is
> >    active on and choose one SGP for sending the message based
> >    on congestion level and also whether we have received any DRST
> >    message from any of the SGPs.
> 
> This approach is applicable to multiple SGs, but not to multiple SGPs
> within a
> single SG.
> 
> >    approach 2:
> > 
> >    An SGP can also be viewed as providing route to a set of DPCs
> >    and the routing can be based on the DPC for the message alone.
> >    This approach is reduces the complexity but adds a situation
> >    where the RK may not be active on that association. And also is
> >    is mandatory to send RC on this association and if so what could
> >    the SGP make out of the RC?
> 
> RC should be coordinated and the same across multiple SGPs within an SG.
> 
> > 
> >    Is there a preferred approach to this issue?
> > 
> 
> Typically, the logic can be something like this: (but there are several
> other
> schools of thought):
> 
> Single SG case: (multiple SGs is more complicated)
> 
>   MTP-TRANSFER request is issued by an MTP-User.  The MTP-User is bound
> to an
>   MTP-SAP.  The MTP-SAP is associated with an AS/RC/RK.  There is a pool
> of
>   SGPs on an SG for which the AS/RC/RK is active.  The AS may have
> received
>   MTP-PAUSE/RESUME/STATUS indications from the SG and may choose to
> honor that
>   information or not.  If the ASP chooses not to honor this information
> it can
>   blindly send messages to the SGP and rely upon a DUNA/SCON response
> from the
>   SGP later.
> 
>   Selection of an SGP within an SG is based on the traffic mode for the
> SGP.
>   This traffic mode is not managed by M3UA, however, M3UA provides for
>   distribution of traffic over SGP based on any of the methods described
> for
>   ASPs (active/standby, load-share, broadcast).  A typical method is
>   load-share based on SLS.  In this scheme, using the SLS in the
> MTP-TRANSFER
>   request, the ASP selects load-shares traffic over the available SGP.
> 
> Multiple SG case:
> 
>   In the more complicated multiple SG case, the ASP must first select an
> SG
>   before it selects an SGP within the SG.  The ASP must maintain some
>   additional routing information to be able to properly select an SG.
> This
>   routing information is updated by collecting DUNA/DAVA/DRST messages
>   received from (any of the SGP in) the SG.  To select the outgoing SG,
> the
>   ASP must examine the destination of the MTP-TRANSFER request.
> 
>   (If the SG has no SGP active for the AS/RC/RK, all destinations can be
>   considered prohibited).
> 
>   If the destination is available and unrestricted for several SGs, the
> ASP
>   should select an SG on a load-sharing basis (based on SLS) and then
> select
>   an active SGP within the SG on the basis of the traffic mode for the
> SG.
> 
>   If some SG are restricted for the specified destination (based on
> received
>   DRST messages from the SG), the ASP should load-share across the
> available
>   unrestricted SGs.  If all SGs are restricted for a given destination,
> the
>   ASP should load-share across the available SGs and ignore the
> restricted
>   status.
>   
>   If some SG are prohibited for the specified destination (based on
> received
>   DUNA messages from the SG), the ASP should load-share across the
> available
>   non-prohibited SGs.  If all SGs are prohibited for a given destination
> (or
>   no SGP is active for the AS/RC/RK in any SG), the ASP should respond
> to the
>   MTP-User with an MTP-PAUSE in accordance with the style of the
> MTP-User
>   interface (ITU-T and ANSI differ here).
> 
> Properly selecting SGs requires that the ASP maintain the DUNA/DAVA/DRST
> information for each destination received from any SGP in an SG, on a
> per-SG
> basis.  This is the same as MTP Level 3 ROUTE status.  However, SCON
> information should only be maintained on a per-destination basis (and
> not
> per-SG).  This is the same as MTP Level 3 ROUTESET status.
> 
> Note that, in general, it is a bad idea to consider congestion (SCON)
> when
> selecting an SG.  SCON does not necessarily indicate congestion at an SG
> or on
> a path to an SG, but indicates congestion at the affected destination or
> somewhere (perhaps distant) in the SS7 network.  SCON is
> ROUTESET-specific
> (applies to the destination), whereas DUNA/DAVA/DRST is ROUTE-specific
> (applies to the destination and path).  SCON should only be used to
> determine
> whether a message should be dropped completely and an MTP-STATUS
> returned to
> the MTP-User according to the style of the MTP-User interface (ITU-T and
> ANSI
> differ here again).
> 
> So, to summarize:  on behalf of the AS/RC/RK/MTP-User, the ASP
> determines
> whether to send a message based on SCON received for the specified
> destination, then selects an SG based on DUNA/DAVA/DRST received for the
> specified destination and load-shares based on SLS across the eligible
> SGs.
> Once an SG is selected, an active SGP (active for the AS/RC/RK) is
> selected
> within the SG based on the traffic mode of the SG (active/standby,
> load-share,
> broadcast: but typically load-share on SLS).
> 
> As I said, there are other schools of thought, but that is my
> understanding.
> 
> --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 mailnull@www1.ietf.org  Tue Jan 28 03:52: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 DAA19359
	for <sigtran-archive@odin.ietf.org>; Tue, 28 Jan 2003 03:52:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0S9DKp03310
	for sigtran-archive@odin.ietf.org; Tue, 28 Jan 2003 04:13:20 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0S9D9J03300;
	Tue, 28 Jan 2003 04:13:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0S9CYJ03268
	for <sigtran@optimus.ietf.org>; Tue, 28 Jan 2003 04:12:34 -0500
Received: from cbibipnt05.hc.bt.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19334
	for <sigtran@ietf.org>; Tue, 28 Jan 2003 03:51:12 -0500 (EST)
From: karen.d.king@bt.com
Received: by cbibipnt05.hc.bt.com with Internet Mail Service (5.5.2654.89)
	id <DY0WPQL0>; Tue, 28 Jan 2003 08:53:53 -0000
Message-ID: <B1F38D7B53615140BCEA6677DF9F2F8C5B1A2A@i2km11-ukbr.domain1.systemhost.net>
To: bidulock@openss7.org
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M2PA Draft 7 comment
Date: Tue, 28 Jan 2003 08:53:34 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.89)
content-class: urn:content-classes:message
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,

I feel that my first comment is a minor editorial change that clarifies the
behaviour needed.

As for the last point, yes, you'd hope this was obvious, but for those with
less experience of SS7 functionality, it's an important clarification of
behaviour that can easily be overlooked. I feel the addition of a note on
this would make clear the intended use of processor outage, without
detracting from the 'correct' specification of the behaviour.

Regards,

Karen

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: 24 January 2003 21:28
To: King,KD,Karen,DEN8 KINGKD R
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA Draft 7 comment


karen.d.king,

karen.d.king@bt.com wrote:
(Fri, 24 Jan 2003 14:10:33)
> Hi,
> 
> I still have the comments, from draft 5, on the use of processor outage
> (section 4.1.4).
> 
> When processor outage ceases, the buffers need to be flushed. Therefore
> please can you move the paragraph "MTP3 may send Flush Buffers or
> Continue......."  to after the paragraph starting, "When processor outage
> ceases....".
> 
> Please could you also add a statement that processor outage should not be
> used to cover the situations when MTP3 or user parts are encountering
> congestion, or where the user part is unavailable.

Doesn't this last point go without saying?

--brian

> 
> Regards,
> 
> Karen
> 
> Karen King
> BTexact Technologies
> Orion Building MLB1/PP9
> Adastral Park
> Martlesham Heath
> IPSWICH
> Suffolk   IP5 3RE
> 
> Tel: (01473) 605389
> karen.d.king@bt.com
> 
> BTexact Technologies is a trademark of British Telecommunications plc
> Registered office: 81 Newgate Street London EC1A 7AJ
> Registered in England no. 1800000
> 
> This electronic message contains information from British
Telecommunications
> plc which may be privileged or confidential. The information is intended
to
> be for the use of the individual(s) or entity named above. If you are not
> the intended recipient be aware that any disclosure, copying, distribution
> or use of the contents of this information is prohibited. If you have
> received this electronic message in error, please notify us by telephone
or
> email (to the numbers or address above) immediately.
> Activity and use of British Telecommunications plc E-mail system is
> monitored to secure its effective operation and for other lawful business
> purposes. Communications using this system will also be monitored and may
be
> recorded to secure effective operation and for other lawful business
> purposes.
> 
> _______________________________________________
> 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 Jan 28 04:02: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 EAA19535
	for <sigtran-archive@odin.ietf.org>; Tue, 28 Jan 2003 04:02:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0S9NaZ03766
	for sigtran-archive@odin.ietf.org; Tue, 28 Jan 2003 04:23:36 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0S9NCJ03726;
	Tue, 28 Jan 2003 04:23:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0S9KeJ03601
	for <sigtran@optimus.ietf.org>; Tue, 28 Jan 2003 04:20:40 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19449
	for <sigtran@ietf.org>; Tue, 28 Jan 2003 03:59:18 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:CaMKmeJBn34cgZlZtopDvbCHb7AGw3PC@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0S92lD17264;
	Tue, 28 Jan 2003 02:02:47 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0S92lJ06236;
	Tue, 28 Jan 2003 02:02:47 -0700
Date: Tue, 28 Jan 2003 02:02:47 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: karen.d.king@bt.com
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA Draft 7 comment
Message-ID: <20030128020247.A6085@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: karen.d.king@bt.com, sigtran@ietf.org
References: <B1F38D7B53615140BCEA6677DF9F2F8C5B1A2A@i2km11-ukbr.domain1.systemhost.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <B1F38D7B53615140BCEA6677DF9F2F8C5B1A2A@i2km11-ukbr.domain1.systemhost.net>; from karen.d.king@bt.com on Tue, Jan 28, 2003 at 08:53:34AM -0000
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>

karen.d.king,

karen.d.king@bt.com wrote:                                                    (Tue, 28 Jan 2003 08:53:34)
> Brian,
> 
> I feel that my first comment is a minor editorial change that clarifies the
> behaviour needed.

I don't have a problem with the first comment.

> 
> As for the last point, yes, you'd hope this was obvious, but for those with
> less experience of SS7 functionality, it's an important clarification of
> behaviour that can easily be overlooked. I feel the addition of a note on
> this would make clear the intended use of processor outage, without
> detracting from the 'correct' specification of the behaviour.

How would anyone think to use a Level 2 procedure to perform a Level 3
function is beyond me.  If the reader is both that bold and ignorant
there will be no stopping them.  There are some 20 or so other Level 3
procedures for which processor outage cannot be used: are we to list
all of those too?

--brian

> 
> Regards,
> 
> Karen
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: 24 January 2003 21:28
> To: King,KD,Karen,DEN8 KINGKD R
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] M2PA Draft 7 comment
> 
> 
> karen.d.king,
> 
> karen.d.king@bt.com wrote:
> (Fri, 24 Jan 2003 14:10:33)
> > Hi,
> > 
> > I still have the comments, from draft 5, on the use of processor outage
> > (section 4.1.4).
> > 
> > When processor outage ceases, the buffers need to be flushed. Therefore
> > please can you move the paragraph "MTP3 may send Flush Buffers or
> > Continue......."  to after the paragraph starting, "When processor outage
> > ceases....".
> > 
> > Please could you also add a statement that processor outage should not be
> > used to cover the situations when MTP3 or user parts are encountering
> > congestion, or where the user part is unavailable.
> 
> Doesn't this last point go without saying?
> 
> --brian
> 
> > 
> > Regards,
> > 
> > Karen
> > 
> > Karen King
> > BTexact Technologies
> > Orion Building MLB1/PP9
> > Adastral Park
> > Martlesham Heath
> > IPSWICH
> > Suffolk   IP5 3RE
> > 
> > Tel: (01473) 605389
> > karen.d.king@bt.com
> > 
> > BTexact Technologies is a trademark of British Telecommunications plc
> > Registered office: 81 Newgate Street London EC1A 7AJ
> > Registered in England no. 1800000
> > 
> > This electronic message contains information from British
> Telecommunications
> > plc which may be privileged or confidential. The information is intended
> to
> > be for the use of the individual(s) or entity named above. If you are not
> > the intended recipient be aware that any disclosure, copying, distribution
> > or use of the contents of this information is prohibited. If you have
> > received this electronic message in error, please notify us by telephone
> or
> > email (to the numbers or address above) immediately.
> > Activity and use of British Telecommunications plc E-mail system is
> > monitored to secure its effective operation and for other lawful business
> > purposes. Communications using this system will also be monitored and may
> be
> > recorded to secure effective operation and for other lawful business
> > purposes.
> > 
> > _______________________________________________
> > 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 mailnull@www1.ietf.org  Tue Jan 28 04:48: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 EAA19959
	for <sigtran-archive@odin.ietf.org>; Tue, 28 Jan 2003 04:48:13 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0SA95t06577
	for sigtran-archive@odin.ietf.org; Tue, 28 Jan 2003 05:09:05 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0SA8ZJ06547;
	Tue, 28 Jan 2003 05:08:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0SA7cJ06514
	for <sigtran@optimus.ietf.org>; Tue, 28 Jan 2003 05:07:38 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19922
	for <sigtran@ietf.org>; Tue, 28 Jan 2003 04:46:14 -0500 (EST)
X-Priority: 3 (Normal)
Importance: Normal
To: sigtran@ietf.org
Message-ID: <OF17E746B2.9F2178CF-ONC2256CBC.0035AD63@LocalDomain>
From: "TOLGA ASVEREN" <tolga.asveren@o2.com.tr>
Date: Tue, 28 Jan 2003 11:46:18 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/28/2003
 11:46:22 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Sigtran] M3UA SG-SG (again)
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 everybody,

Recently I submitted 02 for SG-SG.
http://www.ietf.org/internet-drafts/draft-bidas-sigtran-sgsg-02.txt

It was updated based on some off-list comments and additional sections are
added to clarify some procedures, nothing conceptually new though. Still
some more sections can be added but first I prefer to get some feedback.

I still think that it should be a WG item, as it addresses some existing
problems. I would appreciate any feedback.

     Regards,
      TolgaHi everybody,

Recently I submitted 02 for SG-SG.
http://www.ietf.org/internet-drafts/draft-bidas-sigtran-sgsg-02.txt

It was updated based on some off-list comments and additional sections are
added to clarify some procedures, nothing conceptually new though. Still
some more sections can be added but first I prefer to get some feedback.

I still think that it should be a WG item, as it addresses some existing
problems. I would appreciate any feedback.

     Regards,
      Tolga

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



From mailnull@www1.ietf.org  Tue Jan 28 06:05:19 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 GAA20851
	for <sigtran-archive@odin.ietf.org>; Tue, 28 Jan 2003 06:05:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0SBQDo10509
	for sigtran-archive@odin.ietf.org; Tue, 28 Jan 2003 06:26:13 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0SBPmJ10480;
	Tue, 28 Jan 2003 06:25:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0SBOLJ10396
	for <sigtran@optimus.ietf.org>; Tue, 28 Jan 2003 06:24:21 -0500
Received: from cbibipnt05.hc.bt.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20825
	for <sigtran@ietf.org>; Tue, 28 Jan 2003 06:02:55 -0500 (EST)
From: karen.d.king@bt.com
Received: by cbibipnt05.hc.bt.com with Internet Mail Service (5.5.2654.89)
	id <D5MLKA46>; Tue, 28 Jan 2003 11:06:40 -0000
Message-ID: <B1F38D7B53615140BCEA6677DF9F2F8C579C1E@i2km11-ukbr.domain1.systemhost.net>
To: bidulock@openss7.org
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M2PA Draft 7 comment
Date: Tue, 28 Jan 2003 11:06:16 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.89)
content-class: urn:content-classes:message
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,

Good you're happy with the first comment.

OK - I understand your point that no one should think this behaviour would
be appropriate and, at the end of the day, we can't spec out everything a
poor/incorrect implementation 'might' do. I do seem to remember some emails
a while ago that mentioned processor outage and congestion in the same
sentence. I therefore get concerned that some do not understand its correct
use.

Regards,

Karen



-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: 28 January 2003 09:03
To: King,KD,Karen,DEN8 KINGKD R
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA Draft 7 comment


karen.d.king,

karen.d.king@bt.com wrote:
(Tue, 28 Jan 2003 08:53:34)
> Brian,
> 
> I feel that my first comment is a minor editorial change that clarifies
the
> behaviour needed.

I don't have a problem with the first comment.

> 
> As for the last point, yes, you'd hope this was obvious, but for those
with
> less experience of SS7 functionality, it's an important clarification of
> behaviour that can easily be overlooked. I feel the addition of a note on
> this would make clear the intended use of processor outage, without
> detracting from the 'correct' specification of the behaviour.

How would anyone think to use a Level 2 procedure to perform a Level 3
function is beyond me.  If the reader is both that bold and ignorant
there will be no stopping them.  There are some 20 or so other Level 3
procedures for which processor outage cannot be used: are we to list
all of those too?

--brian

> 
> Regards,
> 
> Karen
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: 24 January 2003 21:28
> To: King,KD,Karen,DEN8 KINGKD R
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] M2PA Draft 7 comment
> 
> 
> karen.d.king,
> 
> karen.d.king@bt.com wrote:
> (Fri, 24 Jan 2003 14:10:33)
> > Hi,
> > 
> > I still have the comments, from draft 5, on the use of processor outage
> > (section 4.1.4).
> > 
> > When processor outage ceases, the buffers need to be flushed. Therefore
> > please can you move the paragraph "MTP3 may send Flush Buffers or
> > Continue......."  to after the paragraph starting, "When processor
outage
> > ceases....".
> > 
> > Please could you also add a statement that processor outage should not
be
> > used to cover the situations when MTP3 or user parts are encountering
> > congestion, or where the user part is unavailable.
> 
> Doesn't this last point go without saying?
> 
> --brian
> 
> > 
> > Regards,
> > 
> > Karen
> > 
> > Karen King
> > BTexact Technologies
> > Orion Building MLB1/PP9
> > Adastral Park
> > Martlesham Heath
> > IPSWICH
> > Suffolk   IP5 3RE
> > 
> > Tel: (01473) 605389
> > karen.d.king@bt.com
> > 
> > BTexact Technologies is a trademark of British Telecommunications plc
> > Registered office: 81 Newgate Street London EC1A 7AJ
> > Registered in England no. 1800000
> > 
> > This electronic message contains information from British
> Telecommunications
> > plc which may be privileged or confidential. The information is intended
> to
> > be for the use of the individual(s) or entity named above. If you are
not
> > the intended recipient be aware that any disclosure, copying,
distribution
> > or use of the contents of this information is prohibited. If you have
> > received this electronic message in error, please notify us by telephone
> or
> > email (to the numbers or address above) immediately.
> > Activity and use of British Telecommunications plc E-mail system is
> > monitored to secure its effective operation and for other lawful
business
> > purposes. Communications using this system will also be monitored and
may
> be
> > recorded to secure effective operation and for other lawful business
> > purposes.
> > 
> > _______________________________________________
> > 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 mailnull@www1.ietf.org  Tue Jan 28 16:23: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 QAA08248
	for <sigtran-archive@odin.ietf.org>; Tue, 28 Jan 2003 16:23:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0SLiY121756
	for sigtran-archive@odin.ietf.org; Tue, 28 Jan 2003 16:44:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0SLhVJ21692;
	Tue, 28 Jan 2003 16:43:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0SLdTJ21460
	for <sigtran@optimus.ietf.org>; Tue, 28 Jan 2003 16:39:29 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07979
	for <sigtran@ietf.org>; Tue, 28 Jan 2003 16:17:50 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0SLLIeW020419;
	Tue, 28 Jan 2003 15:21:18 -0600 (CST)
Message-ID: <3E36F44E.67074A69@alcatel.com>
Date: Tue, 28 Jan 2003 15:21:18 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] m2pa comment: author list
References: <2135200C183FD5119588009027DE572302836C0A@webdev-owa.oni.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

"Ong, Lyndon" wrote:
  [...] 
> Also, references need to be sorted into Normative and Non-normative,
> in separate sections.
  [...]

Brian had already done this work for me, but I did not put it into
version 7.

Here is what the updated section 9 will look like.

=============================================================
9.  References 

9.1 Normative

  [JT-Q704]
       TTC, "Message Transfer Part Signalling Network Functions," TTC
       Standard JT-Q704, Telecommunication Technology Committee (TTC)
       (April 28, 1992).

  [Q.703]
       ITU, "Signalling System No. 7 - Signalling Link," ITU-T
       Recommendation Q.703, ITU-T Telecommunication Standardization
       Sector of ITU (March 1993).

  [Q.704]
       ITU, "Message Transfer Part - Signalling Network Functions and
       Messages," ITU-T Recommendation Q.704, ITU-T Telecommunication
       Standardization Sector of ITU (March 1993).

  [Q.2140]
       ITU, "B-ISDN ATM Adaptation Layer - Service Specific
       Coordination Function for Signalling at the Network Node
       Interface (SSCF at NNI)," ITU-T Recommendation Q.2140, ITU-T
       Telecommunication Standardization Sector of ITU (February
       1996).

  [Q.2210]
       ITU, "Message Transfer Part Level 3 Functions and Messages
       Using the Services of ITU-T Recommendation Q.2140," ITU-T
       Recommendation Q.2210, ITU-T Telecommunication Standardization
       Sector of ITU (July 1996).

  [RFC791]
       Information Sciences Institute, "Internet Protocol - DARPA
       Internet Program - Protocol Specification," RFC 791, The
       Internet Society (September 1981).

  [RFC2119]
       S. Bradner, "Key words for use in RFCs to Indicate Requirement
       Levels," BCP 14, RFC 2119, Internet Engineering Task Force
       (March 1997). 

  [RFC2196]
       B. Y. Frazer, "Site Security Handbook," RFC 2196, Internet
       Engineering Task Force (September 1997). 

  [RFC2401]
       S. Kent, R. Atkinson, "Security Architecture for the Internet
       Protocol," RFC 2401, Internet Engineering Task Force (November
       1998). 

  [RFC2434]
       T. Narten, H. T. Alvestrand, "Guidelines for Writing an IANA
       Considerations Section in RFCs," BCP 26, RFC 2434, The Internet
       Society (October, 1998).

  [RFC2960]
       R. Stewart, et. al., "Stream Control Transmission Protocol
       (SCTP)," RFC 2960, The Internet Society (February 2000).

  [T1.111]
       ANSI, "American National Standard for Telecommunications -
       Signaling System Number 7 (SS7) - Message Transfer Part (MTP),"
       ANSI T1.111-2000, American National Standards Institute (2000).

9.2 Informative

  [M2UA]
       K. Morneault, et. al., "Signaling System 7 (SS7) Message
       Transfer Part 2 (MTP2) - User Adaptation Layer," RFC 3331,
       Internet Engineering Task Force - Signalling Transport Working
       Group (September, 2002).

  [Q.700]
       ITU, "Introduction to CCITT Signalling System No. 7," ITU-T
       Recommendation Q.700, ITU-T Telecommunication Standardization
       Sector of ITU (March 1993).

  [Q.701]
       ITU, "Functional Description of the Message Transfer Part (MTP)
       of Signalling System No. 7," ITU-T Recommendation Q.701, ITU-T
       Telecommunication Standardization Sector of ITU (March 1993).

  [Q.702]
       ITU, "Signalling Data Link," ITU-T Recommendation Q.702, ITU-T
       Telecommunication Standardization Sector of ITU (March 1993).

  [Q.705]
       ITU, "Signalling System No. 7 - Signalling Network Structure,"
       ITU-T Recommendation Q.705, ITU-T Telecommunication
       Standardization Sector of ITU (March 1993).

  [RFC2719]
       L. Ong, et. al., "Framework Architecture for Signaling
       Transport," RFC 2719, The Internet Society (October 1999).
=============================================================

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 28 16:49: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 QAA09021
	for <sigtran-archive@odin.ietf.org>; Tue, 28 Jan 2003 16:49:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0SMAvg23972
	for sigtran-archive@odin.ietf.org; Tue, 28 Jan 2003 17:10:57 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0SMAHJ23934;
	Tue, 28 Jan 2003 17:10:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0SM6YJ23104
	for <sigtran@optimus.ietf.org>; Tue, 28 Jan 2003 17:06:34 -0500
Received: from ilsa.franken.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08918
	for <sigtran@ietf.org>; Tue, 28 Jan 2003 16:44:53 -0500 (EST)
Received: from lurchi.franken.de (pD9E4F598.dip.t-dialin.net [217.228.245.152])
	by ilsa.franken.de (Postfix) with ESMTP
	id B47D724676; Tue, 28 Jan 2003 22:47:12 +0100 (CET)
Date: Tue, 28 Jan 2003 22:44:05 +0100
Subject: Re: [Sigtran] m2pa comment: author list
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
To: Tom George <Tom.George@alcatel.com>
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <3E36F44E.67074A69@alcatel.com>
Message-Id: <9F9D9BFE-3309-11D7-B4A3-0030654C1AB6@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
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 Tim,
Shouldn't you also have a reference to RFC 3309 as a normative
reference. And what about draft-ietf-sigtran-security-0?.txt?

Best regards
Michael
On Tuesday, Jan 28, 2003, at 22:21 Europe/Berlin, Tom George wrote:

> "Ong, Lyndon" wrote:
>   [...]
>> Also, references need to be sorted into Normative and Non-normative,
>> in separate sections.
>   [...]
>
> Brian had already done this work for me, but I did not put it into
> version 7.
>
> Here is what the updated section 9 will look like.
>
> =============================================================
> 9.  References
>
> 9.1 Normative
>
>   [JT-Q704]
>        TTC, "Message Transfer Part Signalling Network Functions," TTC
>        Standard JT-Q704, Telecommunication Technology Committee (TTC)
>        (April 28, 1992).
>
>   [Q.703]
>        ITU, "Signalling System No. 7 - Signalling Link," ITU-T
>        Recommendation Q.703, ITU-T Telecommunication Standardization
>        Sector of ITU (March 1993).
>
>   [Q.704]
>        ITU, "Message Transfer Part - Signalling Network Functions and
>        Messages," ITU-T Recommendation Q.704, ITU-T Telecommunication
>        Standardization Sector of ITU (March 1993).
>
>   [Q.2140]
>        ITU, "B-ISDN ATM Adaptation Layer - Service Specific
>        Coordination Function for Signalling at the Network Node
>        Interface (SSCF at NNI)," ITU-T Recommendation Q.2140, ITU-T
>        Telecommunication Standardization Sector of ITU (February
>        1996).
>
>   [Q.2210]
>        ITU, "Message Transfer Part Level 3 Functions and Messages
>        Using the Services of ITU-T Recommendation Q.2140," ITU-T
>        Recommendation Q.2210, ITU-T Telecommunication Standardization
>        Sector of ITU (July 1996).
>
>   [RFC791]
>        Information Sciences Institute, "Internet Protocol - DARPA
>        Internet Program - Protocol Specification," RFC 791, The
>        Internet Society (September 1981).
>
>   [RFC2119]
>        S. Bradner, "Key words for use in RFCs to Indicate Requirement
>        Levels," BCP 14, RFC 2119, Internet Engineering Task Force
>        (March 1997).
>
>   [RFC2196]
>        B. Y. Frazer, "Site Security Handbook," RFC 2196, Internet
>        Engineering Task Force (September 1997).
>
>   [RFC2401]
>        S. Kent, R. Atkinson, "Security Architecture for the Internet
>        Protocol," RFC 2401, Internet Engineering Task Force (November
>        1998).
>
>   [RFC2434]
>        T. Narten, H. T. Alvestrand, "Guidelines for Writing an IANA
>        Considerations Section in RFCs," BCP 26, RFC 2434, The Internet
>        Society (October, 1998).
>
>   [RFC2960]
>        R. Stewart, et. al., "Stream Control Transmission Protocol
>        (SCTP)," RFC 2960, The Internet Society (February 2000).
>
>   [T1.111]
>        ANSI, "American National Standard for Telecommunications -
>        Signaling System Number 7 (SS7) - Message Transfer Part (MTP),"
>        ANSI T1.111-2000, American National Standards Institute (2000).
>
> 9.2 Informative
>
>   [M2UA]
>        K. Morneault, et. al., "Signaling System 7 (SS7) Message
>        Transfer Part 2 (MTP2) - User Adaptation Layer," RFC 3331,
>        Internet Engineering Task Force - Signalling Transport Working
>        Group (September, 2002).
>
>   [Q.700]
>        ITU, "Introduction to CCITT Signalling System No. 7," ITU-T
>        Recommendation Q.700, ITU-T Telecommunication Standardization
>        Sector of ITU (March 1993).
>
>   [Q.701]
>        ITU, "Functional Description of the Message Transfer Part (MTP)
>        of Signalling System No. 7," ITU-T Recommendation Q.701, ITU-T
>        Telecommunication Standardization Sector of ITU (March 1993).
>
>   [Q.702]
>        ITU, "Signalling Data Link," ITU-T Recommendation Q.702, ITU-T
>        Telecommunication Standardization Sector of ITU (March 1993).
>
>   [Q.705]
>        ITU, "Signalling System No. 7 - Signalling Network Structure,"
>        ITU-T Recommendation Q.705, ITU-T Telecommunication
>        Standardization Sector of ITU (March 1993).
>
>   [RFC2719]
>        L. Ong, et. al., "Framework Architecture for Signaling
>        Transport," RFC 2719, The Internet Society (October 1999).
> =============================================================
>
> -- 
> * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> * Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
> * 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  Tue Jan 28 17:28:19 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 RAA10089
	for <sigtran-archive@odin.ietf.org>; Tue, 28 Jan 2003 17:28:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0SMnQA26478
	for sigtran-archive@odin.ietf.org; Tue, 28 Jan 2003 17:49:26 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0SMmcJ26418;
	Tue, 28 Jan 2003 17:48:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0SMjeJ26314
	for <sigtran@optimus.ietf.org>; Tue, 28 Jan 2003 17:45:40 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09992
	for <sigtran@ietf.org>; Tue, 28 Jan 2003 17:24:00 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Peb2mW6ndlUEm5SIWQCAl1u2S9dmh63i@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0SMRRD30745;
	Tue, 28 Jan 2003 15:27:27 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0SMRRs30402;
	Tue, 28 Jan 2003 15:27:27 -0700
Date: Tue, 28 Jan 2003 15:27:27 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Cc: Tom George <Tom.George@alcatel.com>,
        "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] m2pa comment: author list
Message-ID: <20030128152727.A29107@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	Tom George <Tom.George@alcatel.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <3E36F44E.67074A69@alcatel.com> <9F9D9BFE-3309-11D7-B4A3-0030654C1AB6@lurchi.franken.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <9F9D9BFE-3309-11D7-B4A3-0030654C1AB6@lurchi.franken.de>; from Michael.Tuexen@lurchi.franken.de on Tue, Jan 28, 2003 at 10:44:05PM +0100
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>

Michael,

Sure:

--- tmp.txt	Tue Jan 28 15:24:11 2003
+++ draft-ietf-sigtran-m2pa-07.txt	Tue Jan 28 15:24:28 2003
@@ -923,7 +923,8 @@
 
 It is RECOMMENDED that the filler field contain a number pattern which
 varies among the Link Status Proving messages, and that will allow the
-SCTP checksum to be used to verify the accuracy of transmission.
+SCTP checksum [RFC 3309] to be used to verify the accuracy of
+transmission.
 
 3.  M2PA Link State Control
 
@@ -2656,6 +2656,11 @@
 
 Internet-Draft                    M2PA                  January 7, 2003
 
+[RFC 3309]
+   J. Stone, R. Stewart and D. Otis, "Stream Control Transmission
+   Protocol (SCTP) Checksum Change," RFC 3309, The Internet Society
+   (September 2002).
+
 [RFC 2196]
    B. Y. Frazer, "Site Security Handbook," RFC 2196, Internet
    Engineering Task Force (September 1997).
 
--brian


Michael Tuexen wrote:                                                              (Tue, 28 Jan 2003 22:44:05)
> Hi Tim,
> Shouldn't you also have a reference to RFC 3309 as a normative
> reference. And what about draft-ietf-sigtran-security-0?.txt?
> 
> Best regards
> Michael
> On Tuesday, Jan 28, 2003, at 22:21 Europe/Berlin, Tom George wrote:
> 
> > "Ong, Lyndon" wrote:
> >   [...]
> >> Also, references need to be sorted into Normative and Non-normative,
> >> in separate sections.
> >   [...]
> >
> > Brian had already done this work for me, but I did not put it into
> > version 7.
> >
> > Here is what the updated section 9 will look like.
> >
> > =============================================================
> > 9.  References
> >
> > 9.1 Normative
> >
> >   [JT-Q704]
> >        TTC, "Message Transfer Part Signalling Network Functions," TTC
> >        Standard JT-Q704, Telecommunication Technology Committee (TTC)
> >        (April 28, 1992).
> >
> >   [Q.703]
> >        ITU, "Signalling System No. 7 - Signalling Link," ITU-T
> >        Recommendation Q.703, ITU-T Telecommunication Standardization
> >        Sector of ITU (March 1993).
> >
> >   [Q.704]
> >        ITU, "Message Transfer Part - Signalling Network Functions and
> >        Messages," ITU-T Recommendation Q.704, ITU-T Telecommunication
> >        Standardization Sector of ITU (March 1993).
> >
> >   [Q.2140]
> >        ITU, "B-ISDN ATM Adaptation Layer - Service Specific
> >        Coordination Function for Signalling at the Network Node
> >        Interface (SSCF at NNI)," ITU-T Recommendation Q.2140, ITU-T
> >        Telecommunication Standardization Sector of ITU (February
> >        1996).
> >
> >   [Q.2210]
> >        ITU, "Message Transfer Part Level 3 Functions and Messages
> >        Using the Services of ITU-T Recommendation Q.2140," ITU-T
> >        Recommendation Q.2210, ITU-T Telecommunication Standardization
> >        Sector of ITU (July 1996).
> >
> >   [RFC791]
> >        Information Sciences Institute, "Internet Protocol - DARPA
> >        Internet Program - Protocol Specification," RFC 791, The
> >        Internet Society (September 1981).
> >
> >   [RFC2119]
> >        S. Bradner, "Key words for use in RFCs to Indicate Requirement
> >        Levels," BCP 14, RFC 2119, Internet Engineering Task Force
> >        (March 1997).
> >
> >   [RFC2196]
> >        B. Y. Frazer, "Site Security Handbook," RFC 2196, Internet
> >        Engineering Task Force (September 1997).
> >
> >   [RFC2401]
> >        S. Kent, R. Atkinson, "Security Architecture for the Internet
> >        Protocol," RFC 2401, Internet Engineering Task Force (November
> >        1998).
> >
> >   [RFC2434]
> >        T. Narten, H. T. Alvestrand, "Guidelines for Writing an IANA
> >        Considerations Section in RFCs," BCP 26, RFC 2434, The Internet
> >        Society (October, 1998).
> >
> >   [RFC2960]
> >        R. Stewart, et. al., "Stream Control Transmission Protocol
> >        (SCTP)," RFC 2960, The Internet Society (February 2000).
> >
> >   [T1.111]
> >        ANSI, "American National Standard for Telecommunications -
> >        Signaling System Number 7 (SS7) - Message Transfer Part (MTP),"
> >        ANSI T1.111-2000, American National Standards Institute (2000).
> >
> > 9.2 Informative
> >
> >   [M2UA]
> >        K. Morneault, et. al., "Signaling System 7 (SS7) Message
> >        Transfer Part 2 (MTP2) - User Adaptation Layer," RFC 3331,
> >        Internet Engineering Task Force - Signalling Transport Working
> >        Group (September, 2002).
> >
> >   [Q.700]
> >        ITU, "Introduction to CCITT Signalling System No. 7," ITU-T
> >        Recommendation Q.700, ITU-T Telecommunication Standardization
> >        Sector of ITU (March 1993).
> >
> >   [Q.701]
> >        ITU, "Functional Description of the Message Transfer Part (MTP)
> >        of Signalling System No. 7," ITU-T Recommendation Q.701, ITU-T
> >        Telecommunication Standardization Sector of ITU (March 1993).
> >
> >   [Q.702]
> >        ITU, "Signalling Data Link," ITU-T Recommendation Q.702, ITU-T
> >        Telecommunication Standardization Sector of ITU (March 1993).
> >
> >   [Q.705]
> >        ITU, "Signalling System No. 7 - Signalling Network Structure,"
> >        ITU-T Recommendation Q.705, ITU-T Telecommunication
> >        Standardization Sector of ITU (March 1993).
> >
> >   [RFC2719]
> >        L. Ong, et. al., "Framework Architecture for Signaling
> >        Transport," RFC 2719, The Internet Society (October 1999).
> > =============================================================
> >
> > -- 
> > * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> > * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> > * Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
> > * 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

-- 
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 Jan 28 19:07: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 TAA12036
	for <sigtran-archive@odin.ietf.org>; Tue, 28 Jan 2003 19:07:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0T0T5832255
	for sigtran-archive@odin.ietf.org; Tue, 28 Jan 2003 19:29:05 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T0SLJ32221;
	Tue, 28 Jan 2003 19:28:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T0PdJ32126
	for <sigtran@optimus.ietf.org>; Tue, 28 Jan 2003 19:25:39 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11991
	for <sigtran@ietf.org>; Tue, 28 Jan 2003 19:03:57 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0T07ReW017753;
	Tue, 28 Jan 2003 18:07:27 -0600 (CST)
Message-ID: <3E371B3F.92864BE1@alcatel.com>
Date: Tue, 28 Jan 2003 18:07:27 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] m2pa comment: author list
References: <3E36F44E.67074A69@alcatel.com> <9F9D9BFE-3309-11D7-B4A3-0030654C1AB6@lurchi.franken.de> <20030128152727.A29107@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

Michael and Brian,

This looks good to me. Since I mention the checksum in section 2.3.2.1,
it is a good idea to reference RFC 3309.

tomG.

"Brian F. G. Bidulock" wrote:
> 
> Michael,
> 
> Sure:
> 
> --- tmp.txt     Tue Jan 28 15:24:11 2003
> +++ draft-ietf-sigtran-m2pa-07.txt      Tue Jan 28 15:24:28 2003
> @@ -923,7 +923,8 @@
> 
>  It is RECOMMENDED that the filler field contain a number pattern which
>  varies among the Link Status Proving messages, and that will allow the
> -SCTP checksum to be used to verify the accuracy of transmission.
> +SCTP checksum [RFC 3309] to be used to verify the accuracy of
> +transmission.
> 
>  3.  M2PA Link State Control
> 
> @@ -2656,6 +2656,11 @@
> 
>  Internet-Draft                    M2PA                  January 7, 2003
> 
> +[RFC 3309]
> +   J. Stone, R. Stewart and D. Otis, "Stream Control Transmission
> +   Protocol (SCTP) Checksum Change," RFC 3309, The Internet Society
> +   (September 2002).
> +
>  [RFC 2196]
>     B. Y. Frazer, "Site Security Handbook," RFC 2196, Internet
>     Engineering Task Force (September 1997).
> 
> --brian
> 
> Michael Tuexen wrote:                                                              (Tue, 28 Jan 2003 22:44:05)
> > Hi Tim,
> > Shouldn't you also have a reference to RFC 3309 as a normative
> > reference. And what about draft-ietf-sigtran-security-0?.txt?
> >
> > Best regards
> > Michael
  [...]

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 28 19:08: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 TAA12051
	for <sigtran-archive@odin.ietf.org>; Tue, 28 Jan 2003 19:08:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0T0TH232279
	for sigtran-archive@odin.ietf.org; Tue, 28 Jan 2003 19:29:17 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T0T6J32270;
	Tue, 28 Jan 2003 19:29:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T0SVJ32223
	for <sigtran@optimus.ietf.org>; Tue, 28 Jan 2003 19:28:31 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12016
	for <sigtran@ietf.org>; Tue, 28 Jan 2003 19:06:50 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0T0AKeW018056;
	Tue, 28 Jan 2003 18:10:20 -0600 (CST)
Message-ID: <3E371BEC.91CD70A9@alcatel.com>
Date: Tue, 28 Jan 2003 18:10:20 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
CC: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] m2pa comment: author list
References: <9F9D9BFE-3309-11D7-B4A3-0030654C1AB6@lurchi.franken.de>
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

Michael,

Lyndon said the security draft is coming out soon. I thought I would
wait until then and see how I need to incorporate it into M2PA. 

tomG.

Michael Tuexen wrote:
> 
> Hi Tim,
> Shouldn't you also have a reference to RFC 3309 as a normative
> reference. And what about draft-ietf-sigtran-security-0?.txt?
> 
> Best regards
> Michael
  [...]

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 28 19:21: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 TAA12276
	for <sigtran-archive@odin.ietf.org>; Tue, 28 Jan 2003 19:21:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0T0gNd00971
	for sigtran-archive@odin.ietf.org; Tue, 28 Jan 2003 19:42:23 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T0gDJ00928;
	Tue, 28 Jan 2003 19:42:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T0eQJ00826
	for <sigtran@optimus.ietf.org>; Tue, 28 Jan 2003 19:40:26 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12227
	for <sigtran@ietf.org>; Tue, 28 Jan 2003 19:18:44 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0T0MFeW019266;
	Tue, 28 Jan 2003 18:22:15 -0600 (CST)
Message-ID: <3E371EB6.9FFAC43C@alcatel.com>
Date: Tue, 28 Jan 2003 18:22:14 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA Draft 7 comment
References: <B1F38D7B53615140BCEA6677DF9F2F8C579C1E@i2km11-ukbr.domain1.systemhost.net>
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

Karen,

If it is the discussion I am thinking about, we were discussing what
would happen if a processor outage (a real one) happened while there
were congestion problems. I don't think anyone suggested that proc
outage be used improperly.

tomG.


karen.d.king@bt.com wrote:
> 
> Brian,
> 
> Good you're happy with the first comment.
> 
> OK - I understand your point that no one should think this behaviour would
> be appropriate and, at the end of the day, we can't spec out everything a
> poor/incorrect implementation 'might' do. I do seem to remember some emails
> a while ago that mentioned processor outage and congestion in the same
> sentence. I therefore get concerned that some do not understand its correct
> use.
> 
> Regards,
> 
> Karen
  [...]

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 28 19:32: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 TAA12582
	for <sigtran-archive@odin.ietf.org>; Tue, 28 Jan 2003 19:32:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0T0rnM01559
	for sigtran-archive@odin.ietf.org; Tue, 28 Jan 2003 19:53:49 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T0r7J01499;
	Tue, 28 Jan 2003 19:53:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T0qIJ01447
	for <sigtran@optimus.ietf.org>; Tue, 28 Jan 2003 19:52:18 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12517
	for <sigtran@ietf.org>; Tue, 28 Jan 2003 19:30:36 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0T0Y6eW020600;
	Tue, 28 Jan 2003 18:34:06 -0600 (CST)
Message-ID: <3E37217E.7D1FEE37@alcatel.com>
Date: Tue, 28 Jan 2003 18:34:06 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA Draft 7 comment
References: <B1F38D7B53615140BCEA6677DF9F2F8C579C1E@i2km11-ukbr.domain1.systemhost.net>
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 is the new section after moving the paragraphs around (Karen's 1st
comment). I also moved the paragraph after, since they go together.

==========================================================
4.1.4 Processor Outage

A processor outage occurs when M2PA cannot transfer messages because
of a condition at a higher layer than M2PA.

When M2PA detects a local processor outage, it sends a Link Status
message to its peer with status Processor Outage. M2PA SHALL also
cease sending User Data messages to SCTP for transmission. M2PA SHALL
stop acknowledging received User Data messages.

M2PA MAY send additional Link Status Processor Outage messages as long
as there is a local processor outage and the link is in service. If
the link is out of service, M2PA SHOULD locally mark that it is in
local processor outage.

The peer M2PA, upon receiving the Link Status Processor Outage
message, SHALL report Remote Processor Outage to its MTP3. The peer
M2PA ceases sending User Data messages. M2PA stops the Remote
Congestion timer T6 (see section 4.1.5 Level 2 Flow Control) if it is
running, and timer T7, if it is running.

When the processor outage ceases, MTP3 sends a Local Processor
Recovered indication to M2PA. The local M2PA notifies its peer by
sending a Link Status message with status Processor Outage Ended. The
local M2PA SHALL resume receiving and transmitting messages.

[moved]
MTP3 may send a Flush Buffers or Continue command to M2PA as part of
its processor outage procedure (See section 4.2.4 Flush Buffers and
Continue). The use of Flush Buffers and Continue is specified in Q.703
[Q.703] and T1.111.3 [T1.111].

[moved]
Alternatively, MTP3 may perform data retrieval as part of a changeover
procedure.

If the peer is in the IN SERVICE state, it uses the Remote Processor
Recovered Indication to notify its MTP3 that the remote processor
outage condition has ceased.
==========================================================


-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 29 02:32: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 CAA12444
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 02:32:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0T7rQF02926
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 02:53:26 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T7qdJ02887;
	Wed, 29 Jan 2003 02:52:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T7olJ02774
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 02:50:47 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12300
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 02:28:55 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:s0kz0hQO5bhefBUlXmp0zhWQ0m0Cpe0I@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0T7W5D06306;
	Wed, 29 Jan 2003 00:32:05 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0T7W4208902;
	Wed, 29 Jan 2003 00:32:04 -0700
Date: Wed, 29 Jan 2003 00:32:04 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Somesh <somesh@indts.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>, Vasudeva <vasudeva@indts.com>
Message-ID: <20030129003204.A8750@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Somesh <somesh@indts.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>,
	Vasudeva <vasudeva@indts.com>
References: <F73B646FCC01D5118F530002B32C337201761D2A@INDTS_FS>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <F73B646FCC01D5118F530002B32C337201761D2A@INDTS_FS>; from somesh@indts.com on Wed, Jan 29, 2003 at 12:22:40PM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: IUA message on stream identifier "0"
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>

Somesh,

MGMT messages include ERR and NTFY.

--brian

Somesh wrote:                                                                       (Wed, 29 Jan 2003 12:22:40)
> 
> Hi,
> 
> we have a doubt regarding an IUA message sent on the stream identifier
> "0".RFC 3057 says "The "Invalid Stream Identifier" error would be sent if a
> message was received on an unexpected SCTP stream (i.e., a MGMT message was
> received on a stream other than "0").What should be the response if ASPTM
> message like "ASP Active" is sent on the stream identifier "0"?
> 
> rgds
> Somesh
> Test Engineer
>  
>  
> Ind-TeleSoft Pvt. Ltd. | Open Services Solutions for Converged Networks
> Ph: +91-80-550 8930 | Ext. 301 | Fx: +91-80-552 1164
> E-mail: somesh@indts.com <mailto:somesh@indts.com>  URL: www.telesoftinc.com
> <http://www.telesoftinc.com/>
>  
> Information contained in this E-MAIL being proprietary to Ind TeleSoft is
> 'privileged' and 'confidential' and intended for use only by the individual
> or entity to which it is addressed. If you are not the intended recipient
> (or have received this e-mail in error) please notify the sender immediately
> and destroy this e-mail. You are notified that any use, copying, disclosure
> or dissemination of the information contained in the E-MAIL in any manner
> whatsoever is strictly prohibited. Please advise immediately if you or your
> employer does not consent to Internet email for messages of this kind.
> Opinions, conclusions and other information in this message that do not
> relate to the official business of my firm shall be understood as neither
> given nor endorsed by it.
>  
> 

-- 
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 Jan 29 04:05: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 EAA13803
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 04:05:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0T9R9o09018
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 04:27:09 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T9PtJ08976;
	Wed, 29 Jan 2003 04:25:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T9OTJ08930
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 04:24:29 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13785
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 04:02:35 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:o9rzzOyd1TxUkhqEpzAc/qX3/CPNRhXH@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0T95hD07723;
	Wed, 29 Jan 2003 02:05:43 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0T95hp11625;
	Wed, 29 Jan 2003 02:05:43 -0700
Date: Wed, 29 Jan 2003 02:05:42 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Somesh <somesh@indts.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>, Vasudeva <vasudeva@indts.com>
Message-ID: <20030129020542.A11362@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Somesh <somesh@indts.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>,
	Vasudeva <vasudeva@indts.com>
References: <F73B646FCC01D5118F530002B32C337201761D2B@INDTS_FS>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <F73B646FCC01D5118F530002B32C337201761D2B@INDTS_FS>; from somesh@indts.com on Wed, Jan 29, 2003 at 02:25:18PM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Subject: [Sigtran] Re: IUA message on stream identifier "0"
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>

Somesh,

Somesh wrote:                                                                       (Wed, 29 Jan 2003 14:25:18)
> Brian,
> 
> 1.Should there be a response in form of "Error" message if ASPTM message
> like "ASP Active" is sent on the stream identifier "0"? 

Where does it say that ASPTM cannot be sent on stream '0'?

> 2.Is "Invalid Stream Identifier" error restricted only to MGMT message ?

If elsehwere in the spec it says that some message cannot be sent on some
stream, then this error would also be appropriate in that situation.

--brian

> 
> Somesh
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Wednesday, January 29, 2003 1:02 PM
> To: Somesh
> Cc: 'sigtran@ietf.org'; Vasudeva
> Subject: Re: IUA message on stream identifier "0"
> 
> 
> Somesh,
> 
> MGMT messages include ERR and NTFY.
> 
> --brian
> 
> Somesh wrote:
> (Wed, 29 Jan 2003 12:22:40)
> > 
> > Hi,
> > 
> > we have a doubt regarding an IUA message sent on the stream identifier
> > "0".RFC 3057 says "The "Invalid Stream Identifier" error would be sent if
> a
> > message was received on an unexpected SCTP stream (i.e., a MGMT message
> was
> > received on a stream other than "0").What should be the response if ASPTM
> > message like "ASP Active" is sent on the stream identifier "0"?
> > 
> > rgds
> > Somesh
> > Test Engineer
> >  
> >  
> > Ind-TeleSoft Pvt. Ltd. | Open Services Solutions for Converged Networks
> > Ph: +91-80-550 8930 | Ext. 301 | Fx: +91-80-552 1164
> > E-mail: somesh@indts.com <mailto:somesh@indts.com>  URL:
> www.telesoftinc.com
> > <http://www.telesoftinc.com/>
> >  
> > Information contained in this E-MAIL being proprietary to Ind TeleSoft is
> > 'privileged' and 'confidential' and intended for use only by the
> individual
> > or entity to which it is addressed. If you are not the intended recipient
> > (or have received this e-mail in error) please notify the sender
> immediately
> > and destroy this e-mail. You are notified that any use, copying,
> disclosure
> > or dissemination of the information contained in the E-MAIL in any manner
> > whatsoever is strictly prohibited. Please advise immediately if you or
> your
> > employer does not consent to Internet email for messages of this kind.
> > Opinions, conclusions and other information in this message that do not
> > relate to the official business of my firm shall be understood as neither
> > given nor endorsed by it.
> >  
> > 
> 
> -- 
> 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 mailnull@www1.ietf.org  Wed Jan 29 04:28: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 EAA14010
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 04:28:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0T9nma10503
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 04:49:48 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T9nXJ10471;
	Wed, 29 Jan 2003 04:49:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T7BAJ27053
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 02:11:10 -0500
Received: from telesoft.indts.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17834
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 01:49:18 -0500 (EST)
Received: from indts_fs.indts.com (indts_fs.indts.com [201.64.64.29])
	by telesoft.indts.com (8.11.6/8.11.6) with ESMTP id h0T6jwX17652;
	Wed, 29 Jan 2003 12:16:00 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <CZBA6YRB>; Wed, 29 Jan 2003 12:22:40 +0530
Message-ID: <F73B646FCC01D5118F530002B32C337201761D2A@INDTS_FS>
From: Somesh <somesh@indts.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>,
        "'bidulock@openss7.org'"
	 <bidulock@openss7.org>,
        Vasudeva <vasudeva@indts.com>
Date: Wed, 29 Jan 2003 12:22:40 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] IUA message on stream identifier "0"
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,

we have a doubt regarding an IUA message sent on the stream identifier
"0".RFC 3057 says "The "Invalid Stream Identifier" error would be sent if a
message was received on an unexpected SCTP stream (i.e., a MGMT message was
received on a stream other than "0").What should be the response if ASPTM
message like "ASP Active" is sent on the stream identifier "0"?

rgds
Somesh
Test Engineer
 
 
Ind-TeleSoft Pvt. Ltd. | Open Services Solutions for Converged Networks
Ph: +91-80-550 8930 | Ext. 301 | Fx: +91-80-552 1164
E-mail: somesh@indts.com <mailto:somesh@indts.com>  URL: www.telesoftinc.com
<http://www.telesoftinc.com/>
 
Information contained in this E-MAIL being proprietary to Ind TeleSoft is
'privileged' and 'confidential' and intended for use only by the individual
or entity to which it is addressed. If you are not the intended recipient
(or have received this e-mail in error) please notify the sender immediately
and destroy this e-mail. You are notified that any use, copying, disclosure
or dissemination of the information contained in the E-MAIL in any manner
whatsoever is strictly prohibited. Please advise immediately if you or your
employer does not consent to Internet email for messages of this kind.
Opinions, conclusions and other information in this message that do not
relate to the official business of my firm shall be understood as neither
given nor endorsed by it.
 


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



From mailnull@www1.ietf.org  Wed Jan 29 04: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 EAA14023
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 04:28:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0T9nqQ10523
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 04:49:52 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T9nZJ10486;
	Wed, 29 Jan 2003 04:49:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T9EOJ08497
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 04:14:24 -0500
Received: from telesoft.indts.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13629
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 03:52:25 -0500 (EST)
Received: from indts_fs.indts.com (indts_fs.indts.com [201.64.64.29])
	by telesoft.indts.com (8.11.6/8.11.6) with ESMTP id h0T8maX31079;
	Wed, 29 Jan 2003 14:18:46 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <CZBA6YWS>; Wed, 29 Jan 2003 14:25:19 +0530
Message-ID: <F73B646FCC01D5118F530002B32C337201761D2B@INDTS_FS>
From: Somesh <somesh@indts.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>,
        Somesh
	 <somesh@indts.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>, Vasudeva <vasudeva@indts.com>
Date: Wed, 29 Jan 2003 14:25:18 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] RE: IUA message on stream identifier "0"
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.Should there be a response in form of "Error" message if ASPTM message
like "ASP Active" is sent on the stream identifier "0"? 
2.Is "Invalid Stream Identifier" error restricted only to MGMT message ?

Somesh

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: Wednesday, January 29, 2003 1:02 PM
To: Somesh
Cc: 'sigtran@ietf.org'; Vasudeva
Subject: Re: IUA message on stream identifier "0"


Somesh,

MGMT messages include ERR and NTFY.

--brian

Somesh wrote:
(Wed, 29 Jan 2003 12:22:40)
> 
> Hi,
> 
> we have a doubt regarding an IUA message sent on the stream identifier
> "0".RFC 3057 says "The "Invalid Stream Identifier" error would be sent if
a
> message was received on an unexpected SCTP stream (i.e., a MGMT message
was
> received on a stream other than "0").What should be the response if ASPTM
> message like "ASP Active" is sent on the stream identifier "0"?
> 
> rgds
> Somesh
> Test Engineer
>  
>  
> Ind-TeleSoft Pvt. Ltd. | Open Services Solutions for Converged Networks
> Ph: +91-80-550 8930 | Ext. 301 | Fx: +91-80-552 1164
> E-mail: somesh@indts.com <mailto:somesh@indts.com>  URL:
www.telesoftinc.com
> <http://www.telesoftinc.com/>
>  
> Information contained in this E-MAIL being proprietary to Ind TeleSoft is
> 'privileged' and 'confidential' and intended for use only by the
individual
> or entity to which it is addressed. If you are not the intended recipient
> (or have received this e-mail in error) please notify the sender
immediately
> and destroy this e-mail. You are notified that any use, copying,
disclosure
> or dissemination of the information contained in the E-MAIL in any manner
> whatsoever is strictly prohibited. Please advise immediately if you or
your
> employer does not consent to Internet email for messages of this kind.
> Opinions, conclusions and other information in this message that do not
> relate to the official business of my firm shall be understood as neither
> given nor endorsed by it.
>  
> 

-- 
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 Jan 29 04:28: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 EAA14036
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 04:28:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0T9o5N10575
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 04:50:05 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0T9nAJ10451;
	Wed, 29 Jan 2003 04:49:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0S93rJ02258
	for <sigtran@optimus.ietf.org>; Tue, 28 Jan 2003 04:03:53 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19282
	for <sigtran@ietf.org>; Tue, 28 Jan 2003 03:42:25 -0500 (EST)
X-Priority: 3 (Normal)
Importance: Normal
Subject: RE: RE: [Sigtran] M3UA: ASP to SGP communication
To: sigtran@ietf.org
Message-ID: <OFEC77243A.47A4213E-ONC2256CBC.002FD630@LocalDomain>
From: "TOLGA ASVEREN" <tolga.asveren@o2.com.tr>
Date: Tue, 28 Jan 2003 10:42:30 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/28/2003
 10:42:33 AM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0S94BJ02265
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

Jolan,

> -----Original Message-----
> From: "Jolan Evans" <jolan.evans@opentelecommunications.com>
> Sent: Tuesday, January 28, 2003 10:17 AM
> To: "Sigtran" <sigtran@ietf.org>
> Cc: <bidulock@openss7.org>
> Subject: RE: [Sigtran] M3UA: ASP to SGP communication (Sent by
> sigtran-admin@ietf.org on behalf of "Jolan Evans"
> <jolan.evans@opentelecommunications.com> )
>
>
> I would like to raise a few issues regarding your procedures below for
> ASP to SGP routing. I know this discussion took places a
> while ago, but
> it has taken me some time to come up to speed with the RFC as I have
> been busy on other things until recently.
>
> Please note that I have inserted "M3UA" into the subject line of the
> original email.
>
>
>
> 1. Nomenclature
> AsPc: Point code of an AS. In defining routing keys, the RFC uses DPC
> for this term as it takes the SG's frame of reference.
> RemotePc: Point code of an SS7 MTP entity with which an AS
> communicates
> via an SG, or directly in the case of IPSP-IPSP communication. In
> defining routing keys, the RFC uses OPC for this term as it takes the
> SG's frame of reference again.
>
>
>
> 2. Background Assumptions
> As per Brian's introduction, we assume that zero or more
> MTP-User's are
> bound to an MTP-SAP. The MTP-SAP exists in a particular MTP-Network,
> which has a particular MTP protocol variant. An SG is
> associated with a
> single MTP-Network. A RK is defined as in the RFC, but, for
> clarity, is
> independent of any SG and associated with a single MTP-Network. An
> SgRouteSet is uniquely defined by an RK, an SG and an MTP-SAP (the RK
> and SG must be both associated with the same MTP-Network) and also
> specifies the network appearance for the MTP-Network to be
> used with the
> SG and the RC of each SGP in the SG. Therefore, an SgRouteSet is
> implicitly associated with a single MTP-Network. An MTP-SAP is
> associated with zero or more SgRouteSet's and therefore an MTP-SAP is
> associated with zero or more RKs. In contrast, it appears that Brian
> assumes that an MTP-SAP can only be associated with one RK. Given this
> extension, we have the following requirement.
>
>
>
> 3. Routing Keys Requirements to Support Unique SS7 Destination Status
> Let RemotePcSet(Rk) be the set of RemotePc's reachable via the SG from
> the ASP where the RK is defined.
> Consider any two SgRouteSet's SgRsA and SgRsA which are
> associated with
> the same MTP-SAP.
> Let the routing key of SgRsA and SgRsB be RkA and RkB respectively.
> If the intersection of RemotePcSet(RkA) and RemotePcSet(RkB)
> is non-nil
> then the routing keys MUST be identical in every respect apart from
> their RemotePcSet.
> If this wasn't the case, an ASP could never indicate an
> MTP-RESUME to an
> MTP-USER because an MTP-RESUME can only specify a RemotePc
> and no other
> SS7 element. I assume here for simplicity that every MTP-User of a
> MTP-SAP must be given the same MTP status (i.e. different MTP-Users of
> the same MTP-SAP cannot be given different MTP-Status indications
> depending on what traffic they have requested).
>
> Here's a concrete example of why this is so. Consider an ASP with the
> following routing keys:
> RkA: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={A}
> RkB: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={B}
> RkC: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={M}
> RkD: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={N}
>
> Assume that RkA and RkB were both active in SgpA and SgpB respectively
> and are associated with the same MTP-SAP, but different SGs.
> Also assume
> that a DAVA has been received for RemotePc=X from SgpA after
> a DUNA from
> SgpB for the same RemotePc. We might consider generating an MTP-Resume
> to all the MTP-Users of the MTP-SAP for RemotePc X. However, if an
> MTP-User requests an MTP-Transfer with an AsPc of B then SgpB
> may not be
> able to transfer it as indicated by the DUNA it sent the ASP.
>
> The same explanation applies to RkC and RkD.
>
> In practice this requirement probably won't cause too many headaches
> because it is likely that there would be two different MTP-Users, one
> using only RkA/RkC and the other using only RkB/RkD. In this case, we
> can simply create two MTP-SAPs in the same MTP-Network and associate
> each routing key with a different MTP-SAP. Of course, this
> would require
> the M3UA implementation to support more than one MTP-SAP per
> MTP-Network, which would be extra work obviously.
[TOLGA] IMO there is no problem. It might be extra work but people are free
to support such a configuration or not.
>
>
>
> 4. ASP-SGP Routing should use SS7 Destination Availability/Restricted
> Status on a per-SGP rather than a per-SG basis.
>
> I believe your ASP-SGP procedures should be amended (I only amend the
> multiple SG case as the single SG case is a special case of
> the former)
> as follows:
>
> Change:
> "This routing information is updated by collecting DUNA/DAVA/DRST
> messages received from (any of the SGP in) the SG."
> To:
> "This routing information is updated by collecting DUNA/DAVA/DRST
> information on a per-(SGP,destination) basis. An SG is
> considered to be
> available and unrestricted for a particular destination if
> any SGP in it
> is available and unrestricted for that destination. Otherwise
> if this is
> not he case, then an SG is considered to be restricted for a
> particular
> destination if there is at least one SGP in the SG restricted for that
> destination. Otherwise if this is not the case, the SG is
> considered to
> be prohibited for that destination."
>
> The RFC is not particular clear on this point. In section 1.4.1 para 3
> it states that "MTP3 routeset, SPMC and remote AS/ASP states
> of each SGP
> SHOULD be coordinated across all the SGPs". However, this
> uses "SHOULD"
> which implies it is only recommended and it also doesn't specifically
> state that SS7 destination availability, restriction and congestion
> status ("SS7 destination status" for short) should be
> coordinated across
> all SGPs. I don't think that "MTP3 routeset" necessarily implies SS7
> destination status. Also, in section 1.3.2.5 1.4.2.5 it suggests in
> should be on a per-SGP basis. Section 4.5.2.2 uses the word "SG" but
> also uses the term "affected route(s)". Section 1.3.2.5 and section
> 1.4.2.5 suggest the word "route" refers to an SGP and not an
> SG. Hence,
> given the ambiguity of section 4.5.2.2 I think that route can be
> considered to refer to an SGP.
>
> A configuration where per-SGP SS7 destination status is
> necessary is as
> follows. Consider an SEP SG which has two SGP's acting as a redundant
> pair. Each SGP has it's own link set to a particular STP. While in
> section 1.4.1 para 3 it states that "Rerouting of traffic between the
> SGPs MAY also be supported", it uses "MAY" and hence this is optional.
> If one link set fails but not the other, one SGP will be able to reach
> the SS7 network but not the other if rerouting between SGPs is not
> supported or the rerouting link has also failed. Hence, it would be
> possible for one SGP to send a DUNA for a particular
> destination but not
> the other.
[TOLGA] Again I don´t see a problem. I only agree that "MAY" in the
sentence you refer was better changed to a "SHOULD". If somebody thinks
that creating a unique layer3 view among SGPs belonging to the same SG is
hard to implement/not necessary, then it is possible to have SGs consisting
of one SGP, without violating the protocol. In that case, SSNM will be
received separetly from each SGP, because they belong to different SGs.
>
>
> Your feedback would be appreciated.
>
> Jolan.
>
>
> --
> Jolan Evans
> Open Telecommunications
> jolan.evans@opentelecommunications.com
>
>
> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org] On Behalf
> Of Brian F. G. Bidulock
> Sent: Tuesday, 8 October 2002 17:47
> To: Srikanth Yandapalli
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] ASP to SGP communication
>
> Srikanth,
>
> Srikanth Yandapalli wrote:               (Tue, 08 Oct 2002 12:03:52)
> >
> >    I am late entrant to this group.I am quite sure all this should
> have
> >    been discussed and I am sorry about this.
>
> Welcome.
>
> >
> >    In the context of a single ASP in communication with
> multiple SGPs,
> >    how should the routing of a MTP_DATA_REQ take place at the ASP?
>
> I assume you are talking about M3UA?  As we are dealing with 5 or more
> UAs
> now, in the future it would be helpful to add M3UA (or
> whichever) to the
> subject line.
>
> >
> >    approach 1:
> >
> >    We may find out the  RK and find out the SGP list that the RK is
> >    active on and choose one SGP for sending the message based
> >    on congestion level and also whether we have received any DRST
> >    message from any of the SGPs.
>
> This approach is applicable to multiple SGs, but not to multiple SGPs
> within a
> single SG.
>
> >    approach 2:
> >
> >    An SGP can also be viewed as providing route to a set of DPCs
> >    and the routing can be based on the DPC for the message alone.
> >    This approach is reduces the complexity but adds a situation
> >    where the RK may not be active on that association. And also is
> >    is mandatory to send RC on this association and if so what could
> >    the SGP make out of the RC?
>
> RC should be coordinated and the same across multiple SGPs
> within an SG.
>
> >
> >    Is there a preferred approach to this issue?
> >
>
> Typically, the logic can be something like this: (but there
> are several
> other
> schools of thought):
>
> Single SG case: (multiple SGs is more complicated)
>
>   MTP-TRANSFER request is issued by an MTP-User.  The
> MTP-User is bound
> to an
>   MTP-SAP.  The MTP-SAP is associated with an AS/RC/RK.
> There is a pool
> of
>   SGPs on an SG for which the AS/RC/RK is active.  The AS may have
> received
>   MTP-PAUSE/RESUME/STATUS indications from the SG and may choose to
> honor that
>   information or not.  If the ASP chooses not to honor this
> information
> it can
>   blindly send messages to the SGP and rely upon a DUNA/SCON response
> from the
>   SGP later.
>
>   Selection of an SGP within an SG is based on the traffic
> mode for the
> SGP.
>   This traffic mode is not managed by M3UA, however, M3UA provides for
>   distribution of traffic over SGP based on any of the
> methods described
> for
>   ASPs (active/standby, load-share, broadcast).  A typical method is
>   load-share based on SLS.  In this scheme, using the SLS in the
> MTP-TRANSFER
>   request, the ASP selects load-shares traffic over the available SGP.
>
> Multiple SG case:
>
>   In the more complicated multiple SG case, the ASP must
> first select an
> SG
>   before it selects an SGP within the SG.  The ASP must maintain some
>   additional routing information to be able to properly select an SG.
> This
>   routing information is updated by collecting DUNA/DAVA/DRST messages
>   received from (any of the SGP in) the SG.  To select the
> outgoing SG,
> the
>   ASP must examine the destination of the MTP-TRANSFER request.
>
>   (If the SG has no SGP active for the AS/RC/RK, all
> destinations can be
>   considered prohibited).
>
>   If the destination is available and unrestricted for
> several SGs, the
> ASP
>   should select an SG on a load-sharing basis (based on SLS) and then
> select
>   an active SGP within the SG on the basis of the traffic mode for the
> SG.
>
>   If some SG are restricted for the specified destination (based on
> received
>   DRST messages from the SG), the ASP should load-share across the
> available
>   unrestricted SGs.  If all SGs are restricted for a given
> destination,
> the
>   ASP should load-share across the available SGs and ignore the
> restricted
>   status.
>
>   If some SG are prohibited for the specified destination (based on
> received
>   DUNA messages from the SG), the ASP should load-share across the
> available
>   non-prohibited SGs.  If all SGs are prohibited for a given
> destination
> (or
>   no SGP is active for the AS/RC/RK in any SG), the ASP should respond
> to the
>   MTP-User with an MTP-PAUSE in accordance with the style of the
> MTP-User
>   interface (ITU-T and ANSI differ here).
>
> Properly selecting SGs requires that the ASP maintain the
> DUNA/DAVA/DRST
> information for each destination received from any SGP in an SG, on a
> per-SG
> basis.  This is the same as MTP Level 3 ROUTE status.  However, SCON
> information should only be maintained on a per-destination basis (and
> not
> per-SG).  This is the same as MTP Level 3 ROUTESET status.
>
> Note that, in general, it is a bad idea to consider congestion (SCON)
> when
> selecting an SG.  SCON does not necessarily indicate
> congestion at an SG
> or on
> a path to an SG, but indicates congestion at the affected
> destination or
> somewhere (perhaps distant) in the SS7 network.  SCON is
> ROUTESET-specific
> (applies to the destination), whereas DUNA/DAVA/DRST is ROUTE-specific
> (applies to the destination and path).  SCON should only be used to
> determine
> whether a message should be dropped completely and an MTP-STATUS
> returned to
> the MTP-User according to the style of the MTP-User interface
> (ITU-T and
> ANSI
> differ here again).
>
> So, to summarize:  on behalf of the AS/RC/RK/MTP-User, the ASP
> determines
> whether to send a message based on SCON received for the specified
> destination, then selects an SG based on DUNA/DAVA/DRST
> received for the
> specified destination and load-shares based on SLS across the eligible
> SGs.
> Once an SG is selected, an active SGP (active for the AS/RC/RK) is
> selected
> within the SG based on the traffic mode of the SG (active/standby,
> load-share,
> broadcast: but typically load-share on SLS).
>
> As I said, there are other schools of thought, but that is my
> understanding.
>
> --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
> Jolan,

> -----Original Message-----
> From: "Jolan Evans" <jolan.evans@opentelecommunications.com>
> Sent: Tuesday, January 28, 2003 10:17 AM
> To: "Sigtran" <sigtran@ietf.org>
> Cc: <bidulock@openss7.org>
> Subject: RE: [Sigtran] M3UA: ASP to SGP communication (Sent by
> sigtran-admin@ietf.org on behalf of "Jolan Evans"
> <jolan.evans@opentelecommunications.com> )
>
>
> I would like to raise a few issues regarding your procedures below for
> ASP to SGP routing. I know this discussion took places a
> while ago, but
> it has taken me some time to come up to speed with the RFC as I have
> been busy on other things until recently.
>
> Please note that I have inserted "M3UA" into the subject line of the
> original email.
>
>
>
> 1. Nomenclature
> AsPc: Point code of an AS. In defining routing keys, the RFC uses DPC
> for this term as it takes the SG's frame of reference.
> RemotePc: Point code of an SS7 MTP entity with which an AS
> communicates
> via an SG, or directly in the case of IPSP-IPSP communication. In
> defining routing keys, the RFC uses OPC for this term as it takes the
> SG's frame of reference again.
>
>
>
> 2. Background Assumptions
> As per Brian's introduction, we assume that zero or more
> MTP-User's are
> bound to an MTP-SAP. The MTP-SAP exists in a particular MTP-Network,
> which has a particular MTP protocol variant. An SG is
> associated with a
> single MTP-Network. A RK is defined as in the RFC, but, for
> clarity, is
> independent of any SG and associated with a single MTP-Network. An
> SgRouteSet is uniquely defined by an RK, an SG and an MTP-SAP (the RK
> and SG must be both associated with the same MTP-Network) and also
> specifies the network appearance for the MTP-Network to be
> used with the
> SG and the RC of each SGP in the SG. Therefore, an SgRouteSet is
> implicitly associated with a single MTP-Network. An MTP-SAP is
> associated with zero or more SgRouteSet's and therefore an MTP-SAP is
> associated with zero or more RKs. In contrast, it appears that Brian
> assumes that an MTP-SAP can only be associated with one RK. Given this
> extension, we have the following requirement.
>
>
>
> 3. Routing Keys Requirements to Support Unique SS7 Destination Status
> Let RemotePcSet(Rk) be the set of RemotePc's reachable via the SG from
> the ASP where the RK is defined.
> Consider any two SgRouteSet's SgRsA and SgRsA which are
> associated with
> the same MTP-SAP.
> Let the routing key of SgRsA and SgRsB be RkA and RkB respectively.
> If the intersection of RemotePcSet(RkA) and RemotePcSet(RkB)
> is non-nil
> then the routing keys MUST be identical in every respect apart from
> their RemotePcSet.
> If this wasn't the case, an ASP could never indicate an
> MTP-RESUME to an
> MTP-USER because an MTP-RESUME can only specify a RemotePc
> and no other
> SS7 element. I assume here for simplicity that every MTP-User of a
> MTP-SAP must be given the same MTP status (i.e. different MTP-Users of
> the same MTP-SAP cannot be given different MTP-Status indications
> depending on what traffic they have requested).
>
> Here's a concrete example of why this is so. Consider an ASP with the
> following routing keys:
> RkA: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={A}
> RkB: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={B}
> RkC: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={M}
> RkD: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={N}
>
> Assume that RkA and RkB were both active in SgpA and SgpB respectively
> and are associated with the same MTP-SAP, but different SGs.
> Also assume
> that a DAVA has been received for RemotePc=X from SgpA after
> a DUNA from
> SgpB for the same RemotePc. We might consider generating an MTP-Resume
> to all the MTP-Users of the MTP-SAP for RemotePc X. However, if an
> MTP-User requests an MTP-Transfer with an AsPc of B then SgpB
> may not be
> able to transfer it as indicated by the DUNA it sent the ASP.
>
> The same explanation applies to RkC and RkD.
>
> In practice this requirement probably won't cause too many headaches
> because it is likely that there would be two different MTP-Users, one
> using only RkA/RkC and the other using only RkB/RkD. In this case, we
> can simply create two MTP-SAPs in the same MTP-Network and associate
> each routing key with a different MTP-SAP. Of course, this
> would require
> the M3UA implementation to support more than one MTP-SAP per
> MTP-Network, which would be extra work obviously.
[TOLGA] IMO there is no problem. It might be extra work but people are free
to support such a configuration or not. In your example, most probably
there should be two different user part entities processing messages for
RkA and RkB respectively. Each of them will only primitives related with
them, i.e. primitives which are caused by messages arrived for the
corresponding RK.
(BTW your RkC and RkD are invalid because they don´t contain DPC field)
>
>
>
> 4. ASP-SGP Routing should use SS7 Destination Availability/Restricted
> Status on a per-SGP rather than a per-SG basis.
>
> I believe your ASP-SGP procedures should be amended (I only amend the
> multiple SG case as the single SG case is a special case of
> the former)
> as follows:
>
> Change:
> "This routing information is updated by collecting DUNA/DAVA/DRST
> messages received from (any of the SGP in) the SG."
> To:
> "This routing information is updated by collecting DUNA/DAVA/DRST
> information on a per-(SGP,destination) basis. An SG is
> considered to be
> available and unrestricted for a particular destination if
> any SGP in it
> is available and unrestricted for that destination. Otherwise
> if this is
> not he case, then an SG is considered to be restricted for a
> particular
> destination if there is at least one SGP in the SG restricted for that
> destination. Otherwise if this is not the case, the SG is
> considered to
> be prohibited for that destination."
>
> The RFC is not particular clear on this point. In section 1.4.1 para 3
> it states that "MTP3 routeset, SPMC and remote AS/ASP states
> of each SGP
> SHOULD be coordinated across all the SGPs". However, this
> uses "SHOULD"
> which implies it is only recommended and it also doesn't specifically
> state that SS7 destination availability, restriction and congestion
> status ("SS7 destination status" for short) should be
> coordinated across
> all SGPs. I don't think that "MTP3 routeset" necessarily implies SS7
> destination status. Also, in section 1.3.2.5 1.4.2.5 it suggests in
> should be on a per-SGP basis. Section 4.5.2.2 uses the word "SG" but
> also uses the term "affected route(s)". Section 1.3.2.5 and section
> 1.4.2.5 suggest the word "route" refers to an SGP and not an
> SG. Hence,
> given the ambiguity of section 4.5.2.2 I think that route can be
> considered to refer to an SGP.
>
> A configuration where per-SGP SS7 destination status is
> necessary is as
> follows. Consider an SEP SG which has two SGP's acting as a redundant
> pair. Each SGP has it's own link set to a particular STP. While in
> section 1.4.1 para 3 it states that "Rerouting of traffic between the
> SGPs MAY also be supported", it uses "MAY" and hence this is optional.
> If one link set fails but not the other, one SGP will be able to reach
> the SS7 network but not the other if rerouting between SGPs is not
> supported or the rerouting link has also failed. Hence, it would be
> possible for one SGP to send a DUNA for a particular
> destination but not
> the other.
[TOLGA] Again I don´t see a problem. I only agree that "MAY" in the
sentence you refer was better changed to a "SHOULD". If somebody thinks
that creating a unique layer3 view among SGPs belonging to the same SG is
hard to implement/not necessary, then it is possible to have SGs consisting
of one SGP, without violating the protocol. In that case, SSNM will be
received separetly from each SGP, because they belong to different SGs.
>
>
> Your feedback would be appreciated.
>
> Jolan.
>
>
> --
> Jolan Evans
> Open Telecommunications
> jolan.evans@opentelecommunications.com
>
>
> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org] On Behalf
> Of Brian F. G. Bidulock
> Sent: Tuesday, 8 October 2002 17:47
> To: Srikanth Yandapalli
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] ASP to SGP communication
>
> Srikanth,
>
> Srikanth Yandapalli wrote:               (Tue, 08 Oct 2002 12:03:52)
> >
> >    I am late entrant to this group.I am quite sure all this should
> have
> >    been discussed and I am sorry about this.
>
> Welcome.
>
> >
> >    In the context of a single ASP in communication with
> multiple SGPs,
> >    how should the routing of a MTP_DATA_REQ take place at the ASP?
>
> I assume you are talking about M3UA?  As we are dealing with 5 or more
> UAs
> now, in the future it would be helpful to add M3UA (or
> whichever) to the
> subject line.
>
> >
> >    approach 1:
> >
> >    We may find out the  RK and find out the SGP list that the RK is
> >    active on and choose one SGP for sending the message based
> >    on congestion level and also whether we have received any DRST
> >    message from any of the SGPs.
>
> This approach is applicable to multiple SGs, but not to multiple SGPs
> within a
> single SG.
>
> >    approach 2:
> >
> >    An SGP can also be viewed as providing route to a set of DPCs
> >    and the routing can be based on the DPC for the message alone.
> >    This approach is reduces the complexity but adds a situation
> >    where the RK may not be active on that association. And also is
> >    is mandatory to send RC on this association and if so what could
> >    the SGP make out of the RC?
>
> RC should be coordinated and the same across multiple SGPs
> within an SG.
>
> >
> >    Is there a preferred approach to this issue?
> >
>
> Typically, the logic can be something like this: (but there
> are several
> other
> schools of thought):
>
> Single SG case: (multiple SGs is more complicated)
>
>   MTP-TRANSFER request is issued by an MTP-User.  The
> MTP-User is bound
> to an
>   MTP-SAP.  The MTP-SAP is associated with an AS/RC/RK.
> There is a pool
> of
>   SGPs on an SG for which the AS/RC/RK is active.  The AS may have
> received
>   MTP-PAUSE/RESUME/STATUS indications from the SG and may choose to
> honor that
>   information or not.  If the ASP chooses not to honor this
> information
> it can
>   blindly send messages to the SGP and rely upon a DUNA/SCON response
> from the
>   SGP later.
>
>   Selection of an SGP within an SG is based on the traffic
> mode for the
> SGP.
>   This traffic mode is not managed by M3UA, however, M3UA provides for
>   distribution of traffic over SGP based on any of the
> methods described
> for
>   ASPs (active/standby, load-share, broadcast).  A typical method is
>   load-share based on SLS.  In this scheme, using the SLS in the
> MTP-TRANSFER
>   request, the ASP selects load-shares traffic over the available SGP.
>
> Multiple SG case:
>
>   In the more complicated multiple SG case, the ASP must
> first select an
> SG
>   before it selects an SGP within the SG.  The ASP must maintain some
>   additional routing information to be able to properly select an SG.
> This
>   routing information is updated by collecting DUNA/DAVA/DRST messages
>   received from (any of the SGP in) the SG.  To select the
> outgoing SG,
> the
>   ASP must examine the destination of the MTP-TRANSFER request.
>
>   (If the SG has no SGP active for the AS/RC/RK, all
> destinations can be
>   considered prohibited).
>
>   If the destination is available and unrestricted for
> several SGs, the
> ASP
>   should select an SG on a load-sharing basis (based on SLS) and then
> select
>   an active SGP within the SG on the basis of the traffic mode for the
> SG.
>
>   If some SG are restricted for the specified destination (based on
> received
>   DRST messages from the SG), the ASP should load-share across the
> available
>   unrestricted SGs.  If all SGs are restricted for a given
> destination,
> the
>   ASP should load-share across the available SGs and ignore the
> restricted
>   status.
>
>   If some SG are prohibited for the specified destination (based on
> received
>   DUNA messages from the SG), the ASP should load-share across the
> available
>   non-prohibited SGs.  If all SGs are prohibited for a given
> destination
> (or
>   no SGP is active for the AS/RC/RK in any SG), the ASP should respond
> to the
>   MTP-User with an MTP-PAUSE in accordance with the style of the
> MTP-User
>   interface (ITU-T and ANSI differ here).
>
> Properly selecting SGs requires that the ASP maintain the
> DUNA/DAVA/DRST
> information for each destination received from any SGP in an SG, on a
> per-SG
> basis.  This is the same as MTP Level 3 ROUTE status.  However, SCON
> information should only be maintained on a per-destination basis (and
> not
> per-SG).  This is the same as MTP Level 3 ROUTESET status.
>
> Note that, in general, it is a bad idea to consider congestion (SCON)
> when
> selecting an SG.  SCON does not necessarily indicate
> congestion at an SG
> or on
> a path to an SG, but indicates congestion at the affected
> destination or
> somewhere (perhaps distant) in the SS7 network.  SCON is
> ROUTESET-specific
> (applies to the destination), whereas DUNA/DAVA/DRST is ROUTE-specific
> (applies to the destination and path).  SCON should only be used to
> determine
> whether a message should be dropped completely and an MTP-STATUS
> returned to
> the MTP-User according to the style of the MTP-User interface
> (ITU-T and
> ANSI
> differ here again).
>
> So, to summarize:  on behalf of the AS/RC/RK/MTP-User, the ASP
> determines
> whether to send a message based on SCON received for the specified
> destination, then selects an SG based on DUNA/DAVA/DRST
> received for the
> specified destination and load-shares based on SLS across the eligible
> SGs.
> Once an SG is selected, an active SGP (active for the AS/RC/RK) is
> selected
> within the SG based on the traffic mode of the SG (active/standby,
> load-share,
> broadcast: but typically load-share on SLS).
>
> As I said, there are other schools of thought, but that is my
> understanding.
>
> --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
> Jolan,

> -----Original Message-----
> From: "Jolan Evans" <jolan.evans@opentelecommunications.com>
> Sent: Tuesday, January 28, 2003 10:17 AM
> To: "Sigtran" <sigtran@ietf.org>
> Cc: <bidulock@openss7.org>
> Subject: RE: [Sigtran] M3UA: ASP to SGP communication (Sent by
> sigtran-admin@ietf.org on behalf of "Jolan Evans"
> <jolan.evans@opentelecommunications.com> )
>
>
> I would like to raise a few issues regarding your procedures below for
> ASP to SGP routing. I know this discussion took places a
> while ago, but
> it has taken me some time to come up to speed with the RFC as I have
> been busy on other things until recently.
>
> Please note that I have inserted "M3UA" into the subject line of the
> original email.
>
>
>
> 1. Nomenclature
> AsPc: Point code of an AS. In defining routing keys, the RFC uses DPC
> for this term as it takes the SG's frame of reference.
> RemotePc: Point code of an SS7 MTP entity with which an AS
> communicates
> via an SG, or directly in the case of IPSP-IPSP communication. In
> defining routing keys, the RFC uses OPC for this term as it takes the
> SG's frame of reference again.
>
>
>
> 2. Background Assumptions
> As per Brian's introduction, we assume that zero or more
> MTP-User's are
> bound to an MTP-SAP. The MTP-SAP exists in a particular MTP-Network,
> which has a particular MTP protocol variant. An SG is
> associated with a
> single MTP-Network. A RK is defined as in the RFC, but, for
> clarity, is
> independent of any SG and associated with a single MTP-Network. An
> SgRouteSet is uniquely defined by an RK, an SG and an MTP-SAP (the RK
> and SG must be both associated with the same MTP-Network) and also
> specifies the network appearance for the MTP-Network to be
> used with the
> SG and the RC of each SGP in the SG. Therefore, an SgRouteSet is
> implicitly associated with a single MTP-Network. An MTP-SAP is
> associated with zero or more SgRouteSet's and therefore an MTP-SAP is
> associated with zero or more RKs. In contrast, it appears that Brian
> assumes that an MTP-SAP can only be associated with one RK. Given this
> extension, we have the following requirement.
>
>
>
> 3. Routing Keys Requirements to Support Unique SS7 Destination Status
> Let RemotePcSet(Rk) be the set of RemotePc's reachable via the SG from
> the ASP where the RK is defined.
> Consider any two SgRouteSet's SgRsA and SgRsA which are
> associated with
> the same MTP-SAP.
> Let the routing key of SgRsA and SgRsB be RkA and RkB respectively.
> If the intersection of RemotePcSet(RkA) and RemotePcSet(RkB)
> is non-nil
> then the routing keys MUST be identical in every respect apart from
> their RemotePcSet.
> If this wasn't the case, an ASP could never indicate an
> MTP-RESUME to an
> MTP-USER because an MTP-RESUME can only specify a RemotePc
> and no other
> SS7 element. I assume here for simplicity that every MTP-User of a
> MTP-SAP must be given the same MTP status (i.e. different MTP-Users of
> the same MTP-SAP cannot be given different MTP-Status indications
> depending on what traffic they have requested).
>
> Here's a concrete example of why this is so. Consider an ASP with the
> following routing keys:
> RkA: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={A}
> RkB: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={B}
> RkC: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={M}
> RkD: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={N}
>
> Assume that RkA and RkB were both active in SgpA and SgpB respectively
> and are associated with the same MTP-SAP, but different SGs.
> Also assume
> that a DAVA has been received for RemotePc=X from SgpA after
> a DUNA from
> SgpB for the same RemotePc. We might consider generating an MTP-Resume
> to all the MTP-Users of the MTP-SAP for RemotePc X. However, if an
> MTP-User requests an MTP-Transfer with an AsPc of B then SgpB
> may not be
> able to transfer it as indicated by the DUNA it sent the ASP.
>
> The same explanation applies to RkC and RkD.
>
> In practice this requirement probably won't cause too many headaches
> because it is likely that there would be two different MTP-Users, one
> using only RkA/RkC and the other using only RkB/RkD. In this case, we
> can simply create two MTP-SAPs in the same MTP-Network and associate
> each routing key with a different MTP-SAP. Of course, this
> would require
> the M3UA implementation to support more than one MTP-SAP per
> MTP-Network, which would be extra work obviously.
[TOLGA] IMO there is no problem. It might be extra work but people are free
to support such a configuration or not. In your example, most probably
there should be two different user part entities processing messages for
RkA and RkB respectively. Each of them will receive only primitives related
with them, i.e. primitives which are caused by messages arrived for the
corresponding RK.
(BTW your RkC and RkD are invalid because they don´t contain DPC field)
>
>
>
> 4. ASP-SGP Routing should use SS7 Destination Availability/Restricted
> Status on a per-SGP rather than a per-SG basis.
>
> I believe your ASP-SGP procedures should be amended (I only amend the
> multiple SG case as the single SG case is a special case of
> the former)
> as follows:
>
> Change:
> "This routing information is updated by collecting DUNA/DAVA/DRST
> messages received from (any of the SGP in) the SG."
> To:
> "This routing information is updated by collecting DUNA/DAVA/DRST
> information on a per-(SGP,destination) basis. An SG is
> considered to be
> available and unrestricted for a particular destination if
> any SGP in it
> is available and unrestricted for that destination. Otherwise
> if this is
> not he case, then an SG is considered to be restricted for a
> particular
> destination if there is at least one SGP in the SG restricted for that
> destination. Otherwise if this is not the case, the SG is
> considered to
> be prohibited for that destination."
>
> The RFC is not particular clear on this point. In section 1.4.1 para 3
> it states that "MTP3 routeset, SPMC and remote AS/ASP states
> of each SGP
> SHOULD be coordinated across all the SGPs". However, this
> uses "SHOULD"
> which implies it is only recommended and it also doesn't specifically
> state that SS7 destination availability, restriction and congestion
> status ("SS7 destination status" for short) should be
> coordinated across
> all SGPs. I don't think that "MTP3 routeset" necessarily implies SS7
> destination status. Also, in section 1.3.2.5 1.4.2.5 it suggests in
> should be on a per-SGP basis. Section 4.5.2.2 uses the word "SG" but
> also uses the term "affected route(s)". Section 1.3.2.5 and section
> 1.4.2.5 suggest the word "route" refers to an SGP and not an
> SG. Hence,
> given the ambiguity of section 4.5.2.2 I think that route can be
> considered to refer to an SGP.
>
> A configuration where per-SGP SS7 destination status is
> necessary is as
> follows. Consider an SEP SG which has two SGP's acting as a redundant
> pair. Each SGP has it's own link set to a particular STP. While in
> section 1.4.1 para 3 it states that "Rerouting of traffic between the
> SGPs MAY also be supported", it uses "MAY" and hence this is optional.
> If one link set fails but not the other, one SGP will be able to reach
> the SS7 network but not the other if rerouting between SGPs is not
> supported or the rerouting link has also failed. Hence, it would be
> possible for one SGP to send a DUNA for a particular
> destination but not
> the other.
[TOLGA] Personally again I don´t see a problem. I only agree that "MAY" in
the sentence you refer was better changed to a "SHOULD". If somebody thinks
that creating a unique layer3 view among SGPs belonging to the same SG is
hard to implement/not necessary, then it is possible to have SGs consisting
of one SGP, without violating the protocol. In that case, SSNM will be
received separetly from each SGP, because they belong to different SGs.
>
>
> Your feedback would be appreciated.
>
> Jolan.
>
>
> --
> Jolan Evans
> Open Telecommunications
> jolan.evans@opentelecommunications.com
>
>
> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org] On Behalf
> Of Brian F. G. Bidulock
> Sent: Tuesday, 8 October 2002 17:47
> To: Srikanth Yandapalli
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] ASP to SGP communication
>
> Srikanth,
>
> Srikanth Yandapalli wrote:               (Tue, 08 Oct 2002 12:03:52)
> >
> >    I am late entrant to this group.I am quite sure all this should
> have
> >    been discussed and I am sorry about this.
>
> Welcome.
>
> >
> >    In the context of a single ASP in communication with
> multiple SGPs,
> >    how should the routing of a MTP_DATA_REQ take place at the ASP?
>
> I assume you are talking about M3UA?  As we are dealing with 5 or more
> UAs
> now, in the future it would be helpful to add M3UA (or
> whichever) to the
> subject line.
>
> >
> >    approach 1:
> >
> >    We may find out the  RK and find out the SGP list that the RK is
> >    active on and choose one SGP for sending the message based
> >    on congestion level and also whether we have received any DRST
> >    message from any of the SGPs.
>
> This approach is applicable to multiple SGs, but not to multiple SGPs
> within a
> single SG.
>
> >    approach 2:
> >
> >    An SGP can also be viewed as providing route to a set of DPCs
> >    and the routing can be based on the DPC for the message alone.
> >    This approach is reduces the complexity but adds a situation
> >    where the RK may not be active on that association. And also is
> >    is mandatory to send RC on this association and if so what could
> >    the SGP make out of the RC?
>
> RC should be coordinated and the same across multiple SGPs
> within an SG.
>
> >
> >    Is there a preferred approach to this issue?
> >
>
> Typically, the logic can be something like this: (but there
> are several
> other
> schools of thought):
>
> Single SG case: (multiple SGs is more complicated)
>
>   MTP-TRANSFER request is issued by an MTP-User.  The
> MTP-User is bound
> to an
>   MTP-SAP.  The MTP-SAP is associated with an AS/RC/RK.
> There is a pool
> of
>   SGPs on an SG for which the AS/RC/RK is active.  The AS may have
> received
>   MTP-PAUSE/RESUME/STATUS indications from the SG and may choose to
> honor that
>   information or not.  If the ASP chooses not to honor this
> information
> it can
>   blindly send messages to the SGP and rely upon a DUNA/SCON response
> from the
>   SGP later.
>
>   Selection of an SGP within an SG is based on the traffic
> mode for the
> SGP.
>   This traffic mode is not managed by M3UA, however, M3UA provides for
>   distribution of traffic over SGP based on any of the
> methods described
> for
>   ASPs (active/standby, load-share, broadcast).  A typical method is
>   load-share based on SLS.  In this scheme, using the SLS in the
> MTP-TRANSFER
>   request, the ASP selects load-shares traffic over the available SGP.
>
> Multiple SG case:
>
>   In the more complicated multiple SG case, the ASP must
> first select an
> SG
>   before it selects an SGP within the SG.  The ASP must maintain some
>   additional routing information to be able to properly select an SG.
> This
>   routing information is updated by collecting DUNA/DAVA/DRST messages
>   received from (any of the SGP in) the SG.  To select the
> outgoing SG,
> the
>   ASP must examine the destination of the MTP-TRANSFER request.
>
>   (If the SG has no SGP active for the AS/RC/RK, all
> destinations can be
>   considered prohibited).
>
>   If the destination is available and unrestricted for
> several SGs, the
> ASP
>   should select an SG on a load-sharing basis (based on SLS) and then
> select
>   an active SGP within the SG on the basis of the traffic mode for the
> SG.
>
>   If some SG are restricted for the specified destination (based on
> received
>   DRST messages from the SG), the ASP should load-share across the
> available
>   unrestricted SGs.  If all SGs are restricted for a given
> destination,
> the
>   ASP should load-share across the available SGs and ignore the
> restricted
>   status.
>
>   If some SG are prohibited for the specified destination (based on
> received
>   DUNA messages from the SG), the ASP should load-share across the
> available
>   non-prohibited SGs.  If all SGs are prohibited for a given
> destination
> (or
>   no SGP is active for the AS/RC/RK in any SG), the ASP should respond
> to the
>   MTP-User with an MTP-PAUSE in accordance with the style of the
> MTP-User
>   interface (ITU-T and ANSI differ here).
>
> Properly selecting SGs requires that the ASP maintain the
> DUNA/DAVA/DRST
> information for each destination received from any SGP in an SG, on a
> per-SG
> basis.  This is the same as MTP Level 3 ROUTE status.  However, SCON
> information should only be maintained on a per-destination basis (and
> not
> per-SG).  This is the same as MTP Level 3 ROUTESET status.
>
> Note that, in general, it is a bad idea to consider congestion (SCON)
> when
> selecting an SG.  SCON does not necessarily indicate
> congestion at an SG
> or on
> a path to an SG, but indicates congestion at the affected
> destination or
> somewhere (perhaps distant) in the SS7 network.  SCON is
> ROUTESET-specific
> (applies to the destination), whereas DUNA/DAVA/DRST is ROUTE-specific
> (applies to the destination and path).  SCON should only be used to
> determine
> whether a message should be dropped completely and an MTP-STATUS
> returned to
> the MTP-User according to the style of the MTP-User interface
> (ITU-T and
> ANSI
> differ here again).
>
> So, to summarize:  on behalf of the AS/RC/RK/MTP-User, the ASP
> determines
> whether to send a message based on SCON received for the specified
> destination, then selects an SG based on DUNA/DAVA/DRST
> received for the
> specified destination and load-shares based on SLS across the eligible
> SGs.
> Once an SG is selected, an active SGP (active for the AS/RC/RK) is
> selected
> within the SG based on the traffic mode of the SG (active/standby,
> load-share,
> broadcast: but typically load-share on SLS).
>
> As I said, there are other schools of thought, but that is my
> understanding.
>
> --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
>

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



From mailnull@www1.ietf.org  Wed Jan 29 04:50: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 EAA14300
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 04:50:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0TABsu12048
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 05:11:54 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TABAJ12022;
	Wed, 29 Jan 2003 05:11:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TAAVJ11988
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 05:10:31 -0500
Received: from cbibipnt08.hc.bt.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14253
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 04:48:38 -0500 (EST)
From: karen.d.king@bt.com
Received: by cbibipnt08.hc.bt.com with Internet Mail Service (5.5.2654.89)
	id <D58VJPVS>; Wed, 29 Jan 2003 09:51:36 -0000
Message-ID: <B1F38D7B53615140BCEA6677DF9F2F8C579C24@i2km11-ukbr.domain1.systemhost.net>
To: Tom.George@alcatel.com
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M2PA Draft 7 comment
Date: Wed, 29 Jan 2003 09:51:13 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.89)
content-class: urn:content-classes:message
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 Tom,

Thanks, this looks better. One further thought -  data retrieval is only
appropriate for a very short time (or else you end up with 'stale'
information). Do we need a note to cover this, or is this sufficiently
covered else where?

On my other comment - if the correct use of processor outage is well
understood (and the spec leaves no room for misunderstanding) then I'm
happy.

Regards,

Karen

-----Original Message-----
From: Tom George [mailto:Tom.George@alcatel.com]
Sent: 29 January 2003 00:34
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA Draft 7 comment


Here is the new section after moving the paragraphs around (Karen's 1st
comment). I also moved the paragraph after, since they go together.

==========================================================
4.1.4 Processor Outage

A processor outage occurs when M2PA cannot transfer messages because
of a condition at a higher layer than M2PA.

When M2PA detects a local processor outage, it sends a Link Status
message to its peer with status Processor Outage. M2PA SHALL also
cease sending User Data messages to SCTP for transmission. M2PA SHALL
stop acknowledging received User Data messages.

M2PA MAY send additional Link Status Processor Outage messages as long
as there is a local processor outage and the link is in service. If
the link is out of service, M2PA SHOULD locally mark that it is in
local processor outage.

The peer M2PA, upon receiving the Link Status Processor Outage
message, SHALL report Remote Processor Outage to its MTP3. The peer
M2PA ceases sending User Data messages. M2PA stops the Remote
Congestion timer T6 (see section 4.1.5 Level 2 Flow Control) if it is
running, and timer T7, if it is running.

When the processor outage ceases, MTP3 sends a Local Processor
Recovered indication to M2PA. The local M2PA notifies its peer by
sending a Link Status message with status Processor Outage Ended. The
local M2PA SHALL resume receiving and transmitting messages.

[moved]
MTP3 may send a Flush Buffers or Continue command to M2PA as part of
its processor outage procedure (See section 4.2.4 Flush Buffers and
Continue). The use of Flush Buffers and Continue is specified in Q.703
[Q.703] and T1.111.3 [T1.111].

[moved]
Alternatively, MTP3 may perform data retrieval as part of a changeover
procedure.

If the peer is in the IN SERVICE state, it uses the Remote Processor
Recovered Indication to notify its MTP3 that the remote processor
outage condition has ceased.
==========================================================


-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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  Wed Jan 29 05:06: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 FAA14654
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 05:06:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0TARgk12625
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 05:27:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TAQrJ12583;
	Wed, 29 Jan 2003 05:26:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TAPUJ12505
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 05:25:30 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14598
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 05:03:36 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:UA3QZSmLOb6l6ZVwjmVnUoJCTx3pN+b8@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0TA77D08652;
	Wed, 29 Jan 2003 03:07:07 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0TA76s13121;
	Wed, 29 Jan 2003 03:07:06 -0700
Date: Wed, 29 Jan 2003 03:07:06 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: karen.d.king@bt.com
Cc: Tom.George@alcatel.com, sigtran@ietf.org
Subject: Re: [Sigtran] M2PA Draft 7 comment
Message-ID: <20030129030706.A12923@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: karen.d.king@bt.com, Tom.George@alcatel.com,
	sigtran@ietf.org
References: <B1F38D7B53615140BCEA6677DF9F2F8C579C24@i2km11-ukbr.domain1.systemhost.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <B1F38D7B53615140BCEA6677DF9F2F8C579C24@i2km11-ukbr.domain1.systemhost.net>; from karen.d.king@bt.com on Wed, Jan 29, 2003 at 09:51:13AM -0000
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>

Karen,

karen.d.king@bt.com wrote:                                                    (Wed, 29 Jan 2003 09:51:13)
> Hi Tom,
> 
> Thanks, this looks better. One further thought -  data retrieval is only
> appropriate for a very short time (or else you end up with 'stale'
> information). Do we need a note to cover this, or is this sufficiently
> covered else where?

Handling of stale information in retrieval buffers is handled by normal MTP
Level 3 procedures (buffer flushing).  Level 2 keeps data for retrieval until
it is either retrieved by Level 3 or it is told to flush such information by
Level 3.  Addressing Level 3 procedures is out of scope for M2PA.  It is
sufficient that M2PA provides the same upper boundary to MTP Level 3 as is
provided by a normal signalling link.  This includes retrieval_requiest_and-
_fsnc and flush_buffers, resume, clear_rtb signals.

--brian

> 
> On my other comment - if the correct use of processor outage is well
> understood (and the spec leaves no room for misunderstanding) then I'm
> happy.
> 
> Regards,
> 
> Karen
> 
> -----Original Message-----
> From: Tom George [mailto:Tom.George@alcatel.com]
> Sent: 29 January 2003 00:34
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] M2PA Draft 7 comment
> 
> 
> Here is the new section after moving the paragraphs around (Karen's 1st
> comment). I also moved the paragraph after, since they go together.
> 
> ==========================================================
> 4.1.4 Processor Outage
> 
> A processor outage occurs when M2PA cannot transfer messages because
> of a condition at a higher layer than M2PA.
> 
> When M2PA detects a local processor outage, it sends a Link Status
> message to its peer with status Processor Outage. M2PA SHALL also
> cease sending User Data messages to SCTP for transmission. M2PA SHALL
> stop acknowledging received User Data messages.
> 
> M2PA MAY send additional Link Status Processor Outage messages as long
> as there is a local processor outage and the link is in service. If
> the link is out of service, M2PA SHOULD locally mark that it is in
> local processor outage.
> 
> The peer M2PA, upon receiving the Link Status Processor Outage
> message, SHALL report Remote Processor Outage to its MTP3. The peer
> M2PA ceases sending User Data messages. M2PA stops the Remote
> Congestion timer T6 (see section 4.1.5 Level 2 Flow Control) if it is
> running, and timer T7, if it is running.
> 
> When the processor outage ceases, MTP3 sends a Local Processor
> Recovered indication to M2PA. The local M2PA notifies its peer by
> sending a Link Status message with status Processor Outage Ended. The
> local M2PA SHALL resume receiving and transmitting messages.
> 
> [moved]
> MTP3 may send a Flush Buffers or Continue command to M2PA as part of
> its processor outage procedure (See section 4.2.4 Flush Buffers and
> Continue). The use of Flush Buffers and Continue is specified in Q.703
> [Q.703] and T1.111.3 [T1.111].
> 
> [moved]
> Alternatively, MTP3 may perform data retrieval as part of a changeover
> procedure.
> 
> If the peer is in the IN SERVICE state, it uses the Remote Processor
> Recovered Indication to notify its MTP3 that the remote processor
> outage condition has ceased.
> ==========================================================
> 
> 
> -- 
> * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> * Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
> * 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

-- 
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 Jan 29 05:45:19 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 FAA15388
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 05:45:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0TB6gj14969
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 06:06:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TB6GJ14950;
	Wed, 29 Jan 2003 06:06:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TB5mJ14921
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 06:05:48 -0500
Received: from chuckie.dgms.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15361
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 05:43:53 -0500 (EST)
Received: from navy.fr.ulticom.com (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with ESMTP id FAA20421
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 05:47:23 -0500 (EST)
Received: from PCGASTAUDL (pc-gastaud-l.fr.ulticom.com [172.26.32.87])
	by navy.fr.ulticom.com (8.11.6+Sun/8.11.6) with SMTP id h0TAlBL18344
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 11:47:11 +0100 (MET)
From: "Valerie Gastaud" <valerie.gastaud@ulticom.com>
To: "Sigtran" <sigtran@ietf.org>
Date: Wed, 29 Jan 2003 12:12:31 +0100
Message-ID: <NDBBIHAOCKGAMIKNLALOKEIADKAA.valerie.gastaud@ulticom.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.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] SUA - NTT
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


As far as I know, NTT SCCP does not have SSN management but GTT management.
The equivalent SUA messages are not supported in SUA draft 14.  I think this
would require the addition of a new GT parameter to the DUNA/DAVA messages.
If there is an NTT SCCP expert on the list, please confirm.

Valerie

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



From mailnull@www1.ietf.org  Wed Jan 29 05:55: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 FAA15637
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 05:55:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0TBGf816016
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 06:16:41 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TBGHJ15994;
	Wed, 29 Jan 2003 06:16:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TBFwJ15964
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 06:15:58 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15596
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 05:54:03 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:n9RmNL4S+261roX4sP458T21rrghPk1W@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0TAvYD09322;
	Wed, 29 Jan 2003 03:57:34 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0TAvYu14193;
	Wed, 29 Jan 2003 03:57:34 -0700
Date: Wed, 29 Jan 2003 03:57:34 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Valerie Gastaud <valerie.gastaud@ulticom.com>
Cc: Sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA - NTT
Message-ID: <20030129035734.A14097@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Valerie Gastaud <valerie.gastaud@ulticom.com>,
	Sigtran <sigtran@ietf.org>
References: <NDBBIHAOCKGAMIKNLALOKEIADKAA.valerie.gastaud@ulticom.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: <NDBBIHAOCKGAMIKNLALOKEIADKAA.valerie.gastaud@ulticom.com>; from valerie.gastaud@ulticom.com on Wed, Jan 29, 2003 at 12:12:31PM +0100
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>

Valerie,

Last I checked TTC didn't have any SCCP management whatsoever.

--brian

Valerie Gastaud wrote:                             (Wed, 29 Jan 2003 12:12:31)
> 
> As far as I know, NTT SCCP does not have SSN management but GTT management.
> The equivalent SUA messages are not supported in SUA draft 14.  I think this
> would require the addition of a new GT parameter to the DUNA/DAVA messages.
> If there is an NTT SCCP expert on the list, please confirm.
> 
> Valerie
> 
> _______________________________________________
> 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 Jan 29 06:01: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 GAA15751
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 06:01:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0TBMlA16287
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 06:22:47 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TBM8J16250;
	Wed, 29 Jan 2003 06:22:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TBLnJ16227
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 06:21:49 -0500
Received: from chuckie.dgms.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15710
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 05:59:54 -0500 (EST)
Received: from navy.fr.ulticom.com (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with ESMTP id GAA21492;
	Wed, 29 Jan 2003 06:03:24 -0500 (EST)
Received: from PCGASTAUDL (pc-gastaud-l.fr.ulticom.com [172.26.32.87])
	by navy.fr.ulticom.com (8.11.6+Sun/8.11.6) with SMTP id h0TB3CL18729;
	Wed, 29 Jan 2003 12:03:13 +0100 (MET)
From: "Valerie Gastaud" <valerie.gastaud@ulticom.com>
To: <bidulock@openss7.org>
Cc: "Sigtran" <sigtran@ietf.org>
Subject: RE: [Sigtran] SUA - NTT
Date: Wed, 29 Jan 2003 12:28:32 +0100
Message-ID: <NDBBIHAOCKGAMIKNLALOCEICDKAA.valerie.gastaud@ulticom.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: <20030129035734.A14097@openss7.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
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

Brian,
this is true for TTC that does not have SCCP management at all but NTT has
Global Title management.
Valerie

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: mercredi 29 janvier 2003 11:58
To: Valerie Gastaud
Cc: Sigtran
Subject: Re: [Sigtran] SUA - NTT


Valerie,

Last I checked TTC didn't have any SCCP management whatsoever.

--brian

Valerie Gastaud wrote:                             (Wed, 29 Jan 2003
12:12:31)
>
> As far as I know, NTT SCCP does not have SSN management but GTT
management.
> The equivalent SUA messages are not supported in SUA draft 14.  I think
this
> would require the addition of a new GT parameter to the DUNA/DAVA
messages.
> If there is an NTT SCCP expert on the list, please confirm.
>
> Valerie
>
> _______________________________________________
> 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 Jan 29 07:43: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 HAA18057
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 07:43:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0TD4VF22496
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 08:04:31 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TD3xJ22475;
	Wed, 29 Jan 2003 08:03:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TD2XJ22392
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 08:02:33 -0500
Received: from cbibipnt08.hc.bt.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18001
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 07:40:35 -0500 (EST)
From: karen.d.king@bt.com
Received: by cbibipnt08.hc.bt.com with Internet Mail Service (5.5.2654.89)
	id <D58VLTBN>; Wed, 29 Jan 2003 12:43:51 -0000
Message-ID: <B1F38D7B53615140BCEA6677DF9F2F8C579C26@i2km11-ukbr.domain1.systemhost.net>
To: bidulock@openss7.org
Cc: Tom.George@alcatel.com, sigtran@ietf.org
Subject: RE: [Sigtran] M2PA Draft 7 comment
Date: Wed, 29 Jan 2003 12:43:25 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.89)
content-class: urn:content-classes:message
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>

Ok - thanks Brian.

Regards,

Karen

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: 29 January 2003 10:07
To: King,KD,Karen,DEN8 KINGKD R
Cc: Tom.George@alcatel.com; sigtran@ietf.org
Subject: Re: [Sigtran] M2PA Draft 7 comment


Karen,

karen.d.king@bt.com wrote:
(Wed, 29 Jan 2003 09:51:13)
> Hi Tom,
> 
> Thanks, this looks better. One further thought -  data retrieval is only
> appropriate for a very short time (or else you end up with 'stale'
> information). Do we need a note to cover this, or is this sufficiently
> covered else where?

Handling of stale information in retrieval buffers is handled by normal MTP
Level 3 procedures (buffer flushing).  Level 2 keeps data for retrieval
until
it is either retrieved by Level 3 or it is told to flush such information by
Level 3.  Addressing Level 3 procedures is out of scope for M2PA.  It is
sufficient that M2PA provides the same upper boundary to MTP Level 3 as is
provided by a normal signalling link.  This includes retrieval_requiest_and-
_fsnc and flush_buffers, resume, clear_rtb signals.

--brian

> 
> On my other comment - if the correct use of processor outage is well
> understood (and the spec leaves no room for misunderstanding) then I'm
> happy.
> 
> Regards,
> 
> Karen
> 
> -----Original Message-----
> From: Tom George [mailto:Tom.George@alcatel.com]
> Sent: 29 January 2003 00:34
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] M2PA Draft 7 comment
> 
> 
> Here is the new section after moving the paragraphs around (Karen's 1st
> comment). I also moved the paragraph after, since they go together.
> 
> ==========================================================
> 4.1.4 Processor Outage
> 
> A processor outage occurs when M2PA cannot transfer messages because
> of a condition at a higher layer than M2PA.
> 
> When M2PA detects a local processor outage, it sends a Link Status
> message to its peer with status Processor Outage. M2PA SHALL also
> cease sending User Data messages to SCTP for transmission. M2PA SHALL
> stop acknowledging received User Data messages.
> 
> M2PA MAY send additional Link Status Processor Outage messages as long
> as there is a local processor outage and the link is in service. If
> the link is out of service, M2PA SHOULD locally mark that it is in
> local processor outage.
> 
> The peer M2PA, upon receiving the Link Status Processor Outage
> message, SHALL report Remote Processor Outage to its MTP3. The peer
> M2PA ceases sending User Data messages. M2PA stops the Remote
> Congestion timer T6 (see section 4.1.5 Level 2 Flow Control) if it is
> running, and timer T7, if it is running.
> 
> When the processor outage ceases, MTP3 sends a Local Processor
> Recovered indication to M2PA. The local M2PA notifies its peer by
> sending a Link Status message with status Processor Outage Ended. The
> local M2PA SHALL resume receiving and transmitting messages.
> 
> [moved]
> MTP3 may send a Flush Buffers or Continue command to M2PA as part of
> its processor outage procedure (See section 4.2.4 Flush Buffers and
> Continue). The use of Flush Buffers and Continue is specified in Q.703
> [Q.703] and T1.111.3 [T1.111].
> 
> [moved]
> Alternatively, MTP3 may perform data retrieval as part of a changeover
> procedure.
> 
> If the peer is in the IN SERVICE state, it uses the Remote Processor
> Recovered Indication to notify its MTP3 that the remote processor
> outage condition has ceased.
> ==========================================================
> 
> 
> -- 
> * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> * Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
> * 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

-- 
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 Jan 29 09:56: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 JAA20729
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 09:56:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0TFHaU32256
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 10:17:36 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TFGrJ32206;
	Wed, 29 Jan 2003 10:16:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TFDZJ32050
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 10:13:36 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20662
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 09:51:30 -0500 (EST)
Subject: Re: [Sigtran] M3UA SG-SG (again)
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF2C1EE7D3.B627A825-ONC2256CBD.0050CBAD@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Wed, 29 Jan 2003 16:51:33 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/29/2003
 04:51:46 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>


Ken,

I will try to answer your questions separetly (BTW in general I agree that
some more sections are probably necessary to explain in more detail SG-SG
procedures, my idea was just to get an initial feedback from the WG and to
see whether it can be moved to charter):
                  4.4.1 Changeover Request Message(COR)

                  COR is used to relay changeover order/emergency
changeover order
                  information to/from a SS7 peer. There are two scenarios,
where it
                  can be used. Either it is received from a peer SG, where
a
                  corresponding COO/ECM is sent to peer SS7 node or it can
be
                  generated to a peer SG, after receiving COO/ECM from a
SS7 node.

                  COR message contains the following parameters:

                  Network Appearance: 32 bits (Semi-mandatory)

                  See M3UA Section 3.1.1


                  SLC :  5 bits (Mandatory)

                  The Signalling Link Code of the failed link.


                  FSN :  24 bits (Semi-mandatory)

[KAM] Where does FSN come from?  Are you going to add FSN to Data messages?
Is
this related to Correlation ID?

[TOLGA]FSN will be taken from COO received from SS7. The idea is not to add
FSN to DATA messages or provide a similar mechanism for communination
between peers in IP domain. The whole purpose of changeover/changeback
related SG-SG messages is to be able to relay corresponding
changeover/chnageback SS7 messages for the case explained in Figure7. In
fact probably this should be emphasized more strongly.



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



From mailnull@www1.ietf.org  Wed Jan 29 15:27: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 PAA28843
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 15:27:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0TKmwf21675
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 15:48:58 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TKmOJ21640;
	Wed, 29 Jan 2003 15:48:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TKkXJ21561
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 15:46:33 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28743
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 15:24:26 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0TKRveW022308;
	Wed, 29 Jan 2003 14:27:58 -0600 (CST)
Message-ID: <3E38394D.8C0BAAEE@alcatel.com>
Date: Wed, 29 Jan 2003 14:27:57 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA Draft 7 comment
References: <B1F38D7B53615140BCEA6677DF9F2F8C579C24@i2km11-ukbr.domain1.systemhost.net> <20030129030706.A12923@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

I agree that it would be out of scope to specify how MTP3 must use flush
or retrieve data. 

The proc outage reminded me of an old question. In ATM links (Q.2140),
there is no processor outage procedure as in Q.703. The link is just
failed when there is a "proc outage". Does anyone know why there is no
Q.703-like proc outage procedure in Q.2140?

tomG.

"Brian F. G. Bidulock" wrote:
> 
> Karen,
> 
> karen.d.king@bt.com wrote:                                                    (Wed, 29 Jan 2003 09:51:13)
> > Hi Tom,
> >
> > Thanks, this looks better. One further thought -  data retrieval is only
> > appropriate for a very short time (or else you end up with 'stale'
> > information). Do we need a note to cover this, or is this sufficiently
> > covered else where?
> 
> Handling of stale information in retrieval buffers is handled by normal MTP
> Level 3 procedures (buffer flushing).  Level 2 keeps data for retrieval until
> it is either retrieved by Level 3 or it is told to flush such information by
> Level 3.  Addressing Level 3 procedures is out of scope for M2PA.  It is
> sufficient that M2PA provides the same upper boundary to MTP Level 3 as is
> provided by a normal signalling link.  This includes retrieval_requiest_and-
> _fsnc and flush_buffers, resume, clear_rtb signals.
> 
> --brian
> 
> >
> > On my other comment - if the correct use of processor outage is well
> > understood (and the spec leaves no room for misunderstanding) then I'm
> > happy.
> >
> > Regards,
> >
> > Karen
  [...]

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 29 15:32:15 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 PAA29005
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 15:32:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0TKrpJ21947
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 15:53:51 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TKr7J21926;
	Wed, 29 Jan 2003 15:53:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TKqmJ21899
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 15:52:48 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28948
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 15:30:41 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0TKYCeW023655;
	Wed, 29 Jan 2003 14:34:12 -0600 (CST)
Message-ID: <3E383AC4.4EA7492E@alcatel.com>
Date: Wed, 29 Jan 2003 14:34:12 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: sigtran@ietf.org
References: <OF602FCCBB.9172BC42-ONC2256CB6.001D3A69@LocalDomain>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M2PA Flush Buffers (was: M2PA version 7 changes)
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,

I am not sure what you are asking. Could you be more specific?

tomG.

TOLGA ASVEREN wrote:
> 
> Tom,
> Is there also a decision about what to do while flushing buffers?
> 
>    Tolga
> 
> _______________________________________________
> 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 USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 29 16:16: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 QAA00111
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 16:16:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0TLcAv25346
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 16:38:10 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TLbOJ25180;
	Wed, 29 Jan 2003 16:37:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TLYwJ24533
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 16:34:58 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00047
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 16:12:48 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:m0E45H149pf5KW8V+dGQtGh4PWRjtdj0@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0TLGKD19950;
	Wed, 29 Jan 2003 14:16:20 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0TLGKR02795;
	Wed, 29 Jan 2003 14:16:20 -0700
Date: Wed, 29 Jan 2003 14:16:20 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tom George <Tom.George@alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA Draft 7 comment
Message-ID: <20030129141620.A2178@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tom George <Tom.George@alcatel.com>, sigtran@ietf.org
References: <B1F38D7B53615140BCEA6677DF9F2F8C579C24@i2km11-ukbr.domain1.systemhost.net> <20030129030706.A12923@openss7.org> <3E38394D.8C0BAAEE@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: <3E38394D.8C0BAAEE@alcatel.com>; from Tom.George@alcatel.com on Wed, Jan 29, 2003 at 02:27:57PM -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>

Tom,

Becauwe for SSCOP the "processor" is normally the ATM cell processor
as well.  Also, MTP3b does not necessarily incur a cost for realigning
a link (because proving can be skipped, and unlike M2PA, there is no
slow-start to surmount).  So, for Q.2140 there is little difference
between a processor outage and out-of-service state.  It does mean
that asserting processor outage while performing network management
(which is provided in Q.704) cannot be properly used for MTP3b links.

--brian

Tom George wrote:                                                                      (Wed, 29 Jan 2003 14:27:57)
> I agree that it would be out of scope to specify how MTP3 must use flush
> or retrieve data. 
> 
> The proc outage reminded me of an old question. In ATM links (Q.2140),
> there is no processor outage procedure as in Q.703. The link is just
> failed when there is a "proc outage". Does anyone know why there is no
> Q.703-like proc outage procedure in Q.2140?
> 
> tomG.
> 
> "Brian F. G. Bidulock" wrote:
> > 
> > Karen,
> > 
> > karen.d.king@bt.com wrote:                                                    (Wed, 29 Jan 2003 09:51:13)
> > > Hi Tom,
> > >
> > > Thanks, this looks better. One further thought -  data retrieval is only
> > > appropriate for a very short time (or else you end up with 'stale'
> > > information). Do we need a note to cover this, or is this sufficiently
> > > covered else where?
> > 
> > Handling of stale information in retrieval buffers is handled by normal MTP
> > Level 3 procedures (buffer flushing).  Level 2 keeps data for retrieval until
> > it is either retrieved by Level 3 or it is told to flush such information by
> > Level 3.  Addressing Level 3 procedures is out of scope for M2PA.  It is
> > sufficient that M2PA provides the same upper boundary to MTP Level 3 as is
> > provided by a normal signalling link.  This includes retrieval_requiest_and-
> > _fsnc and flush_buffers, resume, clear_rtb signals.
> > 
> > --brian
> > 
> > >
> > > On my other comment - if the correct use of processor outage is well
> > > understood (and the spec leaves no room for misunderstanding) then I'm
> > > happy.
> > >
> > > Regards,
> > >
> > > Karen
>   [...]
> 
> -- 
> * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> * Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
> * 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 Jan 29 16:28:02 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 QAA00456
	for <sigtran-archive@odin.ietf.org>; Wed, 29 Jan 2003 16:28:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0TLnd725774
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 16:49:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TLmpJ25744;
	Wed, 29 Jan 2003 16:48:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TLlDJ25691
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 16:47:13 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00397
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 16:25:04 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0TLRoeW002941;
	Wed, 29 Jan 2003 15:28:05 -0600 (CST)
Message-ID: <3E384756.B8A59A62@alcatel.com>
Date: Wed, 29 Jan 2003 15:27:50 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: sigtran@ietf.org
References: <3D72C18DF140D311A54F0008C7DBAC8D02917425@MCHH252E>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M2PA T3 and T4 (was M2PA version 7 changes)
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

Gaiser Franz wrote:
> 
> Dear All,
> 
> some remarks to the new draft version 07:
> 
  [...]
> 5.) Figure 13. Example: Link Initialization - Proving
> New Timer T3 "ALIGNED" is missing in the figure.
> 
> best regards, Franz

Franz,

Thanks for pointing this out. While looking at this, I found another
error in 4.1.3. 

================================================
When M2PA has both sent and received the Link Status Alignment
message, it has completed alignment.  M2PA starts the aligned timer T3
and moves to the proving state.

M2PA stops timer T3 when it receives a Link Status Proving Normal or
Proving Emergency message and starts proving period timer T4.

If timer T3 expires, then M2PA reports to MTP3 that the link is out of
service.  M2PA sends Link Status Out of Service to its peer.  M2PA
SHOULD leave the association established.  M2PA waits for MTP3 to
initiate the alignment procedure again.

During the proving period (i.e., after M2PA starts the proving period
timer T4), M2PA sends Link Status Proving messages to its peer at an
interval defined by the protocol parameter Proving_Interval. M2PA
================================================

This way, both sides will send and receive LS Alignment, start their
respective T3 timers, and sit and wait for the other side to send LS
Proving. 

I think this problem crept in when I was inserting the new text about
T3. I should say something like this: 

================================================
When M2PA has both sent and received the Link Status Alignment
message, it has completed alignment.  M2PA starts the aligned timer T3
**and the proving period timer T4,** and moves to the proving state.

M2PA stops timer T3 when it receives a Link Status Proving Normal or
Proving Emergency message[DELETE "and starts proving period timer T4"].

If timer T3 expires, then M2PA reports to MTP3 that the link is out of
service.  M2PA sends Link Status Out of Service to its peer.  M2PA
SHOULD leave the association established.  M2PA waits for MTP3 to
initiate the alignment procedure again.

During the proving period (i.e., after M2PA starts the proving period
timer T4), M2PA sends Link Status Proving messages to its peer at an
interval defined by the protocol parameter Proving_Interval. M2PA
================================================

And, of course, Figure 13 should be updated accordingly.


-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 30 00:31: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 AAA09050
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 00:31:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0TMH1M28469
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 17:17:01 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TMFrJ28405;
	Wed, 29 Jan 2003 17:15:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TMApJ27995
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 17:10:51 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01192
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 16:48:42 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0TLqEJT006516;
	Wed, 29 Jan 2003 15:52:14 -0600 (CST)
Message-ID: <3E384D0E.AF500008@alcatel.com>
Date: Wed, 29 Jan 2003 15:52:14 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: sigtran@ietf.org
References: <3D72C18DF140D311A54F0008C7DBAC8D02917425@MCHH252E>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M2PA Link OOS (was: M2PA version 7 changes)
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

Franz and others,

Yes, in that case M2PA should send LS OOS to its peer. 

There are several places in the document where the link goes OOS. As it
stands now, I do not always state all of the actions to be taken because
they are more-or-less understood:

- Send LS OOS to the peer.
- Notify MTP3 of Out of Service condition.
- Leave the SCTP association up. (a SHOULD)
- Wait for MTP3 to begin alignment.

What is the best way to explain this? Repeat it throughout the document,
or have a little OOS section (similar to 4.2.3  Link deactivation), or
just leave it as is and count on the reader to understand it?

tomG.

Gaiser Franz wrote:
> 
> Dear All,
> 
> some remarks to the new draft version 07:
> 
  [...]
> 4.) 4.2.1 Paragraph "If M2PA receives a User Data message with 
> an FSN that is out of order, M2PA SHALL take the link out of service."
> Does "take the link out of service"  mean also that the peer side is 
> informed via sending LS OOS message.
  [...]

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 30 00:47: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 AAA09338
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 00:47:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U69Uk26072
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 01:09:30 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U68XJ25962;
	Thu, 30 Jan 2003 01:08:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U5w1J24715
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 00:58:01 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09174
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 00:35:44 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:l+HbNd/BQgX07vVdixlM6nIyJaLjtQFM@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0U5dGD26294;
	Wed, 29 Jan 2003 22:39:16 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0U5dFk20615;
	Wed, 29 Jan 2003 22:39:15 -0700
Date: Wed, 29 Jan 2003 22:39:15 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA Flush Buffers (was: M2PA version 7 changes)
Message-ID: <20030129223915.D1341@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF058D8FAB.B6526DCE-ONC2256CBE.001D41FE@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF058D8FAB.B6526DCE-ONC2256CBE.001D41FE@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Thu, Jan 30, 2003 at 07:20:14AM +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>

TOLGA,

What does it matter?

--brian

TOLGA ASVEREN wrote:                                                                 (Thu, 30 Jan 2003 07:20:14)
> 
> Tom,
> 
> I mean, during flushing, what to do with SCTP buffers?
> 
>    Tolga
> --- Tom George <Tom.George@alcatel.com> wrote:
> > Tolga,
> >
> > I am not sure what you are asking. Could you be more
> > specific?
> >
> > tomG.
> >
> > TOLGA ASVEREN wrote:
> > >
> > > Tom,
> > > Is there also a decision about what to do while
> > flushing buffers?
> > >
> > >    Tolga
> > >
> > > _______________________________________________
> > > 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 USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO;
> > Plano TX 75075-5813  *
> > * 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

-- 
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 Jan 30 00:51: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 AAA09427
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 00:51:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U6DYO26279
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 01:13:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U6CdJ26221;
	Thu, 30 Jan 2003 01:12:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U61KJ24890
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 01:01:20 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09194
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 00:39:02 -0500 (EST)
Subject: Re: [Sigtran] M2PA Flush Buffers (was: M2PA version 7 changes)
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF6E38DEEA.89D92DA5-ONC2256CBE.001EEB80@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Thu, 30 Jan 2003 07:39:08 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/30/2003
 07:39:11 AM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0U61KJ24891
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


Brian,

So the decision is that during flushing we don´t need to flush messages in
SCTP buffers(?).

     Tolga


                                                                                                           
                    "Brian F. G.                                                                           
                    Bidulock"            To:     TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>                   
                    <bidulock@open       cc:     sigtran@ietf.org                                          
                    ss7.org>             Subject:     Re: [Sigtran] M2PA Flush Buffers (was: M2PA version  
                                          7 changes)                                                       
                    30.01.2003                                                                             
                    07:39                                                                                  
                    Please respond                                                                         
                    to bidulock                                                                            
                                                                                                           
                                                                                                           




TOLGA,

What does it matter?

--brian

TOLGA ASVEREN wrote:
(Thu, 30 Jan 2003 07:20:14)
>
> Tom,
>
> I mean, during flushing, what to do with SCTP buffers?
>
>    Tolga
> --- Tom George <Tom.George@alcatel.com> wrote:
> > Tolga,
> >
> > I am not sure what you are asking. Could you be more
> > specific?
> >
> > tomG.
> >
> > TOLGA ASVEREN wrote:
> > >
> > > Tom,
> > > Is there also a decision about what to do while
> > flushing buffers?
> > >
> > >    Tolga
> > >
> > > _______________________________________________
> > > 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 USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO;
> > Plano TX 75075-5813  *
> > * 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

--
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 Jan 30 00:51:52 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 AAA09444
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 00:51:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U6DcD26297
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 01:13:38 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U6DTJ26268;
	Thu, 30 Jan 2003 01:13:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U630J24933
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 01:03:00 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09208
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 00:40:42 -0500 (EST)
Subject: Re: [Sigtran] M3UA SG-SG (again)
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFEA857C8E.46EA7548-ONC2256CBE.001E8FE3@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Thu, 30 Jan 2003 07:40:48 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/30/2003
 07:40:51 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>


Ken,

[KAM] i don't understand how SG-SG improves upon M3UA for asymmetric RKs

[TOLGA] This was based on that SE model was allowed for IPSP in IG.
Depending on the changes in IG about IPSP, this needs to be updated.


Tolga,

I agree that the SG-SG draft is worthwhile and should move forward.  I
have attached an edited version with more questions than comments.

Regards,

Ken





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



From mailnull@www1.ietf.org  Thu Jan 30 01:02:56 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 BAA09577
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 01:02:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U5kvV24014
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 00:46:57 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U5jxJ23955;
	Thu, 30 Jan 2003 00:46:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U5gPJ23837
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 00:42:25 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08584
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 00:20:09 -0500 (EST)
Subject: Re: [Sigtran] M2PA Flush Buffers (was: M2PA version 7 changes)
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF058D8FAB.B6526DCE-ONC2256CBE.001D41FE@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Thu, 30 Jan 2003 07:20:14 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/30/2003
 07:20: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>


Tom,

I mean, during flushing, what to do with SCTP buffers?

   Tolga
--- Tom George <Tom.George@alcatel.com> wrote:
> Tolga,
>
> I am not sure what you are asking. Could you be more
> specific?
>
> tomG.
>
> TOLGA ASVEREN wrote:
> >
> > Tom,
> > Is there also a decision about what to do while
> flushing buffers?
> >
> >    Tolga
> >
> > _______________________________________________
> > 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 USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO;
> Plano TX 75075-5813  *
> * 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  Thu Jan 30 01:03:57 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 BAA09614
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 01:03:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U5whk24759
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 00:58:43 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U5wXJ24743;
	Thu, 30 Jan 2003 00:58:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U5tVJ24546
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 00:55:31 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09141
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 00:33:14 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:cNQEDOP/PrNPAAoV2KnfENdtqTeeHQR5@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0U5ajD26265;
	Wed, 29 Jan 2003 22:36:45 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0U5ajF20323;
	Wed, 29 Jan 2003 22:36:45 -0700
Date: Wed, 29 Jan 2003 22:36:45 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
Message-ID: <20030129223645.C1341@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
References: <OFEC77243A.47A4213E-ONC2256CBC.002FD630@LocalDomain> <3E38AC51.B358D2E7@axes-mach01.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: <3E38AC51.B358D2E7@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Thu, Jan 30, 2003 at 10:08:41AM +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>

Srini,

ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 10:08:41)
> Tolga,
> 
> An ASP can be a part of different ASs. Similarly, Can a SGP be a part of
> different SGs?

Sure.  But from the viewpoint of an ASP, the SGP belongs to one SG.  If an
SGP were to perform the function for two SGs for the same AS, the ASP would
have to form two associations with the SGP: one for SG-A, the other for SG-B.
The SGP would also need some way of knowing (e.g. static port allocation)
for which SG the ASP was forming an association.

--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  Thu Jan 30 01:04: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 BAA09634
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 01:04:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U5vEi24671
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 00:57:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U5uCJ24565;
	Thu, 30 Jan 2003 00:56:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U5q3J24332
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 00:52:03 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08985
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 00:29:46 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:yZr2T2BgLSHHoeXJ9+2U21/EdU55bLq5@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0U5XFD26230;
	Wed, 29 Jan 2003 22:33:15 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0U5XFr19940;
	Wed, 29 Jan 2003 22:33:15 -0700
Date: Wed, 29 Jan 2003 22:33:15 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <tolga.asveren@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
Message-ID: <20030129223315.B1341@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
References: <OFEC77243A.47A4213E-ONC2256CBC.002FD630@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OFEC77243A.47A4213E-ONC2256CBC.002FD630@LocalDomain>; from tolga.asveren@o2.com.tr on Tue, Jan 28, 2003 at 10:42:30AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Tue, 28 Jan 2003 10:42:30)
> > A configuration where per-SGP SS7 destination status is
> > necessary is as
> > follows. Consider an SEP SG which has two SGP's acting as a redundant
> > pair. Each SGP has it's own link set to a particular STP. While in
> > section 1.4.1 para 3 it states that "Rerouting of traffic between the
> > SGPs MAY also be supported", it uses "MAY" and hence this is optional.
> > If one link set fails but not the other, one SGP will be able to reach
> > the SS7 network but not the other if rerouting between SGPs is not
> > supported or the rerouting link has also failed. Hence, it would be
> > possible for one SGP to send a DUNA for a particular
> > destination but not
> > the other.
> [TOLGA] Again I don´t see a problem. I only agree that "MAY" in the
> sentence you refer was better changed to a "SHOULD". If somebody thinks
> that creating a unique layer3 view among SGPs belonging to the same SG is
> hard to implement/not necessary, then it is possible to have SGs consisting
> of one SGP, without violating the protocol. In that case, SSNM will be
> received separetly from each SGP, because they belong to different SGs.

SHOULD was changed to MAY because the RFC cannot force the internal
architecture of the SG.  I cited several examples where it was possible to
have SGP not transfer traffic between them (an SGP can simply drop
associations or send unsolicited ASPIA ACK when it is faced with routing
traffic to another SGP.)

I don't see any reason to change it back.

--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  Thu Jan 30 01:04:57 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 BAA09648
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 01:04:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U5lHo24055
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 00:47:17 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U5l3J24039;
	Thu, 30 Jan 2003 00:47:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U5kbJ23999
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 00:46:37 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08835
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 00:24:18 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:N1qQkvjCsOeTksACxVnlTQLgBMRyXcf8@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0U5RmD26048;
	Wed, 29 Jan 2003 22:27:49 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0U5RmT19266;
	Wed, 29 Jan 2003 22:27:48 -0700
Date: Wed, 29 Jan 2003 22:27:48 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Jolan Evans <jolan.evans@opentelecommunications.com>
Cc: "'Sigtran'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
Message-ID: <20030129222748.A1341@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Jolan Evans <jolan.evans@opentelecommunications.com>,
	'Sigtran' <sigtran@ietf.org>
References: <20030128015258.A5712@openss7.org> <005b01c2c80f$89c41970$900c460a@Mars>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <005b01c2c80f$89c41970$900c460a@Mars>; from jolan.evans@opentelecommunications.com on Thu, Jan 30, 2003 at 02:27:28PM +1100
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>

Jolan,

More comments below....

Jolan Evans wrote:                                                                   (Thu, 30 Jan 2003 14:27:28)
> See my comments below...
> 
> 
> --
> Jolan Evans
> Open Telecommunications
> jolan.evans@opentelecommunications.com
> 
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Tuesday, 28 January 2003 19:53
> > To: Jolan Evans
> > Cc: Sigtran
> > Subject: Re: [Sigtran] M3UA: ASP to SGP communication
> > 
> > Jolan,
> > 
> > You are a litte of track: please see comments below...
> > 
> > Jolan Evans wrote:
> > (Tue, 28 Jan 2003 19:01:56)
> > > I would like to raise a few issues regarding your procedures below
> for
> > > ASP to SGP routing. I know this discussion took places a while ago,
> but
> > > it has taken me some time to come up to speed with the RFC as I have
> > > been busy on other things until recently.
> > >
> > > Please note that I have inserted "M3UA" into the subject line of the
> > > original email.
> > >
> > >
> > >
> > > 1. Nomenclature
> > > AsPc: Point code of an AS. In defining routing keys, the RFC uses
> DPC
> > > for this term as it takes the SG's frame of reference.
> > > RemotePc: Point code of an SS7 MTP entity with which an AS
> communicates
> > > via an SG, or directly in the case of IPSP-IPSP communication. In
> > > defining routing keys, the RFC uses OPC for this term as it takes
> the
> > > SG's frame of reference again.
> > >
> > >
> > >
> > > 2. Background Assumptions
> > > As per Brian's introduction, we assume that zero or more MTP-User's
> are
> > > bound to an MTP-SAP. The MTP-SAP exists in a particular MTP-Network,
> > > which has a particular MTP protocol variant. An SG is associated
> with a
> > > single MTP-Network. A RK is defined as in the RFC, but, for clarity,
> is
> > > independent of any SG and associated with a single MTP-Network. An
> > > SgRouteSet is uniquely defined by an RK, an SG and an MTP-SAP (the
> RK
> > > and SG must be both associated with the same MTP-Network) and also
> > > specifies the network appearance for the MTP-Network to be used with
> the
> > > SG and the RC of each SGP in the SG. Therefore, an SgRouteSet is
> > > implicitly associated with a single MTP-Network. An MTP-SAP is
> > > associated with zero or more SgRouteSet's and therefore an MTP-SAP
> is
> > > associated with zero or more RKs.
> > 
> > Bad assumption.  An MTP-SAP is assocated with one RK.  This is the
> > 1:1:1 rule between AS:RK:RC.
> 
> Ok, I neglected to state the circumstances and in particular the network
> topologies which drove me to make these assumptions, and in particular,
> the 1:many association between MTP-SAP:RK. Nonetheless, I can't find
> statements in the RFC to support your statement that an "MTP-SAP is
> assocated with one RK" and hence I would have to call this an assumption
> also. However, I stand corrected if this is not the case.

Secion 1.2 Terminology: Application Server:

  "... Note that there is a 1:1 relationship between an AS and a
  Routing Key".

> 
> Without further ado, here is one of the network topologies in which our
> ASP M3UA must operate. NB This is defined by our customers so we can't
> change it.
> 
> We must communicate with a number of SGs, for simplicity let's just say
> 2 as that's all that I need to illustrate my point. Likewise, it's not
> important how many SGP's they each have, so for simplicity let's assume
> that each SG has just one. Here is the network to which the ASP is
> connected:
> 
> MtpNetworkA: Protocol=ITU 92
> 
> MtpSapA: Network=MtpNetworkA

An MTP-SAP cannot be defined as an entire network (even just for SS7),
and there is no reason to do so.

> 
> SgA: Network=MtpNetworkA
> SgB: Network=MtpNetworkA
> 
> SgpA: Sg=SgA, etc
> SgpB: Sg=SgB, etc
> 
> RkA: Network=MtpNetworkA, AsPcSet={PcA, PcB}, RemotePcSet={PcW, PcX}
> RkA: Network=MtpNetworkA, AsPcSet={PcC, PcD}, RemotePcSet={PcY, PcZ}

I think you mean RkB on this last entry?

Also, the only way you can have multiple point codes in the AsPcSet
is if the point codes are "aliases" for the same signalling point.
In which case, the accessibility, for example, from PcA to PcW is
identical to the accesssibility from PcB to PcW.

> 
> SgRouteSetA: Sap=MtpSapA, RoutingKey=RkA, Sg=SgA, NetworkAppearance=0,
> SgpSet={(SgpA, Rc=0)}
> SgRouteSetB: Sap=MtpSapA, RoutingKey=RkB, Sg=SgB, NetworkAppearance=0,
> SgpSet={(SgpB, Rc=0)}

Again you try to have one AS serving multiple Routing Keys.  This violates
the 1:1 rule.  Because you have two RKs, you have two AS (and at least
two MTP-SAPs).

> 
> In this model, when the ASP-ACTIVE ACK is received for RkA (RkB), the
> ASP will audit the state of the RemotePcSet of RkA (RkB) at SgpA (SgpB).
> Ie the RemotePcSet of a routing key determine which remote PCs should
> have their status audited at a particular SG (I'll ignore the issue of
> whether it is SG or SGP for now).
> 
> I'm not clear how this would be translated to your model. As I see it,
> there is a problem because an MTP-SAP is only allowed to have one RK but
> the MTP-User of the SAP wants to talk with 2 different SGs, each with
> their own routing keys.

It is not my model.

Because you have two AS, there is not problem.  AS-A audits remote
desinations on RkA, AS-B audits remote destinations on RkB.

> 
> I can see 2 obvious ways to translate this configuration into your
> model: Either define just one RK or define two MTP-SAPs.

It is not my model.

But, you are required to define two AS because of the 1:1 rule.  How
many MTP-SAPs you have at the ASP is implementation dependent.

> 
> However, if there is one RK then we can no longer rely upon the
> RemotePcSet of the RK to determine the set of remote PCs of which the
> status should be audited when an ASP goes active with an SGP. This seems
> awkward and would seemingly require the RemotePcSet to be an attribute
> of the SgRouteSet.
> 
> If there are two MTP-SAPs then we are burdening the MTP-USER which must
> now aggregate traffic and destination status from two different
> MTP-SAPs. As far as I'm aware, in plain old MTP3 an MTP-USER can happily
> talk via just one MTP-SAP to two different STPs which have routesets to
> a different set of remote PCs.

For this situation, you do not need to burden the MTP-User.  It is the
M3UA layer at the ASP which is burdened.  In the multiple SG scenario,
the M3UA layer at the ASP is responsible for understanding which AS
correspond to which MTP-SAPs, and handling routing, and determining when
to send an MTP-User an MTP-PAUSE or RESUME based on DUNA and DAVA received
from each of the various SG.

So, in effect, although you require two AS, how many MTP-SAPs you have
at the ASP is implementation dependent.

In the non-multiple SG scenario (or where access is via a pair of SG
acting a an STP pair), the AS nicely maps 1:1 to an MTP-SAP.

> 
> Most of your remaining comments on my original items 2 and 3 are on the
> basis that one cannot assume a 1-many MTP-SAP:RK relationship. I won't
> reply to such comments as the real issue is the assumption itself.

You cannot have a 1:many AS:RK relationship.  How many AS you map into
an MTP-SAP is the implementation's business.

But your statement that the remainder of my comments are based on this
is untrue.  SSNM on a per-SGP basis is false and was ruled out in the
design of the protocol.  This has nothing to do with multiple RKs for
an MTP-SAP.

--brian

> 
> > 
> > > In contrast, it appears that Brian
> > > assumes that an MTP-SAP can only be associated with one RK. Given
> this
> > > extension, we have the following requirement.
> > >
> > >
> > >
> > > 3. Routing Keys Requirements to Support Unique SS7 Destination
> Status
> > > Let RemotePcSet(Rk) be the set of RemotePc's reachable via the SG
> from
> > > the ASP where the RK is defined.
> > 
> > RKs do not have to be defined at ASPs, just MTP-SAPs.
> > 
> > > Consider any two SgRouteSet's SgRsA and SgRsA which are associated
> with
> > > the same MTP-SAP.
> > 
> > I think you mean SgRsA and SgRsB <---.
> > 
> > > Let the routing key of SgRsA and SgRsB be RkA and RkB respectively.
> > > If the intersection of RemotePcSet(RkA) and RemotePcSet(RkB) is
> non-nil
> > > then the routing keys MUST be identical in every respect apart from
> > > their RemotePcSet.
> > 
> > RkA and RkB must be identical or they cannot be associated with the
> > same MTP-SAP.  See 1:1:1 rule above.
> > 
> > > If this wasn't the case, an ASP could never indicate an MTP-RESUME
> to an
> > > MTP-USER because an MTP-RESUME can only specify a RemotePc and no
> other
> > > SS7 element. I assume here for simplicity that every MTP-User of a
> > > MTP-SAP must be given the same MTP status (i.e. different MTP-Users
> of
> > > the same MTP-SAP cannot be given different MTP-Status indications
> > > depending on what traffic they have requested).
> > 
> > The AS can deliver whatever MTP-STATUS indications it cares to.  If
> > there are SI values represented by the MTP-SAP, it is normally the
> > MTP-User's responsibility to sort out the MTP-STATUS indications.
> 
> I don't know what you mean by "whatever MTP-STATUS indications it cares
> to" but ITU Q.701 Table 1 shows that MTP-PAUSE and MTP-RESUME only
> contain the affected DPC. A lot of MTP-user software has been written on
> this assumption so we can't afford to change this.
> 
> > 
> > >
> > > Here's a concrete example of why this is so. Consider an ASP with
> the
> > > following routing keys:
> > > RkA: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={A}
> > > RkB: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={B}
> > > RkC: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={M}
> > > RkD: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={N}
> > >
> > > Assume that RkA and RkB were both active in SgpA and SgpB
> respectively
> > > and are associated with the same MTP-SAP, but different SGs.
> > 
> > To be associated with the same MTP-SAP, RkA and RkB must be identical,
> > which implies that AsPcSetA and AsPcSetB are also identical.
> > 
> > > Also assume that a DAVA has been received for RemotePc=X from SgpA
> after
> > a
> > > DUNA from SgpB for the same RemotePc. We might consider generating
> an
> > > MTP-Resume to all the MTP-Users of the MTP-SAP for RemotePc X.
> However,
> > if
> > > an MTP-User requests an MTP-Transfer with an AsPc of B then SgpB may
> not
> > be
> > > able to transfer it as indicated by the DUNA it sent the ASP.
> > 
> > This is not a problem because AsPc A must be identical to AsPc B.
> Also,
> > you do not seem to realize that DAVA and DUNA are specific to the SG.
> > A DUNA received from one SG does not indicate that the affected
> > destination
> > is also unavailable via the other SG.  It takes a DUNA from both SGs
> > to indicate that the affected destination is inaccessible.
> > 
> > >
> > > The same explanation applies to RkC and RkD.
> > 
> > For RkC and RkD to be associated with the same MTP-SAP requires that
> > they are identical according to the 1:1:1 rule above.
> > 
> > >
> > > In practice this requirement probably won't cause too many headaches
> > > because it is likely that there would be two different MTP-Users,
> one
> > > using only RkA/RkC and the other using only RkB/RkD.
> > 
> > In fact there must be two different MTP-SAPs (and necessarily
> different
> > MTP-Users from the perspective of the SG) for RkA/RkC to tbe different
> > from RkB/RkD.
> > 
> > > In this case, we can simply create two MTP-SAPs in the same
> MTP-Network
> > and
> > > associate each routing key with a different MTP-SAP. Of course, this
> > would
> > > require the M3UA implementation to support more than one MTP-SAP per
> > > MTP-Network, which would be extra work obviously.
> > 
> > It is not extra work.  M3UA not only supports this but requires it.
> > An MTP-SAP is an AS.  Having multiple AS (whether in a single network
> > or not) is fundamental to the SIGTRAN model.
> > 
> > >
> > > 4. ASP-SGP Routing should use SS7 Destination
> Availability/Restricted
> > > Status on a per-SGP rather than a per-SG basis.
> > 
> > Wrong.  ASPSM/ASPTM is per-SGP.  SSNM is per-SG.
> > 
> > >
> > > I believe your ASP-SGP procedures should be amended (I only amend
> the
> > > multiple SG case as the single SG case is a special case of the
> former)
> > > as follows:
> > >
> > > Change:
> > > "This routing information is updated by collecting DUNA/DAVA/DRST
> > > messages received from (any of the SGP in) the SG."
> > > To:
> > > "This routing information is updated by collecting DUNA/DAVA/DRST
> > > information on a per-(SGP,destination) basis. An SG is considered to
> be
> > > available and unrestricted for a particular destination if any SGP
> in it
> > > is available and unrestricted for that destination. Otherwise if
> this is
> > > not he case, then an SG is considered to be restricted for a
> particular
> > > destination if there is at least one SGP in the SG restricted for
> that
> > > destination. Otherwise if this is not the case, the SG is considered
> to
> > > be prohibited for that destination."
> > >
> > > The RFC is not particular clear on this point. In section 1.4.1 para
> 3
> > > it states that "MTP3 routeset, SPMC and remote AS/ASP states of each
> SGP
> > > SHOULD be coordinated across all the SGPs". However, this uses
> "SHOULD"
> > > which implies it is only recommended and it also doesn't
> specifically
> > > state that SS7 destination availability, restriction and congestion
> > > status ("SS7 destination status" for short) should be coordinated
> across
> > > all SGPs. I don't think that "MTP3 routeset" necessarily implies SS7
> > > destination status. Also, in section 1.3.2.5 1.4.2.5 it suggests in
> > > should be on a per-SGP basis. Section 4.5.2.2 uses the word "SG" but
> > > also uses the term "affected route(s)". Section 1.3.2.5 and section
> > > 1.4.2.5 suggest the word "route" refers to an SGP and not an SG.
> Hence,
> > > given the ambiguity of section 4.5.2.2 I think that route can be
> > > considered to refer to an SGP.
> > 
> > Each SGP in an SG offers identical connectivity to the SS7 network.
> > This means that a destination which is inaccessible to one SGP is
> > inaccessible to all, congested, restricted, accessible, etc.
> 
> RFC section 1.4.1 para 3 makes it clear that the static configuration of
> the connectivity of the SGPs must be identical, but it doesn't make it
> clear that the SGPs should be designed to ensure identical connectivity
> at runtime. In particular I am referring to the statement "Rerouting of
> traffic between the MAY also be supported". If rerouting isn't supported
> amongst the SGPs of an SG (either in the SGP's M3UA or within an MTP3
> stack distributed between the SGPs) then I don't see how the SGPs can be
> expected to have identical connectivity in the event of a single point
> of failure.
> 
> Hence, I think that statements mirroring what you have said should be in
> the implementor's guide. Otherwise, without reading these emails, other
> people may be confused as to whether DAVA/DUNA/DRST destination status
> should be kept on a per-SG or a per-SGP basis.
> 
> > 
> > >
> > > A configuration where per-SGP SS7 destination status is necessary is
> as
> > > follows. Consider an SEP SG which has two SGP's acting as a
> redundant
> > > pair. Each SGP has it's own link set to a particular STP. While in
> > > section 1.4.1 para 3 it states that "Rerouting of traffic between
> the
> > > SGPs MAY also be supported", it uses "MAY" and hence this is
> optional.
> > > If one link set fails but not the other, one SGP will be able to
> reach
> > > the SS7 network but not the other if rerouting between SGPs is not
> > > supported or the rerouting link has also failed. Hence, it would be
> > > possible for one SGP to send a DUNA for a particular destination but
> not
> > > the other.
> > 
> > This is addressed.  The SGP has suffered a complete failure (it is
> unable
> > to process traffic) and can simply drop its associations to the ASPs.
> > DUNA is incorrect here: the destination is still accessible from the
> SG.
> > One SGP has simply broken it's contract (providing identical
> connectivity
> > to the SS7 network as other SGP in the SG) and must be placed out of
> > service.
> > 
> > --brian
> > 
> > >
> > >
> > > Your feedback would be appreciated.
> > >
> > > Jolan.
> > >
> > >
> > > --
> > > Jolan Evans
> > > Open Telecommunications
> > > jolan.evans@opentelecommunications.com
> > >
> > >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org] On
> Behalf
> > > Of Brian F. G. Bidulock
> > > Sent: Tuesday, 8 October 2002 17:47
> > > To: Srikanth Yandapalli
> > > Cc: sigtran@ietf.org
> > > Subject: Re: [Sigtran] ASP to SGP communication
> > >
> > > Srikanth,
> > >
> > > Srikanth Yandapalli wrote:               (Tue, 08 Oct 2002 12:03:52)
> > > >
> > > >    I am late entrant to this group.I am quite sure all this should
> > > have
> > > >    been discussed and I am sorry about this.
> > >
> > > Welcome.
> > >
> > > >
> > > >    In the context of a single ASP in communication with multiple
> SGPs,
> > > >    how should the routing of a MTP_DATA_REQ take place at the ASP?
> > >
> > > I assume you are talking about M3UA?  As we are dealing with 5 or
> more
> > > UAs
> > > now, in the future it would be helpful to add M3UA (or whichever) to
> the
> > > subject line.
> > >
> > > >
> > > >    approach 1:
> > > >
> > > >    We may find out the  RK and find out the SGP list that the RK
> is
> > > >    active on and choose one SGP for sending the message based
> > > >    on congestion level and also whether we have received any DRST
> > > >    message from any of the SGPs.
> > >
> > > This approach is applicable to multiple SGs, but not to multiple
> SGPs
> > > within a
> > > single SG.
> > >
> > > >    approach 2:
> > > >
> > > >    An SGP can also be viewed as providing route to a set of DPCs
> > > >    and the routing can be based on the DPC for the message alone.
> > > >    This approach is reduces the complexity but adds a situation
> > > >    where the RK may not be active on that association. And also is
> > > >    is mandatory to send RC on this association and if so what
> could
> > > >    the SGP make out of the RC?
> > >
> > > RC should be coordinated and the same across multiple SGPs within an
> SG.
> > >
> > > >
> > > >    Is there a preferred approach to this issue?
> > > >
> > >
> > > Typically, the logic can be something like this: (but there are
> several
> > > other
> > > schools of thought):
> > >
> > > Single SG case: (multiple SGs is more complicated)
> > >
> > >   MTP-TRANSFER request is issued by an MTP-User.  The MTP-User is
> bound
> > > to an
> > >   MTP-SAP.  The MTP-SAP is associated with an AS/RC/RK.  There is a
> pool
> > > of
> > >   SGPs on an SG for which the AS/RC/RK is active.  The AS may have
> > > received
> > >   MTP-PAUSE/RESUME/STATUS indications from the SG and may choose to
> > > honor that
> > >   information or not.  If the ASP chooses not to honor this
> information
> > > it can
> > >   blindly send messages to the SGP and rely upon a DUNA/SCON
> response
> > > from the
> > >   SGP later.
> > >
> > >   Selection of an SGP within an SG is based on the traffic mode for
> the
> > > SGP.
> > >   This traffic mode is not managed by M3UA, however, M3UA provides
> for
> > >   distribution of traffic over SGP based on any of the methods
> described
> > > for
> > >   ASPs (active/standby, load-share, broadcast).  A typical method is
> > >   load-share based on SLS.  In this scheme, using the SLS in the
> > > MTP-TRANSFER
> > >   request, the ASP selects load-shares traffic over the available
> SGP.
> > >
> > > Multiple SG case:
> > >
> > >   In the more complicated multiple SG case, the ASP must first
> select an
> > > SG
> > >   before it selects an SGP within the SG.  The ASP must maintain
> some
> > >   additional routing information to be able to properly select an
> SG.
> > > This
> > >   routing information is updated by collecting DUNA/DAVA/DRST
> messages
> > >   received from (any of the SGP in) the SG.  To select the outgoing
> SG,
> > > the
> > >   ASP must examine the destination of the MTP-TRANSFER request.
> > >
> > >   (If the SG has no SGP active for the AS/RC/RK, all destinations
> can be
> > >   considered prohibited).
> > >
> > >   If the destination is available and unrestricted for several SGs,
> the
> > > ASP
> > >   should select an SG on a load-sharing basis (based on SLS) and
> then
> > > select
> > >   an active SGP within the SG on the basis of the traffic mode for
> the
> > > SG.
> > >
> > >   If some SG are restricted for the specified destination (based on
> > > received
> > >   DRST messages from the SG), the ASP should load-share across the
> > > available
> > >   unrestricted SGs.  If all SGs are restricted for a given
> destination,
> > > the
> > >   ASP should load-share across the available SGs and ignore the
> > > restricted
> > >   status.
> > >
> > >   If some SG are prohibited for the specified destination (based on
> > > received
> > >   DUNA messages from the SG), the ASP should load-share across the
> > > available
> > >   non-prohibited SGs.  If all SGs are prohibited for a given
> destination
> > > (or
> > >   no SGP is active for the AS/RC/RK in any SG), the ASP should
> respond
> > > to the
> > >   MTP-User with an MTP-PAUSE in accordance with the style of the
> > > MTP-User
> > >   interface (ITU-T and ANSI differ here).
> > >
> > > Properly selecting SGs requires that the ASP maintain the
> DUNA/DAVA/DRST
> > > information for each destination received from any SGP in an SG, on
> a
> > > per-SG
> > > basis.  This is the same as MTP Level 3 ROUTE status.  However, SCON
> > > information should only be maintained on a per-destination basis
> (and
> > > not
> > > per-SG).  This is the same as MTP Level 3 ROUTESET status.
> > >
> > > Note that, in general, it is a bad idea to consider congestion
> (SCON)
> > > when
> > > selecting an SG.  SCON does not necessarily indicate congestion at
> an SG
> > > or on
> > > a path to an SG, but indicates congestion at the affected
> destination or
> > > somewhere (perhaps distant) in the SS7 network.  SCON is
> > > ROUTESET-specific
> > > (applies to the destination), whereas DUNA/DAVA/DRST is
> ROUTE-specific
> > > (applies to the destination and path).  SCON should only be used to
> > > determine
> > > whether a message should be dropped completely and an MTP-STATUS
> > > returned to
> > > the MTP-User according to the style of the MTP-User interface (ITU-T
> and
> > > ANSI
> > > differ here again).
> > >
> > > So, to summarize:  on behalf of the AS/RC/RK/MTP-User, the ASP
> > > determines
> > > whether to send a message based on SCON received for the specified
> > > destination, then selects an SG based on DUNA/DAVA/DRST received for
> the
> > > specified destination and load-shares based on SLS across the
> eligible
> > > SGs.
> > > Once an SG is selected, an active SGP (active for the AS/RC/RK) is
> > > selected
> > > within the SG based on the traffic mode of the SG (active/standby,
> > > load-share,
> > > broadcast: but typically load-share on SLS).
> > >
> > > As I said, there are other schools of thought, but that is my
> > > understanding.
> > >
> > > --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/

-- 
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 Jan 30 01:06: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 BAA09687
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 01:06:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U4wu020764
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 23:58:56 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U4w1J20702;
	Wed, 29 Jan 2003 23:58:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U4uaJ20646
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 23:56:36 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08013
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 23:34:20 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0U4bmqe029232;
	Wed, 29 Jan 2003 22:37:50 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id JAA23760; Thu, 30 Jan 2003 09:06:57 -0500 (GMT)
Message-ID: <3E38AC51.B358D2E7@axes-mach01.usa.alcatel.com>
Date: Thu, 30 Jan 2003 10:08:41 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: TOLGA ASVEREN <tolga.asveren@o2.com.tr>
CC: sigtran@ietf.org
References: <OFEC77243A.47A4213E-ONC2256CBC.002FD630@LocalDomain>
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M3UA: ASP to SGP communication
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,

An ASP can be a part of different ASs. Similarly, Can a SGP be a part of
different SGs?

--Srini

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



From mailnull@www1.ietf.org  Thu Jan 30 01:08: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 BAA09765
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 01:08:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U4R3318792
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 23:27:03 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U4QFJ18764;
	Wed, 29 Jan 2003 23:26:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U4PpJ18730
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 23:25:51 -0500
Received: from spf1.us.outblaze.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA07704
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 23:03:34 -0500 (EST)
Received: (qmail 12218 invoked from network); 30 Jan 2003 04:07:04 -0000
Received: from unknown (205.158.62.68)
  by spf1.us.outblaze.com with QMQP; 30 Jan 2003 04:07:04 -0000
Received: (qmail 91901 invoked from network); 30 Jan 2003 04:07:00 -0000
Received: from unknown (HELO ws1-7.us4.outblaze.com) (205.158.62.57)
  by 205-158-62-153.outblaze.com with SMTP; 30 Jan 2003 04:07:00 -0000
Received: (qmail 10786 invoked by uid 1001); 30 Jan 2003 04:06:58 -0000
Message-ID: <20030130040658.10785.qmail@mail.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from [216.118.68.52] by ws1-7.us4.outblaze.com with http for
    jli@iname.com; Wed, 29 Jan 2003 23:06:58 -0500
From: "John Li" <jli@iname.com>
To: sigtran@ietf.org
Date: Wed, 29 Jan 2003 23:06:58 -0500
X-Originating-Ip: 216.118.68.52
X-Originating-Server: ws1-7.us4.outblaze.com
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M2PA Draft 7 comment
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 the following comments on the draft. Thanks,
John

===========================================================================

1.	In section 1.5: the following statement is somewhat confusing.
“The SG is an IPSP equipped with both traditional SS7 and IP
network connections. In effect, the Signaling Gateway acts as a
Signal Transfer Point (STP)” 

Perhaps we can say "The SG interconnects SS7 and IP networks by converting signaling traffic" or just refer to the definition in section 1.2


2.	Section 2.1.5 Message length
Should we specify the valid value range of the length?

3.	Section 2.3.1 User Data

statement "M2PA does not add padding to the MTP3 message.". I think we should make it a requirement: “M2PA should not add padding to the MTP3 message.”


4.	In section 4.1.3 Link alignment

perhaps we can specify the recommended practice for choosing emergency proving vs. normal proving during alignment procedure.


5.	Section 4.1.8: 
"If a Link Status Alignment message with an unsupported
received by the newer version, the receiving end's M2PA
SHALL NOT complete the alignment procedure."

can we clearly define the behavior of not completing the alignment procedure?

6.	section 4.2.1 sending and receiving messages
When M2PA receives a User Data message with Backward Sequence Number
equal to 'n', it may remove all messages with Forward Sequence Number
<= n from its queue.

This is incorrect. Consider at the time SN is cycled to 0 from 127 (assume 128 buffers), there are 127, 126, etc are waiting for acknowledgement. We should replace it with “The message n and all outstanding (not yet acknowledged) messages sent before the message n may be removed from its queue.

7.	section 4.2.1
If M2PA receives an empty User Data message, it SHALL NOT send an
acknowledgement of that message.

What is empty User Data message? FISUs? 


-- 
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

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



From mailnull@www1.ietf.org  Thu Jan 30 01:13: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 BAA09918
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 01:13:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U3onG16892
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 22:50:49 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U3nqJ16832;
	Wed, 29 Jan 2003 22:49:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U3loJ16583
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 22:47:50 -0500
Received: from envoy.ot.com.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA06992
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 22:25:30 -0500 (EST)
Received: (qmail 18413 invoked by uid 40); 30 Jan 2003 03:29:00 -0000
Received: from jolan.evans@opentelecommunications.com by envoy by uid 51 with qmail-scanner-1.12 (. Clear:. Processed in 0.308058 secs); 30 Jan 2003 03:29:00 -0000
X-Qmail-Scanner-Mail-From: jolan.evans@opentelecommunications.com via envoy
X-Qmail-Scanner: 1.12 (Clear:. Processed in 0.308058 secs)
Received: from unknown (HELO nobel.in.ot.com.au) (10.70.10.5)
  by envoy.ot.com.au with SMTP; 30 Jan 2003 03:28:59 -0000
Received: (qmail 5001 invoked from network); 30 Jan 2003 03:28:33 -0000
Received: from druid.in.ot.com.au (10.70.80.5)
  by nobel.syd.ot with SMTP; 30 Jan 2003 03:28:33 -0000
Received: (qmail 18316 invoked from network); 30 Jan 2003 03:28:24 -0000
Received: from unknown (HELO Mars) (10.70.12.144)
  by druid.in.ot.com.au with SMTP; 30 Jan 2003 03:28:24 -0000
From: "Jolan Evans" <jolan.evans@opentelecommunications.com>
To: <bidulock@openss7.org>
Cc: "'Sigtran'" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: ASP to SGP communication
Date: Thu, 30 Jan 2003 14:27:28 +1100
Organization: Open Telecommunications
Message-ID: <005b01c2c80f$89c41970$900c460a@Mars>
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, Build 10.0.2627
In-Reply-To: <20030128015258.A5712@openss7.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
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

See my comments below...


--
Jolan Evans
Open Telecommunications
jolan.evans@opentelecommunications.com


> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Tuesday, 28 January 2003 19:53
> To: Jolan Evans
> Cc: Sigtran
> Subject: Re: [Sigtran] M3UA: ASP to SGP communication
> 
> Jolan,
> 
> You are a litte of track: please see comments below...
> 
> Jolan Evans wrote:
> (Tue, 28 Jan 2003 19:01:56)
> > I would like to raise a few issues regarding your procedures below
for
> > ASP to SGP routing. I know this discussion took places a while ago,
but
> > it has taken me some time to come up to speed with the RFC as I have
> > been busy on other things until recently.
> >
> > Please note that I have inserted "M3UA" into the subject line of the
> > original email.
> >
> >
> >
> > 1. Nomenclature
> > AsPc: Point code of an AS. In defining routing keys, the RFC uses
DPC
> > for this term as it takes the SG's frame of reference.
> > RemotePc: Point code of an SS7 MTP entity with which an AS
communicates
> > via an SG, or directly in the case of IPSP-IPSP communication. In
> > defining routing keys, the RFC uses OPC for this term as it takes
the
> > SG's frame of reference again.
> >
> >
> >
> > 2. Background Assumptions
> > As per Brian's introduction, we assume that zero or more MTP-User's
are
> > bound to an MTP-SAP. The MTP-SAP exists in a particular MTP-Network,
> > which has a particular MTP protocol variant. An SG is associated
with a
> > single MTP-Network. A RK is defined as in the RFC, but, for clarity,
is
> > independent of any SG and associated with a single MTP-Network. An
> > SgRouteSet is uniquely defined by an RK, an SG and an MTP-SAP (the
RK
> > and SG must be both associated with the same MTP-Network) and also
> > specifies the network appearance for the MTP-Network to be used with
the
> > SG and the RC of each SGP in the SG. Therefore, an SgRouteSet is
> > implicitly associated with a single MTP-Network. An MTP-SAP is
> > associated with zero or more SgRouteSet's and therefore an MTP-SAP
is
> > associated with zero or more RKs.
> 
> Bad assumption.  An MTP-SAP is assocated with one RK.  This is the
> 1:1:1 rule between AS:RK:RC.

Ok, I neglected to state the circumstances and in particular the network
topologies which drove me to make these assumptions, and in particular,
the 1:many association between MTP-SAP:RK. Nonetheless, I can't find
statements in the RFC to support your statement that an "MTP-SAP is
assocated with one RK" and hence I would have to call this an assumption
also. However, I stand corrected if this is not the case.

Without further ado, here is one of the network topologies in which our
ASP M3UA must operate. NB This is defined by our customers so we can't
change it.

We must communicate with a number of SGs, for simplicity let's just say
2 as that's all that I need to illustrate my point. Likewise, it's not
important how many SGP's they each have, so for simplicity let's assume
that each SG has just one. Here is the network to which the ASP is
connected:

MtpNetworkA: Protocol=ITU 92

MtpSapA: Network=MtpNetworkA

SgA: Network=MtpNetworkA
SgB: Network=MtpNetworkA

SgpA: Sg=SgA, etc
SgpB: Sg=SgB, etc

RkA: Network=MtpNetworkA, AsPcSet={PcA, PcB}, RemotePcSet={PcW, PcX}
RkA: Network=MtpNetworkA, AsPcSet={PcC, PcD}, RemotePcSet={PcY, PcZ}

SgRouteSetA: Sap=MtpSapA, RoutingKey=RkA, Sg=SgA, NetworkAppearance=0,
SgpSet={(SgpA, Rc=0)}
SgRouteSetB: Sap=MtpSapA, RoutingKey=RkB, Sg=SgB, NetworkAppearance=0,
SgpSet={(SgpB, Rc=0)}

In this model, when the ASP-ACTIVE ACK is received for RkA (RkB), the
ASP will audit the state of the RemotePcSet of RkA (RkB) at SgpA (SgpB).
Ie the RemotePcSet of a routing key determine which remote PCs should
have their status audited at a particular SG (I'll ignore the issue of
whether it is SG or SGP for now).

I'm not clear how this would be translated to your model. As I see it,
there is a problem because an MTP-SAP is only allowed to have one RK but
the MTP-User of the SAP wants to talk with 2 different SGs, each with
their own routing keys.

I can see 2 obvious ways to translate this configuration into your
model: Either define just one RK or define two MTP-SAPs.

However, if there is one RK then we can no longer rely upon the
RemotePcSet of the RK to determine the set of remote PCs of which the
status should be audited when an ASP goes active with an SGP. This seems
awkward and would seemingly require the RemotePcSet to be an attribute
of the SgRouteSet.

If there are two MTP-SAPs then we are burdening the MTP-USER which must
now aggregate traffic and destination status from two different
MTP-SAPs. As far as I'm aware, in plain old MTP3 an MTP-USER can happily
talk via just one MTP-SAP to two different STPs which have routesets to
a different set of remote PCs.

Most of your remaining comments on my original items 2 and 3 are on the
basis that one cannot assume a 1-many MTP-SAP:RK relationship. I won't
reply to such comments as the real issue is the assumption itself.

> 
> > In contrast, it appears that Brian
> > assumes that an MTP-SAP can only be associated with one RK. Given
this
> > extension, we have the following requirement.
> >
> >
> >
> > 3. Routing Keys Requirements to Support Unique SS7 Destination
Status
> > Let RemotePcSet(Rk) be the set of RemotePc's reachable via the SG
from
> > the ASP where the RK is defined.
> 
> RKs do not have to be defined at ASPs, just MTP-SAPs.
> 
> > Consider any two SgRouteSet's SgRsA and SgRsA which are associated
with
> > the same MTP-SAP.
> 
> I think you mean SgRsA and SgRsB <---.
> 
> > Let the routing key of SgRsA and SgRsB be RkA and RkB respectively.
> > If the intersection of RemotePcSet(RkA) and RemotePcSet(RkB) is
non-nil
> > then the routing keys MUST be identical in every respect apart from
> > their RemotePcSet.
> 
> RkA and RkB must be identical or they cannot be associated with the
> same MTP-SAP.  See 1:1:1 rule above.
> 
> > If this wasn't the case, an ASP could never indicate an MTP-RESUME
to an
> > MTP-USER because an MTP-RESUME can only specify a RemotePc and no
other
> > SS7 element. I assume here for simplicity that every MTP-User of a
> > MTP-SAP must be given the same MTP status (i.e. different MTP-Users
of
> > the same MTP-SAP cannot be given different MTP-Status indications
> > depending on what traffic they have requested).
> 
> The AS can deliver whatever MTP-STATUS indications it cares to.  If
> there are SI values represented by the MTP-SAP, it is normally the
> MTP-User's responsibility to sort out the MTP-STATUS indications.

I don't know what you mean by "whatever MTP-STATUS indications it cares
to" but ITU Q.701 Table 1 shows that MTP-PAUSE and MTP-RESUME only
contain the affected DPC. A lot of MTP-user software has been written on
this assumption so we can't afford to change this.

> 
> >
> > Here's a concrete example of why this is so. Consider an ASP with
the
> > following routing keys:
> > RkA: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={A}
> > RkB: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={B}
> > RkC: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={M}
> > RkD: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={N}
> >
> > Assume that RkA and RkB were both active in SgpA and SgpB
respectively
> > and are associated with the same MTP-SAP, but different SGs.
> 
> To be associated with the same MTP-SAP, RkA and RkB must be identical,
> which implies that AsPcSetA and AsPcSetB are also identical.
> 
> > Also assume that a DAVA has been received for RemotePc=X from SgpA
after
> a
> > DUNA from SgpB for the same RemotePc. We might consider generating
an
> > MTP-Resume to all the MTP-Users of the MTP-SAP for RemotePc X.
However,
> if
> > an MTP-User requests an MTP-Transfer with an AsPc of B then SgpB may
not
> be
> > able to transfer it as indicated by the DUNA it sent the ASP.
> 
> This is not a problem because AsPc A must be identical to AsPc B.
Also,
> you do not seem to realize that DAVA and DUNA are specific to the SG.
> A DUNA received from one SG does not indicate that the affected
> destination
> is also unavailable via the other SG.  It takes a DUNA from both SGs
> to indicate that the affected destination is inaccessible.
> 
> >
> > The same explanation applies to RkC and RkD.
> 
> For RkC and RkD to be associated with the same MTP-SAP requires that
> they are identical according to the 1:1:1 rule above.
> 
> >
> > In practice this requirement probably won't cause too many headaches
> > because it is likely that there would be two different MTP-Users,
one
> > using only RkA/RkC and the other using only RkB/RkD.
> 
> In fact there must be two different MTP-SAPs (and necessarily
different
> MTP-Users from the perspective of the SG) for RkA/RkC to tbe different
> from RkB/RkD.
> 
> > In this case, we can simply create two MTP-SAPs in the same
MTP-Network
> and
> > associate each routing key with a different MTP-SAP. Of course, this
> would
> > require the M3UA implementation to support more than one MTP-SAP per
> > MTP-Network, which would be extra work obviously.
> 
> It is not extra work.  M3UA not only supports this but requires it.
> An MTP-SAP is an AS.  Having multiple AS (whether in a single network
> or not) is fundamental to the SIGTRAN model.
> 
> >
> > 4. ASP-SGP Routing should use SS7 Destination
Availability/Restricted
> > Status on a per-SGP rather than a per-SG basis.
> 
> Wrong.  ASPSM/ASPTM is per-SGP.  SSNM is per-SG.
> 
> >
> > I believe your ASP-SGP procedures should be amended (I only amend
the
> > multiple SG case as the single SG case is a special case of the
former)
> > as follows:
> >
> > Change:
> > "This routing information is updated by collecting DUNA/DAVA/DRST
> > messages received from (any of the SGP in) the SG."
> > To:
> > "This routing information is updated by collecting DUNA/DAVA/DRST
> > information on a per-(SGP,destination) basis. An SG is considered to
be
> > available and unrestricted for a particular destination if any SGP
in it
> > is available and unrestricted for that destination. Otherwise if
this is
> > not he case, then an SG is considered to be restricted for a
particular
> > destination if there is at least one SGP in the SG restricted for
that
> > destination. Otherwise if this is not the case, the SG is considered
to
> > be prohibited for that destination."
> >
> > The RFC is not particular clear on this point. In section 1.4.1 para
3
> > it states that "MTP3 routeset, SPMC and remote AS/ASP states of each
SGP
> > SHOULD be coordinated across all the SGPs". However, this uses
"SHOULD"
> > which implies it is only recommended and it also doesn't
specifically
> > state that SS7 destination availability, restriction and congestion
> > status ("SS7 destination status" for short) should be coordinated
across
> > all SGPs. I don't think that "MTP3 routeset" necessarily implies SS7
> > destination status. Also, in section 1.3.2.5 1.4.2.5 it suggests in
> > should be on a per-SGP basis. Section 4.5.2.2 uses the word "SG" but
> > also uses the term "affected route(s)". Section 1.3.2.5 and section
> > 1.4.2.5 suggest the word "route" refers to an SGP and not an SG.
Hence,
> > given the ambiguity of section 4.5.2.2 I think that route can be
> > considered to refer to an SGP.
> 
> Each SGP in an SG offers identical connectivity to the SS7 network.
> This means that a destination which is inaccessible to one SGP is
> inaccessible to all, congested, restricted, accessible, etc.

RFC section 1.4.1 para 3 makes it clear that the static configuration of
the connectivity of the SGPs must be identical, but it doesn't make it
clear that the SGPs should be designed to ensure identical connectivity
at runtime. In particular I am referring to the statement "Rerouting of
traffic between the MAY also be supported". If rerouting isn't supported
amongst the SGPs of an SG (either in the SGP's M3UA or within an MTP3
stack distributed between the SGPs) then I don't see how the SGPs can be
expected to have identical connectivity in the event of a single point
of failure.

Hence, I think that statements mirroring what you have said should be in
the implementor's guide. Otherwise, without reading these emails, other
people may be confused as to whether DAVA/DUNA/DRST destination status
should be kept on a per-SG or a per-SGP basis.

> 
> >
> > A configuration where per-SGP SS7 destination status is necessary is
as
> > follows. Consider an SEP SG which has two SGP's acting as a
redundant
> > pair. Each SGP has it's own link set to a particular STP. While in
> > section 1.4.1 para 3 it states that "Rerouting of traffic between
the
> > SGPs MAY also be supported", it uses "MAY" and hence this is
optional.
> > If one link set fails but not the other, one SGP will be able to
reach
> > the SS7 network but not the other if rerouting between SGPs is not
> > supported or the rerouting link has also failed. Hence, it would be
> > possible for one SGP to send a DUNA for a particular destination but
not
> > the other.
> 
> This is addressed.  The SGP has suffered a complete failure (it is
unable
> to process traffic) and can simply drop its associations to the ASPs.
> DUNA is incorrect here: the destination is still accessible from the
SG.
> One SGP has simply broken it's contract (providing identical
connectivity
> to the SS7 network as other SGP in the SG) and must be placed out of
> service.
> 
> --brian
> 
> >
> >
> > Your feedback would be appreciated.
> >
> > Jolan.
> >
> >
> > --
> > Jolan Evans
> > Open Telecommunications
> > jolan.evans@opentelecommunications.com
> >
> >
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org] On
Behalf
> > Of Brian F. G. Bidulock
> > Sent: Tuesday, 8 October 2002 17:47
> > To: Srikanth Yandapalli
> > Cc: sigtran@ietf.org
> > Subject: Re: [Sigtran] ASP to SGP communication
> >
> > Srikanth,
> >
> > Srikanth Yandapalli wrote:               (Tue, 08 Oct 2002 12:03:52)
> > >
> > >    I am late entrant to this group.I am quite sure all this should
> > have
> > >    been discussed and I am sorry about this.
> >
> > Welcome.
> >
> > >
> > >    In the context of a single ASP in communication with multiple
SGPs,
> > >    how should the routing of a MTP_DATA_REQ take place at the ASP?
> >
> > I assume you are talking about M3UA?  As we are dealing with 5 or
more
> > UAs
> > now, in the future it would be helpful to add M3UA (or whichever) to
the
> > subject line.
> >
> > >
> > >    approach 1:
> > >
> > >    We may find out the  RK and find out the SGP list that the RK
is
> > >    active on and choose one SGP for sending the message based
> > >    on congestion level and also whether we have received any DRST
> > >    message from any of the SGPs.
> >
> > This approach is applicable to multiple SGs, but not to multiple
SGPs
> > within a
> > single SG.
> >
> > >    approach 2:
> > >
> > >    An SGP can also be viewed as providing route to a set of DPCs
> > >    and the routing can be based on the DPC for the message alone.
> > >    This approach is reduces the complexity but adds a situation
> > >    where the RK may not be active on that association. And also is
> > >    is mandatory to send RC on this association and if so what
could
> > >    the SGP make out of the RC?
> >
> > RC should be coordinated and the same across multiple SGPs within an
SG.
> >
> > >
> > >    Is there a preferred approach to this issue?
> > >
> >
> > Typically, the logic can be something like this: (but there are
several
> > other
> > schools of thought):
> >
> > Single SG case: (multiple SGs is more complicated)
> >
> >   MTP-TRANSFER request is issued by an MTP-User.  The MTP-User is
bound
> > to an
> >   MTP-SAP.  The MTP-SAP is associated with an AS/RC/RK.  There is a
pool
> > of
> >   SGPs on an SG for which the AS/RC/RK is active.  The AS may have
> > received
> >   MTP-PAUSE/RESUME/STATUS indications from the SG and may choose to
> > honor that
> >   information or not.  If the ASP chooses not to honor this
information
> > it can
> >   blindly send messages to the SGP and rely upon a DUNA/SCON
response
> > from the
> >   SGP later.
> >
> >   Selection of an SGP within an SG is based on the traffic mode for
the
> > SGP.
> >   This traffic mode is not managed by M3UA, however, M3UA provides
for
> >   distribution of traffic over SGP based on any of the methods
described
> > for
> >   ASPs (active/standby, load-share, broadcast).  A typical method is
> >   load-share based on SLS.  In this scheme, using the SLS in the
> > MTP-TRANSFER
> >   request, the ASP selects load-shares traffic over the available
SGP.
> >
> > Multiple SG case:
> >
> >   In the more complicated multiple SG case, the ASP must first
select an
> > SG
> >   before it selects an SGP within the SG.  The ASP must maintain
some
> >   additional routing information to be able to properly select an
SG.
> > This
> >   routing information is updated by collecting DUNA/DAVA/DRST
messages
> >   received from (any of the SGP in) the SG.  To select the outgoing
SG,
> > the
> >   ASP must examine the destination of the MTP-TRANSFER request.
> >
> >   (If the SG has no SGP active for the AS/RC/RK, all destinations
can be
> >   considered prohibited).
> >
> >   If the destination is available and unrestricted for several SGs,
the
> > ASP
> >   should select an SG on a load-sharing basis (based on SLS) and
then
> > select
> >   an active SGP within the SG on the basis of the traffic mode for
the
> > SG.
> >
> >   If some SG are restricted for the specified destination (based on
> > received
> >   DRST messages from the SG), the ASP should load-share across the
> > available
> >   unrestricted SGs.  If all SGs are restricted for a given
destination,
> > the
> >   ASP should load-share across the available SGs and ignore the
> > restricted
> >   status.
> >
> >   If some SG are prohibited for the specified destination (based on
> > received
> >   DUNA messages from the SG), the ASP should load-share across the
> > available
> >   non-prohibited SGs.  If all SGs are prohibited for a given
destination
> > (or
> >   no SGP is active for the AS/RC/RK in any SG), the ASP should
respond
> > to the
> >   MTP-User with an MTP-PAUSE in accordance with the style of the
> > MTP-User
> >   interface (ITU-T and ANSI differ here).
> >
> > Properly selecting SGs requires that the ASP maintain the
DUNA/DAVA/DRST
> > information for each destination received from any SGP in an SG, on
a
> > per-SG
> > basis.  This is the same as MTP Level 3 ROUTE status.  However, SCON
> > information should only be maintained on a per-destination basis
(and
> > not
> > per-SG).  This is the same as MTP Level 3 ROUTESET status.
> >
> > Note that, in general, it is a bad idea to consider congestion
(SCON)
> > when
> > selecting an SG.  SCON does not necessarily indicate congestion at
an SG
> > or on
> > a path to an SG, but indicates congestion at the affected
destination or
> > somewhere (perhaps distant) in the SS7 network.  SCON is
> > ROUTESET-specific
> > (applies to the destination), whereas DUNA/DAVA/DRST is
ROUTE-specific
> > (applies to the destination and path).  SCON should only be used to
> > determine
> > whether a message should be dropped completely and an MTP-STATUS
> > returned to
> > the MTP-User according to the style of the MTP-User interface (ITU-T
and
> > ANSI
> > differ here again).
> >
> > So, to summarize:  on behalf of the AS/RC/RK/MTP-User, the ASP
> > determines
> > whether to send a message based on SCON received for the specified
> > destination, then selects an SG based on DUNA/DAVA/DRST received for
the
> > specified destination and load-shares based on SLS across the
eligible
> > SGs.
> > Once an SG is selected, an active SGP (active for the AS/RC/RK) is
> > selected
> > within the SG based on the traffic mode of the SG (active/standby,
> > load-share,
> > broadcast: but typically load-share on SLS).
> >
> > As I said, there are other schools of thought, but that is my
> > understanding.
> >
> > --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 mailnull@www1.ietf.org  Thu Jan 30 01:22: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 BAA10154
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 01:22:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U6iWU28168
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 01:44:32 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U6iAJ28147;
	Thu, 30 Jan 2003 01:44:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U6haJ28123
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 01:43:36 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10128
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 01:21:18 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:r59OzPG+pAXnRvacK3GzLCH6+oa5iH7h@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0U6OoD26822;
	Wed, 29 Jan 2003 23:24:50 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0U6OnG25600;
	Wed, 29 Jan 2003 23:24:49 -0700
Date: Wed, 29 Jan 2003 23:24:49 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA Flush Buffers (was: M2PA version 7 changes)
Message-ID: <20030129232449.A24921@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
References: <OF6E38DEEA.89D92DA5-ONC2256CBE.001EEB80@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF6E38DEEA.89D92DA5-ONC2256CBE.001EEB80@LocalDomain>; from TOLGA.ASVEREN@o2.com.tr on Thu, Jan 30, 2003 at 07:39:08AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: 8bit
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

TOLGA,

TOLGA ASVEREN wrote:                                                                 (Thu, 30 Jan 2003 07:39:08)
> 
> Brian,
> 
> So the decision is that during flushing we don´t need to flush messages in
> SCTP buffers(?).
> 

What does it matter?

--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  Thu Jan 30 01:27: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 BAA10222
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 01:27:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U0Rxc03759
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 19:27:59 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U0RFJ03743;
	Wed, 29 Jan 2003 19:27:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U0QCJ03708
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 19:26:12 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03866
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 19:03:28 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:zRyEfBvN1zu+4ZaHgiQY+0D3XOTNHxNA@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0U06xD22258;
	Wed, 29 Jan 2003 17:06:59 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0U06xu17282;
	Wed, 29 Jan 2003 17:06:59 -0700
Date: Wed, 29 Jan 2003 17:06:59 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tom George <Tom.George@alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA LPO during alignment/proving (was: M2PA version 7 changes)
Message-ID: <20030129170659.B13613@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tom George <Tom.George@alcatel.com>, sigtran@ietf.org
References: <3D72C18DF140D311A54F0008C7DBAC8D02917425@MCHH252E> <3E38613F.FF645442@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: <3E38613F.FF645442@alcatel.com>; from Tom.George@alcatel.com on Wed, Jan 29, 2003 at 05:18:23PM -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>

Tom,

The problem is the LSC doesn't really have a proving state (only IAC
has proving state).  LSC always moves from INITIAL ALIGNMENT to either
ALIGNED READY or ALIGNED NOT READY.  You might change the diagram as
follows:

 From: 

  |                       |                            |                
  |                       | MTP3 Start                 |                
  |                       V                            |                
  |                 +-----------+                      |                
  |                 |  INITIAL  |                      |                
  +<----------------| ALIGNMENT |--------------------->+                
  |      MTP3 Stop  +-----------+     SCTP Comm Error  |                
  |   OR T2 Expiry        |  ^     OR SCTP Comm Lost   |                
  |   OR Receive LS OOS   |  |                         |                
  |                       |  +-------------------------|--------+      
  |                       |              LPO/LPR       |        |      
  |                       |                            |        |
  |                       | Receive LS Align           |        |
  |                       |                            |        |
  |                       V                            |        |
  |                 +-----------+        LPO/LPR       |        |
  |                 |  PROVING  |<---------------------|--------+
  |<----------------|           |--------------------->+        |
  |      MTP3 Stop  +-----------+     SCTP Comm Error  |        |
  |   OR T3 Expiry        |        OR SCTP Comm Lost   |        |
  |   OR Receive LS OOS   |                            |        |      
  |                       | T4 Expiry                  |        |      
  |                       | Send LS Ready              |        |      
  |                       V                            |        V      
  |                 +-----------+        LPO/LPR       |  +-----------+
  |                 |  ALIGNED  |<---------------------|->|  ALIGNED  |
  +<----------------|   READY   |--------------------->+  | NOT READY |
  |      MTP3 Stop  +-----------+     SCTP Comm Error     +-----------+
  |   OR T1 Expiry        |        OR SCTP Comm Lost         |       |
  |   OR Receive LS OOS   |                                  |   T1  | 
  |   OR Receive LS Align | Receive LS Ready      Receive    | Expiry|
  |                       | OR Receive User Data    LS Ready | OR Rcv|
  |                       |                       OR Receive |    LS |
  |                       |                         LS PO    |  Align|
  |                       |                                  |       |

 To:

  |                       |                            |               
  |                       | MTP3 Start                 |               
  |                       V                            |               
  |                 +-----------+        LPO/LPR       |  +-----------+
  |                 |  INITIAL  |<---------------------|->|  INITIAL  |
  +<----------------| ALIGNMENT |--------------------->+  | ALIGNMENT |
  |      MTP3 Stop  +-----------+     SCTP Comm Error  |  +-----------+
  |   OR T2 Expiry        |        OR SCTP Comm Lost   |        |      
  |   OR Receive LS OOS   |                            |        |      
  |                       | Receive                    |   Recv |      
  |                       | LS Align                   |     LS |      
  |                       |                            |  Align |      
  |                       V                            |        V      
  |                 +-----------+        LPO/LPR       |  +-----------+
  |                 |  PROVING  |<---------------------|->|  PROVING  |
  |<----------------|           |--------------------->+<-|           |
  |      MTP3 Stop  +-----------+     SCTP Comm Error  |  +-----------+
  |   OR T3 Expiry        |        OR SCTP Comm Lost   |        |      
  |   OR Receive LS OOS   |                            | T4 Exp |      
  |                       | T4 Expiry                  |   Send |      
  |                       | Send LS Ready              |  LS PO |      
  |                       V                            |        V      
  |                 +-----------+        LPO/LPR       |  +-----------+
  |                 |  ALIGNED  |<---------------------|->|  ALIGNED  |
  +<----------------|   READY   |--------------------->+  | NOT READY |
  |      MTP3 Stop  +-----------+     SCTP Comm Error     +-----------+
  |   OR T1 Expiry        |        OR SCTP Comm Lost         |       | 
  |   OR Receive LS OOS   |                                  |   T1  | 
  |   OR Receive LS Align | Receive LS Ready      Receive    | Expiry| 
  |                       | OR Receive User Data    LS Ready | OR Rcv| 
  |                       |                       OR Receive |    LS | 
  |                       |                         LS PO    |  Align| 
  |                       |                                  |       | 
  |                       |                                  |       | 
  |                       V                                  V       | 
  |                 +-----------+        LPO/LPR       +-----------+ | 
  |                 |    IN     |<-------------------->| PROCESSOR | | 
  |                 |  SERVICE  |                      |   OUTAGE  | | 
  |                 +-----------+                      +-----------+ | 

This would indicates that the LSC moves from INITIAL ALIGNMENT to
ALIGNED READY or ALIGNED NOT READY regardless of PROVING.  That is what the
line from INITIAL alignment to ALIGNED NOT READY was intended to indicate
in shorthand.

I suppose one could draw it as:

  |                       | MTP3 Start                 |               
  |                       |                            |               
  |                       |   +-------+                |               
  |                       |   |       | LPO/LPR        |               
  |                       V   V       |                |               
  |                 +-----------+     |                |               
  |                 |  INITIAL  |<----+                |               
  +<----------------| ALIGNMENT |--------------------->+               
  |      MTP3 Stop  +-----------+     SCTP Comm Error  |               
  |   OR T2 Expiry        |        OR SCTP Comm Lost   |               
  |   OR Receive LS OOS   |                            |               
  |                       | Receive                    |               
  |                       | LS Align                   |               
  |                       |                            |               
  |                       |   +-------+                |               
  |                       |   |       | LPO/LPR        |               
  |                       V   V       |                |               
  |                 +-----------+     |                |               
  |                 |  PROVING  |<----+                |               
  |<----------------|           |--------------------->+               
  |      MTP3 Stop  +-----------+     SCTP Comm Error  |               
  |   OR T3 Expiry        | |      OR SCTP Comm Lost   |               
  |   OR Receive LS OOS   | |                          |               
  |                       | +--------------------------|--------+      
  |                       |                            |   T4   |      
  |                       | T4 Expiry                  | Expiry |      
  |                       | Send LS Ready              | Send   |      
  |                       V                            | LS PO  V      
  |                 +-----------+        LPO/LPR       |  +-----------+
  |                 |  ALIGNED  |<---------------------|->|  ALIGNED  |
  +<----------------|   READY   |--------------------->+  | NOT READY |
  |      MTP3 Stop  +-----------+     SCTP Comm Error     +-----------+
  |   OR T1 Expiry        |        OR SCTP Comm Lost         |       | 
  |   OR Receive LS OOS   |                                  |   T1  | 
  |   OR Receive LS Align | Receive LS Ready      Receive    | Expiry| 
  |                       | OR Receive User Data    LS Ready | OR Rcv| 
  |                       |                       OR Receive |    LS | 
  |                       |                         LS PO    |  Align| 
  |                       |                                  |       | 
  |                       |                                  |       | 
  |                       V                                  V       | 
  |                 +-----------+        LPO/LPR       +-----------+ | 
  |                 |    IN     |<-------------------->| PROCESSOR | | 
  |                 |  SERVICE  |                      |   OUTAGE  | | 
  |                 +-----------+                      +-----------+ | 

The effect is the same.  The diagram is certainly not intended to be 100%
complete, it is an overview.  The text should be consulted.

--brian

Tom George wrote:                                   (Wed, 29 Jan 2003 17:18:23)
> IMHO if there is a local PO while in INITIAL ALIGNMENT, M2PA should
> continue sending/receiving LS Alignment, i.e., remain in INITIAL
> ALIGNMENT. 
> 
> After the LS Alignment is sent and received, M2PA would move to PROVING
> and send/receive LS Proving messages. 
> 
> When T4 expires, it seems to me that M2PA would go ahead and
> send/receive the LS Ready messages. That's the ALIGNED READY state. 
> 
> In short, it looks to me that if there is a local PO, M2PA should
> continue with alignment and proving and should not go into ALIGNED NOT
> READY until it is completed with the ALIGNED READY state.
> 
> Or if M2PA does go to ALIGNED NOT READY earlier than that, it should
> continue doing what it would have done in INITIAL ALIGNMENT, PROVING,
> and ALIGNED READY. Which looks like a confusing way to explain it. 
> 
> tomG.
> 
> Gaiser Franz wrote:
> > 
> > Dear All,
> > 
> > some remarks to the new draft version 07:
> > 
> > 1.)  Figure 7. M2PA Link State Transition Diagram:
> > Why is there an arrow from state INITIAL ALIGNMENT to state 
> > ALIGNED NOT READY  ? If the local side is in processor outage, 
> > the PROVING period should be passed before moving to 
> > ALIGNED NOT READY state.
>   [...]
> 
> -- 
> * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> * Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
> * 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 Jan 30 01:36: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 BAA10373
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 01:36:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U6wgT28658
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 01:58:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U6w7J28622;
	Thu, 30 Jan 2003 01:58:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U6vWJ28581
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 01:57:32 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10350
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 01:35:14 -0500 (EST)
Subject: Re: [Sigtran] M3UA SG-SG (again)
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFA717662C.8242F4B8-ONC2256CBE.00227E20@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Thu, 30 Jan 2003 08:35:19 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/30/2003
 08:35:24 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>


Ken,

[KAM] do you plan to apply for a different SCTP port for SG-SG or reuse
M3UA port of 2905?

[TOLGA]I would think 2905 should be fine. Unless we restrict ASPs to use a
specific port (which is allocated for SG-SG), still we would need to look
to ASPID in ASPUP to decide for the type of peer, when dynamic addressing
is used.

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



From mailnull@www1.ietf.org  Thu Jan 30 01:38: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 BAA10409
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 01:38:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0TNfJf01621
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 18:41:19 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TNecJ01576;
	Wed, 29 Jan 2003 18:40:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TNb3J00852
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 18:37:03 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03162
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 18:14:53 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0TNINqe029676;
	Wed, 29 Jan 2003 17:18:23 -0600 (CST)
Message-ID: <3E38613F.FF645442@alcatel.com>
Date: Wed, 29 Jan 2003 17:18:23 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: sigtran@ietf.org
References: <3D72C18DF140D311A54F0008C7DBAC8D02917425@MCHH252E>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M2PA LPO during alignment/proving (was: M2PA version 7 changes)
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

IMHO if there is a local PO while in INITIAL ALIGNMENT, M2PA should
continue sending/receiving LS Alignment, i.e., remain in INITIAL
ALIGNMENT. 

After the LS Alignment is sent and received, M2PA would move to PROVING
and send/receive LS Proving messages. 

When T4 expires, it seems to me that M2PA would go ahead and
send/receive the LS Ready messages. That's the ALIGNED READY state. 

In short, it looks to me that if there is a local PO, M2PA should
continue with alignment and proving and should not go into ALIGNED NOT
READY until it is completed with the ALIGNED READY state.

Or if M2PA does go to ALIGNED NOT READY earlier than that, it should
continue doing what it would have done in INITIAL ALIGNMENT, PROVING,
and ALIGNED READY. Which looks like a confusing way to explain it. 

tomG.

Gaiser Franz wrote:
> 
> Dear All,
> 
> some remarks to the new draft version 07:
> 
> 1.)  Figure 7. M2PA Link State Transition Diagram:
> Why is there an arrow from state INITIAL ALIGNMENT to state 
> ALIGNED NOT READY  ? If the local side is in processor outage, 
> the PROVING period should be passed before moving to 
> ALIGNED NOT READY state.
  [...]

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
* 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 Jan 30 01:40:57 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 BAA10506
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 01:40:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0TMkkM30480
	for sigtran-archive@odin.ietf.org; Wed, 29 Jan 2003 17:46:46 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TMkIJ30458;
	Wed, 29 Jan 2003 17:46:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TMjhJ30428
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 17:45:43 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02242
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 17:23:35 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:r155XUEYKSl17PBFbQdgL0cWfberKKXa@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0TMR5D20896;
	Wed, 29 Jan 2003 15:27:05 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0TMR5g05645;
	Wed, 29 Jan 2003 15:27:05 -0700
Date: Wed, 29 Jan 2003 15:27:05 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tom George <Tom.George@alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA Link OOS (was: M2PA version 7 changes)
Message-ID: <20030129152705.A4253@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tom George <Tom.George@alcatel.com>, sigtran@ietf.org
References: <3D72C18DF140D311A54F0008C7DBAC8D02917425@MCHH252E> <3E384D0E.AF500008@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: <3E384D0E.AF500008@alcatel.com>; from Tom.George@alcatel.com on Wed, Jan 29, 2003 at 03:52:14PM -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>

Tom,

I like the little OOS section idea.

--brian

Tom George wrote:                                                                      (Wed, 29 Jan 2003 15:52:14)
> Franz and others,
> 
> Yes, in that case M2PA should send LS OOS to its peer. 
> 
> There are several places in the document where the link goes OOS. As it
> stands now, I do not always state all of the actions to be taken because
> they are more-or-less understood:
> 
> - Send LS OOS to the peer.
> - Notify MTP3 of Out of Service condition.
> - Leave the SCTP association up. (a SHOULD)
> - Wait for MTP3 to begin alignment.
> 
> What is the best way to explain this? Repeat it throughout the document,
> or have a little OOS section (similar to 4.2.3  Link deactivation), or
> just leave it as is and count on the reader to understand it?
> 
> tomG.
> 
> Gaiser Franz wrote:
> > 
> > Dear All,
> > 
> > some remarks to the new draft version 07:
> > 
>   [...]
> > 4.) 4.2.1 Paragraph "If M2PA receives a User Data message with 
> > an FSN that is out of order, M2PA SHALL take the link out of service."
> > Does "take the link out of service"  mean also that the peer side is 
> > informed via sending LS OOS message.
>   [...]
> 
> -- 
> * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> * Alcatel USA, Inc.; 1000 Coit Rd, MS PB7-SWPRO; Plano TX 75075-5813  *
> * 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 Jan 30 01: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 BAA10902
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 01:57:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U7JHv07562
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 02:19:17 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U7IoJ07540;
	Thu, 30 Jan 2003 02:18:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U7HTJ07484
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 02:17:29 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10820
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 01:55:10 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0U6wceW026863;
	Thu, 30 Jan 2003 00:58:39 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id LAA27952; Thu, 30 Jan 2003 11:27:26 -0500 (GMT)
Message-ID: <3E38CD3F.94A343E5@axes-mach01.usa.alcatel.com>
Date: Thu, 30 Jan 2003 12:29:11 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
References: <OFEC77243A.47A4213E-ONC2256CBC.002FD630@LocalDomain> <3E38AC51.B358D2E7@axes-mach01.usa.alcatel.com> <20030129223645.C1341@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

      Can you please tell me, how a message received from the SS7 network is routed using such a SGP(having two
different associations) to the AS?.

--Srini.

"Brian F. G. Bidulock" wrote:

> Srini,
>
> ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 10:08:41)
> > Tolga,
> >
> > An ASP can be a part of different ASs. Similarly, Can a SGP be a part of
> > different SGs?
>
> Sure.  But from the viewpoint of an ASP, the SGP belongs to one SG.  If an
> SGP were to perform the function for two SGs for the same AS, the ASP would
> have to form two associations with the SGP: one for SG-A, the other for SG-B.
> The SGP would also need some way of knowing (e.g. static port allocation)
> for which SG the ASP was forming an association.
>
> --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 mailnull@www1.ietf.org  Thu Jan 30 01:58: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 BAA10951
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 01:58:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U7KKu07657
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 02:20:20 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U7KAJ07640;
	Thu, 30 Jan 2003 02:20:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U7JuJ07589
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 02:19:56 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10916
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 01:57:37 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:6Jbv9Z10x5kTgBNBnb6eccVz3J0EtjOW@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0U718D27285;
	Thu, 30 Jan 2003 00:01:08 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0U718E29600;
	Thu, 30 Jan 2003 00:01:08 -0700
Date: Thu, 30 Jan 2003 00:01:08 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
Message-ID: <20030130000108.A28966@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
References: <OFEC77243A.47A4213E-ONC2256CBC.002FD630@LocalDomain> <3E38AC51.B358D2E7@axes-mach01.usa.alcatel.com> <20030129223645.C1341@openss7.org> <3E38CD3F.94A343E5@axes-mach01.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: <3E38CD3F.94A343E5@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Thu, Jan 30, 2003 at 12:29:11PM +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>

Srini,

The association would be chosen on the basis of for which SG the
message from the SS7 network arrived.

--brian

ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:29:11)
> Brian,
> 
>       Can you please tell me, how a message received from the SS7 network is routed using such a SGP(having two
> different associations) to the AS?.
> 
> --Srini.
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Srini,
> >
> > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 10:08:41)
> > > Tolga,
> > >
> > > An ASP can be a part of different ASs. Similarly, Can a SGP be a part of
> > > different SGs?
> >
> > Sure.  But from the viewpoint of an ASP, the SGP belongs to one SG.  If an
> > SGP were to perform the function for two SGs for the same AS, the ASP would
> > have to form two associations with the SGP: one for SG-A, the other for SG-B.
> > The SGP would also need some way of knowing (e.g. static port allocation)
> > for which SG the ASP was forming an association.
> >
> > --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 mailnull@www1.ietf.org  Thu Jan 30 02:10: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 CAA21065
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 02:10:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U7WbD08525
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 02:32:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U7W7J08503;
	Thu, 30 Jan 2003 02:32:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U7VLJ08453
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 02:31:21 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21043
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 02:09:01 -0500 (EST)
Subject: Re: [Sigtran] M3UA SG-SG (again)
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF4E9B7D1F.84FBCFCD-ONC2256CBE.0025C9E4@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Thu, 30 Jan 2003 09:09:07 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/30/2003
 09:09:11 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>


Ken,

[KAM] SGP must maintain state on a per SGP peer basis.  Is SGP up after
sending
ASP UP, or after receiving ASP UP ACK, or after DE transfer of ASP UP and
ASP
UP ACK?

[KAM] i'm not sure you say anywhere in the text that ASPUP is double-ended.
certainly,
this needs to be discussed in the state machines above.

[TOLGA]When ASPUP or ASPUP-ACK is received from peer, remote ASP switches
to ASPUP state.
In fact in "2.5 Point Code Status Information Exchange" this is explained:
"After a SCTP association is established, peers SHOULD declare the
availability of their M3UA layer with ASPUP messages. A received
ASPUP message is replied with ASPUP-ACK. If one of the peers
receives ASPUP message before sending ASPUP, it MAY or MAY NOT send
ASPUP message, ASPUP-ACK message declares availability of the remote
peer. Each SGP should declare its availability to each SGP of the
remote SGs separately. A SGP can declare its unavailability with
ASPDN message. ASPDN message is acknowledged with ASPDN-ACK message."

 Also in state machine for SGP, SGP switches to SGPUP state with ASPUP or
ASPUP-ACK.

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



From mailnull@www1.ietf.org  Thu Jan 30 02:18:57 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 CAA21214
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 02:18:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U7ek009711
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 02:40:46 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U7e9J09694;
	Thu, 30 Jan 2003 02:40:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U7d3J09631
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 02:39:03 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21166
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 02:16:43 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0U7KBeW028934;
	Thu, 30 Jan 2003 01:20:12 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id LAA28562; Thu, 30 Jan 2003 11:48:52 -0500 (GMT)
Message-ID: <3E38D245.A5C93237@axes-mach01.usa.alcatel.com>
Date: Thu, 30 Jan 2003 12:50:37 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
References: <OFEC77243A.47A4213E-ONC2256CBC.002FD630@LocalDomain> <3E38AC51.B358D2E7@axes-mach01.usa.alcatel.com> <20030129223645.C1341@openss7.org> <3E38CD3F.94A343E5@axes-mach01.usa.alcatel.com> <20030130000108.A28966@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

    So, the M3UA at the SGP should be informed the SG which received this message.

--Srini

"Brian F. G. Bidulock" wrote:

> Srini,
>
> The association would be chosen on the basis of for which SG the
> message from the SS7 network arrived.
>
> --brian
>
> ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:29:11)
> > Brian,
> >
> >       Can you please tell me, how a message received from the SS7 network is routed using such a SGP(having two
> > different associations) to the AS?.
> >
> > --Srini.
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > Srini,
> > >
> > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 10:08:41)
> > > > Tolga,
> > > >
> > > > An ASP can be a part of different ASs. Similarly, Can a SGP be a part of
> > > > different SGs?
> > >
> > > Sure.  But from the viewpoint of an ASP, the SGP belongs to one SG.  If an
> > > SGP were to perform the function for two SGs for the same AS, the ASP would
> > > have to form two associations with the SGP: one for SG-A, the other for SG-B.
> > > The SGP would also need some way of knowing (e.g. static port allocation)
> > > for which SG the ASP was forming an association.
> > >
> > > --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

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



From mailnull@www1.ietf.org  Thu Jan 30 02:54: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 CAA21753
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 02:54:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U8G1o11822
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 03:16:01 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U8FJJ11774;
	Thu, 30 Jan 2003 03:15:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U8ECJ11720
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 03:14:12 -0500
Received: from envoy.ot.com.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA21701
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 02:51:47 -0500 (EST)
Received: (qmail 24422 invoked by uid 40); 30 Jan 2003 07:55:18 -0000
Received: from jolan.evans@opentelecommunications.com by envoy by uid 51 with qmail-scanner-1.12 (. Clear:. Processed in 0.261202 secs); 30 Jan 2003 07:55:18 -0000
X-Qmail-Scanner-Mail-From: jolan.evans@opentelecommunications.com via envoy
X-Qmail-Scanner: 1.12 (Clear:. Processed in 0.261202 secs)
Received: from unknown (HELO nobel.in.ot.com.au) (10.70.10.5)
  by envoy.ot.com.au with SMTP; 30 Jan 2003 07:55:17 -0000
Received: (qmail 13664 invoked from network); 30 Jan 2003 07:54:51 -0000
Received: from druid.in.ot.com.au (10.70.80.5)
  by nobel.syd.ot with SMTP; 30 Jan 2003 07:54:51 -0000
Received: (qmail 18554 invoked from network); 30 Jan 2003 07:54:50 -0000
Received: from unknown (HELO Mars) (10.70.12.144)
  by druid.in.ot.com.au with SMTP; 30 Jan 2003 07:54:50 -0000
From: "Jolan Evans" <jolan.evans@opentelecommunications.com>
To: <bidulock@openss7.org>
Cc: "Sigtran" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: ASP to SGP communication
Date: Thu, 30 Jan 2003 18:53:54 +1100
Organization: Open Telecommunications
Message-ID: <005c01c2c834$bce760d0$900c460a@Mars>
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, Build 10.0.2627
In-Reply-To: <20030129222748.A1341@openss7.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
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

More comments below...


--
Jolan Evans


Open Telecommunications
jolan.evans@opentelecommunications.com


> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Thursday, 30 January 2003 16:28
> To: Jolan Evans
> Cc: 'Sigtran'
> Subject: Re: [Sigtran] M3UA: ASP to SGP communication
> 
> Jolan,
> 
> More comments below....
> 
> Jolan Evans wrote:
> (Thu, 30 Jan 2003 14:27:28)
> > See my comments below...
> >
> >
> > --
> > Jolan Evans
> > Open Telecommunications
> > jolan.evans@opentelecommunications.com
> >
> >
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: Tuesday, 28 January 2003 19:53
> > > To: Jolan Evans
> > > Cc: Sigtran
> > > Subject: Re: [Sigtran] M3UA: ASP to SGP communication
> > >
> > > Jolan,
> > >
> > > You are a litte of track: please see comments below...
> > >
> > > Jolan Evans wrote:
> > > (Tue, 28 Jan 2003 19:01:56)
> > > > I would like to raise a few issues regarding your procedures
below
> > for
> > > > ASP to SGP routing. I know this discussion took places a while
ago,
> > but
> > > > it has taken me some time to come up to speed with the RFC as I
have
> > > > been busy on other things until recently.
> > > >
> > > > Please note that I have inserted "M3UA" into the subject line of
the
> > > > original email.
> > > >
> > > >
> > > >
> > > > 1. Nomenclature
> > > > AsPc: Point code of an AS. In defining routing keys, the RFC
uses
> > DPC
> > > > for this term as it takes the SG's frame of reference.
> > > > RemotePc: Point code of an SS7 MTP entity with which an AS
> > communicates
> > > > via an SG, or directly in the case of IPSP-IPSP communication.
In
> > > > defining routing keys, the RFC uses OPC for this term as it
takes
> > the
> > > > SG's frame of reference again.
> > > >
> > > >
> > > >
> > > > 2. Background Assumptions
> > > > As per Brian's introduction, we assume that zero or more
MTP-User's
> > are
> > > > bound to an MTP-SAP. The MTP-SAP exists in a particular
MTP-Network,
> > > > which has a particular MTP protocol variant. An SG is associated
> > with a
> > > > single MTP-Network. A RK is defined as in the RFC, but, for
clarity,
> > is
> > > > independent of any SG and associated with a single MTP-Network.
An
> > > > SgRouteSet is uniquely defined by an RK, an SG and an MTP-SAP
(the
> > RK
> > > > and SG must be both associated with the same MTP-Network) and
also
> > > > specifies the network appearance for the MTP-Network to be used
with
> > the
> > > > SG and the RC of each SGP in the SG. Therefore, an SgRouteSet is
> > > > implicitly associated with a single MTP-Network. An MTP-SAP is
> > > > associated with zero or more SgRouteSet's and therefore an
MTP-SAP
> > is
> > > > associated with zero or more RKs.
> > >
> > > Bad assumption.  An MTP-SAP is assocated with one RK.  This is the
> > > 1:1:1 rule between AS:RK:RC.
> >
> > Ok, I neglected to state the circumstances and in particular the
network
> > topologies which drove me to make these assumptions, and in
particular,
> > the 1:many association between MTP-SAP:RK. Nonetheless, I can't find
> > statements in the RFC to support your statement that an "MTP-SAP is
> > assocated with one RK" and hence I would have to call this an
assumption
> > also. However, I stand corrected if this is not the case.
> 
> Secion 1.2 Terminology: Application Server:
> 
>   "... Note that there is a 1:1 relationship between an AS and a
>   Routing Key".

You seem to be misreading what I have written. I've never said anything
to contradict that there is a 1:1 relationship between an AS and a RK.
My assumption is that there is a 1:many relationship between  RK's (or
AS's) and MTP-SAPs. I quote myself: "an MTP-SAP is associated with zero
or more RKs".

Your assumption is that there is a 1:1 relationship between RK's (or
AS's) and MTP-SAP's. I quote you: "An MTP-SAP is assocated with one RK".


Both of these statements are assumptions as far as the RFC is concerned
because the RFC makes no mention of an MTP-SAP entity (it only defines
an MTP-User).

> 
> >
> > Without further ado, here is one of the network topologies in which
our
> > ASP M3UA must operate. NB This is defined by our customers so we
can't
> > change it.
> >
> > We must communicate with a number of SGs, for simplicity let's just
say
> > 2 as that's all that I need to illustrate my point. Likewise, it's
not
> > important how many SGP's they each have, so for simplicity let's
assume
> > that each SG has just one. Here is the network to which the ASP is
> > connected:
> >
> > MtpNetworkA: Protocol=ITU 92
> >
> > MtpSapA: Network=MtpNetworkA
> 
> An MTP-SAP cannot be defined as an entire network (even just for SS7),
> and there is no reason to do so.

Again, as the RFC doesn't define an MTP-SAP, I'm free to define it.

> 
> >
> > SgA: Network=MtpNetworkA
> > SgB: Network=MtpNetworkA
> >
> > SgpA: Sg=SgA, etc
> > SgpB: Sg=SgB, etc
> >
> > RkA: Network=MtpNetworkA, AsPcSet={PcA, PcB}, RemotePcSet={PcW, PcX}
> > RkA: Network=MtpNetworkA, AsPcSet={PcC, PcD}, RemotePcSet={PcY, PcZ}
> 
> I think you mean RkB on this last entry?

Yes, a typo.

> 
> Also, the only way you can have multiple point codes in the AsPcSet
> is if the point codes are "aliases" for the same signalling point.
> In which case, the accessibility, for example, from PcA to PcW is
> identical to the accesssibility from PcB to PcW.

Fair enough.

> 
> >
> > SgRouteSetA: Sap=MtpSapA, RoutingKey=RkA, Sg=SgA,
NetworkAppearance=0,
> > SgpSet={(SgpA, Rc=0)}
> > SgRouteSetB: Sap=MtpSapA, RoutingKey=RkB, Sg=SgB,
NetworkAppearance=0,
> > SgpSet={(SgpB, Rc=0)}
> 
> Again you try to have one AS serving multiple Routing Keys.  This
violates
> the 1:1 rule.  Because you have two RKs, you have two AS (and at least
> two MTP-SAPs).

No, you appear to have misread what I have written. The one MTP-SAP (not
the same as an AS) has two RKs (or AS's).

> 
> >
> > In this model, when the ASP-ACTIVE ACK is received for RkA (RkB),
the
> > ASP will audit the state of the RemotePcSet of RkA (RkB) at SgpA
(SgpB).
> > Ie the RemotePcSet of a routing key determine which remote PCs
should
> > have their status audited at a particular SG (I'll ignore the issue
of
> > whether it is SG or SGP for now).
> >
> > I'm not clear how this would be translated to your model. As I see
it,
> > there is a problem because an MTP-SAP is only allowed to have one RK
but
> > the MTP-User of the SAP wants to talk with 2 different SGs, each
with
> > their own routing keys.
> 
> It is not my model.
> 
> Because you have two AS, there is not problem.  AS-A audits remote
> desinations on RkA, AS-B audits remote destinations on RkB.
> 

Again, you appear to have misread what I have written. The one MTP-SAP
(not the same as an AS) has two RKs (or AS's).

> >
> > I can see 2 obvious ways to translate this configuration into your
> > model: Either define just one RK or define two MTP-SAPs.
> 
> It is not my model.
> 
> But, you are required to define two AS because of the 1:1 rule.  How
> many MTP-SAPs you have at the ASP is implementation dependent.

Now we seem to be in agreement! To keep our MTP-Users simple, our
implementation will allow the one MTP-SAP to be associated with both
AS's, and as you state, the number of MTP-SAPs is implementation
dependent.

> 
> >
> > However, if there is one RK then we can no longer rely upon the
> > RemotePcSet of the RK to determine the set of remote PCs of which
the
> > status should be audited when an ASP goes active with an SGP. This
seems
> > awkward and would seemingly require the RemotePcSet to be an
attribute
> > of the SgRouteSet.
> >
> > If there are two MTP-SAPs then we are burdening the MTP-USER which
must
> > now aggregate traffic and destination status from two different
> > MTP-SAPs. As far as I'm aware, in plain old MTP3 an MTP-USER can
happily
> > talk via just one MTP-SAP to two different STPs which have routesets
to
> > a different set of remote PCs.
> 
> For this situation, you do not need to burden the MTP-User.  It is the
> M3UA layer at the ASP which is burdened.  In the multiple SG scenario,
> the M3UA layer at the ASP is responsible for understanding which AS
> correspond to which MTP-SAPs, and handling routing, and determining
when
> to send an MTP-User an MTP-PAUSE or RESUME based on DUNA and DAVA
received
> from each of the various SG.

Sorry, but I don't understand how the MTP-User is not burdened. If there
are two MTP-SAPs upon which the MTP-User can receive MTP-Resume,
presumably the MTP-User will have to keep track of which one is
accessible for a particular remote PC and then send traffic on an
MTP-SAP in which the destination is accessible.

> 
> So, in effect, although you require two AS, how many MTP-SAPs you have
> at the ASP is implementation dependent.
> 
> In the non-multiple SG scenario (or where access is via a pair of SG
> acting a an STP pair), the AS nicely maps 1:1 to an MTP-SAP.

Agreed.

> 
> >
> > Most of your remaining comments on my original items 2 and 3 are on
the
> > basis that one cannot assume a 1-many MTP-SAP:RK relationship. I
won't
> > reply to such comments as the real issue is the assumption itself.
> 
> You cannot have a 1:many AS:RK relationship.  How many AS you map into
> an MTP-SAP is the implementation's business.
> 
> But your statement that the remainder of my comments are based on this
> is untrue.  SSNM on a per-SGP basis is false and was ruled out in the
> design of the protocol.  This has nothing to do with multiple RKs for
> an MTP-SAP.

You appear to have missed the "items 2 and 3" qualification. SSNM on a
per-SGP basis was in item 4.

> 
> --brian
> 
> >
> > >
> > > > In contrast, it appears that Brian
> > > > assumes that an MTP-SAP can only be associated with one RK.
Given
> > this
> > > > extension, we have the following requirement.
> > > >
> > > >
> > > >
> > > > 3. Routing Keys Requirements to Support Unique SS7 Destination
> > Status
> > > > Let RemotePcSet(Rk) be the set of RemotePc's reachable via the
SG
> > from
> > > > the ASP where the RK is defined.
> > >
> > > RKs do not have to be defined at ASPs, just MTP-SAPs.
> > >
> > > > Consider any two SgRouteSet's SgRsA and SgRsA which are
associated
> > with
> > > > the same MTP-SAP.
> > >
> > > I think you mean SgRsA and SgRsB <---.
> > >
> > > > Let the routing key of SgRsA and SgRsB be RkA and RkB
respectively.
> > > > If the intersection of RemotePcSet(RkA) and RemotePcSet(RkB) is
> > non-nil
> > > > then the routing keys MUST be identical in every respect apart
from
> > > > their RemotePcSet.
> > >
> > > RkA and RkB must be identical or they cannot be associated with
the
> > > same MTP-SAP.  See 1:1:1 rule above.
> > >
> > > > If this wasn't the case, an ASP could never indicate an
MTP-RESUME
> > to an
> > > > MTP-USER because an MTP-RESUME can only specify a RemotePc and
no
> > other
> > > > SS7 element. I assume here for simplicity that every MTP-User of
a
> > > > MTP-SAP must be given the same MTP status (i.e. different
MTP-Users
> > of
> > > > the same MTP-SAP cannot be given different MTP-Status
indications
> > > > depending on what traffic they have requested).
> > >
> > > The AS can deliver whatever MTP-STATUS indications it cares to.
If
> > > there are SI values represented by the MTP-SAP, it is normally the
> > > MTP-User's responsibility to sort out the MTP-STATUS indications.
> >
> > I don't know what you mean by "whatever MTP-STATUS indications it
cares
> > to" but ITU Q.701 Table 1 shows that MTP-PAUSE and MTP-RESUME only
> > contain the affected DPC. A lot of MTP-user software has been
written on
> > this assumption so we can't afford to change this.
> >
> > >
> > > >
> > > > Here's a concrete example of why this is so. Consider an ASP
with
> > the
> > > > following routing keys:
> > > > RkA: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={A}
> > > > RkB: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={B}
> > > > RkC: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={M}
> > > > RkD: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={N}
> > > >
> > > > Assume that RkA and RkB were both active in SgpA and SgpB
> > respectively
> > > > and are associated with the same MTP-SAP, but different SGs.
> > >
> > > To be associated with the same MTP-SAP, RkA and RkB must be
identical,
> > > which implies that AsPcSetA and AsPcSetB are also identical.
> > >
> > > > Also assume that a DAVA has been received for RemotePc=X from
SgpA
> > after
> > > a
> > > > DUNA from SgpB for the same RemotePc. We might consider
generating
> > an
> > > > MTP-Resume to all the MTP-Users of the MTP-SAP for RemotePc X.
> > However,
> > > if
> > > > an MTP-User requests an MTP-Transfer with an AsPc of B then SgpB
may
> > not
> > > be
> > > > able to transfer it as indicated by the DUNA it sent the ASP.
> > >
> > > This is not a problem because AsPc A must be identical to AsPc B.
> > Also,
> > > you do not seem to realize that DAVA and DUNA are specific to the
SG.
> > > A DUNA received from one SG does not indicate that the affected
> > > destination
> > > is also unavailable via the other SG.  It takes a DUNA from both
SGs
> > > to indicate that the affected destination is inaccessible.
> > >
> > > >
> > > > The same explanation applies to RkC and RkD.
> > >
> > > For RkC and RkD to be associated with the same MTP-SAP requires
that
> > > they are identical according to the 1:1:1 rule above.
> > >
> > > >
> > > > In practice this requirement probably won't cause too many
headaches
> > > > because it is likely that there would be two different
MTP-Users,
> > one
> > > > using only RkA/RkC and the other using only RkB/RkD.
> > >
> > > In fact there must be two different MTP-SAPs (and necessarily
> > different
> > > MTP-Users from the perspective of the SG) for RkA/RkC to tbe
different
> > > from RkB/RkD.
> > >
> > > > In this case, we can simply create two MTP-SAPs in the same
> > MTP-Network
> > > and
> > > > associate each routing key with a different MTP-SAP. Of course,
this
> > > would
> > > > require the M3UA implementation to support more than one MTP-SAP
per
> > > > MTP-Network, which would be extra work obviously.
> > >
> > > It is not extra work.  M3UA not only supports this but requires
it.
> > > An MTP-SAP is an AS.  Having multiple AS (whether in a single
network
> > > or not) is fundamental to the SIGTRAN model.
> > >
> > > >
> > > > 4. ASP-SGP Routing should use SS7 Destination
> > Availability/Restricted
> > > > Status on a per-SGP rather than a per-SG basis.
> > >
> > > Wrong.  ASPSM/ASPTM is per-SGP.  SSNM is per-SG.
> > >
> > > >
> > > > I believe your ASP-SGP procedures should be amended (I only
amend
> > the
> > > > multiple SG case as the single SG case is a special case of the
> > former)
> > > > as follows:
> > > >
> > > > Change:
> > > > "This routing information is updated by collecting
DUNA/DAVA/DRST
> > > > messages received from (any of the SGP in) the SG."
> > > > To:
> > > > "This routing information is updated by collecting
DUNA/DAVA/DRST
> > > > information on a per-(SGP,destination) basis. An SG is
considered to
> > be
> > > > available and unrestricted for a particular destination if any
SGP
> > in it
> > > > is available and unrestricted for that destination. Otherwise if
> > this is
> > > > not he case, then an SG is considered to be restricted for a
> > particular
> > > > destination if there is at least one SGP in the SG restricted
for
> > that
> > > > destination. Otherwise if this is not the case, the SG is
considered
> > to
> > > > be prohibited for that destination."
> > > >
> > > > The RFC is not particular clear on this point. In section 1.4.1
para
> > 3
> > > > it states that "MTP3 routeset, SPMC and remote AS/ASP states of
each
> > SGP
> > > > SHOULD be coordinated across all the SGPs". However, this uses
> > "SHOULD"
> > > > which implies it is only recommended and it also doesn't
> > specifically
> > > > state that SS7 destination availability, restriction and
congestion
> > > > status ("SS7 destination status" for short) should be
coordinated
> > across
> > > > all SGPs. I don't think that "MTP3 routeset" necessarily implies
SS7
> > > > destination status. Also, in section 1.3.2.5 1.4.2.5 it suggests
in
> > > > should be on a per-SGP basis. Section 4.5.2.2 uses the word "SG"
but
> > > > also uses the term "affected route(s)". Section 1.3.2.5 and
section
> > > > 1.4.2.5 suggest the word "route" refers to an SGP and not an SG.
> > Hence,
> > > > given the ambiguity of section 4.5.2.2 I think that route can be
> > > > considered to refer to an SGP.
> > >
> > > Each SGP in an SG offers identical connectivity to the SS7
network.
> > > This means that a destination which is inaccessible to one SGP is
> > > inaccessible to all, congested, restricted, accessible, etc.
> >
> > RFC section 1.4.1 para 3 makes it clear that the static
configuration of
> > the connectivity of the SGPs must be identical, but it doesn't make
it
> > clear that the SGPs should be designed to ensure identical
connectivity
> > at runtime. In particular I am referring to the statement "Rerouting
of
> > traffic between the MAY also be supported". If rerouting isn't
supported
> > amongst the SGPs of an SG (either in the SGP's M3UA or within an
MTP3
> > stack distributed between the SGPs) then I don't see how the SGPs
can be
> > expected to have identical connectivity in the event of a single
point
> > of failure.
> >
> > Hence, I think that statements mirroring what you have said should
be in
> > the implementor's guide. Otherwise, without reading these emails,
other
> > people may be confused as to whether DAVA/DUNA/DRST destination
status
> > should be kept on a per-SG or a per-SGP basis.
> >
> > >
> > > >
> > > > A configuration where per-SGP SS7 destination status is
necessary is
> > as
> > > > follows. Consider an SEP SG which has two SGP's acting as a
> > redundant
> > > > pair. Each SGP has it's own link set to a particular STP. While
in
> > > > section 1.4.1 para 3 it states that "Rerouting of traffic
between
> > the
> > > > SGPs MAY also be supported", it uses "MAY" and hence this is
> > optional.
> > > > If one link set fails but not the other, one SGP will be able to
> > reach
> > > > the SS7 network but not the other if rerouting between SGPs is
not
> > > > supported or the rerouting link has also failed. Hence, it would
be
> > > > possible for one SGP to send a DUNA for a particular destination
but
> > not
> > > > the other.
> > >
> > > This is addressed.  The SGP has suffered a complete failure (it is
> > unable
> > > to process traffic) and can simply drop its associations to the
ASPs.
> > > DUNA is incorrect here: the destination is still accessible from
the
> > SG.
> > > One SGP has simply broken it's contract (providing identical
> > connectivity
> > > to the SS7 network as other SGP in the SG) and must be placed out
of
> > > service.
> > >
> > > --brian
> > >
> > > >
> > > >
> > > > Your feedback would be appreciated.
> > > >
> > > > Jolan.
> > > >
> > > >
> > > > --
> > > > Jolan Evans
> > > > Open Telecommunications
> > > > jolan.evans@opentelecommunications.com
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org] On
> > Behalf
> > > > Of Brian F. G. Bidulock
> > > > Sent: Tuesday, 8 October 2002 17:47
> > > > To: Srikanth Yandapalli
> > > > Cc: sigtran@ietf.org
> > > > Subject: Re: [Sigtran] ASP to SGP communication
> > > >
> > > > Srikanth,
> > > >
> > > > Srikanth Yandapalli wrote:               (Tue, 08 Oct 2002
12:03:52)
> > > > >
> > > > >    I am late entrant to this group.I am quite sure all this
should
> > > > have
> > > > >    been discussed and I am sorry about this.
> > > >
> > > > Welcome.
> > > >
> > > > >
> > > > >    In the context of a single ASP in communication with
multiple
> > SGPs,
> > > > >    how should the routing of a MTP_DATA_REQ take place at the
ASP?
> > > >
> > > > I assume you are talking about M3UA?  As we are dealing with 5
or
> > more
> > > > UAs
> > > > now, in the future it would be helpful to add M3UA (or
whichever) to
> > the
> > > > subject line.
> > > >
> > > > >
> > > > >    approach 1:
> > > > >
> > > > >    We may find out the  RK and find out the SGP list that the
RK
> > is
> > > > >    active on and choose one SGP for sending the message based
> > > > >    on congestion level and also whether we have received any
DRST
> > > > >    message from any of the SGPs.
> > > >
> > > > This approach is applicable to multiple SGs, but not to multiple
> > SGPs
> > > > within a
> > > > single SG.
> > > >
> > > > >    approach 2:
> > > > >
> > > > >    An SGP can also be viewed as providing route to a set of
DPCs
> > > > >    and the routing can be based on the DPC for the message
alone.
> > > > >    This approach is reduces the complexity but adds a
situation
> > > > >    where the RK may not be active on that association. And
also is
> > > > >    is mandatory to send RC on this association and if so what
> > could
> > > > >    the SGP make out of the RC?
> > > >
> > > > RC should be coordinated and the same across multiple SGPs
within an
> > SG.
> > > >
> > > > >
> > > > >    Is there a preferred approach to this issue?
> > > > >
> > > >
> > > > Typically, the logic can be something like this: (but there are
> > several
> > > > other
> > > > schools of thought):
> > > >
> > > > Single SG case: (multiple SGs is more complicated)
> > > >
> > > >   MTP-TRANSFER request is issued by an MTP-User.  The MTP-User
is
> > bound
> > > > to an
> > > >   MTP-SAP.  The MTP-SAP is associated with an AS/RC/RK.  There
is a
> > pool
> > > > of
> > > >   SGPs on an SG for which the AS/RC/RK is active.  The AS may
have
> > > > received
> > > >   MTP-PAUSE/RESUME/STATUS indications from the SG and may choose
to
> > > > honor that
> > > >   information or not.  If the ASP chooses not to honor this
> > information
> > > > it can
> > > >   blindly send messages to the SGP and rely upon a DUNA/SCON
> > response
> > > > from the
> > > >   SGP later.
> > > >
> > > >   Selection of an SGP within an SG is based on the traffic mode
for
> > the
> > > > SGP.
> > > >   This traffic mode is not managed by M3UA, however, M3UA
provides
> > for
> > > >   distribution of traffic over SGP based on any of the methods
> > described
> > > > for
> > > >   ASPs (active/standby, load-share, broadcast).  A typical
method is
> > > >   load-share based on SLS.  In this scheme, using the SLS in the
> > > > MTP-TRANSFER
> > > >   request, the ASP selects load-shares traffic over the
available
> > SGP.
> > > >
> > > > Multiple SG case:
> > > >
> > > >   In the more complicated multiple SG case, the ASP must first
> > select an
> > > > SG
> > > >   before it selects an SGP within the SG.  The ASP must maintain
> > some
> > > >   additional routing information to be able to properly select
an
> > SG.
> > > > This
> > > >   routing information is updated by collecting DUNA/DAVA/DRST
> > messages
> > > >   received from (any of the SGP in) the SG.  To select the
outgoing
> > SG,
> > > > the
> > > >   ASP must examine the destination of the MTP-TRANSFER request.
> > > >
> > > >   (If the SG has no SGP active for the AS/RC/RK, all
destinations
> > can be
> > > >   considered prohibited).
> > > >
> > > >   If the destination is available and unrestricted for several
SGs,
> > the
> > > > ASP
> > > >   should select an SG on a load-sharing basis (based on SLS) and
> > then
> > > > select
> > > >   an active SGP within the SG on the basis of the traffic mode
for
> > the
> > > > SG.
> > > >
> > > >   If some SG are restricted for the specified destination (based
on
> > > > received
> > > >   DRST messages from the SG), the ASP should load-share across
the
> > > > available
> > > >   unrestricted SGs.  If all SGs are restricted for a given
> > destination,
> > > > the
> > > >   ASP should load-share across the available SGs and ignore the
> > > > restricted
> > > >   status.
> > > >
> > > >   If some SG are prohibited for the specified destination (based
on
> > > > received
> > > >   DUNA messages from the SG), the ASP should load-share across
the
> > > > available
> > > >   non-prohibited SGs.  If all SGs are prohibited for a given
> > destination
> > > > (or
> > > >   no SGP is active for the AS/RC/RK in any SG), the ASP should
> > respond
> > > > to the
> > > >   MTP-User with an MTP-PAUSE in accordance with the style of the
> > > > MTP-User
> > > >   interface (ITU-T and ANSI differ here).
> > > >
> > > > Properly selecting SGs requires that the ASP maintain the
> > DUNA/DAVA/DRST
> > > > information for each destination received from any SGP in an SG,
on
> > a
> > > > per-SG
> > > > basis.  This is the same as MTP Level 3 ROUTE status.  However,
SCON
> > > > information should only be maintained on a per-destination basis
> > (and
> > > > not
> > > > per-SG).  This is the same as MTP Level 3 ROUTESET status.
> > > >
> > > > Note that, in general, it is a bad idea to consider congestion
> > (SCON)
> > > > when
> > > > selecting an SG.  SCON does not necessarily indicate congestion
at
> > an SG
> > > > or on
> > > > a path to an SG, but indicates congestion at the affected
> > destination or
> > > > somewhere (perhaps distant) in the SS7 network.  SCON is
> > > > ROUTESET-specific
> > > > (applies to the destination), whereas DUNA/DAVA/DRST is
> > ROUTE-specific
> > > > (applies to the destination and path).  SCON should only be used
to
> > > > determine
> > > > whether a message should be dropped completely and an MTP-STATUS
> > > > returned to
> > > > the MTP-User according to the style of the MTP-User interface
(ITU-T
> > and
> > > > ANSI
> > > > differ here again).
> > > >
> > > > So, to summarize:  on behalf of the AS/RC/RK/MTP-User, the ASP
> > > > determines
> > > > whether to send a message based on SCON received for the
specified
> > > > destination, then selects an SG based on DUNA/DAVA/DRST received
for
> > the
> > > > specified destination and load-shares based on SLS across the
> > eligible
> > > > SGs.
> > > > Once an SG is selected, an active SGP (active for the AS/RC/RK)
is
> > > > selected
> > > > within the SG based on the traffic mode of the SG
(active/standby,
> > > > load-share,
> > > > broadcast: but typically load-share on SLS).
> > > >
> > > > As I said, there are other schools of thought, but that is my
> > > > understanding.
> > > >
> > > > --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/
> 
> --
> 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 Jan 30 03:11:50 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 DAA21989
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 03:11:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0U8Xei12740
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 03:33:40 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U8WsJ12698;
	Thu, 30 Jan 2003 03:32:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U8VAJ12648
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 03:31:10 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21958
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 03:08:49 -0500 (EST)
Subject: Re: [Sigtran] M3UA SG-SG (again)
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OFEA4573BE.D1673292-ONC2256CBE.002C2E8E@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Thu, 30 Jan 2003 10:08:56 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/30/2003
 10:08:59 AM
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 h0U8VAJ12649
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


Ken,

[KAM] so ASPAC is not Double-ended?  Is ASP ACTIVE ACK used?
                    SGP1      SGP2          SGP3      SGP4
                        |        |              |        |
                        |-------DUNA(PC1)------>|        |
                        |        |              |        |

                        |-------DRST(PC2)------>|        |
                        |        |              |        |
                        |-------ASPAC---------->|        |
                        |        |              |        |
                        |<------DATA(PC3)-------+--------|
[KAM] how can data be sent.  SGP4 has not sent an ASP ACTIVE.
                        |        |              |        |
                        |        |<---DUNA(PC4)-|        |
                        |        |              |        |
                        |        |<---ASPAC-----|        |
                        |        |              |        |
                        |--------+-DATA(PC5)----+------->|
                        |        |              |        |
                        |        |              |        |
                        |        |              |        |

[TOLGA] ASPAC is used instead of TRA of MTP3(just not to introduce a new
message ASPAC is reused). But yes, there is a problem with sending DATA
just after receiving ASPAC from the peer. This conflicts with the following
sentence from 9.3.2. from Q.704:
"When a traffic restart allowed message has been received by X from
signalling point Y, and a TRA message has been sent by X to Y, X stops
timer 21."
So, both sides should receive ASPAC before any of them can send DATA. And
to assure that the peer has received ASPAC, ASPAC should be replied with
ASPAC-ACK(otherwise DATA from different stream,whºch is sent after ASPAC
might arrive earlier). I will update the draft accordingly.

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



From mailnull@www1.ietf.org  Thu Jan 30 05:16: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 FAA23639
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 05:16:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0UAcKL20885
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 05:38:20 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UAc5J20872;
	Thu, 30 Jan 2003 05:38:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UAbJJ20249
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 05:37:19 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23625
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 05:14:54 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:COjmWpeI9T34arV7N501xt6o0Yrc3Hsz@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0UAIRD29932;
	Thu, 30 Jan 2003 03:18:28 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0UAIR818915;
	Thu, 30 Jan 2003 03:18:27 -0700
Date: Thu, 30 Jan 2003 03:18:27 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
Message-ID: <20030130031827.B10733@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
References: <OFEC77243A.47A4213E-ONC2256CBC.002FD630@LocalDomain> <3E38AC51.B358D2E7@axes-mach01.usa.alcatel.com> <20030129223645.C1341@openss7.org> <3E38CD3F.94A343E5@axes-mach01.usa.alcatel.com> <20030130000108.A28966@openss7.org> <3E38D245.A5C93237@axes-mach01.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: <3E38D245.A5C93237@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Thu, Jan 30, 2003 at 12:50:37PM +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>

Srini,

If they don't have different connectivity to the SS7 network, they can hardly
be viewed as separate and different SGs.

--brian

ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:50:37)
> Brian,
> 
>     So, the M3UA at the SGP should be informed the SG which received this message.
> 
> --Srini
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Srini,
> >
> > The association would be chosen on the basis of for which SG the
> > message from the SS7 network arrived.
> >
> > --brian
> >
> > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:29:11)
> > > Brian,
> > >
> > >       Can you please tell me, how a message received from the SS7 network is routed using such a SGP(having two
> > > different associations) to the AS?.
> > >
> > > --Srini.
> > >
> > > "Brian F. G. Bidulock" wrote:
> > >
> > > > Srini,
> > > >
> > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 10:08:41)
> > > > > Tolga,
> > > > >
> > > > > An ASP can be a part of different ASs. Similarly, Can a SGP be a part of
> > > > > different SGs?
> > > >
> > > > Sure.  But from the viewpoint of an ASP, the SGP belongs to one SG.  If an
> > > > SGP were to perform the function for two SGs for the same AS, the ASP would
> > > > have to form two associations with the SGP: one for SG-A, the other for SG-B.
> > > > The SGP would also need some way of knowing (e.g. static port allocation)
> > > > for which SG the ASP was forming an association.
> > > >
> > > > --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

-- 
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 Jan 30 05:16: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 FAA23652
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 05:16:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0UAcbc20931
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 05:38:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UAbAJ20181;
	Thu, 30 Jan 2003 05:37:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UAZ3J20089
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 05:35:03 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23551
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 05:12:34 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:wWQBdyk3DM02rjmtAcAUsIn/Eg5QkT3n@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0UAG7D29909;
	Thu, 30 Jan 2003 03:16:07 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0UAG7B18662;
	Thu, 30 Jan 2003 03:16:07 -0700
Date: Thu, 30 Jan 2003 03:16:07 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Jolan Evans <jolan.evans@opentelecommunications.com>
Cc: Sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
Message-ID: <20030130031607.A10733@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Jolan Evans <jolan.evans@opentelecommunications.com>,
	Sigtran <sigtran@ietf.org>
References: <20030129222748.A1341@openss7.org> <005c01c2c834$bce760d0$900c460a@Mars>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <005c01c2c834$bce760d0$900c460a@Mars>; from jolan.evans@opentelecommunications.com on Thu, Jan 30, 2003 at 06:53:54PM +1100
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>

Jolan,

Jolan Evans wrote:                                                                   (Thu, 30 Jan 2003 18:53:54)
> More comments below...
> 
> 
> --
> Jolan Evans
> 
> 
> Open Telecommunications
> jolan.evans@opentelecommunications.com
> 
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Thursday, 30 January 2003 16:28
> > To: Jolan Evans
> > Cc: 'Sigtran'
> > Subject: Re: [Sigtran] M3UA: ASP to SGP communication
> > 
> > Jolan,
> > 
> > More comments below....
> > 
> > Jolan Evans wrote:
> > (Thu, 30 Jan 2003 14:27:28)
> > > See my comments below...
> > >
> > >
> > > --
> > > Jolan Evans
> > > Open Telecommunications
> > > jolan.evans@opentelecommunications.com
> > >
> > >
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: Tuesday, 28 January 2003 19:53
> > > > To: Jolan Evans
> > > > Cc: Sigtran
> > > > Subject: Re: [Sigtran] M3UA: ASP to SGP communication
> > > >
> > > > Jolan,
> > > >
> > > > You are a litte of track: please see comments below...
> > > >
> > > > Jolan Evans wrote:
> > > > (Tue, 28 Jan 2003 19:01:56)
> > > > > I would like to raise a few issues regarding your procedures
> below
> > > for
> > > > > ASP to SGP routing. I know this discussion took places a while
> ago,
> > > but
> > > > > it has taken me some time to come up to speed with the RFC as I
> have
> > > > > been busy on other things until recently.
> > > > >
> > > > > Please note that I have inserted "M3UA" into the subject line of
> the
> > > > > original email.
> > > > >
> > > > >
> > > > >
> > > > > 1. Nomenclature
> > > > > AsPc: Point code of an AS. In defining routing keys, the RFC
> uses
> > > DPC
> > > > > for this term as it takes the SG's frame of reference.
> > > > > RemotePc: Point code of an SS7 MTP entity with which an AS
> > > communicates
> > > > > via an SG, or directly in the case of IPSP-IPSP communication.
> In
> > > > > defining routing keys, the RFC uses OPC for this term as it
> takes
> > > the
> > > > > SG's frame of reference again.
> > > > >
> > > > >
> > > > >
> > > > > 2. Background Assumptions
> > > > > As per Brian's introduction, we assume that zero or more
> MTP-User's
> > > are
> > > > > bound to an MTP-SAP. The MTP-SAP exists in a particular
> MTP-Network,
> > > > > which has a particular MTP protocol variant. An SG is associated
> > > with a
> > > > > single MTP-Network. A RK is defined as in the RFC, but, for
> clarity,
> > > is
> > > > > independent of any SG and associated with a single MTP-Network.
> An
> > > > > SgRouteSet is uniquely defined by an RK, an SG and an MTP-SAP
> (the
> > > RK
> > > > > and SG must be both associated with the same MTP-Network) and
> also
> > > > > specifies the network appearance for the MTP-Network to be used
> with
> > > the
> > > > > SG and the RC of each SGP in the SG. Therefore, an SgRouteSet is
> > > > > implicitly associated with a single MTP-Network. An MTP-SAP is
> > > > > associated with zero or more SgRouteSet's and therefore an
> MTP-SAP
> > > is
> > > > > associated with zero or more RKs.
> > > >
> > > > Bad assumption.  An MTP-SAP is assocated with one RK.  This is the
> > > > 1:1:1 rule between AS:RK:RC.
> > >
> > > Ok, I neglected to state the circumstances and in particular the
> network
> > > topologies which drove me to make these assumptions, and in
> particular,
> > > the 1:many association between MTP-SAP:RK. Nonetheless, I can't find
> > > statements in the RFC to support your statement that an "MTP-SAP is
> > > assocated with one RK" and hence I would have to call this an
> assumption
> > > also. However, I stand corrected if this is not the case.
> > 
> > Secion 1.2 Terminology: Application Server:
> > 
> >   "... Note that there is a 1:1 relationship between an AS and a
> >   Routing Key".
> 
> You seem to be misreading what I have written. I've never said anything
> to contradict that there is a 1:1 relationship between an AS and a RK.
> My assumption is that there is a 1:many relationship between  RK's (or
> AS's) and MTP-SAPs. I quote myself: "an MTP-SAP is associated with zero
> or more RKs".
> 
> Your assumption is that there is a 1:1 relationship between RK's (or
> AS's) and MTP-SAP's. I quote you: "An MTP-SAP is assocated with one RK".

Normally.  You need multiple network appearances for it to be otherwise.
(An AS and an RK cannot span network appearances.)

Nevetheless, there is no problem with the RFC model, as the RFC uses
the concept of an Application Server which is limited to a single SPMC
and a single network appearance.

Define your MTP-SAPs how you like, it does not invalidate the RFC model.

> 
> 
> Both of these statements are assumptions as far as the RFC is concerned
> because the RFC makes no mention of an MTP-SAP entity (it only defines
> an MTP-User).

The RFC deos not define an MTP-User: the SS7 specifications define an
MTP-User.

> 
> > 
> > >
> > > Without further ado, here is one of the network topologies in which
> our
> > > ASP M3UA must operate. NB This is defined by our customers so we
> can't
> > > change it.
> > >
> > > We must communicate with a number of SGs, for simplicity let's just
> say
> > > 2 as that's all that I need to illustrate my point. Likewise, it's
> not
> > > important how many SGP's they each have, so for simplicity let's
> assume
> > > that each SG has just one. Here is the network to which the ASP is
> > > connected:
> > >
> > > MtpNetworkA: Protocol=ITU 92
> > >
> > > MtpSapA: Network=MtpNetworkA
> > 
> > An MTP-SAP cannot be defined as an entire network (even just for SS7),
> > and there is no reason to do so.
> 
> Again, as the RFC doesn't define an MTP-SAP, I'm free to define it.

Go right ahead.  But don't say that there is a problem with SSNM messages
which are referenced to the AS.  If you want your MTP-SAPs to span
network appearances, you will need to have mutliple AS per MTP-SAP.

> 
> > 
> > >
> > > SgA: Network=MtpNetworkA
> > > SgB: Network=MtpNetworkA
> > >
> > > SgpA: Sg=SgA, etc
> > > SgpB: Sg=SgB, etc
> > >
> > > RkA: Network=MtpNetworkA, AsPcSet={PcA, PcB}, RemotePcSet={PcW, PcX}
> > > RkA: Network=MtpNetworkA, AsPcSet={PcC, PcD}, RemotePcSet={PcY, PcZ}
> > 
> > I think you mean RkB on this last entry?
> 
> Yes, a typo.
> 
> > 
> > Also, the only way you can have multiple point codes in the AsPcSet
> > is if the point codes are "aliases" for the same signalling point.
> > In which case, the accessibility, for example, from PcA to PcW is
> > identical to the accesssibility from PcB to PcW.
> 
> Fair enough.
> 
> > 
> > >
> > > SgRouteSetA: Sap=MtpSapA, RoutingKey=RkA, Sg=SgA,
> NetworkAppearance=0,
> > > SgpSet={(SgpA, Rc=0)}
> > > SgRouteSetB: Sap=MtpSapA, RoutingKey=RkB, Sg=SgB,
> NetworkAppearance=0,
> > > SgpSet={(SgpB, Rc=0)}
> > 
> > Again you try to have one AS serving multiple Routing Keys.  This
> violates
> > the 1:1 rule.  Because you have two RKs, you have two AS (and at least
> > two MTP-SAPs).
> 
> No, you appear to have misread what I have written. The one MTP-SAP (not
> the same as an AS) has two RKs (or AS's).

So what?  M3UA messages are only sent referenced on AS, not on MTP-SAP.

> 
> > 
> > >
> > > In this model, when the ASP-ACTIVE ACK is received for RkA (RkB),
> the
> > > ASP will audit the state of the RemotePcSet of RkA (RkB) at SgpA
> (SgpB).
> > > Ie the RemotePcSet of a routing key determine which remote PCs
> should
> > > have their status audited at a particular SG (I'll ignore the issue
> of
> > > whether it is SG or SGP for now).
> > >
> > > I'm not clear how this would be translated to your model. As I see
> it,
> > > there is a problem because an MTP-SAP is only allowed to have one RK
> but
> > > the MTP-User of the SAP wants to talk with 2 different SGs, each
> with
> > > their own routing keys.
> > 
> > It is not my model.
> > 
> > Because you have two AS, there is not problem.  AS-A audits remote
> > desinations on RkA, AS-B audits remote destinations on RkB.
> > 
> 
> Again, you appear to have misread what I have written. The one MTP-SAP
> (not the same as an AS) has two RKs (or AS's).

So what?  Define your MTP-SAPs how you like.  But, M3UA messages are
sent to the AS, not the MTP-SAP.

> 
> > >
> > > I can see 2 obvious ways to translate this configuration into your
> > > model: Either define just one RK or define two MTP-SAPs.
> > 
> > It is not my model.
> > 
> > But, you are required to define two AS because of the 1:1 rule.  How
> > many MTP-SAPs you have at the ASP is implementation dependent.
> 
> Now we seem to be in agreement! To keep our MTP-Users simple, our
> implementation will allow the one MTP-SAP to be associated with both
> AS's, and as you state, the number of MTP-SAPs is implementation
> dependent.

But it is only necessary to do so if you have more than one network
apperance for an MTP-SAP.  For most cases, the MTP-SAP and the AS
are the same entity.

> 
> > 
> > >
> > > However, if there is one RK then we can no longer rely upon the
> > > RemotePcSet of the RK to determine the set of remote PCs of which
> the
> > > status should be audited when an ASP goes active with an SGP. This
> seems
> > > awkward and would seemingly require the RemotePcSet to be an
> attribute
> > > of the SgRouteSet.
> > >
> > > If there are two MTP-SAPs then we are burdening the MTP-USER which
> must
> > > now aggregate traffic and destination status from two different
> > > MTP-SAPs. As far as I'm aware, in plain old MTP3 an MTP-USER can
> happily
> > > talk via just one MTP-SAP to two different STPs which have routesets
> to
> > > a different set of remote PCs.
> > 
> > For this situation, you do not need to burden the MTP-User.  It is the
> > M3UA layer at the ASP which is burdened.  In the multiple SG scenario,
> > the M3UA layer at the ASP is responsible for understanding which AS
> > correspond to which MTP-SAPs, and handling routing, and determining
> when
> > to send an MTP-User an MTP-PAUSE or RESUME based on DUNA and DAVA
> received
> > from each of the various SG.
> 
> Sorry, but I don't understand how the MTP-User is not burdened. If there
> are two MTP-SAPs upon which the MTP-User can receive MTP-Resume,
> presumably the MTP-User will have to keep track of which one is
> accessible for a particular remote PC and then send traffic on an
> MTP-SAP in which the destination is accessible.

MTP-Users as defined in the SS7 specifications do not have multiple
MTP-SAPs based on remote point codes.  The MTP-SAP is based on local
point code only.  The MTP-User as defined in the SS7 specifications can
only have one MTP-SAP in this circumstance.  Therefore, M3UA at the ASP
must interwork multiple AS into one MTP-SAP.  The MTP-User is not
burdended.

> 
> > 
> > So, in effect, although you require two AS, how many MTP-SAPs you have
> > at the ASP is implementation dependent.
> > 
> > In the non-multiple SG scenario (or where access is via a pair of SG
> > acting a an STP pair), the AS nicely maps 1:1 to an MTP-SAP.
> 
> Agreed.

So what is your problem?  The RFC model works fine.

> 
> > 
> > >
> > > Most of your remaining comments on my original items 2 and 3 are on
> the
> > > basis that one cannot assume a 1-many MTP-SAP:RK relationship. I
> won't
> > > reply to such comments as the real issue is the assumption itself.
> > 
> > You cannot have a 1:many AS:RK relationship.  How many AS you map into
> > an MTP-SAP is the implementation's business.
> > 
> > But your statement that the remainder of my comments are based on this
> > is untrue.  SSNM on a per-SGP basis is false and was ruled out in the
> > design of the protocol.  This has nothing to do with multiple RKs for
> > an MTP-SAP.
> 
> You appear to have missed the "items 2 and 3" qualification. SSNM on a
> per-SGP basis was in item 4.

Sorry, see below...

> 
> > 
> > --brian
> > 
> > >
> > > >
> > > > > In contrast, it appears that Brian
> > > > > assumes that an MTP-SAP can only be associated with one RK.
> Given
> > > this
> > > > > extension, we have the following requirement.
> > > > >
> > > > >
> > > > >
> > > > > 3. Routing Keys Requirements to Support Unique SS7 Destination
> > > Status
> > > > > Let RemotePcSet(Rk) be the set of RemotePc's reachable via the
> SG
> > > from
> > > > > the ASP where the RK is defined.
> > > >
> > > > RKs do not have to be defined at ASPs, just MTP-SAPs.
> > > >
> > > > > Consider any two SgRouteSet's SgRsA and SgRsA which are
> associated
> > > with
> > > > > the same MTP-SAP.
> > > >
> > > > I think you mean SgRsA and SgRsB <---.
> > > >
> > > > > Let the routing key of SgRsA and SgRsB be RkA and RkB
> respectively.
> > > > > If the intersection of RemotePcSet(RkA) and RemotePcSet(RkB) is
> > > non-nil
> > > > > then the routing keys MUST be identical in every respect apart
> from
> > > > > their RemotePcSet.
> > > >
> > > > RkA and RkB must be identical or they cannot be associated with
> the
> > > > same MTP-SAP.  See 1:1:1 rule above.
> > > >
> > > > > If this wasn't the case, an ASP could never indicate an
> MTP-RESUME
> > > to an
> > > > > MTP-USER because an MTP-RESUME can only specify a RemotePc and
> no
> > > other
> > > > > SS7 element. I assume here for simplicity that every MTP-User of
> a
> > > > > MTP-SAP must be given the same MTP status (i.e. different
> MTP-Users
> > > of
> > > > > the same MTP-SAP cannot be given different MTP-Status
> indications
> > > > > depending on what traffic they have requested).
> > > >
> > > > The AS can deliver whatever MTP-STATUS indications it cares to.
> If
> > > > there are SI values represented by the MTP-SAP, it is normally the
> > > > MTP-User's responsibility to sort out the MTP-STATUS indications.
> > >
> > > I don't know what you mean by "whatever MTP-STATUS indications it
> cares
> > > to" but ITU Q.701 Table 1 shows that MTP-PAUSE and MTP-RESUME only
> > > contain the affected DPC. A lot of MTP-user software has been
> written on
> > > this assumption so we can't afford to change this.

I did not say anything different.

> > >
> > > >
> > > > >
> > > > > Here's a concrete example of why this is so. Consider an ASP
> with
> > > the
> > > > > following routing keys:
> > > > > RkA: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={A}
> > > > > RkB: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={B}
> > > > > RkC: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={M}
> > > > > RkD: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={N}
> > > > >
> > > > > Assume that RkA and RkB were both active in SgpA and SgpB
> > > respectively
> > > > > and are associated with the same MTP-SAP, but different SGs.
> > > >
> > > > To be associated with the same MTP-SAP, RkA and RkB must be
> identical,
> > > > which implies that AsPcSetA and AsPcSetB are also identical.
> > > >
> > > > > Also assume that a DAVA has been received for RemotePc=X from
> SgpA
> > > after
> > > > a
> > > > > DUNA from SgpB for the same RemotePc. We might consider
> generating
> > > an
> > > > > MTP-Resume to all the MTP-Users of the MTP-SAP for RemotePc X.
> > > However,
> > > > if
> > > > > an MTP-User requests an MTP-Transfer with an AsPc of B then SgpB
> may
> > > not
> > > > be
> > > > > able to transfer it as indicated by the DUNA it sent the ASP.
> > > >
> > > > This is not a problem because AsPc A must be identical to AsPc B.
> > > Also,
> > > > you do not seem to realize that DAVA and DUNA are specific to the
> SG.
> > > > A DUNA received from one SG does not indicate that the affected
> > > > destination
> > > > is also unavailable via the other SG.  It takes a DUNA from both
> SGs
> > > > to indicate that the affected destination is inaccessible.
> > > >
> > > > >
> > > > > The same explanation applies to RkC and RkD.
> > > >
> > > > For RkC and RkD to be associated with the same MTP-SAP requires
> that
> > > > they are identical according to the 1:1:1 rule above.
> > > >
> > > > >
> > > > > In practice this requirement probably won't cause too many
> headaches
> > > > > because it is likely that there would be two different
> MTP-Users,
> > > one
> > > > > using only RkA/RkC and the other using only RkB/RkD.
> > > >
> > > > In fact there must be two different MTP-SAPs (and necessarily
> > > different
> > > > MTP-Users from the perspective of the SG) for RkA/RkC to tbe
> different
> > > > from RkB/RkD.
> > > >
> > > > > In this case, we can simply create two MTP-SAPs in the same
> > > MTP-Network
> > > > and
> > > > > associate each routing key with a different MTP-SAP. Of course,
> this
> > > > would
> > > > > require the M3UA implementation to support more than one MTP-SAP
> per
> > > > > MTP-Network, which would be extra work obviously.
> > > >
> > > > It is not extra work.  M3UA not only supports this but requires
> it.
> > > > An MTP-SAP is an AS.  Having multiple AS (whether in a single
> network
> > > > or not) is fundamental to the SIGTRAN model.
> > > >
> > > > >
> > > > > 4. ASP-SGP Routing should use SS7 Destination
> > > Availability/Restricted
> > > > > Status on a per-SGP rather than a per-SG basis.
> > > >
> > > > Wrong.  ASPSM/ASPTM is per-SGP.  SSNM is per-SG.
> > > >
> > > > >
> > > > > I believe your ASP-SGP procedures should be amended (I only
> amend
> > > the
> > > > > multiple SG case as the single SG case is a special case of the
> > > former)
> > > > > as follows:
> > > > >
> > > > > Change:
> > > > > "This routing information is updated by collecting
> DUNA/DAVA/DRST
> > > > > messages received from (any of the SGP in) the SG."
> > > > > To:
> > > > > "This routing information is updated by collecting
> DUNA/DAVA/DRST
> > > > > information on a per-(SGP,destination) basis. An SG is
> considered to
> > > be
> > > > > available and unrestricted for a particular destination if any
> SGP
> > > in it
> > > > > is available and unrestricted for that destination. Otherwise if
> > > this is
> > > > > not he case, then an SG is considered to be restricted for a
> > > particular
> > > > > destination if there is at least one SGP in the SG restricted
> for
> > > that
> > > > > destination. Otherwise if this is not the case, the SG is
> considered
> > > to
> > > > > be prohibited for that destination."
> > > > >
> > > > > The RFC is not particular clear on this point. In section 1.4.1
> para
> > > 3
> > > > > it states that "MTP3 routeset, SPMC and remote AS/ASP states of
> each
> > > SGP
> > > > > SHOULD be coordinated across all the SGPs". However, this uses
> > > "SHOULD"
> > > > > which implies it is only recommended and it also doesn't
> > > specifically
> > > > > state that SS7 destination availability, restriction and
> congestion
> > > > > status ("SS7 destination status" for short) should be
> coordinated
> > > across
> > > > > all SGPs. I don't think that "MTP3 routeset" necessarily implies
> SS7
> > > > > destination status. Also, in section 1.3.2.5 1.4.2.5 it suggests
> in
> > > > > should be on a per-SGP basis. Section 4.5.2.2 uses the word "SG"
> but
> > > > > also uses the term "affected route(s)". Section 1.3.2.5 and
> section
> > > > > 1.4.2.5 suggest the word "route" refers to an SGP and not an SG.
> > > Hence,
> > > > > given the ambiguity of section 4.5.2.2 I think that route can be
> > > > > considered to refer to an SGP.
> > > >
> > > > Each SGP in an SG offers identical connectivity to the SS7
> network.
> > > > This means that a destination which is inaccessible to one SGP is
> > > > inaccessible to all, congested, restricted, accessible, etc.
> > >
> > > RFC section 1.4.1 para 3 makes it clear that the static
> configuration of
> > > the connectivity of the SGPs must be identical, but it doesn't make
> it
> > > clear that the SGPs should be designed to ensure identical
> connectivity
> > > at runtime. In particular I am referring to the statement "Rerouting
> of
> > > traffic between the MAY also be supported". If rerouting isn't
> supported
> > > amongst the SGPs of an SG (either in the SGP's M3UA or within an
> MTP3
> > > stack distributed between the SGPs) then I don't see how the SGPs
> can be
> > > expected to have identical connectivity in the event of a single
> point
> > > of failure.

It is the SGP's responsibility to remove itself from service if it
suffers a partial failure.  It can drop the SS7 association (which is
stated in the RFC), or it can send unsolicited ASPIA Ack, which according
to the ASP Inactive procedures will require to the ASP to consider itself in
the ASP Inactive state for the AS and allow it to attempt to reactivate
(which can be denied).

> > >
> > > Hence, I think that statements mirroring what you have said should
> be in
> > > the implementor's guide. Otherwise, without reading these emails,
> other
> > > people may be confused as to whether DAVA/DUNA/DRST destination
> status
> > > should be kept on a per-SG or a per-SGP basis.

IMO, it is clear from sections 4.5.1 and 4.5.2 of the RFC.

--brian

> > >
> > > >
> > > > >
> > > > > A configuration where per-SGP SS7 destination status is
> necessary is
> > > as
> > > > > follows. Consider an SEP SG which has two SGP's acting as a
> > > redundant
> > > > > pair. Each SGP has it's own link set to a particular STP. While
> in
> > > > > section 1.4.1 para 3 it states that "Rerouting of traffic
> between
> > > the
> > > > > SGPs MAY also be supported", it uses "MAY" and hence this is
> > > optional.
> > > > > If one link set fails but not the other, one SGP will be able to
> > > reach
> > > > > the SS7 network but not the other if rerouting between SGPs is
> not
> > > > > supported or the rerouting link has also failed. Hence, it would
> be
> > > > > possible for one SGP to send a DUNA for a particular destination
> but
> > > not
> > > > > the other.
> > > >
> > > > This is addressed.  The SGP has suffered a complete failure (it is
> > > unable
> > > > to process traffic) and can simply drop its associations to the
> ASPs.
> > > > DUNA is incorrect here: the destination is still accessible from
> the
> > > SG.
> > > > One SGP has simply broken it's contract (providing identical
> > > connectivity
> > > > to the SS7 network as other SGP in the SG) and must be placed out
> of
> > > > service.
> > > >
> > > > --brian
> > > >
> > > > >
> > > > >
> > > > > Your feedback would be appreciated.
> > > > >
> > > > > Jolan.
> > > > >
> > > > >
> > > > > --
> > > > > Jolan Evans
> > > > > Open Telecommunications
> > > > > jolan.evans@opentelecommunications.com
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org] On
> > > Behalf
> > > > > Of Brian F. G. Bidulock
> > > > > Sent: Tuesday, 8 October 2002 17:47
> > > > > To: Srikanth Yandapalli
> > > > > Cc: sigtran@ietf.org
> > > > > Subject: Re: [Sigtran] ASP to SGP communication
> > > > >
> > > > > Srikanth,
> > > > >
> > > > > Srikanth Yandapalli wrote:               (Tue, 08 Oct 2002
> 12:03:52)
> > > > > >
> > > > > >    I am late entrant to this group.I am quite sure all this
> should
> > > > > have
> > > > > >    been discussed and I am sorry about this.
> > > > >
> > > > > Welcome.
> > > > >
> > > > > >
> > > > > >    In the context of a single ASP in communication with
> multiple
> > > SGPs,
> > > > > >    how should the routing of a MTP_DATA_REQ take place at the
> ASP?
> > > > >
> > > > > I assume you are talking about M3UA?  As we are dealing with 5
> or
> > > more
> > > > > UAs
> > > > > now, in the future it would be helpful to add M3UA (or
> whichever) to
> > > the
> > > > > subject line.
> > > > >
> > > > > >
> > > > > >    approach 1:
> > > > > >
> > > > > >    We may find out the  RK and find out the SGP list that the
> RK
> > > is
> > > > > >    active on and choose one SGP for sending the message based
> > > > > >    on congestion level and also whether we have received any
> DRST
> > > > > >    message from any of the SGPs.
> > > > >
> > > > > This approach is applicable to multiple SGs, but not to multiple
> > > SGPs
> > > > > within a
> > > > > single SG.
> > > > >
> > > > > >    approach 2:
> > > > > >
> > > > > >    An SGP can also be viewed as providing route to a set of
> DPCs
> > > > > >    and the routing can be based on the DPC for the message
> alone.
> > > > > >    This approach is reduces the complexity but adds a
> situation
> > > > > >    where the RK may not be active on that association. And
> also is
> > > > > >    is mandatory to send RC on this association and if so what
> > > could
> > > > > >    the SGP make out of the RC?
> > > > >
> > > > > RC should be coordinated and the same across multiple SGPs
> within an
> > > SG.
> > > > >
> > > > > >
> > > > > >    Is there a preferred approach to this issue?
> > > > > >
> > > > >
> > > > > Typically, the logic can be something like this: (but there are
> > > several
> > > > > other
> > > > > schools of thought):
> > > > >
> > > > > Single SG case: (multiple SGs is more complicated)
> > > > >
> > > > >   MTP-TRANSFER request is issued by an MTP-User.  The MTP-User
> is
> > > bound
> > > > > to an
> > > > >   MTP-SAP.  The MTP-SAP is associated with an AS/RC/RK.  There
> is a
> > > pool
> > > > > of
> > > > >   SGPs on an SG for which the AS/RC/RK is active.  The AS may
> have
> > > > > received
> > > > >   MTP-PAUSE/RESUME/STATUS indications from the SG and may choose
> to
> > > > > honor that
> > > > >   information or not.  If the ASP chooses not to honor this
> > > information
> > > > > it can
> > > > >   blindly send messages to the SGP and rely upon a DUNA/SCON
> > > response
> > > > > from the
> > > > >   SGP later.
> > > > >
> > > > >   Selection of an SGP within an SG is based on the traffic mode
> for
> > > the
> > > > > SGP.
> > > > >   This traffic mode is not managed by M3UA, however, M3UA
> provides
> > > for
> > > > >   distribution of traffic over SGP based on any of the methods
> > > described
> > > > > for
> > > > >   ASPs (active/standby, load-share, broadcast).  A typical
> method is
> > > > >   load-share based on SLS.  In this scheme, using the SLS in the
> > > > > MTP-TRANSFER
> > > > >   request, the ASP selects load-shares traffic over the
> available
> > > SGP.
> > > > >
> > > > > Multiple SG case:
> > > > >
> > > > >   In the more complicated multiple SG case, the ASP must first
> > > select an
> > > > > SG
> > > > >   before it selects an SGP within the SG.  The ASP must maintain
> > > some
> > > > >   additional routing information to be able to properly select
> an
> > > SG.
> > > > > This
> > > > >   routing information is updated by collecting DUNA/DAVA/DRST
> > > messages
> > > > >   received from (any of the SGP in) the SG.  To select the
> outgoing
> > > SG,
> > > > > the
> > > > >   ASP must examine the destination of the MTP-TRANSFER request.
> > > > >
> > > > >   (If the SG has no SGP active for the AS/RC/RK, all
> destinations
> > > can be
> > > > >   considered prohibited).
> > > > >
> > > > >   If the destination is available and unrestricted for several
> SGs,
> > > the
> > > > > ASP
> > > > >   should select an SG on a load-sharing basis (based on SLS) and
> > > then
> > > > > select
> > > > >   an active SGP within the SG on the basis of the traffic mode
> for
> > > the
> > > > > SG.
> > > > >
> > > > >   If some SG are restricted for the specified destination (based
> on
> > > > > received
> > > > >   DRST messages from the SG), the ASP should load-share across
> the
> > > > > available
> > > > >   unrestricted SGs.  If all SGs are restricted for a given
> > > destination,
> > > > > the
> > > > >   ASP should load-share across the available SGs and ignore the
> > > > > restricted
> > > > >   status.
> > > > >
> > > > >   If some SG are prohibited for the specified destination (based
> on
> > > > > received
> > > > >   DUNA messages from the SG), the ASP should load-share across
> the
> > > > > available
> > > > >   non-prohibited SGs.  If all SGs are prohibited for a given
> > > destination
> > > > > (or
> > > > >   no SGP is active for the AS/RC/RK in any SG), the ASP should
> > > respond
> > > > > to the
> > > > >   MTP-User with an MTP-PAUSE in accordance with the style of the
> > > > > MTP-User
> > > > >   interface (ITU-T and ANSI differ here).
> > > > >
> > > > > Properly selecting SGs requires that the ASP maintain the
> > > DUNA/DAVA/DRST
> > > > > information for each destination received from any SGP in an SG,
> on
> > > a
> > > > > per-SG
> > > > > basis.  This is the same as MTP Level 3 ROUTE status.  However,
> SCON
> > > > > information should only be maintained on a per-destination basis
> > > (and
> > > > > not
> > > > > per-SG).  This is the same as MTP Level 3 ROUTESET status.
> > > > >
> > > > > Note that, in general, it is a bad idea to consider congestion
> > > (SCON)
> > > > > when
> > > > > selecting an SG.  SCON does not necessarily indicate congestion
> at
> > > an SG
> > > > > or on
> > > > > a path to an SG, but indicates congestion at the affected
> > > destination or
> > > > > somewhere (perhaps distant) in the SS7 network.  SCON is
> > > > > ROUTESET-specific
> > > > > (applies to the destination), whereas DUNA/DAVA/DRST is
> > > ROUTE-specific
> > > > > (applies to the destination and path).  SCON should only be used
> to
> > > > > determine
> > > > > whether a message should be dropped completely and an MTP-STATUS
> > > > > returned to
> > > > > the MTP-User according to the style of the MTP-User interface
> (ITU-T
> > > and
> > > > > ANSI
> > > > > differ here again).
> > > > >
> > > > > So, to summarize:  on behalf of the AS/RC/RK/MTP-User, the ASP
> > > > > determines
> > > > > whether to send a message based on SCON received for the
> specified
> > > > > destination, then selects an SG based on DUNA/DAVA/DRST received
> for
> > > the
> > > > > specified destination and load-shares based on SLS across the
> > > eligible
> > > > > SGs.
> > > > > Once an SG is selected, an active SGP (active for the AS/RC/RK)
> is
> > > > > selected
> > > > > within the SG based on the traffic mode of the SG
> (active/standby,
> > > > > load-share,
> > > > > broadcast: but typically load-share on SLS).
> > > > >
> > > > > As I said, there are other schools of thought, but that is my
> > > > > understanding.
> > > > >
> > > > > --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/
> > 
> > --
> > 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 mailnull@www1.ietf.org  Thu Jan 30 05:54: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 FAA24035
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 05:54:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0UBFxd22786
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 06:15:59 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UBFEJ22744;
	Thu, 30 Jan 2003 06:15:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UBEIJ22717
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 06:14:18 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24016
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 05:51:55 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0UAtMJT023543;
	Thu, 30 Jan 2003 04:55:24 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id PAA04173; Thu, 30 Jan 2003 15:24:19 -0500 (GMT)
Message-ID: <3E3904A4.7BDAFD7E@axes-mach01.usa.alcatel.com>
Date: Thu, 30 Jan 2003 16:25:33 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
References: <OFEC77243A.47A4213E-ONC2256CBC.002FD630@LocalDomain> <3E38AC51.B358D2E7@axes-mach01.usa.alcatel.com> <20030129223645.C1341@openss7.org> <3E38CD3F.94A343E5@axes-mach01.usa.alcatel.com> <20030130000108.A28966@openss7.org> <3E38D245.A5C93237@axes-mach01.usa.alcatel.com> <20030130031827.B10733@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

     Can you clear my basic doubt,

    How an SGP is selected when a message from the SS7 network is received at the SG?.

--Srini

"Brian F. G. Bidulock" wrote:

> Srini,
>
> If they don't have different connectivity to the SS7 network, they can hardly
> be viewed as separate and different SGs.
>
> --brian
>
> ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:50:37)
> > Brian,
> >
> >     So, the M3UA at the SGP should be informed the SG which received this message.
> >
> > --Srini
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > Srini,
> > >
> > > The association would be chosen on the basis of for which SG the
> > > message from the SS7 network arrived.
> > >
> > > --brian
> > >
> > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:29:11)
> > > > Brian,
> > > >
> > > >       Can you please tell me, how a message received from the SS7 network is routed using such a SGP(having two
> > > > different associations) to the AS?.
> > > >
> > > > --Srini.
> > > >
> > > > "Brian F. G. Bidulock" wrote:
> > > >
> > > > > Srini,
> > > > >
> > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 10:08:41)
> > > > > > Tolga,
> > > > > >
> > > > > > An ASP can be a part of different ASs. Similarly, Can a SGP be a part of
> > > > > > different SGs?
> > > > >
> > > > > Sure.  But from the viewpoint of an ASP, the SGP belongs to one SG.  If an
> > > > > SGP were to perform the function for two SGs for the same AS, the ASP would
> > > > > have to form two associations with the SGP: one for SG-A, the other for SG-B.
> > > > > The SGP would also need some way of knowing (e.g. static port allocation)
> > > > > for which SG the ASP was forming an association.
> > > > >
> > > > > --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
>
> --
> 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 mailnull@www1.ietf.org  Thu Jan 30 06:07: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 GAA24230
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 06:07:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0UBStc23246
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 06:28:55 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UBS5J23208;
	Thu, 30 Jan 2003 06:28:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UBRdJ23193
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 06:27:39 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24168
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 06:05:14 -0500 (EST)
Subject: Re: [Sigtran] M3UA SG-SG (again)
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF11A095A3.A86ADBAC-ONC2256CBE.003CD302@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Thu, 30 Jan 2003 13:05:18 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/30/2003
 01:05:24 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>


a typo:

to use a specific port ===> not to use a specific port


Ken,

[KAM] do you plan to apply for a different SCTP port for SG-SG or reuse
M3UA port of 2905?

[TOLGA]I would think 2905 should be fine. Unless we restrict ASPs to use a
specific port (which is allocated for SG-SG), still we would need to look
to ASPID in ASPUP to decide for the type of peer, when dynamic addressing
is used.

_______________________________________________
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 Jan 30 06:10:50 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 GAA24303
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 06:10:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0UBWgd23402
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 06:32:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UBW6J23380;
	Thu, 30 Jan 2003 06:32:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UBVoJ23364
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 06:31:50 -0500
Received: from postman (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24287
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 06:09:25 -0500 (EST)
Subject: Re: [Sigtran] M3UA SG-SG (again)
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF51826E43.2087CD15-ONC2256CBE.003D0B7D@LocalDomain>
From: "TOLGA ASVEREN" <TOLGA.ASVEREN@o2.com.tr>
Date: Thu, 30 Jan 2003 13:09:30 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 01/30/2003
 01:09:35 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>


Ken,

                 IP-SP  IP Signalling Point

[KAM] does this have same definition as IPSP in M3UA?

[TOLGA] No. This one is a SS7 signalling point, which (also) uses SCTP
associations to transfer messages. I will add the definition to the
draft(also the other editorials).

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



From mailnull@www1.ietf.org  Thu Jan 30 07:27: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 HAA25385
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 07:27:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0UCnhO28423
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 07:49:43 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UCnPJ28410;
	Thu, 30 Jan 2003 07:49:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UCjDJ28283
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 07:45:13 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25361
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 07:22:47 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:r9A0g5G1LNbCDDD2K4FEGG70rHcQufTD@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0UCQJD32147;
	Thu, 30 Jan 2003 05:26:19 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0UCQIt00468;
	Thu, 30 Jan 2003 05:26:18 -0700
Date: Thu, 30 Jan 2003 05:26:18 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
Message-ID: <20030130052618.B21821@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
References: <OFEC77243A.47A4213E-ONC2256CBC.002FD630@LocalDomain> <3E38AC51.B358D2E7@axes-mach01.usa.alcatel.com> <20030129223645.C1341@openss7.org> <3E38CD3F.94A343E5@axes-mach01.usa.alcatel.com> <20030130000108.A28966@openss7.org> <3E38D245.A5C93237@axes-mach01.usa.alcatel.com> <20030130031827.B10733@openss7.org> <3E3904A4.7BDAFD7E@axes-mach01.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: <3E3904A4.7BDAFD7E@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Thu, Jan 30, 2003 at 04:25:33PM +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>

Srini,

IMO, SLS (or something used to derive SLS such as CIC) is the only rational
basis for SGP selection at an SG.

--brian

ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 16:25:33)
> Brian,
> 
>      Can you clear my basic doubt,
> 
>     How an SGP is selected when a message from the SS7 network is received at the SG?.
> 
> --Srini
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Srini,
> >
> > If they don't have different connectivity to the SS7 network, they can hardly
> > be viewed as separate and different SGs.
> >
> > --brian
> >
> > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:50:37)
> > > Brian,
> > >
> > >     So, the M3UA at the SGP should be informed the SG which received this message.
> > >
> > > --Srini
> > >
> > > "Brian F. G. Bidulock" wrote:
> > >
> > > > Srini,
> > > >
> > > > The association would be chosen on the basis of for which SG the
> > > > message from the SS7 network arrived.
> > > >
> > > > --brian
> > > >
> > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:29:11)
> > > > > Brian,
> > > > >
> > > > >       Can you please tell me, how a message received from the SS7 network is routed using such a SGP(having two
> > > > > different associations) to the AS?.
> > > > >
> > > > > --Srini.
> > > > >
> > > > > "Brian F. G. Bidulock" wrote:
> > > > >
> > > > > > Srini,
> > > > > >
> > > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 10:08:41)
> > > > > > > Tolga,
> > > > > > >
> > > > > > > An ASP can be a part of different ASs. Similarly, Can a SGP be a part of
> > > > > > > different SGs?
> > > > > >
> > > > > > Sure.  But from the viewpoint of an ASP, the SGP belongs to one SG.  If an
> > > > > > SGP were to perform the function for two SGs for the same AS, the ASP would
> > > > > > have to form two associations with the SGP: one for SG-A, the other for SG-B.
> > > > > > The SGP would also need some way of knowing (e.g. static port allocation)
> > > > > > for which SG the ASP was forming an association.
> > > > > >
> > > > > > --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
> >
> > --
> > 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 mailnull@www1.ietf.org  Thu Jan 30 07:37: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 HAA25540
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 07:37:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0UCxck28825
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 07:59:38 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UCxCJ28787;
	Thu, 30 Jan 2003 07:59:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UCw1J28733
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 07:58:01 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25499
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 07:35:36 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0UCd4eW022780;
	Thu, 30 Jan 2003 06:39:05 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id RAA06846; Thu, 30 Jan 2003 17:08:01 -0500 (GMT)
Message-ID: <3E391CF3.DC147530@axes-mach01.usa.alcatel.com>
Date: Thu, 30 Jan 2003 18:09:16 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
References: <OFEC77243A.47A4213E-ONC2256CBC.002FD630@LocalDomain> <3E38AC51.B358D2E7@axes-mach01.usa.alcatel.com> <20030129223645.C1341@openss7.org> <3E38CD3F.94A343E5@axes-mach01.usa.alcatel.com> <20030130000108.A28966@openss7.org> <3E38D245.A5C93237@axes-mach01.usa.alcatel.com> <20030130031827.B10733@openss7.org> <3E3904A4.7BDAFD7E@axes-mach01.usa.alcatel.com> <20030130052618.B21821@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

     I feel once the eligible list of SGPs to reach the AS are found, you answer applies. But my doubt is How to find the
eligible list of SGPs?.

--Srini

"Brian F. G. Bidulock" wrote:

> Srini,
>
> IMO, SLS (or something used to derive SLS such as CIC) is the only rational
> basis for SGP selection at an SG.
>
> --brian
>
> ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 16:25:33)
> > Brian,
> >
> >      Can you clear my basic doubt,
> >
> >     How an SGP is selected when a message from the SS7 network is received at the SG?.
> >
> > --Srini
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > Srini,
> > >
> > > If they don't have different connectivity to the SS7 network, they can hardly
> > > be viewed as separate and different SGs.
> > >
> > > --brian
> > >
> > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:50:37)
> > > > Brian,
> > > >
> > > >     So, the M3UA at the SGP should be informed the SG which received this message.
> > > >
> > > > --Srini
> > > >
> > > > "Brian F. G. Bidulock" wrote:
> > > >
> > > > > Srini,
> > > > >
> > > > > The association would be chosen on the basis of for which SG the
> > > > > message from the SS7 network arrived.
> > > > >
> > > > > --brian
> > > > >
> > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:29:11)
> > > > > > Brian,
> > > > > >
> > > > > >       Can you please tell me, how a message received from the SS7 network is routed using such a SGP(having two
> > > > > > different associations) to the AS?.
> > > > > >
> > > > > > --Srini.
> > > > > >
> > > > > > "Brian F. G. Bidulock" wrote:
> > > > > >
> > > > > > > Srini,
> > > > > > >
> > > > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 10:08:41)
> > > > > > > > Tolga,
> > > > > > > >
> > > > > > > > An ASP can be a part of different ASs. Similarly, Can a SGP be a part of
> > > > > > > > different SGs?
> > > > > > >
> > > > > > > Sure.  But from the viewpoint of an ASP, the SGP belongs to one SG.  If an
> > > > > > > SGP were to perform the function for two SGs for the same AS, the ASP would
> > > > > > > have to form two associations with the SGP: one for SG-A, the other for SG-B.
> > > > > > > The SGP would also need some way of knowing (e.g. static port allocation)
> > > > > > > for which SG the ASP was forming an association.
> > > > > > >
> > > > > > > --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
> > >
> > > --
> > > 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 mailnull@www1.ietf.org  Thu Jan 30 08:00:25 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 IAA26344
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 08:00:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0UDMK730412
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 08:22:20 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UDLIJ30358;
	Thu, 30 Jan 2003 08:21:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UDKEJ30272
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 08:20:14 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26224
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 07:57:47 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:asRUXaUEsdL46vmaZkB37XFMzmWWqtcV@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0UD1ID32633;
	Thu, 30 Jan 2003 06:01:18 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0UD1Ir04680;
	Thu, 30 Jan 2003 06:01:18 -0700
Date: Thu, 30 Jan 2003 06:01:18 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
Message-ID: <20030130060118.A3822@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
References: <OFEC77243A.47A4213E-ONC2256CBC.002FD630@LocalDomain> <3E38AC51.B358D2E7@axes-mach01.usa.alcatel.com> <20030129223645.C1341@openss7.org> <3E38CD3F.94A343E5@axes-mach01.usa.alcatel.com> <20030130000108.A28966@openss7.org> <3E38D245.A5C93237@axes-mach01.usa.alcatel.com> <20030130031827.B10733@openss7.org> <3E3904A4.7BDAFD7E@axes-mach01.usa.alcatel.com> <20030130052618.B21821@openss7.org> <3E391CF3.DC147530@axes-mach01.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: <3E391CF3.DC147530@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Thu, Jan 30, 2003 at 06:09:16PM +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>

Srini,

The eligible list of SGPs is all the SGPs belonging to the SG
that have connectivity to the AS and for which an ASP is in
the ASP-ACTIVE state for the AS.

--brian

ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 18:09:16)
> Brian,
> 
>      I feel once the eligible list of SGPs to reach the AS are found, you answer applies. But my doubt is How to find the
> eligible list of SGPs?.
> 
> --Srini
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Srini,
> >
> > IMO, SLS (or something used to derive SLS such as CIC) is the only rational
> > basis for SGP selection at an SG.
> >
> > --brian
> >
> > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 16:25:33)
> > > Brian,
> > >
> > >      Can you clear my basic doubt,
> > >
> > >     How an SGP is selected when a message from the SS7 network is received at the SG?.
> > >
> > > --Srini
> > >
> > > "Brian F. G. Bidulock" wrote:
> > >
> > > > Srini,
> > > >
> > > > If they don't have different connectivity to the SS7 network, they can hardly
> > > > be viewed as separate and different SGs.
> > > >
> > > > --brian
> > > >
> > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:50:37)
> > > > > Brian,
> > > > >
> > > > >     So, the M3UA at the SGP should be informed the SG which received this message.
> > > > >
> > > > > --Srini
> > > > >
> > > > > "Brian F. G. Bidulock" wrote:
> > > > >
> > > > > > Srini,
> > > > > >
> > > > > > The association would be chosen on the basis of for which SG the
> > > > > > message from the SS7 network arrived.
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:29:11)
> > > > > > > Brian,
> > > > > > >
> > > > > > >       Can you please tell me, how a message received from the SS7 network is routed using such a SGP(having two
> > > > > > > different associations) to the AS?.
> > > > > > >
> > > > > > > --Srini.
> > > > > > >
> > > > > > > "Brian F. G. Bidulock" wrote:
> > > > > > >
> > > > > > > > Srini,
> > > > > > > >
> > > > > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 10:08:41)
> > > > > > > > > Tolga,
> > > > > > > > >
> > > > > > > > > An ASP can be a part of different ASs. Similarly, Can a SGP be a part of
> > > > > > > > > different SGs?
> > > > > > > >
> > > > > > > > Sure.  But from the viewpoint of an ASP, the SGP belongs to one SG.  If an
> > > > > > > > SGP were to perform the function for two SGs for the same AS, the ASP would
> > > > > > > > have to form two associations with the SGP: one for SG-A, the other for SG-B.
> > > > > > > > The SGP would also need some way of knowing (e.g. static port allocation)
> > > > > > > > for which SG the ASP was forming an association.
> > > > > > > >
> > > > > > > > --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
> > > >
> > > > --
> > > > 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/

-- 
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 Jan 30 08:21: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 IAA26751
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 08:21:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0UDh1H31907
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 08:43:01 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UDgHJ31861;
	Thu, 30 Jan 2003 08:42:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UDfjJ31826
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 08:41:45 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26735
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 08:19:18 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0UDMkeW027360;
	Thu, 30 Jan 2003 07:22:47 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id RAA07670; Thu, 30 Jan 2003 17:51:43 -0500 (GMT)
Message-ID: <3E392731.A7431820@axes-mach01.usa.alcatel.com>
Date: Thu, 30 Jan 2003 18:52:58 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
References: <OFEC77243A.47A4213E-ONC2256CBC.002FD630@LocalDomain> <3E38AC51.B358D2E7@axes-mach01.usa.alcatel.com> <20030129223645.C1341@openss7.org> <3E38CD3F.94A343E5@axes-mach01.usa.alcatel.com> <20030130000108.A28966@openss7.org> <3E38D245.A5C93237@axes-mach01.usa.alcatel.com> <20030130031827.B10733@openss7.org> <3E3904A4.7BDAFD7E@axes-mach01.usa.alcatel.com> <20030130052618.B21821@openss7.org> <3E391CF3.DC147530@axes-mach01.usa.alcatel.com> <20030130060118.A3822@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

  How the SGP connectivity to the AS is determined at the SG?. Do we have to have AS-SGPs list?. But in that case we need to look
at the complete routing key table at the SG before selecting the SGP from the AS(RK).

--Srini

"Brian F. G. Bidulock" wrote:

> Srini,
>
> The eligible list of SGPs is all the SGPs belonging to the SG
> that have connectivity to the AS and for which an ASP is in
> the ASP-ACTIVE state for the AS.
>
> --brian
>
> ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 18:09:16)
> > Brian,
> >
> >      I feel once the eligible list of SGPs to reach the AS are found, you answer applies. But my doubt is How to find the
> > eligible list of SGPs?.
> >
> > --Srini
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > Srini,
> > >
> > > IMO, SLS (or something used to derive SLS such as CIC) is the only rational
> > > basis for SGP selection at an SG.
> > >
> > > --brian
> > >
> > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 16:25:33)
> > > > Brian,
> > > >
> > > >      Can you clear my basic doubt,
> > > >
> > > >     How an SGP is selected when a message from the SS7 network is received at the SG?.
> > > >
> > > > --Srini
> > > >
> > > > "Brian F. G. Bidulock" wrote:
> > > >
> > > > > Srini,
> > > > >
> > > > > If they don't have different connectivity to the SS7 network, they can hardly
> > > > > be viewed as separate and different SGs.
> > > > >
> > > > > --brian
> > > > >
> > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:50:37)
> > > > > > Brian,
> > > > > >
> > > > > >     So, the M3UA at the SGP should be informed the SG which received this message.
> > > > > >
> > > > > > --Srini
> > > > > >
> > > > > > "Brian F. G. Bidulock" wrote:
> > > > > >
> > > > > > > Srini,
> > > > > > >
> > > > > > > The association would be chosen on the basis of for which SG the
> > > > > > > message from the SS7 network arrived.
> > > > > > >
> > > > > > > --brian
> > > > > > >
> > > > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:29:11)
> > > > > > > > Brian,
> > > > > > > >
> > > > > > > >       Can you please tell me, how a message received from the SS7 network is routed using such a SGP(having two
> > > > > > > > different associations) to the AS?.
> > > > > > > >
> > > > > > > > --Srini.
> > > > > > > >
> > > > > > > > "Brian F. G. Bidulock" wrote:
> > > > > > > >
> > > > > > > > > Srini,
> > > > > > > > >
> > > > > > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 10:08:41)
> > > > > > > > > > Tolga,
> > > > > > > > > >
> > > > > > > > > > An ASP can be a part of different ASs. Similarly, Can a SGP be a part of
> > > > > > > > > > different SGs?
> > > > > > > > >
> > > > > > > > > Sure.  But from the viewpoint of an ASP, the SGP belongs to one SG.  If an
> > > > > > > > > SGP were to perform the function for two SGs for the same AS, the ASP would
> > > > > > > > > have to form two associations with the SGP: one for SG-A, the other for SG-B.
> > > > > > > > > The SGP would also need some way of knowing (e.g. static port allocation)
> > > > > > > > > for which SG the ASP was forming an association.
> > > > > > > > >
> > > > > > > > > --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
> > > > >
> > > > > --
> > > > > 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/
>
> --
> 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 mailnull@www1.ietf.org  Thu Jan 30 09:00:50 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 JAA28732
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 09:00:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0UEMkY05617
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 09:22:46 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UEKcJ05125;
	Thu, 30 Jan 2003 09:20:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UEJrJ04974
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 09:19:53 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28543
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 08:57:24 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:eXymZVZOTgRVDMgOa2Jj2uupITT8I3wo@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0UE0uD00883;
	Thu, 30 Jan 2003 07:00:56 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0UE0tb11578;
	Thu, 30 Jan 2003 07:00:55 -0700
Date: Thu, 30 Jan 2003 07:00:55 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
Message-ID: <20030130070055.A11092@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
References: <20030129223645.C1341@openss7.org> <3E38CD3F.94A343E5@axes-mach01.usa.alcatel.com> <20030130000108.A28966@openss7.org> <3E38D245.A5C93237@axes-mach01.usa.alcatel.com> <20030130031827.B10733@openss7.org> <3E3904A4.7BDAFD7E@axes-mach01.usa.alcatel.com> <20030130052618.B21821@openss7.org> <3E391CF3.DC147530@axes-mach01.usa.alcatel.com> <20030130060118.A3822@openss7.org> <3E392731.A7431820@axes-mach01.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: <3E392731.A7431820@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Thu, Jan 30, 2003 at 06:52:58PM +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>

Srini,

If the AS corresponds to an MTP-SAP (MTP-User), all that the SGP need do is
find the MTP-User.  How an MTP Level 3 SS7 stack finds the MTP-User is a
matter for the MTP Level 3 SS7 stack.

--brian

ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 18:52:58)
> Brian,
> 
>   How the SGP connectivity to the AS is determined at the SG?. Do we have to have AS-SGPs list?. But in that case we need to look
> at the complete routing key table at the SG before selecting the SGP from the AS(RK).
> 
> --Srini
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Srini,
> >
> > The eligible list of SGPs is all the SGPs belonging to the SG
> > that have connectivity to the AS and for which an ASP is in
> > the ASP-ACTIVE state for the AS.
> >
> > --brian
> >
> > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 18:09:16)
> > > Brian,
> > >
> > >      I feel once the eligible list of SGPs to reach the AS are found, you answer applies. But my doubt is How to find the
> > > eligible list of SGPs?.
> > >
> > > --Srini
> > >
> > > "Brian F. G. Bidulock" wrote:
> > >
> > > > Srini,
> > > >
> > > > IMO, SLS (or something used to derive SLS such as CIC) is the only rational
> > > > basis for SGP selection at an SG.
> > > >
> > > > --brian
> > > >
> > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 16:25:33)
> > > > > Brian,
> > > > >
> > > > >      Can you clear my basic doubt,
> > > > >
> > > > >     How an SGP is selected when a message from the SS7 network is received at the SG?.
> > > > >
> > > > > --Srini
> > > > >
> > > > > "Brian F. G. Bidulock" wrote:
> > > > >
> > > > > > Srini,
> > > > > >
> > > > > > If they don't have different connectivity to the SS7 network, they can hardly
> > > > > > be viewed as separate and different SGs.
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:50:37)
> > > > > > > Brian,
> > > > > > >
> > > > > > >     So, the M3UA at the SGP should be informed the SG which received this message.
> > > > > > >
> > > > > > > --Srini
> > > > > > >
> > > > > > > "Brian F. G. Bidulock" wrote:
> > > > > > >
> > > > > > > > Srini,
> > > > > > > >
> > > > > > > > The association would be chosen on the basis of for which SG the
> > > > > > > > message from the SS7 network arrived.
> > > > > > > >
> > > > > > > > --brian
> > > > > > > >
> > > > > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:29:11)
> > > > > > > > > Brian,
> > > > > > > > >
> > > > > > > > >       Can you please tell me, how a message received from the SS7 network is routed using such a SGP(having two
> > > > > > > > > different associations) to the AS?.
> > > > > > > > >
> > > > > > > > > --Srini.
> > > > > > > > >
> > > > > > > > > "Brian F. G. Bidulock" wrote:
> > > > > > > > >
> > > > > > > > > > Srini,
> > > > > > > > > >
> > > > > > > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 10:08:41)
> > > > > > > > > > > Tolga,
> > > > > > > > > > >
> > > > > > > > > > > An ASP can be a part of different ASs. Similarly, Can a SGP be a part of
> > > > > > > > > > > different SGs?
> > > > > > > > > >
> > > > > > > > > > Sure.  But from the viewpoint of an ASP, the SGP belongs to one SG.  If an
> > > > > > > > > > SGP were to perform the function for two SGs for the same AS, the ASP would
> > > > > > > > > > have to form two associations with the SGP: one for SG-A, the other for SG-B.
> > > > > > > > > > The SGP would also need some way of knowing (e.g. static port allocation)
> > > > > > > > > > for which SG the ASP was forming an association.
> > > > > > > > > >
> > > > > > > > > > --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
> > > > > >
> > > > > > --
> > > > > > 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/
> >
> > --
> > 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 mailnull@www1.ietf.org  Thu Jan 30 09:59: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 JAA00344
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 09:59:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0UF2gf01399
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 10:02:42 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UF1WJ00939;
	Thu, 30 Jan 2003 10:01:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UF0PJ00618
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 10:00:25 -0500
Received: from auds951.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00273
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 09:56:50 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0UF0IJT019609;
	Thu, 30 Jan 2003 09:00:19 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id TAA08843; Thu, 30 Jan 2003 19:02:59 -0500 (GMT)
Message-ID: <3E393793.665779E5@axes-mach01.usa.alcatel.com>
Date: Thu, 30 Jan 2003 20:02:51 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org,
        karlapudi_srini@hotmail.com
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
References: <20030129223645.C1341@openss7.org> <3E38CD3F.94A343E5@axes-mach01.usa.alcatel.com> <20030130000108.A28966@openss7.org> <3E38D245.A5C93237@axes-mach01.usa.alcatel.com> <20030130031827.B10733@openss7.org> <3E3904A4.7BDAFD7E@axes-mach01.usa.alcatel.com> <20030130052618.B21821@openss7.org> <3E391CF3.DC147530@axes-mach01.usa.alcatel.com> <20030130060118.A3822@openss7.org> <3E392731.A7431820@axes-mach01.usa.alcatel.com> <20030130070055.A11092@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

   Yes, I agree with you. Finding the eligible list of SGPs is the matter for MTP Level 3 SS7 stack / NIF. But IMO maintaining the
complete routing keys at the SG itself will enable us to select the eligible SGPs better. Because based on the PC of AS(i.e., DPC)
alone or any other info of routing label alone, will not suffice to select the SGP to reach the AS. Is my assumption right?.

--Srini

"Brian F. G. Bidulock" wrote:

> Srini,
>
> If the AS corresponds to an MTP-SAP (MTP-User), all that the SGP need do is
> find the MTP-User.  How an MTP Level 3 SS7 stack finds the MTP-User is a
> matter for the MTP Level 3 SS7 stack.
>
> --brian
>
> ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 18:52:58)
> > Brian,
> >
> >   How the SGP connectivity to the AS is determined at the SG?. Do we have to have AS-SGPs list?. But in that case we need to look
> > at the complete routing key table at the SG before selecting the SGP from the AS(RK).
> >
> > --Srini
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > Srini,
> > >
> > > The eligible list of SGPs is all the SGPs belonging to the SG
> > > that have connectivity to the AS and for which an ASP is in
> > > the ASP-ACTIVE state for the AS.
> > >
> > > --brian
> > >
> > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 18:09:16)
> > > > Brian,
> > > >
> > > >      I feel once the eligible list of SGPs to reach the AS are found, you answer applies. But my doubt is How to find the
> > > > eligible list of SGPs?.
> > > >
> > > > --Srini
> > > >
> > > > "Brian F. G. Bidulock" wrote:
> > > >
> > > > > Srini,
> > > > >
> > > > > IMO, SLS (or something used to derive SLS such as CIC) is the only rational
> > > > > basis for SGP selection at an SG.
> > > > >
> > > > > --brian
> > > > >
> > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 16:25:33)
> > > > > > Brian,
> > > > > >
> > > > > >      Can you clear my basic doubt,
> > > > > >
> > > > > >     How an SGP is selected when a message from the SS7 network is received at the SG?.
> > > > > >
> > > > > > --Srini
> > > > > >
> > > > > > "Brian F. G. Bidulock" wrote:
> > > > > >
> > > > > > > Srini,
> > > > > > >
> > > > > > > If they don't have different connectivity to the SS7 network, they can hardly
> > > > > > > be viewed as separate and different SGs.
> > > > > > >
> > > > > > > --brian
> > > > > > >
> > > > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:50:37)
> > > > > > > > Brian,
> > > > > > > >
> > > > > > > >     So, the M3UA at the SGP should be informed the SG which received this message.
> > > > > > > >
> > > > > > > > --Srini
> > > > > > > >
> > > > > > > > "Brian F. G. Bidulock" wrote:
> > > > > > > >
> > > > > > > > > Srini,
> > > > > > > > >
> > > > > > > > > The association would be chosen on the basis of for which SG the
> > > > > > > > > message from the SS7 network arrived.
> > > > > > > > >
> > > > > > > > > --brian
> > > > > > > > >
> > > > > > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 12:29:11)
> > > > > > > > > > Brian,
> > > > > > > > > >
> > > > > > > > > >       Can you please tell me, how a message received from the SS7 network is routed using such a SGP(having two
> > > > > > > > > > different associations) to the AS?.
> > > > > > > > > >
> > > > > > > > > > --Srini.
> > > > > > > > > >
> > > > > > > > > > "Brian F. G. Bidulock" wrote:
> > > > > > > > > >
> > > > > > > > > > > Srini,
> > > > > > > > > > >
> > > > > > > > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 10:08:41)
> > > > > > > > > > > > Tolga,
> > > > > > > > > > > >
> > > > > > > > > > > > An ASP can be a part of different ASs. Similarly, Can a SGP be a part of
> > > > > > > > > > > > different SGs?
> > > > > > > > > > >
> > > > > > > > > > > Sure.  But from the viewpoint of an ASP, the SGP belongs to one SG.  If an
> > > > > > > > > > > SGP were to perform the function for two SGs for the same AS, the ASP would
> > > > > > > > > > > have to form two associations with the SGP: one for SG-A, the other for SG-B.
> > > > > > > > > > > The SGP would also need some way of knowing (e.g. static port allocation)
> > > > > > > > > > > for which SG the ASP was forming an association.
> > > > > > > > > > >
> > > > > > > > > > > --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
> > > > > > >
> > > > > > > --
> > > > > > > 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/
> > >
> > > --
> > > 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 mailnull@www1.ietf.org  Thu Jan 30 10:02: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 KAA00476
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 10:02:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0UF5in02377
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 10:05:44 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UF59J02142;
	Thu, 30 Jan 2003 10:05:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UF4VJ01936
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 10:04:31 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00420
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 10:00:56 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:Z3oEmYo8oKBACVnsynfoRckIjpzy/dU3@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0UF4SD01796;
	Thu, 30 Jan 2003 08:04:28 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0UF4RN19689;
	Thu, 30 Jan 2003 08:04:27 -0700
Date: Thu, 30 Jan 2003 08:04:27 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org,
        karlapudi_srini@hotmail.com
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
Message-ID: <20030130080427.A19032@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org,
	karlapudi_srini@hotmail.com
References: <20030130000108.A28966@openss7.org> <3E38D245.A5C93237@axes-mach01.usa.alcatel.com> <20030130031827.B10733@openss7.org> <3E3904A4.7BDAFD7E@axes-mach01.usa.alcatel.com> <20030130052618.B21821@openss7.org> <3E391CF3.DC147530@axes-mach01.usa.alcatel.com> <20030130060118.A3822@openss7.org> <3E392731.A7431820@axes-mach01.usa.alcatel.com> <20030130070055.A11092@openss7.org> <3E393793.665779E5@axes-mach01.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: <3E393793.665779E5@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Thu, Jan 30, 2003 at 08:02:51PM +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>

Srini,

SS7 MTP Level 3 finds the MTP-SAP quite nicely today using
the information from the RL.  The RL (NI/DPC/SI) is all that
is required to locate the AS.

--brian

ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 20:02:51)
> Brian,
> 
>    Yes, I agree with you. Finding the eligible list of SGPs is the matter for MTP Level 3 SS7 stack / NIF. But IMO maintaining the
> complete routing keys at the SG itself will enable us to select the eligible SGPs better. Because based on the PC of AS(i.e., DPC)
> alone or any other info of routing label alone, will not suffice to select the SGP to reach the AS. Is my assumption right?.
> 
> --Srini
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Srini,
> >
> > If the AS corresponds to an MTP-SAP (MTP-User), all that the SGP need do is
> > find the MTP-User.  How an MTP Level 3 SS7 stack finds the MTP-User is a
> > matter for the MTP Level 3 SS7 stack.
> >
> > --brian
> >
> > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 18:52:58)
> > > Brian,
> > >
> > >   How the SGP connectivity to the AS is determined at the SG?. Do we have to have AS-SGPs list?. But in that case we need to look
> > > at the complete routing key table at the SG before selecting the SGP from the AS(RK).
> > >
> > > --Srini
> > >
> > > "Brian F. G. Bidulock" wrote:
> > >
> > > > Srini,
> > > >
> > > > The eligible list of SGPs is all the SGPs belonging to the SG
> > > > that have connectivity to the AS and for which an ASP is in
> > > > the ASP-ACTIVE state for the AS.
> > > >
> > > > --brian
> > > >
> > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 18:09:16)
> > > > > Brian,
> > > > >
> > > > >      I feel once the eligible list of SGPs to reach the AS are found, you answer applies. But my doubt is How to find the
> > > > > eligible list of SGPs?.
> > > > >
> > > > > --Srini
> > > > >
> > > > > "Brian F. G. Bidulock" wrote:
> > > > >

-- 
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 Jan 30 17:33: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 RAA12273
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 17:33:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0UMaYj02120
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 17:36:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UMa8J02096;
	Thu, 30 Jan 2003 17:36:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0U4naJ20343
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 23:49:36 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07931
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 23:27:16 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0U4Ufqe028809;
	Wed, 29 Jan 2003 22:30:42 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id IAA23580; Thu, 30 Jan 2003 08:59:43 -0500 (GMT)
Message-ID: <3E38AA9B.7459550F@axes-mach01.usa.alcatel.com>
Date: Thu, 30 Jan 2003 10:01:26 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: TOLGA ASVEREN <tolga.asveren@o2.com.tr>
CC: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
References: <OFEC77243A.47A4213E-ONC2256CBC.002FD630@LocalDomain>
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
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

Tolga,

   An ASP can be a part of different ASs. Similarly, Can a SGP be a part of
different SGs?

--Srini

TOLGA ASVEREN wrote:

> Jolan,
>
> > -----Original Message-----
> > From: "Jolan Evans" <jolan.evans@opentelecommunications.com>
> > Sent: Tuesday, January 28, 2003 10:17 AM
> > To: "Sigtran" <sigtran@ietf.org>
> > Cc: <bidulock@openss7.org>
> > Subject: RE: [Sigtran] M3UA: ASP to SGP communication (Sent by
> > sigtran-admin@ietf.org on behalf of "Jolan Evans"
> > <jolan.evans@opentelecommunications.com> )
> >
> >
> > I would like to raise a few issues regarding your procedures below for
> > ASP to SGP routing. I know this discussion took places a
> > while ago, but
> > it has taken me some time to come up to speed with the RFC as I have
> > been busy on other things until recently.
> >
> > Please note that I have inserted "M3UA" into the subject line of the
> > original email.
> >
> >
> >
> > 1. Nomenclature
> > AsPc: Point code of an AS. In defining routing keys, the RFC uses DPC
> > for this term as it takes the SG's frame of reference.
> > RemotePc: Point code of an SS7 MTP entity with which an AS
> > communicates
> > via an SG, or directly in the case of IPSP-IPSP communication. In
> > defining routing keys, the RFC uses OPC for this term as it takes the
> > SG's frame of reference again.
> >
> >
> >
> > 2. Background Assumptions
> > As per Brian's introduction, we assume that zero or more
> > MTP-User's are
> > bound to an MTP-SAP. The MTP-SAP exists in a particular MTP-Network,
> > which has a particular MTP protocol variant. An SG is
> > associated with a
> > single MTP-Network. A RK is defined as in the RFC, but, for
> > clarity, is
> > independent of any SG and associated with a single MTP-Network. An
> > SgRouteSet is uniquely defined by an RK, an SG and an MTP-SAP (the RK
> > and SG must be both associated with the same MTP-Network) and also
> > specifies the network appearance for the MTP-Network to be
> > used with the
> > SG and the RC of each SGP in the SG. Therefore, an SgRouteSet is
> > implicitly associated with a single MTP-Network. An MTP-SAP is
> > associated with zero or more SgRouteSet's and therefore an MTP-SAP is
> > associated with zero or more RKs. In contrast, it appears that Brian
> > assumes that an MTP-SAP can only be associated with one RK. Given this
> > extension, we have the following requirement.
> >
> >
> >
> > 3. Routing Keys Requirements to Support Unique SS7 Destination Status
> > Let RemotePcSet(Rk) be the set of RemotePc's reachable via the SG from
> > the ASP where the RK is defined.
> > Consider any two SgRouteSet's SgRsA and SgRsA which are
> > associated with
> > the same MTP-SAP.
> > Let the routing key of SgRsA and SgRsB be RkA and RkB respectively.
> > If the intersection of RemotePcSet(RkA) and RemotePcSet(RkB)
> > is non-nil
> > then the routing keys MUST be identical in every respect apart from
> > their RemotePcSet.
> > If this wasn't the case, an ASP could never indicate an
> > MTP-RESUME to an
> > MTP-USER because an MTP-RESUME can only specify a RemotePc
> > and no other
> > SS7 element. I assume here for simplicity that every MTP-User of a
> > MTP-SAP must be given the same MTP status (i.e. different MTP-Users of
> > the same MTP-SAP cannot be given different MTP-Status indications
> > depending on what traffic they have requested).
> >
> > Here's a concrete example of why this is so. Consider an ASP with the
> > following routing keys:
> > RkA: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={A}
> > RkB: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={B}
> > RkC: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={M}
> > RkD: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={N}
> >
> > Assume that RkA and RkB were both active in SgpA and SgpB respectively
> > and are associated with the same MTP-SAP, but different SGs.
> > Also assume
> > that a DAVA has been received for RemotePc=X from SgpA after
> > a DUNA from
> > SgpB for the same RemotePc. We might consider generating an MTP-Resume
> > to all the MTP-Users of the MTP-SAP for RemotePc X. However, if an
> > MTP-User requests an MTP-Transfer with an AsPc of B then SgpB
> > may not be
> > able to transfer it as indicated by the DUNA it sent the ASP.
> >
> > The same explanation applies to RkC and RkD.
> >
> > In practice this requirement probably won't cause too many headaches
> > because it is likely that there would be two different MTP-Users, one
> > using only RkA/RkC and the other using only RkB/RkD. In this case, we
> > can simply create two MTP-SAPs in the same MTP-Network and associate
> > each routing key with a different MTP-SAP. Of course, this
> > would require
> > the M3UA implementation to support more than one MTP-SAP per
> > MTP-Network, which would be extra work obviously.
> [TOLGA] IMO there is no problem. It might be extra work but people are free
> to support such a configuration or not.
> >
> >
> >
> > 4. ASP-SGP Routing should use SS7 Destination Availability/Restricted
> > Status on a per-SGP rather than a per-SG basis.
> >
> > I believe your ASP-SGP procedures should be amended (I only amend the
> > multiple SG case as the single SG case is a special case of
> > the former)
> > as follows:
> >
> > Change:
> > "This routing information is updated by collecting DUNA/DAVA/DRST
> > messages received from (any of the SGP in) the SG."
> > To:
> > "This routing information is updated by collecting DUNA/DAVA/DRST
> > information on a per-(SGP,destination) basis. An SG is
> > considered to be
> > available and unrestricted for a particular destination if
> > any SGP in it
> > is available and unrestricted for that destination. Otherwise
> > if this is
> > not he case, then an SG is considered to be restricted for a
> > particular
> > destination if there is at least one SGP in the SG restricted for that
> > destination. Otherwise if this is not the case, the SG is
> > considered to
> > be prohibited for that destination."
> >
> > The RFC is not particular clear on this point. In section 1.4.1 para 3
> > it states that "MTP3 routeset, SPMC and remote AS/ASP states
> > of each SGP
> > SHOULD be coordinated across all the SGPs". However, this
> > uses "SHOULD"
> > which implies it is only recommended and it also doesn't specifically
> > state that SS7 destination availability, restriction and congestion
> > status ("SS7 destination status" for short) should be
> > coordinated across
> > all SGPs. I don't think that "MTP3 routeset" necessarily implies SS7
> > destination status. Also, in section 1.3.2.5 1.4.2.5 it suggests in
> > should be on a per-SGP basis. Section 4.5.2.2 uses the word "SG" but
> > also uses the term "affected route(s)". Section 1.3.2.5 and section
> > 1.4.2.5 suggest the word "route" refers to an SGP and not an
> > SG. Hence,
> > given the ambiguity of section 4.5.2.2 I think that route can be
> > considered to refer to an SGP.
> >
> > A configuration where per-SGP SS7 destination status is
> > necessary is as
> > follows. Consider an SEP SG which has two SGP's acting as a redundant
> > pair. Each SGP has it's own link set to a particular STP. While in
> > section 1.4.1 para 3 it states that "Rerouting of traffic between the
> > SGPs MAY also be supported", it uses "MAY" and hence this is optional.
> > If one link set fails but not the other, one SGP will be able to reach
> > the SS7 network but not the other if rerouting between SGPs is not
> > supported or the rerouting link has also failed. Hence, it would be
> > possible for one SGP to send a DUNA for a particular
> > destination but not
> > the other.
> [TOLGA] Again I don´t see a problem. I only agree that "MAY" in the
> sentence you refer was better changed to a "SHOULD". If somebody thinks
> that creating a unique layer3 view among SGPs belonging to the same SG is
> hard to implement/not necessary, then it is possible to have SGs consisting
> of one SGP, without violating the protocol. In that case, SSNM will be
> received separetly from each SGP, because they belong to different SGs.
> >
> >
> > Your feedback would be appreciated.
> >
> > Jolan.
> >
> >
> > --
> > Jolan Evans
> > Open Telecommunications
> > jolan.evans@opentelecommunications.com
> >
> >
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org] On Behalf
> > Of Brian F. G. Bidulock
> > Sent: Tuesday, 8 October 2002 17:47
> > To: Srikanth Yandapalli
> > Cc: sigtran@ietf.org
> > Subject: Re: [Sigtran] ASP to SGP communication
> >
> > Srikanth,
> >
> > Srikanth Yandapalli wrote:               (Tue, 08 Oct 2002 12:03:52)
> > >
> > >    I am late entrant to this group.I am quite sure all this should
> > have
> > >    been discussed and I am sorry about this.
> >
> > Welcome.
> >
> > >
> > >    In the context of a single ASP in communication with
> > multiple SGPs,
> > >    how should the routing of a MTP_DATA_REQ take place at the ASP?
> >
> > I assume you are talking about M3UA?  As we are dealing with 5 or more
> > UAs
> > now, in the future it would be helpful to add M3UA (or
> > whichever) to the
> > subject line.
> >
> > >
> > >    approach 1:
> > >
> > >    We may find out the  RK and find out the SGP list that the RK is
> > >    active on and choose one SGP for sending the message based
> > >    on congestion level and also whether we have received any DRST
> > >    message from any of the SGPs.
> >
> > This approach is applicable to multiple SGs, but not to multiple SGPs
> > within a
> > single SG.
> >
> > >    approach 2:
> > >
> > >    An SGP can also be viewed as providing route to a set of DPCs
> > >    and the routing can be based on the DPC for the message alone.
> > >    This approach is reduces the complexity but adds a situation
> > >    where the RK may not be active on that association. And also is
> > >    is mandatory to send RC on this association and if so what could
> > >    the SGP make out of the RC?
> >
> > RC should be coordinated and the same across multiple SGPs
> > within an SG.
> >
> > >
> > >    Is there a preferred approach to this issue?
> > >
> >
> > Typically, the logic can be something like this: (but there
> > are several
> > other
> > schools of thought):
> >
> > Single SG case: (multiple SGs is more complicated)
> >
> >   MTP-TRANSFER request is issued by an MTP-User.  The
> > MTP-User is bound
> > to an
> >   MTP-SAP.  The MTP-SAP is associated with an AS/RC/RK.
> > There is a pool
> > of
> >   SGPs on an SG for which the AS/RC/RK is active.  The AS may have
> > received
> >   MTP-PAUSE/RESUME/STATUS indications from the SG and may choose to
> > honor that
> >   information or not.  If the ASP chooses not to honor this
> > information
> > it can
> >   blindly send messages to the SGP and rely upon a DUNA/SCON response
> > from the
> >   SGP later.
> >
> >   Selection of an SGP within an SG is based on the traffic
> > mode for the
> > SGP.
> >   This traffic mode is not managed by M3UA, however, M3UA provides for
> >   distribution of traffic over SGP based on any of the
> > methods described
> > for
> >   ASPs (active/standby, load-share, broadcast).  A typical method is
> >   load-share based on SLS.  In this scheme, using the SLS in the
> > MTP-TRANSFER
> >   request, the ASP selects load-shares traffic over the available SGP.
> >
> > Multiple SG case:
> >
> >   In the more complicated multiple SG case, the ASP must
> > first select an
> > SG
> >   before it selects an SGP within the SG.  The ASP must maintain some
> >   additional routing information to be able to properly select an SG.
> > This
> >   routing information is updated by collecting DUNA/DAVA/DRST messages
> >   received from (any of the SGP in) the SG.  To select the
> > outgoing SG,
> > the
> >   ASP must examine the destination of the MTP-TRANSFER request.
> >
> >   (If the SG has no SGP active for the AS/RC/RK, all
> > destinations can be
> >   considered prohibited).
> >
> >   If the destination is available and unrestricted for
> > several SGs, the
> > ASP
> >   should select an SG on a load-sharing basis (based on SLS) and then
> > select
> >   an active SGP within the SG on the basis of the traffic mode for the
> > SG.
> >
> >   If some SG are restricted for the specified destination (based on
> > received
> >   DRST messages from the SG), the ASP should load-share across the
> > available
> >   unrestricted SGs.  If all SGs are restricted for a given
> > destination,
> > the
> >   ASP should load-share across the available SGs and ignore the
> > restricted
> >   status.
> >
> >   If some SG are prohibited for the specified destination (based on
> > received
> >   DUNA messages from the SG), the ASP should load-share across the
> > available
> >   non-prohibited SGs.  If all SGs are prohibited for a given
> > destination
> > (or
> >   no SGP is active for the AS/RC/RK in any SG), the ASP should respond
> > to the
> >   MTP-User with an MTP-PAUSE in accordance with the style of the
> > MTP-User
> >   interface (ITU-T and ANSI differ here).
> >
> > Properly selecting SGs requires that the ASP maintain the
> > DUNA/DAVA/DRST
> > information for each destination received from any SGP in an SG, on a
> > per-SG
> > basis.  This is the same as MTP Level 3 ROUTE status.  However, SCON
> > information should only be maintained on a per-destination basis (and
> > not
> > per-SG).  This is the same as MTP Level 3 ROUTESET status.
> >
> > Note that, in general, it is a bad idea to consider congestion (SCON)
> > when
> > selecting an SG.  SCON does not necessarily indicate
> > congestion at an SG
> > or on
> > a path to an SG, but indicates congestion at the affected
> > destination or
> > somewhere (perhaps distant) in the SS7 network.  SCON is
> > ROUTESET-specific
> > (applies to the destination), whereas DUNA/DAVA/DRST is ROUTE-specific
> > (applies to the destination and path).  SCON should only be used to
> > determine
> > whether a message should be dropped completely and an MTP-STATUS
> > returned to
> > the MTP-User according to the style of the MTP-User interface
> > (ITU-T and
> > ANSI
> > differ here again).
> >
> > So, to summarize:  on behalf of the AS/RC/RK/MTP-User, the ASP
> > determines
> > whether to send a message based on SCON received for the specified
> > destination, then selects an SG based on DUNA/DAVA/DRST
> > received for the
> > specified destination and load-shares based on SLS across the eligible
> > SGs.
> > Once an SG is selected, an active SGP (active for the AS/RC/RK) is
> > selected
> > within the SG based on the traffic mode of the SG (active/standby,
> > load-share,
> > broadcast: but typically load-share on SLS).
> >
> > As I said, there are other schools of thought, but that is my
> > understanding.
> >
> > --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
> > Jolan,
>
> > -----Original Message-----
> > From: "Jolan Evans" <jolan.evans@opentelecommunications.com>
> > Sent: Tuesday, January 28, 2003 10:17 AM
> > To: "Sigtran" <sigtran@ietf.org>
> > Cc: <bidulock@openss7.org>
> > Subject: RE: [Sigtran] M3UA: ASP to SGP communication (Sent by
> > sigtran-admin@ietf.org on behalf of "Jolan Evans"
> > <jolan.evans@opentelecommunications.com> )
> >
> >
> > I would like to raise a few issues regarding your procedures below for
> > ASP to SGP routing. I know this discussion took places a
> > while ago, but
> > it has taken me some time to come up to speed with the RFC as I have
> > been busy on other things until recently.
> >
> > Please note that I have inserted "M3UA" into the subject line of the
> > original email.
> >
> >
> >
> > 1. Nomenclature
> > AsPc: Point code of an AS. In defining routing keys, the RFC uses DPC
> > for this term as it takes the SG's frame of reference.
> > RemotePc: Point code of an SS7 MTP entity with which an AS
> > communicates
> > via an SG, or directly in the case of IPSP-IPSP communication. In
> > defining routing keys, the RFC uses OPC for this term as it takes the
> > SG's frame of reference again.
> >
> >
> >
> > 2. Background Assumptions
> > As per Brian's introduction, we assume that zero or more
> > MTP-User's are
> > bound to an MTP-SAP. The MTP-SAP exists in a particular MTP-Network,
> > which has a particular MTP protocol variant. An SG is
> > associated with a
> > single MTP-Network. A RK is defined as in the RFC, but, for
> > clarity, is
> > independent of any SG and associated with a single MTP-Network. An
> > SgRouteSet is uniquely defined by an RK, an SG and an MTP-SAP (the RK
> > and SG must be both associated with the same MTP-Network) and also
> > specifies the network appearance for the MTP-Network to be
> > used with the
> > SG and the RC of each SGP in the SG. Therefore, an SgRouteSet is
> > implicitly associated with a single MTP-Network. An MTP-SAP is
> > associated with zero or more SgRouteSet's and therefore an MTP-SAP is
> > associated with zero or more RKs. In contrast, it appears that Brian
> > assumes that an MTP-SAP can only be associated with one RK. Given this
> > extension, we have the following requirement.
> >
> >
> >
> > 3. Routing Keys Requirements to Support Unique SS7 Destination Status
> > Let RemotePcSet(Rk) be the set of RemotePc's reachable via the SG from
> > the ASP where the RK is defined.
> > Consider any two SgRouteSet's SgRsA and SgRsA which are
> > associated with
> > the same MTP-SAP.
> > Let the routing key of SgRsA and SgRsB be RkA and RkB respectively.
> > If the intersection of RemotePcSet(RkA) and RemotePcSet(RkB)
> > is non-nil
> > then the routing keys MUST be identical in every respect apart from
> > their RemotePcSet.
> > If this wasn't the case, an ASP could never indicate an
> > MTP-RESUME to an
> > MTP-USER because an MTP-RESUME can only specify a RemotePc
> > and no other
> > SS7 element. I assume here for simplicity that every MTP-User of a
> > MTP-SAP must be given the same MTP status (i.e. different MTP-Users of
> > the same MTP-SAP cannot be given different MTP-Status indications
> > depending on what traffic they have requested).
> >
> > Here's a concrete example of why this is so. Consider an ASP with the
> > following routing keys:
> > RkA: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={A}
> > RkB: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={B}
> > RkC: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={M}
> > RkD: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={N}
> >
> > Assume that RkA and RkB were both active in SgpA and SgpB respectively
> > and are associated with the same MTP-SAP, but different SGs.
> > Also assume
> > that a DAVA has been received for RemotePc=X from SgpA after
> > a DUNA from
> > SgpB for the same RemotePc. We might consider generating an MTP-Resume
> > to all the MTP-Users of the MTP-SAP for RemotePc X. However, if an
> > MTP-User requests an MTP-Transfer with an AsPc of B then SgpB
> > may not be
> > able to transfer it as indicated by the DUNA it sent the ASP.
> >
> > The same explanation applies to RkC and RkD.
> >
> > In practice this requirement probably won't cause too many headaches
> > because it is likely that there would be two different MTP-Users, one
> > using only RkA/RkC and the other using only RkB/RkD. In this case, we
> > can simply create two MTP-SAPs in the same MTP-Network and associate
> > each routing key with a different MTP-SAP. Of course, this
> > would require
> > the M3UA implementation to support more than one MTP-SAP per
> > MTP-Network, which would be extra work obviously.
> [TOLGA] IMO there is no problem. It might be extra work but people are free
> to support such a configuration or not. In your example, most probably
> there should be two different user part entities processing messages for
> RkA and RkB respectively. Each of them will only primitives related with
> them, i.e. primitives which are caused by messages arrived for the
> corresponding RK.
> (BTW your RkC and RkD are invalid because they don´t contain DPC field)
> >
> >
> >
> > 4. ASP-SGP Routing should use SS7 Destination Availability/Restricted
> > Status on a per-SGP rather than a per-SG basis.
> >
> > I believe your ASP-SGP procedures should be amended (I only amend the
> > multiple SG case as the single SG case is a special case of
> > the former)
> > as follows:
> >
> > Change:
> > "This routing information is updated by collecting DUNA/DAVA/DRST
> > messages received from (any of the SGP in) the SG."
> > To:
> > "This routing information is updated by collecting DUNA/DAVA/DRST
> > information on a per-(SGP,destination) basis. An SG is
> > considered to be
> > available and unrestricted for a particular destination if
> > any SGP in it
> > is available and unrestricted for that destination. Otherwise
> > if this is
> > not he case, then an SG is considered to be restricted for a
> > particular
> > destination if there is at least one SGP in the SG restricted for that
> > destination. Otherwise if this is not the case, the SG is
> > considered to
> > be prohibited for that destination."
> >
> > The RFC is not particular clear on this point. In section 1.4.1 para 3
> > it states that "MTP3 routeset, SPMC and remote AS/ASP states
> > of each SGP
> > SHOULD be coordinated across all the SGPs". However, this
> > uses "SHOULD"
> > which implies it is only recommended and it also doesn't specifically
> > state that SS7 destination availability, restriction and congestion
> > status ("SS7 destination status" for short) should be
> > coordinated across
> > all SGPs. I don't think that "MTP3 routeset" necessarily implies SS7
> > destination status. Also, in section 1.3.2.5 1.4.2.5 it suggests in
> > should be on a per-SGP basis. Section 4.5.2.2 uses the word "SG" but
> > also uses the term "affected route(s)". Section 1.3.2.5 and section
> > 1.4.2.5 suggest the word "route" refers to an SGP and not an
> > SG. Hence,
> > given the ambiguity of section 4.5.2.2 I think that route can be
> > considered to refer to an SGP.
> >
> > A configuration where per-SGP SS7 destination status is
> > necessary is as
> > follows. Consider an SEP SG which has two SGP's acting as a redundant
> > pair. Each SGP has it's own link set to a particular STP. While in
> > section 1.4.1 para 3 it states that "Rerouting of traffic between the
> > SGPs MAY also be supported", it uses "MAY" and hence this is optional.
> > If one link set fails but not the other, one SGP will be able to reach
> > the SS7 network but not the other if rerouting between SGPs is not
> > supported or the rerouting link has also failed. Hence, it would be
> > possible for one SGP to send a DUNA for a particular
> > destination but not
> > the other.
> [TOLGA] Again I don´t see a problem. I only agree that "MAY" in the
> sentence you refer was better changed to a "SHOULD". If somebody thinks
> that creating a unique layer3 view among SGPs belonging to the same SG is
> hard to implement/not necessary, then it is possible to have SGs consisting
> of one SGP, without violating the protocol. In that case, SSNM will be
> received separetly from each SGP, because they belong to different SGs.
> >
> >
> > Your feedback would be appreciated.
> >
> > Jolan.
> >
> >
> > --
> > Jolan Evans
> > Open Telecommunications
> > jolan.evans@opentelecommunications.com
> >
> >
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org] On Behalf
> > Of Brian F. G. Bidulock
> > Sent: Tuesday, 8 October 2002 17:47
> > To: Srikanth Yandapalli
> > Cc: sigtran@ietf.org
> > Subject: Re: [Sigtran] ASP to SGP communication
> >
> > Srikanth,
> >
> > Srikanth Yandapalli wrote:               (Tue, 08 Oct 2002 12:03:52)
> > >
> > >    I am late entrant to this group.I am quite sure all this should
> > have
> > >    been discussed and I am sorry about this.
> >
> > Welcome.
> >
> > >
> > >    In the context of a single ASP in communication with
> > multiple SGPs,
> > >    how should the routing of a MTP_DATA_REQ take place at the ASP?
> >
> > I assume you are talking about M3UA?  As we are dealing with 5 or more
> > UAs
> > now, in the future it would be helpful to add M3UA (or
> > whichever) to the
> > subject line.
> >
> > >
> > >    approach 1:
> > >
> > >    We may find out the  RK and find out the SGP list that the RK is
> > >    active on and choose one SGP for sending the message based
> > >    on congestion level and also whether we have received any DRST
> > >    message from any of the SGPs.
> >
> > This approach is applicable to multiple SGs, but not to multiple SGPs
> > within a
> > single SG.
> >
> > >    approach 2:
> > >
> > >    An SGP can also be viewed as providing route to a set of DPCs
> > >    and the routing can be based on the DPC for the message alone.
> > >    This approach is reduces the complexity but adds a situation
> > >    where the RK may not be active on that association. And also is
> > >    is mandatory to send RC on this association and if so what could
> > >    the SGP make out of the RC?
> >
> > RC should be coordinated and the same across multiple SGPs
> > within an SG.
> >
> > >
> > >    Is there a preferred approach to this issue?
> > >
> >
> > Typically, the logic can be something like this: (but there
> > are several
> > other
> > schools of thought):
> >
> > Single SG case: (multiple SGs is more complicated)
> >
> >   MTP-TRANSFER request is issued by an MTP-User.  The
> > MTP-User is bound
> > to an
> >   MTP-SAP.  The MTP-SAP is associated with an AS/RC/RK.
> > There is a pool
> > of
> >   SGPs on an SG for which the AS/RC/RK is active.  The AS may have
> > received
> >   MTP-PAUSE/RESUME/STATUS indications from the SG and may choose to
> > honor that
> >   information or not.  If the ASP chooses not to honor this
> > information
> > it can
> >   blindly send messages to the SGP and rely upon a DUNA/SCON response
> > from the
> >   SGP later.
> >
> >   Selection of an SGP within an SG is based on the traffic
> > mode for the
> > SGP.
> >   This traffic mode is not managed by M3UA, however, M3UA provides for
> >   distribution of traffic over SGP based on any of the
> > methods described
> > for
> >   ASPs (active/standby, load-share, broadcast).  A typical method is
> >   load-share based on SLS.  In this scheme, using the SLS in the
> > MTP-TRANSFER
> >   request, the ASP selects load-shares traffic over the available SGP.
> >
> > Multiple SG case:
> >
> >   In the more complicated multiple SG case, the ASP must
> > first select an
> > SG
> >   before it selects an SGP within the SG.  The ASP must maintain some
> >   additional routing information to be able to properly select an SG.
> > This
> >   routing information is updated by collecting DUNA/DAVA/DRST messages
> >   received from (any of the SGP in) the SG.  To select the
> > outgoing SG,
> > the
> >   ASP must examine the destination of the MTP-TRANSFER request.
> >
> >   (If the SG has no SGP active for the AS/RC/RK, all
> > destinations can be
> >   considered prohibited).
> >
> >   If the destination is available and unrestricted for
> > several SGs, the
> > ASP
> >   should select an SG on a load-sharing basis (based on SLS) and then
> > select
> >   an active SGP within the SG on the basis of the traffic mode for the
> > SG.
> >
> >   If some SG are restricted for the specified destination (based on
> > received
> >   DRST messages from the SG), the ASP should load-share across the
> > available
> >   unrestricted SGs.  If all SGs are restricted for a given
> > destination,
> > the
> >   ASP should load-share across the available SGs and ignore the
> > restricted
> >   status.
> >
> >   If some SG are prohibited for the specified destination (based on
> > received
> >   DUNA messages from the SG), the ASP should load-share across the
> > available
> >   non-prohibited SGs.  If all SGs are prohibited for a given
> > destination
> > (or
> >   no SGP is active for the AS/RC/RK in any SG), the ASP should respond
> > to the
> >   MTP-User with an MTP-PAUSE in accordance with the style of the
> > MTP-User
> >   interface (ITU-T and ANSI differ here).
> >
> > Properly selecting SGs requires that the ASP maintain the
> > DUNA/DAVA/DRST
> > information for each destination received from any SGP in an SG, on a
> > per-SG
> > basis.  This is the same as MTP Level 3 ROUTE status.  However, SCON
> > information should only be maintained on a per-destination basis (and
> > not
> > per-SG).  This is the same as MTP Level 3 ROUTESET status.
> >
> > Note that, in general, it is a bad idea to consider congestion (SCON)
> > when
> > selecting an SG.  SCON does not necessarily indicate
> > congestion at an SG
> > or on
> > a path to an SG, but indicates congestion at the affected
> > destination or
> > somewhere (perhaps distant) in the SS7 network.  SCON is
> > ROUTESET-specific
> > (applies to the destination), whereas DUNA/DAVA/DRST is ROUTE-specific
> > (applies to the destination and path).  SCON should only be used to
> > determine
> > whether a message should be dropped completely and an MTP-STATUS
> > returned to
> > the MTP-User according to the style of the MTP-User interface
> > (ITU-T and
> > ANSI
> > differ here again).
> >
> > So, to summarize:  on behalf of the AS/RC/RK/MTP-User, the ASP
> > determines
> > whether to send a message based on SCON received for the specified
> > destination, then selects an SG based on DUNA/DAVA/DRST
> > received for the
> > specified destination and load-shares based on SLS across the eligible
> > SGs.
> > Once an SG is selected, an active SGP (active for the AS/RC/RK) is
> > selected
> > within the SG based on the traffic mode of the SG (active/standby,
> > load-share,
> > broadcast: but typically load-share on SLS).
> >
> > As I said, there are other schools of thought, but that is my
> > understanding.
> >
> > --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
> > Jolan,
>
> > -----Original Message-----
> > From: "Jolan Evans" <jolan.evans@opentelecommunications.com>
> > Sent: Tuesday, January 28, 2003 10:17 AM
> > To: "Sigtran" <sigtran@ietf.org>
> > Cc: <bidulock@openss7.org>
> > Subject: RE: [Sigtran] M3UA: ASP to SGP communication (Sent by
> > sigtran-admin@ietf.org on behalf of "Jolan Evans"
> > <jolan.evans@opentelecommunications.com> )
> >
> >
> > I would like to raise a few issues regarding your procedures below for
> > ASP to SGP routing. I know this discussion took places a
> > while ago, but
> > it has taken me some time to come up to speed with the RFC as I have
> > been busy on other things until recently.
> >
> > Please note that I have inserted "M3UA" into the subject line of the
> > original email.
> >
> >
> >
> > 1. Nomenclature
> > AsPc: Point code of an AS. In defining routing keys, the RFC uses DPC
> > for this term as it takes the SG's frame of reference.
> > RemotePc: Point code of an SS7 MTP entity with which an AS
> > communicates
> > via an SG, or directly in the case of IPSP-IPSP communication. In
> > defining routing keys, the RFC uses OPC for this term as it takes the
> > SG's frame of reference again.
> >
> >
> >
> > 2. Background Assumptions
> > As per Brian's introduction, we assume that zero or more
> > MTP-User's are
> > bound to an MTP-SAP. The MTP-SAP exists in a particular MTP-Network,
> > which has a particular MTP protocol variant. An SG is
> > associated with a
> > single MTP-Network. A RK is defined as in the RFC, but, for
> > clarity, is
> > independent of any SG and associated with a single MTP-Network. An
> > SgRouteSet is uniquely defined by an RK, an SG and an MTP-SAP (the RK
> > and SG must be both associated with the same MTP-Network) and also
> > specifies the network appearance for the MTP-Network to be
> > used with the
> > SG and the RC of each SGP in the SG. Therefore, an SgRouteSet is
> > implicitly associated with a single MTP-Network. An MTP-SAP is
> > associated with zero or more SgRouteSet's and therefore an MTP-SAP is
> > associated with zero or more RKs. In contrast, it appears that Brian
> > assumes that an MTP-SAP can only be associated with one RK. Given this
> > extension, we have the following requirement.
> >
> >
> >
> > 3. Routing Keys Requirements to Support Unique SS7 Destination Status
> > Let RemotePcSet(Rk) be the set of RemotePc's reachable via the SG from
> > the ASP where the RK is defined.
> > Consider any two SgRouteSet's SgRsA and SgRsA which are
> > associated with
> > the same MTP-SAP.
> > Let the routing key of SgRsA and SgRsB be RkA and RkB respectively.
> > If the intersection of RemotePcSet(RkA) and RemotePcSet(RkB)
> > is non-nil
> > then the routing keys MUST be identical in every respect apart from
> > their RemotePcSet.
> > If this wasn't the case, an ASP could never indicate an
> > MTP-RESUME to an
> > MTP-USER because an MTP-RESUME can only specify a RemotePc
> > and no other
> > SS7 element. I assume here for simplicity that every MTP-User of a
> > MTP-SAP must be given the same MTP status (i.e. different MTP-Users of
> > the same MTP-SAP cannot be given different MTP-Status indications
> > depending on what traffic they have requested).
> >
> > Here's a concrete example of why this is so. Consider an ASP with the
> > following routing keys:
> > RkA: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={A}
> > RkB: MTP-Network=NetworkA, RemotePcSet={X}, AsPcSet={B}
> > RkC: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={M}
> > RkD: MTP-Network=NetworkA, RemotePcSet={Y}, SiSet={N}
> >
> > Assume that RkA and RkB were both active in SgpA and SgpB respectively
> > and are associated with the same MTP-SAP, but different SGs.
> > Also assume
> > that a DAVA has been received for RemotePc=X from SgpA after
> > a DUNA from
> > SgpB for the same RemotePc. We might consider generating an MTP-Resume
> > to all the MTP-Users of the MTP-SAP for RemotePc X. However, if an
> > MTP-User requests an MTP-Transfer with an AsPc of B then SgpB
> > may not be
> > able to transfer it as indicated by the DUNA it sent the ASP.
> >
> > The same explanation applies to RkC and RkD.
> >
> > In practice this requirement probably won't cause too many headaches
> > because it is likely that there would be two different MTP-Users, one
> > using only RkA/RkC and the other using only RkB/RkD. In this case, we
> > can simply create two MTP-SAPs in the same MTP-Network and associate
> > each routing key with a different MTP-SAP. Of course, this
> > would require
> > the M3UA implementation to support more than one MTP-SAP per
> > MTP-Network, which would be extra work obviously.
> [TOLGA] IMO there is no problem. It might be extra work but people are free
> to support such a configuration or not. In your example, most probably
> there should be two different user part entities processing messages for
> RkA and RkB respectively. Each of them will receive only primitives related
> with them, i.e. primitives which are caused by messages arrived for the
> corresponding RK.
> (BTW your RkC and RkD are invalid because they don´t contain DPC field)
> >
> >
> >
> > 4. ASP-SGP Routing should use SS7 Destination Availability/Restricted
> > Status on a per-SGP rather than a per-SG basis.
> >
> > I believe your ASP-SGP procedures should be amended (I only amend the
> > multiple SG case as the single SG case is a special case of
> > the former)
> > as follows:
> >
> > Change:
> > "This routing information is updated by collecting DUNA/DAVA/DRST
> > messages received from (any of the SGP in) the SG."
> > To:
> > "This routing information is updated by collecting DUNA/DAVA/DRST
> > information on a per-(SGP,destination) basis. An SG is
> > considered to be
> > available and unrestricted for a particular destination if
> > any SGP in it
> > is available and unrestricted for that destination. Otherwise
> > if this is
> > not he case, then an SG is considered to be restricted for a
> > particular
> > destination if there is at least one SGP in the SG restricted for that
> > destination. Otherwise if this is not the case, the SG is
> > considered to
> > be prohibited for that destination."
> >
> > The RFC is not particular clear on this point. In section 1.4.1 para 3
> > it states that "MTP3 routeset, SPMC and remote AS/ASP states
> > of each SGP
> > SHOULD be coordinated across all the SGPs". However, this
> > uses "SHOULD"
> > which implies it is only recommended and it also doesn't specifically
> > state that SS7 destination availability, restriction and congestion
> > status ("SS7 destination status" for short) should be
> > coordinated across
> > all SGPs. I don't think that "MTP3 routeset" necessarily implies SS7
> > destination status. Also, in section 1.3.2.5 1.4.2.5 it suggests in
> > should be on a per-SGP basis. Section 4.5.2.2 uses the word "SG" but
> > also uses the term "affected route(s)". Section 1.3.2.5 and section
> > 1.4.2.5 suggest the word "route" refers to an SGP and not an
> > SG. Hence,
> > given the ambiguity of section 4.5.2.2 I think that route can be
> > considered to refer to an SGP.
> >
> > A configuration where per-SGP SS7 destination status is
> > necessary is as
> > follows. Consider an SEP SG which has two SGP's acting as a redundant
> > pair. Each SGP has it's own link set to a particular STP. While in
> > section 1.4.1 para 3 it states that "Rerouting of traffic between the
> > SGPs MAY also be supported", it uses "MAY" and hence this is optional.
> > If one link set fails but not the other, one SGP will be able to reach
> > the SS7 network but not the other if rerouting between SGPs is not
> > supported or the rerouting link has also failed. Hence, it would be
> > possible for one SGP to send a DUNA for a particular
> > destination but not
> > the other.
> [TOLGA] Personally again I don´t see a problem. I only agree that "MAY" in
> the sentence you refer was better changed to a "SHOULD". If somebody thinks
> that creating a unique layer3 view among SGPs belonging to the same SG is
> hard to implement/not necessary, then it is possible to have SGs consisting
> of one SGP, without violating the protocol. In that case, SSNM will be
> received separetly from each SGP, because they belong to different SGs.
> >
> >
> > Your feedback would be appreciated.
> >
> > Jolan.
> >
> >
> > --
> > Jolan Evans
> > Open Telecommunications
> > jolan.evans@opentelecommunications.com
> >
> >
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org] On Behalf
> > Of Brian F. G. Bidulock
> > Sent: Tuesday, 8 October 2002 17:47
> > To: Srikanth Yandapalli
> > Cc: sigtran@ietf.org
> > Subject: Re: [Sigtran] ASP to SGP communication
> >
> > Srikanth,
> >
> > Srikanth Yandapalli wrote:               (Tue, 08 Oct 2002 12:03:52)
> > >
> > >    I am late entrant to this group.I am quite sure all this should
> > have
> > >    been discussed and I am sorry about this.
> >
> > Welcome.
> >
> > >
> > >    In the context of a single ASP in communication with
> > multiple SGPs,
> > >    how should the routing of a MTP_DATA_REQ take place at the ASP?
> >
> > I assume you are talking about M3UA?  As we are dealing with 5 or more
> > UAs
> > now, in the future it would be helpful to add M3UA (or
> > whichever) to the
> > subject line.
> >
> > >
> > >    approach 1:
> > >
> > >    We may find out the  RK and find out the SGP list that the RK is
> > >    active on and choose one SGP for sending the message based
> > >    on congestion level and also whether we have received any DRST
> > >    message from any of the SGPs.
> >
> > This approach is applicable to multiple SGs, but not to multiple SGPs
> > within a
> > single SG.
> >
> > >    approach 2:
> > >
> > >    An SGP can also be viewed as providing route to a set of DPCs
> > >    and the routing can be based on the DPC for the message alone.
> > >    This approach is reduces the complexity but adds a situation
> > >    where the RK may not be active on that association. And also is
> > >    is mandatory to send RC on this association and if so what could
> > >    the SGP make out of the RC?
> >
> > RC should be coordinated and the same across multiple SGPs
> > within an SG.
> >
> > >
> > >    Is there a preferred approach to this issue?
> > >
> >
> > Typically, the logic can be something like this: (but there
> > are several
> > other
> > schools of thought):
> >
> > Single SG case: (multiple SGs is more complicated)
> >
> >   MTP-TRANSFER request is issued by an MTP-User.  The
> > MTP-User is bound
> > to an
> >   MTP-SAP.  The MTP-SAP is associated with an AS/RC/RK.
> > There is a pool
> > of
> >   SGPs on an SG for which the AS/RC/RK is active.  The AS may have
> > received
> >   MTP-PAUSE/RESUME/STATUS indications from the SG and may choose to
> > honor that
> >   information or not.  If the ASP chooses not to honor this
> > information
> > it can
> >   blindly send messages to the SGP and rely upon a DUNA/SCON response
> > from the
> >   SGP later.
> >
> >   Selection of an SGP within an SG is based on the traffic
> > mode for the
> > SGP.
> >   This traffic mode is not managed by M3UA, however, M3UA provides for
> >   distribution of traffic over SGP based on any of the
> > methods described
> > for
> >   ASPs (active/standby, load-share, broadcast).  A typical method is
> >   load-share based on SLS.  In this scheme, using the SLS in the
> > MTP-TRANSFER
> >   request, the ASP selects load-shares traffic over the available SGP.
> >
> > Multiple SG case:
> >
> >   In the more complicated multiple SG case, the ASP must
> > first select an
> > SG
> >   before it selects an SGP within the SG.  The ASP must maintain some
> >   additional routing information to be able to properly select an SG.
> > This
> >   routing information is updated by collecting DUNA/DAVA/DRST messages
> >   received from (any of the SGP in) the SG.  To select the
> > outgoing SG,
> > the
> >   ASP must examine the destination of the MTP-TRANSFER request.
> >
> >   (If the SG has no SGP active for the AS/RC/RK, all
> > destinations can be
> >   considered prohibited).
> >
> >   If the destination is available and unrestricted for
> > several SGs, the
> > ASP
> >   should select an SG on a load-sharing basis (based on SLS) and then
> > select
> >   an active SGP within the SG on the basis of the traffic mode for the
> > SG.
> >
> >   If some SG are restricted for the specified destination (based on
> > received
> >   DRST messages from the SG), the ASP should load-share across the
> > available
> >   unrestricted SGs.  If all SGs are restricted for a given
> > destination,
> > the
> >   ASP should load-share across the available SGs and ignore the
> > restricted
> >   status.
> >
> >   If some SG are prohibited for the specified destination (based on
> > received
> >   DUNA messages from the SG), the ASP should load-share across the
> > available
> >   non-prohibited SGs.  If all SGs are prohibited for a given
> > destination
> > (or
> >   no SGP is active for the AS/RC/RK in any SG), the ASP should respond
> > to the
> >   MTP-User with an MTP-PAUSE in accordance with the style of the
> > MTP-User
> >   interface (ITU-T and ANSI differ here).
> >
> > Properly selecting SGs requires that the ASP maintain the
> > DUNA/DAVA/DRST
> > information for each destination received from any SGP in an SG, on a
> > per-SG
> > basis.  This is the same as MTP Level 3 ROUTE status.  However, SCON
> > information should only be maintained on a per-destination basis (and
> > not
> > per-SG).  This is the same as MTP Level 3 ROUTESET status.
> >
> > Note that, in general, it is a bad idea to consider congestion (SCON)
> > when
> > selecting an SG.  SCON does not necessarily indicate
> > congestion at an SG
> > or on
> > a path to an SG, but indicates congestion at the affected
> > destination or
> > somewhere (perhaps distant) in the SS7 network.  SCON is
> > ROUTESET-specific
> > (applies to the destination), whereas DUNA/DAVA/DRST is ROUTE-specific
> > (applies to the destination and path).  SCON should only be used to
> > determine
> > whether a message should be dropped completely and an MTP-STATUS
> > returned to
> > the MTP-User according to the style of the MTP-User interface
> > (ITU-T and
> > ANSI
> > differ here again).
> >
> > So, to summarize:  on behalf of the AS/RC/RK/MTP-User, the ASP
> > determines
> > whether to send a message based on SCON received for the specified
> > destination, then selects an SG based on DUNA/DAVA/DRST
> > received for the
> > specified destination and load-shares based on SLS across the eligible
> > SGs.
> > Once an SG is selected, an active SGP (active for the AS/RC/RK) is
> > selected
> > within the SG based on the traffic mode of the SG (active/standby,
> > load-share,
> > broadcast: but typically load-share on SLS).
> >
> > As I said, there are other schools of thought, but that is my
> > understanding.
> >
> > --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
> >
>
> _______________________________________________
> 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 Jan 30 17:33:25 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 RAA12275
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 17:33:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0UMacl02135
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 17:36:38 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UMZaJ02068;
	Thu, 30 Jan 2003 17:35:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0TEqvJ30358
	for <sigtran@optimus.ietf.org>; Wed, 29 Jan 2003 09:52:57 -0500
Received: from rtp-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20298
	for <sigtran@ietf.org>; Wed, 29 Jan 2003 09:30:51 -0500 (EST)
Received: from cia.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h0TEZ6uF007839;
	Wed, 29 Jan 2003 09:35:06 -0500 (EST)
Received: from kmorneau-w2k.cisco.com (rtp-vpn1-673.cisco.com [10.82.226.161])
	by cia.cisco.com (Mirapoint)
	with ESMTP id ABN89210;
	Wed, 29 Jan 2003 09:24:09 -0500 (EST)
Message-Id: <4.3.2.7.2.20030129093253.045d5520@cia.cisco.com>
X-Sender: kmorneau@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 29 Jan 2003 09:34:07 -0500
To: "TOLGA ASVEREN" <tolga.asveren@o2.com.tr>, sigtran@ietf.org
From: Ken Morneault <kmorneau@cisco.com>
Subject: Re: [Sigtran] M3UA SG-SG (again)
In-Reply-To: <OF17E746B2.9F2178CF-ONC2256CBC.0035AD63@LocalDomain>
Mime-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=====================_132767539==_"
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>

--=====================_132767539==_
Content-Type: text/plain; charset="us-ascii"



Tolga,

I agree that the SG-SG draft is worthwhile and should move forward.  I
have attached an edited version with more questions than comments.

Regards,

Ken

At 11:46 AM 1/28/2003 +0200, TOLGA ASVEREN wrote:
>Hi everybody,
>
>Recently I submitted 02 for SG-SG.
>http://www.ietf.org/internet-drafts/draft-bidas-sigtran-sgsg-02.txt
>
>It was updated based on some off-list comments and additional sections are
>added to clarify some procedures, nothing conceptually new though. Still
>some more sections can be added but first I prefer to get some feedback.
>
>I still think that it should be a WG item, as it addresses some existing
>problems. I would appreciate any feedback.
>
>     Regards,
>      TolgaHi everybody,
>
>Recently I submitted 02 for SG-SG.
>http://www.ietf.org/internet-drafts/draft-bidas-sigtran-sgsg-02.txt
>
>It was updated based on some off-list comments and additional sections are
>added to clarify some procedures, nothing conceptually new though. Still
>some more sections can be added but first I prefer to get some feedback.
>
>I still think that it should be a WG item, as it addresses some existing
>problems. I would appreciate any feedback.
>
>     Regards,
>      Tolga
>
>_______________________________________________
>Sigtran mailing list
>Sigtran@ietf.org
>https://www1.ietf.org/mailman/listinfo/sigtran 

--=====================_132767539==_
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: attachment; filename="draft-bidas-sigtran-sgsg-02-edit.txt"
Content-Transfer-Encoding: quoted-printable


                  Network Working Group                               Tolga=
 Asveren=20
                  INTERNET DRAFT                                   Oksijen=
 Teknoloji=20
                                                                      Brian=
 Bidulock=20
                                                                 OpenSS7=
 Corporation=20
                  =20
                  =20
                  Expires: July 27, 2003                             =
 January 27, 2003=20
                  =20
                  =20
                  =20
                  =20
                  =20
                  =20
                  =20
                  =20
                  =20
                                         M3UA SG-SG communication=20
                                    <draft-bidas-sigtran-sgsg-02.txt>=20
                                                     =20
                                                     =20
                                                     =20
                                                     =20
                  Status of this Memo=20
                  =20
                  This document is an Internet-Draft and is in full=
 conformance with=20
                  all provisions of Section 10 of RFC 2026. Internet-Drafts=
 are=20
                  working documents of the Internet Engineering Task Force=
 (IETF), its=20
                  areas, and its working groups.  Note that other groups may=
 also=20
                  distribute working documents as Internet-Drafts.=20
                  =20
                  Internet-Drafts are draft documents valid for a maximum of=
 six=20
                  months and may be updated, replaced, or obsoleted by other=
 documents=20
                  at any time.  It is inappropriate to use Internet-Drafts=
 as=20
                  reference material or to cite them other than as 'work in=
 progress.'=20
                  =20
                       The list of current Internet-Drafts can be accessed=
 at=20
                       http://www.ietf.org/1id-abstracts.html=20
                  =20
                       The list of Internet-Draft Shadow Directories can be=
 accesse at=20
                       http://www.ietf.org/shadow.html=20
                  =20
                  To learn the current status of any Internet-Draft, please=
 check the =20
                  '1id-abstracts.txt' listing contained in the Internet-=
 Drafts Shadow =20
                  Directories on ftp.is.co.za (Africa), nic.nordu.net=
 (Europe), =20
                  munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast),=
 or =20
                  ftp.isi.edu (US West Coast).=20
                  =20
                  =20
                  =20
                  =20
                  =20
                  =20
                  Abstract=20
                  =20
                  Asveren/Bidulock                                          =
         1=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                  =20
                  This Internet-Draft describes a protocol to support=
 communication of=20
                  M3UA[1] based SGs over IP. The additional functionality=
 needed by=20
                  SGs to act as relay points between SS7 nodes is also=
 addressed.=20
                  =20
                  =20
                                            TABLE OF CONTENTS=20
                                                     =20
                  1. Introduction. . . . . . . . . . . . . . . . . . . . . .=
 . 2=20
                      1.1 Scope. . . . . . . . . . . . . . . . . . . . . . .=
 . 2=20
                      1.2 Terminology. . . . . . . . . . . . . . . . . . . .=
 . 3=20
                      1.3 Conventions. . . . . . . . . . . . . . . . . . . .=
 . 3=20
                      1.4 Overview . . . . . . . . . . . . . . . . . . . . .=
 . 3=20
                      1.5 Architecture . . . . . . . . . . . . . . . . . . .=
 . 5=20
                      1.6 Possible Uses of SG-SG Communication . . . . . . .=
 . 4=20
                  2. Functional Areas. . . . . . . . . . . . . . . . . . . .=
 . 7=20
                      2.1 Signalling Point Code Representation . . . . . . .=
 . 7=20
                      2.2 Routing Context and Routing Keys . . . . . . . . .=
 . 7=20
                      2.3 Network Appearance . . . . . . . . . . . . . . . .=
 . 7=20
                      2.4 SCTP Association Establishment . . . . . . . . . .=
 . 8=20
                      2.5 Point Code Status Information Exchange . . . . . .=
 . 8=20
                      2.6 Message Distribution . . . . . . . . . . . . . . .=
 . 8=20
                      2.7 Congestion Handling. . . . . . . . . . . . . . . .=
 . 9=20
                      2.8 Restricted Destinations. . . . . . . . . . . . . .=
 . 9=20
                  3. Message Types and Parameters. . . . . . . . . . . . . .=
 . 9=20
                  4. Protocol Messages . . . . . . . . . . . . . . . . . . .=
 . 9=20
                      4.1 Destination User Part Unavailable Message. . . . .=
 . 10=20
                      4.2 Signalling Congestion. . . . . . . . . . . . . . .=
 . 10=20
                      4.3 Congestion Test Message. . . . . . . . . . . . . .=
 . 11=20
                      4.4 Changeover Mechanism Related Messages. . . . . . .=
 . 12=20
                           4.4.1 Changeover Request Message. . . . . . . . .=
 . 13=20
                           4.4.2 Changeover Request Acknowledgement Message.=
 . 14=20
                  5. SG and SGP State Machines . . . . . . . . . . . . . . .=
 . 15=20
                      5.1 SGP State Machine. . . . . . . . . . . . . . . . .=
 . 15=20
                      5.2 SG State Machine . . . . . . . . . . . . . . . . .=
 . 16=20
                  6. Examples. . . . . . . . . . . . . . . . . . . . . . . .=
 . 17=20
                      6.1 M3UA Availability Declaration. . . . . . . . . . .=
 . 17=20
                      6.2 PC Status Announcement . . . . . . . . . . . . . .=
 . 17=20
                  7. Security. . . . . . . . . . . . . . . . . . . . . . . .=
 . 18=20
                  8. Acknowledgements. . . . . . . . . . . . . . . . . . . .=
 . 18=20
                  9. References. . . . . . . . . . . . . . . . . . . . . . .=
 . 18=20
                      9.1 Normative References . . . . . . . . . . . . . . .=
 . 18=20
                      9.2 Informative References . . . . . . . . . . . . . .=
 . 19=20
                  10. Author's Addresses . . . . . . . . . . . . . . . . . .=
 . 19=20
                  =20
                  =20
                  =20
                  1. Introduction=20
                  =20
                  1.1. Scope=20
                  =20
                  M3UA does not have relaying capability between PCs. This=
 might be=20

[KAM] spell out PC, define what you mean by "relaying" (you cover it in=
 paragraph
2 below, but you never say this is what you mean by "relaying".  also at=
 some point in the
draft, you need to be clear about the details of M3UA deficiencies in the=
 area
of "relaying". =20

                  necessary to build hybrid networks, where some part of the=
 signaling=20
                                                                            =
        2=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                  transport is TDM based and some part of it IP based.=
 Relaying might=20
                  be also desirable for redundancy purposes and to have a=
 hierarchy in=20
                  the network based on SS7 constructs. M2PA[2] provides a=
 way to=20
                  achieve relaying but it includes MTP2[3] procedures on top=
 of=20
                  SCTP[4] and emulates SS7 links in IP domain. An=
 alternative approach=20
                  is defined in this document: relaying with a layer3=
 peer-to-peer=20
                  model, without the burden of layer2 procedures and within=
 the M3UA=20
                  procedure with some additional messages and procedures.=20
                  =20
                  For ASP/SGP relationship as defined in M3UA, SPMC logic=
 and user=20
                  parts for a PC reside on different nodes, and=
 communication between=20
                  them is defined mainly based on MTP3/MTP3[5] User=
 relationship. This=20
                  brings some difficulties for modelling and implementation,=
 when SG=20
                  acts  as  STP(non-backhaul  scenarios),  i.e.  when  PC =
 boundary  is=20
                  crossed  between  SG  and  ASP.  SG-SG  communication  is =
 based  on=20
                  MTP3/MTP3 communication and supports such scenarios in a=
 similar way=20
                  as MTP3 does in conventional SS7 network.=20
                  =20
                  SG-SG communication as defined in this document does also=
 provide a=20
                  method for direct communication between M3UA nodes in IP=
 domain,=20
                  where again user part and layer3 logic are provided by the=
 same=20
                  entity.=20
                  =20
                  In general, when PC boundaries are crossed, providing=
 layer3 logic=20
                  on the same side of the relationship with user parts also=
 provides=20
                  an easy way to make a MTP3 stack to support M3UA SG-SG=
 mode of=20
                  communication,  where  some  of  the  routes  are  using =
 IP  based=20
                  communication instead of SS7 links. =20
                  =20
                   =20
                  1.2. Terminology=20
                  =20
                  SG-SG communication draft uses the terminology used in the=
 M3UA=20
                  RFC[3332] with the following additions:=20
                  =20
                  COA    Changeover Acknowledgement MTP3 message=20
                  COO    Changeover Order MTP3 message=20
                  ECA    Emergency changeover acknowledgement MTP3 message=
=20
                  ECM    Emergency changeover MTP3=20message=20
                  IP-SP  IP Signalling Point=20

[KAM] does this have same definition as IPSP in M3UA?

                  RCT    Signalling route set congestion test MTP3 message=
=20
                  TFC    Transferred controlled MTP3 message=20
                  =20

                  1.3. Conventions=20
                  =20
                  The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT,=
 SHOULD,=20
                  SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and=
 OPTIONAL, when=20
                  they appear in this document, are to be interpreted as=
 described in=20
                  [6].=20

[KAM] [6] above should be [7]
               =20
                  =20
                  1.4. Overview=20
                  =20
                                                                            =
        3=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                  The purpose of SG-SG protocol is to increase IP domain=
 communication=20
                  capabilities of M3UA peers and to allow SS7 signalling=
 backhauling=20
                  between SS7 nodes over IP with M3UA protocol.=20
                  =20
                  =20
                       -----              -----=20
                     //     \\          //     \\=20
                    |  SPMC   |        |  SPMC   |=20
                    |  Cloud 1|        |  Cloud 2|=20
                     \\     //          \\     //=20
                       --+--              --+--=20
                         |                  |=20
                         |                  |=20
                      +--+--+            +--+--+=20
                      | SG1 +------------+ SG2 |=20
                      +--+--+            +--+--+=20
                         |                  |=20
                         |                  |=20
                         |                  |=20
                         |     +-----+      |=20
                         +-----+ SG3 +------+=20
                               +--+--+=20
                                  |=20
                                  |=20
                                --+--=20
                              //     \\=20
                             |  SPMC   |=20
                             |  Cloud 3=20
                              \\     //=20
                                -----=20
                  =20
                  Figure 1. Intra-IP communication using SG-SG communication=
=20
                  =20
                  In the configuration in Figure 1 SGs act as transfer=
 points between=20
                  SPMC clouds. Their functionality is similar to the STP=
 functionality=20
                  in SS7 network. The communication between ASPs and SGs is=
 as defined=20
                  in M3UA protocol. It should be noted that a SG can also=
 support a=20
                  local SPMC, i.e. it MAY have user parts running on it,=
 instead of on=20
                  an ASP.=20
                  =20
                  =20
                   +---------+              +---------+=20
                   |   SG1   +--------------+   SG2   |=20
                   +----+----+              +----+----+=20
                        |                        |=20
                        |                        |=20
                   +----+----+              +----+----+=20
                   |SS7 node1|              |SS7 node2|=20
                   +---------+              +---------+=20
                  =20
                  Figure 2. SS7 signalling backhauling using SG-SG=
 communication=20
                  =20

                                                                            =
        4=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                  In the configuration in Figure 2 SGs act as relay points=
 for SS7=20
                  nodes.=20
                  =20
                  =20
                  1.5 Architecture=20
                  =20
                  The goal of SG-SG communication is to define a=
 peer-to-peer=20
                  relationship between two M3UA IP domain entities, which=
 can be used=20
                  both for direct communication and for relaying. For that=
 reason SG-
                  SG communication model tries to mimic the relationship of=
 two=20
                  signaling points in traditional SS7 network. This allows=
 inheritance=20
                  of necessary MTP3[2] procedures without any modelling=
 problems, to=20
                  modify a MTP3 stack easily to make it work also as a M3UA=
 SG and a=20
                  smooth migration from TDM based communication to IP based=
=20
                  communication for SS7 networks.=20
                  =20
                  In fact, in the context of SG-SG communication, SGs can be=
 thought=20
                  as IP Signalling Points(IP-SP). All of the SPMC(layer3)=
 logic=20
                  resides in the local node, which provides a well defined=
 peer-to-
                  peer model, without relying to a remote SPMC control=
 entity for=20
                  local procedures. It should be noted that user parts for a=
 specific=20
                  SPMC MAY reside on the same node with SG itself, or MAY be=
=20
                  distributed across remote nodes, where relationship=
 between those=20
                  nodes and the controlling SG MAY be implementation=
 dependent or MAY=20
                  be based on the ASP/SGP relationship as defined in M3UA.=
 SGs MAY=20
                  also not control any SPMC directly and act only as relay=
 points.=20
                  =20
                  SG-SG communication management is based mainly on SSNM as=
 defined in=20
                  M3UA protocol, with some additional messages to handle=
 changeover=20
                  and congestion as defined in MTP3.=20
                  =20
                  Communication of peers is in PC granularity.=20
                  =20
                  Each SG MAY consist of multiple SGPs. It should be noted,=
 that all=20
                  layer3 logic(both for SPMCs directly controlled and for=
 remote PCs)=20
                  functions as a single entity in the whole SG.=20
                  =20
                                 SG=20
                   ************************************=20
                   * +------------------------------+ *=20
                   * |      Layer3 Logic            | *=20
                   * +----+---+----+---+----+--+----+ *=20
                   * |SGP1|   |SGP2|   |SGP3|  |SGP4| *=20
                   * +-+--+   +-+--+   +-+--+  ++---+ *=20
                   ************************************=20
                       |        |        |      |=20
                  =20
                  Figure 3. SG with single Layer3 Logic and with multiple=
 SGs=20
                  =20
                  =20
                  1.6 Possible Uses of SG-SG Communication=20
                  =20
                  Below, some cases, where SG-SG communication might be used=
 is given.=20
                                                                            =
        5=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                  =20
                  As gateway between networks of different operators:=20
                  It is likely that operators would prefer to centralize=
 interaction=20
                  of their network with networks of other operators for=
 reasons like=20
                  security, management transparency, different protocols=
 used in=20
                  different networks etc... Using concentration nodes=
 instead of a=20
                  fully mesh network also reduces number of necessary SCTP=
=20
                  associations.=20
                  =20
                         -----                     -----=20
                     ////     \\\\             ////     \\\\=20
                    | Network of  |           | Network of  |=20
                   |  Operator1    |         |  Operator2    |=20
                   |               |         |               |=20
                    |             |           |             |=20
                     \\\\     ////             \\\\     ////=20
                         --+--                     --+--=20
                           |                         |=20
                           |                         |=20
                     +-----+------+          +-------+----+=20
                     | SG of      |          | SG of      |=20
                     | Operator1  +----------+ Operator2  |=20
                     +------------+          +------------+=20
                  =20
                  Figure 4. Interaction of two networks via SG-SG=
 communication=20
                  =20
                  To allow asymmetric Routekeys:=20

[KAM] i don't understand how SG-SG improves upon M3UA for asymmetric RKs

                  In large networks and especially when multiple operators=
 are=20
                  present, it might be desirable to have asymmetric traffic=
 ranges at=20
                  the endpoints and to limit impact of configuration changes=
 at=20
                  endpoints to as few other nodes as possible. For example=
 in the=20
                  example below, endpoints are using routing keys in=
 different=20
                  granularities and changing traffic ranges will require=
 configuration=20
                  changes only on the SGs, reconfigured ASP is directly=
 connected to.=20
                  =20
                   AS1:         AS2:              AS3:        AS4:=20
                   DPC=3D1-1-1    DPC=3D1-1-1         DPC=3D2-2-2  =
 DPC=3D3-3-3=20
                   SI=3D3         SI=3D5=20
                   +--------+  +--------+         +--------+ +--------+=20
                   |       =20|  |        |         |        | |        |=20
                   | ASP1   |  | ASP2   |         | ASP3   | | ASP4   |=20
                   +-------++  +-+------+         +-------++ +-+------+=20
                           |     |                        |    |=20
                           |     |                        |    |=20
                          ++-----+-+                    +-+----+-+=20
                          |        |                    |        |=20
                          |  SG1   +--------------------+  SG2   |=20
                          +--------+                    +--------+=20
                  =20
                  Figure 5. Asymmetric Traffic Ranges with SG-SG=
 communication=20
                  =20
                  To build hybrid networks:=20

                                                                            =
        6=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                  SG-SG communication might be utilized to build networks,=
 where TDM=20
                  and IP based transport of messages is used in a mixed way.=
 It should=20
                  be noted that SGs can act as IP-STPs and/or IP-SEPs. For=
 example in=20
                  Figure 5 below, SG3 acts as IP-SEP.=20
                  =20
                  =20
                                     +------+=20
                                     |SS7   |=20
                                     |User  |=20
                                     |Parts |=20
                     +------+        +------+        +------+=20
                     | ASP1 |        | SG3  |        |SS7   |=20
                     |      |        |      |        |node3 |=20
                     +---+--+        +-+--+-+        +---:--+=20
                         |             |  |              :=20
                         |             |  |              :         +------+=
=20
                         |             |  |              :         | ASP2 |=
=20
                     +---+--+          |  |          +---:--+   +--+      |=
=20
                     | SG1  +----------+  +----------+ SG2  +---+  +------+=
=20
                     |      +------------------------+      +---+  +------+=
=20
                     +--:---+                        +---:--+   |  | ASP3 |=
=20
                        :                                :      +--+      |=
=20
                        :                                :         +------+=
=20
                     +--:---+                        +---:--+=20
                     |SS7   |                        |SS7   |=20
                     |node1 |                        |node2 |=20
                     +------+                        +------+=20
                  =20
                  =20
                    ---------  IP based communication=20
                    .. .. ..   TDM based communication=20
                  Figure 6. Hybrid network configuration with SG-SG=
 communication=20
                  =20
                  =20
                  2. Functional Areas=20
                  =20
                  2.1 Signalling Point Code Representation=20
                  =20
                  SGs should control SPMCs as a whole. When a SPMC becomes=
=20
                  unavailable, SG will broadcast DUNA to all SGs, it has an=
=20
                  association with. Similarly when a SPMC becomes available=
 DAVA and=20
                  when a SPMC becomes restricted DRST will be sent.=20
                  =20
                  =20
                  2.2 Routing Context and Routing Keys=20
                  =20
                  Unlike M3UA, there is no Routing Context/Routing Key=
 concept present=20
                  in SG-SG communication.=20
                  =20
                  =20
                  2.3 Network Appearance=20
                  =20
                  NA is used in the messages as described in M3UA.=20
                                                                            =
        7=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                  =20
                  =20
                  2.4 SCTP Association Establishment=20
                  =20
                  There is no client/server relationship between SGPs. SCTP=
=20
                  associations might be initiated from any side. A=
 collision, which=20
                  might happen if both sides try to establish SCTP=
 association=20
                  concurrently, is handled by the SCTP protocol itself. =20
                  =20
                  Although SGPs are allowed to have more than one SCTP=
 association=20
                  between them, such a configuration is NOT RECOMMENDED, as=
 SCTP=20
                  multihoming provides a better way to achieve redundancy in=
 a=20
                  transparent way to upper layers with no message=
 loss/duplication and=20
                  missequencing.=20
                  =20
[KAM] do you plan to apply for a different SCTP port for SG-SG or reuse M3UA=
 port of 2905?
                  =20
                  2.5 Point Code Status Information Exchange=20
                  =20
                  After a SCTP association is established, peers SHOULD=
 declare the=20
                  availability of their M3UA layer with ASPUP messages. A=
 received=20
                  ASPUP message is replied with ASPUP-ACK. If one of the=
 peers=20
                  receives ASPUP message before sending ASPUP, it MAY or MAY=
 NOT send=20
                  ASPUP message, ASPUP-ACK message declares availability of=
 the remote=20
                  peer. Each SGP should declare its availability to each SGP=
 of the=20
                  remote SGs separately. A SGP can declare its=
 unavailability with=20
                  ASPDN message. ASPDN message is acknowledged with=
 ASPDN-ACK message. =20
               =20
                  After availability of M3UA layers is confirmed, SGs will=
 exchange=20
                  SSNM to update the remote peer about the status of the=
 PCs, which=20
                  are configured as reachable on them. Unless a=
 corresponding message=20
                  is received, all configured PCs are assumed as accessible=
 via the=20
                  remote peer. Each SG will send DUNA for unavailable PCs=
 and DRST for=20
                  restricted PCs. The end of this unavailable/restricted PC=
=20
                  announcement procedure is marked with an ASPAC message.=
 Those SSNM=20
                  are sent per SG. A SG SHOULD NOT start sending DATA to a=
 peer,=20
                  unless ASPAC is received. =20
                  =20
                  SSNM, which are sent for point code status information=
 exchange=20
                  procedure and ASPAC SHOULD be sent via stream 0, to=
 prevent the=20
                  remote peer to receive ASPAC before the last SSNM. =20
                  =20
                  =20
                  2.6 Message Distribution=20
                  =20
                  Data messages SHOULD be sent to SGs, via which the=
 destination=20
                  pointcode of the message to be sent is in available=
 status. In case,=20
                  when there is no such peer SG, message SHOULD be sent to=
 SGs, from=20
                  which the destination is declared as restricted. If no=
 such SG=20
                  exists, the message SHOULD be dropped.=20
                  =20
                  Message distribution among remote SGs is implementation=
 dependent.=20
                  =20

                                                                            =
        8=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                  Message distribution method among SGPs belonging to the=
 same SG can=20
                  be either override or loadshare. Traffic Mode Type=
 parameter in=20
                  ASPAC shows the traffic distribution method expected by=
 the sending=20
                  SG, between SGPs belonging to it. If the receiver does not=
 support=20
                  this traffic distribution method, an Error message with=
 Error Code=20
                  "Unsupported Traffic Handling Mode" SHOULD be sent. In=
 such a case,=20
                  the SG, which initiated Error message SHOULD NOT send=
 traffic to the=20
                  peer SG.=20
                  =20
                  Messages, which require sequencing SHOULD be via the same=
 SCTP=20
                  association using the same stream.=20
                  =20
                  In case, the destination to which messages are to be sent=
 changes=20
                  (failover, new active SGP etc...), Timer Procedure as=
 described in=20
                  CORID[6] (1.4.1.4. SPP Restoring Traffic) SHOULD be=
 followed, to=20
                  decrease possibility of missequencing.=20
                  =20
                  =20
                  2.7 Congestion Handling=20
                  =20
                  Congestion handling procedures as defined in relevant MTP3=
 standards=20
                  for signaling points should be followed between SGs. It is=
=20
                  responsibility of a SG, to follow those procedures, on=
 behalf of the=20
                  SPMCs, that it directly controls. While following those=
 procedures,=20
                  SCON instead of TFC and CGT instead of RCT MUST be used,=
 when the=20
                  message needs to be sent to an adjacent node in IP domain.=
=20
                  =20
                  =20
                  2.8 Restricted Destinations=20
                  =20
                  When destinations in IP domain should be declared as=
 restricted is=20
                  implementation dependent.=20
                  =20
                  =20
                  3. Message Types and Parameters=20
                  =20
                  The following new message types are added to SSNM in=
 addition to the=20
                  ones defined in M3UA.=20
                  128      Congestion Test Message (CGT)=20
                  128      Changeover Request Message(COR)=20
                  129      Changeover Request Acknowledgement Message(CORA)=
=20
                  =20
                  =20
                  The following parameters are added in addition to the ones=
 defined=20
                  in M3UA.=20
                  Forward Sequence Number    0x0214=20
                  Signalling Link Code       0x0215=20
                  =20
               =20
                  4. Protocol Messages=20
                  =20
                  Between SGs DATA and SSNM messages as defined in M3UA=
 protocol are=20
                  used. Error from MGMT, ASPUP/ASPUP-ACK from ASPSM and=
 ASPAC from=20
                                                                            =
        9=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                  ASPTM are also used. RC field in messages is not used,i.e.=
 it MUST=20
                  not be filled.=20
                  =20
                  =20
                  4.1 Destination User Part Unavailable (DUPU)=20
                  =20
                  A new field is introduced to DUPU.=20
                  Concerned PC: Destination PC, which has caused DUPU to be=
 generated.=20
                  This parameter is mandatory.=20
                  =20
                  The format for DUPU message parameters is as follows:=20
                  =20
               =20
                      0                   1                   2             =
      3=20
                      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=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0200          |             Length =
           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ =20
                     |                      Network Appearance              =
         |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0012          |          Length =3D=
 8           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |   Mask =3D 0    |                  Affected PC       =
           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0206          |             Length =
           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |    reserved   |                 Concerned DPC        =
         |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0204          |          Length =3D=
 8           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |             Cause             |            User      =
         |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0004          |             Length =
           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     \                                                      =
         \=20
                     /                          INFO String                 =
         /=20
                     \                                                      =
         \=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                  =20
                  =20
                  4.2 Signalling Congestion (SCON)=20
                  =20
                  For SG-SG communication, Concerned DPC parameter is=
 mandatory. It=20
                  contains the point code information for the signaling=
 point, which=20
                  originated the message causing SCON to be generated.=20
                  =20
                  In SG-SG communication, there will be two Affected PC=
 fields=20
                  present. The first one gives the PC of the originator of=
 the SCON=20
                  (or the corresponding TFC) message and the second one=
 gives the PC=20
                  for the congested destination. Those two Affected PC=
 fields MUST be=20
                  sent in this order.=20
                  =20
                  The format for SCON message parameters is as follows:=20
                                                                            =
       10=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                  =20
                      0                   1                   2             =
      3=20
                      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=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0200          |             Length =
           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ =20
                     |                      Network Appearance              =
         |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0012          |             Length =
           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |   reserved    |                 Affected PC1         =
         |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |   reserved    |                 Affected PC2         =
         |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0206          |             Length =
           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |    reserved   |                 Concerned DPC        =
         |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0205          |             Length =
           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |                   Reserved                    | =
 Cong. Level  |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |            Tag =3D 0x0004       |             Length =
           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     \                                                      =
         \=20
                     /                         INFO String                  =
         /=20
                     \                                                      =
         \=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
               =20
                  =20
                  =20
                  4.3 Congestion Test Message (CGT)=20
                  =20
                  CGT is used to support=
 Signalling-route-set-congestion-test(National=20
                  Option) procedures as defined in Q.704. It is used to test=
 the=20
                  congestion status of a PC via a specific SG.=20
                  =20
                  The CGT message contains the following parameters:=20
                  =20
                  Affected PC        Mandatory=20
                  Concerned DPC      Mandatory=20
                  Congestion Level   Mandatory=20
                  Info String        Optional=20
                  =20
                  =20
                  The format for CGT Message parameters is as follows:=20
                  =20
                      0                   1                   2             =
      3=20
                      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=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0200          |             Length =
           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ =20
                     |                      Network Appearance              =
         |=20
                                                                            =
       11=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0012          |             Length=
 =3D 8        |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |      Mask     |                 Affected PC          =
         |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0206          |             Length =
           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |    reserved   |                 Concerned DPC        =
         |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0205          |             Length =
           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
 =20                   |                   Reserved                    | =
 Cong. Level  |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |            Tag =3D 0x0004       |             Length =
           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     \                                                      =
         \=20
                     /                         INFO String                  =
         /=20
                     \                                                      =
         \=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                  =20
                  Network Appearance: 32 bits (Semi-mandatory)=20
                  =20
                  See M3UA Section 3.1.1 =20
                  =20
                  Affected Point Code: 32 bits (Mandatory)=20
                  =20
                  Affected Point Code parameter contains the 14-, 16-,=
 24-bit binary=20
                  formatted point code value, for which CGT message is=
 generated.=20
                  =20
               =20
                  Concerned DPC: 32 bits (Mandatory)=20
               =20
                  Concerned DPC parameter contains the 14-, 16-, 24-bit=
 binary=20
                  formatted point code value, whose congestion status is to=
 be tested.=20
                  =20
               =20
                  Congestion Level: 8 bits (unsigned integer) (Mandatory)=20
                  =20
                  The Congestion Level parameter contains one of the=
 following values:=20
                         0    No Congestion or Undefined=20
                         1    Congestion Level 1=20
                         2    Congestion Level 2=20
                         3    Congestion Level 3=20
                  =20
                  The congestion levels are defined in the congestion method=
 in the=20
                  appropriate national MTP recommendations [. .].=20
                  =20
                  When sending CGT message, procedures defined for=
 Signalling-route-
                  set-congestion-test in Q.704 Clause 13.9 should be=
 followed.=20
                  =20
                  =20
                  4.4 Changeover Mechanism Related Messages=20
                  =20
                                                                            =
       12=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                  Those messages are necessary to support changeover=
 mechanism as=20
                  defined in MTP3. It should be noted that, they will be=
 used, in case=20
                  a SG is relaying corresponding MTP3 changeover messages to=
 another=20
                  SG.=20
                  =20
                         +-------+                +-------+=20
                         | SS7   |                |  SG2  |=20
                         | node1 +--------X-------+       |=20
                   COO(1)+---+---+ ^              +----+--+   CORA(3)=20
                    |   ^    |     |                   |   ^   |=20
                    |   |    |     |                   |   |   |=20
                    |   |    |     |                   |   |   |=20
                    |   |    |     |                   |   |   |=20
                    |   |    |     |                   |   |   |=20
                    |   |    |     |                   |   |   |=20
                    V   |    |     | +-------+         |   |   V=20
                       COA(4)|     | |  SG1  |         |  COR(2)=20
                             +-----+-+       +---------+=20
                                ^  | +-------+     ^=20
                                |  |               |=20
                                |  |               |=20
                                |  |               |=20
                                |  |               |=20
                                 TDM              IP =20
                  Figure 7. SG1 relaying changeover messages to and from SG2=
=20
                  =20
               =20
                  4.4.1 Changeover Request Message(COR)=20
                  =20
                  COR is used to relay changeover order/emergency changeover=
 order=20
                  information to/from a SS7 peer. There are two scenarios,=
 where it=20
                  can be used. Either it is received from a peer SG, where a=
=20
                  corresponding COO/ECM is sent to peer SS7 node or it can=
 be=20
                  generated to a peer SG, after receiving COO/ECM from a SS7=
 node.=20
                  =20
                  COR message contains the following parameters:=20
                  =20
                  Network Appearance: 32 bits (Semi-mandatory)=20
                  =20
                  See M3UA Section 3.1.1=20
                  =20
                  =20
                  SLC :  5 bits (Mandatory)=20
                  =20
                  The Signalling Link Code of the failed link.=20
                  =20
                  =20
                  FSN :  24 bits (Semi-mandatory)=20
                   =20
[KAM] Where does FSN come from?  Are you going to add FSN to Data messages? =
 Is
this related to Correlation ID?

                  Forwards sequence number of the last message signal unit=
 accepted=20
                  from the unavailable signaling link by the sender of=
 message. If COR=20
                  is received from a SG and if FSN is present a=
 corresponding COO MUST=20
                  be generated. If no FSN is present an ECM MUST be=
 generated. When=20
                                                                            =
       13=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                  COO is received from a SS7 peer, FSN MUST be filled in=
 COR. When ECM=20
                  is received from a SS7 peer, FSN MUST NOT be filled.=20
                  =20
                  Affected Point Code: 32 bits (Mandatory)=20
                  Affected Point Code parameter contains the 14-, 16-,=
 24-bit binary=20
                  formatted point code value, which has sent COO/ECM=
 message.=20
                  =20
                  =20
                  Concerned Point Code: 32 bits (Mandatory)=20
                  Concerned Point Code parameter contains the 14-, 16-,=
 24-bit binary=20
                  formatted point code value, to which COO/ECM message is=
 sent.=20
               =20
                  =20
                  The format for COR message parameters is as follows:=20
                  =20
                      0                   1                   2             =
      3=20
                      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=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0200          |             Length =
           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ =20
                     |                      Network Appearance              =
         |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0214          |           Length =
=3D8           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ =20
                     |  Reserve      |               FSN                    =
         | =20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |         Tag =3D 0x0215          |           Length =
=3D8           |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ =20
                     |                Reserved                             |=
   SLC   |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |                 Tag =3D 0x0012          |   Length =
=3D8           |        =20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |  Reserved     |                 Affected PC          =
         |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |                 Tag =3D 0x0206          |   Length =
=3D8           |        =20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                     |  Reserved     |                 Concerned PC         =
         |=20
                    =
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
                  =20
                  =20
                  =20
                  4.4.2 Changeover Request Acknowledgement Message (CORA)=20
                  =20
                  CORA is used to relay the FSN information regarding the=
 last=20
                  accepted MSUs by a failed link between a peer SG and a SS7=
 node as=20
                  an answer to COR.=20
                  =20
                  COR message contains the following parameters:=20
                  =20
                  Network Appearance: 32 bit (Semi-mandatory)=20
                  =20
                  See M3UA Section 3.1.1=20
                  =20
                                                                            =
       14=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
               =20
                  SLC :  5 bits (Mandatory)=20
                  =20
                  The Signalling Link Code of the failed link.=20
                  =20
                  =20
                  FSN :  24 bits (Semi-mandatory)=20
                   =20
                  Forwards sequence number of the last message signal unit=
 accepted=20
                  from the unavailable signaling link by the sender of CORA.=
 . If CORA=20
                  is received from a SG and if FSN is present a=
 corresponding COA MUST=20
                  be generated. If no FSN is present an ECA MUST be=
 generated. When=20
                  COA is received from a SS7 peer, FSN MUST be filled in=
 CORA. When=20
                  ECA is received from a SS7 peer, FSN MUST NOT be filled.=
=20
                  =20
               =20
                  Affected Point Code: 32 bits (Mandatory)=20
                  Affected Point Code parameter contains the 14-, 16-,=
 24-bit binary=20
                  formatted point code value, to which the COA to be=
 generated based=20
                  on the received CORA, should be sent.=20
                  =20
                  =20
                  Concerned Point Code: 32 bits (Mandatory)=20
                  Concerned Point Code parameter contains the 14-, 16-,=
 24-bit binary=20
                  formatted point code value, to which COO/ECM message is=
 sent.=20
                  =20
                  The format for parameters for CORA is the same like COR.=
=20
                  =20
                  =20
                  5. SG and SGP state machines=20
                  =20
                  5.1 SGP State Machine=20
                  =20
                  The state of each remote SGP is maintained in the M3UA=
 layer in the=20
                  SGP. The state of a particular SGP changes due to events.=
 The events=20
                  include:=20
                  *Reception of messages from the peer M3UA layer at the=
 SGP.=20
                  *Reception of indications from the SCTP layer.=20
                  *Local management intervention.=20
                  =20
                  The SGP state transition diagram is shown in Figure 8. The=
 possible=20
                  states of a SGP are:=20
                  =20
                  SGP-DOWN: The remote M3UA peer at the SGP is unavailable=
 and/or the=20
                  related SCTP association is down. Initially all SGPs will=
 be in this=20
                  state. An SGP in this state SHOULD NOT be sent any=
 messages, with=20
                  the exception of Heartbeat, ASP Down Ack and Error=
 messages.=20
                  =20
                  SGP-UP: The remote M3UA peer at the SGP is available(and=
 the related=20
                  SCTP association is up). M3UA messages, which can be sent=
 in this=20
                  state are restricted only by SG state.=20
                  =20
                  =20
[KAM] SGP must maintain state on a per SGP peer basis.  Is SGP up after=
 sending
ASP UP, or after receiving ASP UP ACK, or after DE transfer of ASP UP and=
 ASP
UP ACK?
                                                                            =
       15=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                             +--------+=20
                             |SGP UP  |=20
                             +-+----+-+=20
                         ASPUP/^    | ASPDOWN/ASPDOWN-ACK=20
                     ASPUP-ACK |    | SCTP CDI/SCTP RI=20
                               |    |=20
                               |    v=20
                             +-+----+-+=20
                             |SGP DOWN|=20
                             +--------+=20
                  =20
                  Figure 8. SGP state machine=20
                  =20
                  =20
                  5.2 SG state machine=20
                  =20
                  The state of each remote SG is maintained in the SGP. SGPs=
 belonging=20
                  to the same SG MUST have a unique view of a remote SG. The=
 state of=20
                  a particular SG changes due to events. The events include:=
=20
                  *Reception of messages from the peer SG.=20
                  *State changes of local SGPs.=20
                  *Local management intervention.=20
                  =20
                  The SG state transition diagram is shown in Figure 9.=
 Possible=20
                  states of SG are:=20
                  =20
                  SG DOWN: There is no SGP belonging to this SG in SGP UP=
 state.=20
                  Messages, which are not allowed in SGP DOWN state SHOULD=
 NOT be sent=20
                  to the SG.=20
                  =20
                  SG UP: There is at least one SGP belonging to this SG in=
 SGP UP=20
                  state, but PC status announcement phase is not completed=
 yet. In=20
                  this state no DATA messages SHOULD be sent to the remote=
 SG.=20
                  =20
                  SG ACTIVE: There is at least one SGP belonging to this SG=
 in ASP UP=20
                  state and remote SG has finished PC announcement phase.=
 DATA=20
                  messages can be sent to the SG.=20
                  =20
                              +--------+=20
                              |  SG    |=20
                              |ACTIVE  +---+=20
                              +---+----+   |=20
                                  ^        |=20
                            ASPAC |        |Last SGP in SGP UP state=20
                          from one|        |transitions to SGP DOWN state=20
                        SGP of SG |        |=20
                              +---+----+   |=20
                              |  SG    |   |=20
                              |  UP    |   |=20
                              +-+-----++   |=20
                        one SGP ^     |    |=20
                     transitions|     |Last SGP in SGP UP state=20
                     to SGP UP  |     |transitions to SGP DOWN state=20
                                                                            =
       16=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                      state     |     |    |=20
                                |     v    |=20
                              +-+-----++   |=20
                              |  SG    +<--+=20
                              | DOWN   |=20
                              +--------+=20
                  Figure 9. SG state machine=20
                  =20
               =20
                  6. Examples of SG-SG communication procedures=20
                  =20
                  6.1 M3UA availability declaration=20
                  In the following scenario, SG1 consists of SGP1/SGP2 and=
 SG2=20
                  consists of SGP3/SGP4. After establishment of SCTP=
 associations=20
                  between SGPs, each SGP should make its peers aware that=
 its own M3UA=20
                  is ready.=20
                  =20
[KAM] i'm not sure you say anywhere in the text that ASPUP is double-ended. =
 certainly,
this needs to be discussed in the state machines above.

                  SGP1      SGP2          SGP3      SGP4=20
                     |        |              |        |=20
                     +------ASPUP----------->|        |=20
                     |        |              |        |=20
                     +------ASPUP------------+------->|=20
                     |        |              |        |=20
                     |<-----ASPUP-ACK--------|        |=20
                     |        |              |        |=20
                     |<-----ASPUP------------+--------|=20
                     |        |              |        |=20
                     |<-----ASPUP-ACK--------+--------|=20
                     |        |              |        |=20
                     |------ASPUP-ACK--------+------->|=20
                     |        |              |        |=20
                     |<-----ASPUP------------|        |=20
                     |        |              |        |=20
                     |------ASPUP-ACK------->|        |=20
                     |        |              |        |=20
                     |------ASPUP------------+------->|=20
                     |        |              |        |=20
                     |<-----ASPUP-ACK--------+--------|=20
                     |        |              |        |=20
                     |        |              |        |=20
                  =20
                  6.2 PC status announcement=20
                  In the following scenario, SG1 consists of SGP1/SGP2 and=
 SG2=20
                  consists of SGP3/SGP4. It shows the messages exchanged=
 after M3UA=20
                  availability declaration is finished. PC1/PC2/PC3 are=
 declared as=20
                  reachable via SG2 on SG1 and PC4/PC5 are declared as=
 reachable via=20
                  SG1 on SG2.=20
                  =20
[KAM] so ASPAC is not Double-ended?  Is ASP ACTIVE ACK used?
                  =20
                     SGP1      SGP2          SGP3      SGP4=20
                        |        |              |        |=20
                        |-------DUNA(PC1)------>|        |=20
                        |        |              |        |=20
                                                                            =
       17=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                        |-------DRST(PC2)------>|        |=20
                        |        |              |        |=20
                        |-------ASPAC---------->|        |=20
                        |        |              |        |=20
                        |<------DATA(PC3)-------+--------|=20
[KAM] how can data be sent.  SGP4 has not sent an ASP ACTIVE.
                        |        |              |        |=20
                        |        |<---DUNA(PC4)-|        |=20
                        |        |              |        |=20
                        |        |<---ASPAC-----|        |=20
                        |        |              |        |=20
                        |--------+-DATA(PC5)----+------->|=20
                        |        |              |        |=20
                        |        |              |        |=20
                        |        |              |        |=20
                  =20
                  =20
                  7. Security=20
                  =20
                  SG-SG communication inherits security risks and=
 considerations that=20
                  are present in M3UA. Please see "Security" section of M3UA=
 for those=20
                  security considerations and recommendations.=20
                  =20
                  Because SG-SG communication introduces relaying capability=
 and can=20
                  be placed at network boundaries of networks belonging to=
 different=20
                  operators, additional security might be desirable. Since=
 SS7 related=20
                  outages are very costly and increased interconnections=
 between TDM=20
                  and IP domain make SS7 network more vulnerable to=
 intentional and/or=20
                  accidental disturbances, it is advisable for SGs to have=
 capability=20
                  to screen and act on SS7 messages going through it. For=
 example,=20
                  screening of messages can be made based on configurable=
 lists of=20
                  OPC, DPC, SIO values or any combination of them. Possible=
 actions=20
                  that are taken upon detection of disturbances could be=
 informing=20
                  network management entities, generation of alarms,=
 discarding=20
                  messages, modification of messages, generation of new=
 messages or a=20
                  combination of them. Other more sophisticated message=
 syntax,=20
                  message type and content screening could also be=
 implemented to=20
                  improve security. =20
                  =20
                  =20
                  8. Acknowledgements=20
                  =20
                  The authors would like to thank Manfred Angermayr, Javier=
 Pastor-
                  Balbas, Vaibhav Madan and Kutluk Uslu for their valuable=
 comments=20
                  and suggestions.=20
                  =20
                  =20
                  9. References=20
                  =20
                  9.1 Normative References=20
                  =20
                  [1] RFC[3332] "Signalling System7 (SS7) Message Transfer=
 Part3(MTP3)=20
                  User Adaptation Layer(M3UA)"=20
                  =20
                                                                            =
       18=20
               =20
=0C
               =20
                    Asveren/Bidulock =20
                    Internet Draft    M3UA SG-SG Communication         =
 January, 2003=20
                  [2] RFC[abcd] "SS7 MTP2-User Peer-to-Peer Adaptation=
 Layer"=20
                  =20
                  [3] ITU-T Recommendation Q.703 "Specifications of=
 Signalling System=20
                  No. 7 =FB Message transfer part, Signalling link"=20
                  =20
                  [4] RFC[2960] "Stream Control Transmission Protocol"=20
               =20
                  [5] ITU-T Recommendation Q.704 "Specifications of=
 Signalling System=20
                  No. 7 - Message transfer part  Signalling network=
 functions and=20
                  messages"=20
                  =20
                  [6] draft-bidulock-sigtran-corid-00.txt "Correlation Id=
 and=20
                  Heartbeat Procedures (CORID) Supporting Lossless Fail-Over=
 between=20
                  SCTP Associations for Signalling User Adaptation Layers"=
=20
                  =20
                  =20
                  =20
                  9.2 Informative References=20
                  =20
                  [7] RFC[2119] "Key words for use in RFCs to Indicate=
 Requirement=20
                  Levels"=20
                  =20
                  =20
                  =20
                  10. Author's Addresses=20
                  =20
                  =20
                  Tolga Asveren=20
                  Oksijen Teknoloji=20
                  Dunya Ticaret Merkezi A1=20
                  Istanbul, Turkey=20
                  Email : tolga.asveren@o2.com.tr=20
                  =20
                  =20
                  =20
                  Brian Bidulock=20
                  OpenSS7 Corporation=20
                  1469 Jeffreys Crescent=20
                  Edmonton, AB    T6L 6T1=20
                  EMail : bidulock@openss7.org=20
                  =20
                  =20
                  =20
                  =20
                  =20
                  Expires: July 27, 2003=20
                  =20
               =20
               =20




                                                                            =
       19=20
               =20
=0C


--=====================_132767539==_--

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



From mailnull@www1.ietf.org  Thu Jan 30 22:57:02 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 WAA17612
	for <sigtran-archive@odin.ietf.org>; Thu, 30 Jan 2003 22:57:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0V40Ls19076
	for sigtran-archive@odin.ietf.org; Thu, 30 Jan 2003 23:00:21 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0V3xbJ18997;
	Thu, 30 Jan 2003 22:59:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0V3vrJ18926
	for <sigtran@optimus.ietf.org>; Thu, 30 Jan 2003 22:57:53 -0500
Received: from auds953.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17533
	for <sigtran@ietf.org>; Thu, 30 Jan 2003 22:54:02 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0V3vTeW012840;
	Thu, 30 Jan 2003 21:57:30 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id IAA18243; Fri, 31 Jan 2003 08:26:28 -0500 (GMT)
Message-ID: <3E39F41A.D12E514E@axes-mach01.usa.alcatel.com>
Date: Fri, 31 Jan 2003 09:27:14 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
References: <20030130000108.A28966@openss7.org> <3E38D245.A5C93237@axes-mach01.usa.alcatel.com> <20030130031827.B10733@openss7.org> <3E3904A4.7BDAFD7E@axes-mach01.usa.alcatel.com> <20030130052618.B21821@openss7.org> <3E391CF3.DC147530@axes-mach01.usa.alcatel.com> <20030130060118.A3822@openss7.org> <3E392731.A7431820@axes-mach01.usa.alcatel.com> <20030130070055.A11092@openss7.org> <3E393793.665779E5@axes-mach01.usa.alcatel.com> <20030130080427.A19032@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

Can you please tell me with what the RL is compared/matched with, in finding the MTP-SAP.

--Srini

"Brian F. G. Bidulock" wrote:

> Srini,
>
> SS7 MTP Level 3 finds the MTP-SAP quite nicely today using
> the information from the RL.  The RL (NI/DPC/SI) is all that
> is required to locate the AS.
>
> --brian
>
> ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 20:02:51)
> > Brian,
> >
> >    Yes, I agree with you. Finding the eligible list of SGPs is the matter for MTP Level 3 SS7 stack / NIF. But IMO maintaining the
> > complete routing keys at the SG itself will enable us to select the eligible SGPs better. Because based on the PC of AS(i.e., DPC)
> > alone or any other info of routing label alone, will not suffice to select the SGP to reach the AS. Is my assumption right?.
> >
> > --Srini
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > Srini,
> > >
> > > If the AS corresponds to an MTP-SAP (MTP-User), all that the SGP need do is
> > > find the MTP-User.  How an MTP Level 3 SS7 stack finds the MTP-User is a
> > > matter for the MTP Level 3 SS7 stack.
> > >
> > > --brian
> > >
> > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 18:52:58)
> > > > Brian,
> > > >
> > > >   How the SGP connectivity to the AS is determined at the SG?. Do we have to have AS-SGPs list?. But in that case we need to look
> > > > at the complete routing key table at the SG before selecting the SGP from the AS(RK).
> > > >
> > > > --Srini
> > > >
> > > > "Brian F. G. Bidulock" wrote:
> > > >
> > > > > Srini,
> > > > >
> > > > > The eligible list of SGPs is all the SGPs belonging to the SG
> > > > > that have connectivity to the AS and for which an ASP is in
> > > > > the ASP-ACTIVE state for the AS.
> > > > >
> > > > > --brian
> > > > >
> > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 18:09:16)
> > > > > > Brian,
> > > > > >
> > > > > >      I feel once the eligible list of SGPs to reach the AS are found, you answer applies. But my doubt is How to find the
> > > > > > eligible list of SGPs?.
> > > > > >
> > > > > > --Srini
> > > > > >
> > > > > > "Brian F. G. Bidulock" wrote:
> > > > > >
>
> --
> 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 mailnull@www1.ietf.org  Fri Jan 31 00:30: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 AAA19580
	for <sigtran-archive@odin.ietf.org>; Fri, 31 Jan 2003 00:30:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0V5Xak23259
	for sigtran-archive@odin.ietf.org; Fri, 31 Jan 2003 00:33:36 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0V5X4J23244;
	Fri, 31 Jan 2003 00:33:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0V5VgJ23201
	for <sigtran@optimus.ietf.org>; Fri, 31 Jan 2003 00:31:42 -0500
Received: from gw.openss7.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19541
	for <sigtran@ietf.org>; Fri, 31 Jan 2003 00:27:49 -0500 (EST)
Received: from ns.pigworks.openss7.net (IDENT:KX1M8LXvGmKaJa55LbPg4HFNqQM1B73J@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h0V5VMD13906;
	Thu, 30 Jan 2003 22:31:22 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h0V5VM530531;
	Thu, 30 Jan 2003 22:31:22 -0700
Date: Thu, 30 Jan 2003 22:31:22 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
Cc: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
Message-ID: <20030130223122.A31688@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>,
	TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
References: <20030130031827.B10733@openss7.org> <3E3904A4.7BDAFD7E@axes-mach01.usa.alcatel.com> <20030130052618.B21821@openss7.org> <3E391CF3.DC147530@axes-mach01.usa.alcatel.com> <20030130060118.A3822@openss7.org> <3E392731.A7431820@axes-mach01.usa.alcatel.com> <20030130070055.A11092@openss7.org> <3E393793.665779E5@axes-mach01.usa.alcatel.com> <20030130080427.A19032@openss7.org> <3E39F41A.D12E514E@axes-mach01.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: <3E39F41A.D12E514E@axes-mach01.usa.alcatel.com>; from ksrini@axes-mach01.usa.alcatel.com on Fri, Jan 31, 2003 at 09:27:14AM +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>

Srini,

Normally NI (and the identity of the link upon which the message was received)
to identify the SS7 netowrk and routing, the DPC to identify the destination
for the message, and the SI value to determine the MTP User at the desination
signalling point.  That's about it.  Gateway screening might screen the source
address and some elements of the MTP-User data but will not affect routing.

--brian

ksrinivas wrote:                                                                 (Fri, 31 Jan 2003 09:27:14)
> Brian,
> 
> Can you please tell me with what the RL is compared/matched with, in finding the MTP-SAP.
> 
> --Srini
> 
> "Brian F. G. Bidulock" wrote:
> 
> > Srini,
> >
> > SS7 MTP Level 3 finds the MTP-SAP quite nicely today using
> > the information from the RL.  The RL (NI/DPC/SI) is all that
> > is required to locate the AS.
> >
> > --brian
> >
> > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 20:02:51)
> > > Brian,
> > >
> > >    Yes, I agree with you. Finding the eligible list of SGPs is the matter for MTP Level 3 SS7 stack / NIF. But IMO maintaining the
> > > complete routing keys at the SG itself will enable us to select the eligible SGPs better. Because based on the PC of AS(i.e., DPC)
> > > alone or any other info of routing label alone, will not suffice to select the SGP to reach the AS. Is my assumption right?.
> > >
> > > --Srini
> > >
> > > "Brian F. G. Bidulock" wrote:
> > >
> > > > Srini,
> > > >
> > > > If the AS corresponds to an MTP-SAP (MTP-User), all that the SGP need do is
> > > > find the MTP-User.  How an MTP Level 3 SS7 stack finds the MTP-User is a
> > > > matter for the MTP Level 3 SS7 stack.
> > > >
> > > > --brian
> > > >
> > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 18:52:58)
> > > > > Brian,
> > > > >
> > > > >   How the SGP connectivity to the AS is determined at the SG?. Do we have to have AS-SGPs list?. But in that case we need to look
> > > > > at the complete routing key table at the SG before selecting the SGP from the AS(RK).
> > > > >
> > > > > --Srini
> > > > >
> > > > > "Brian F. G. Bidulock" wrote:
> > > > >
> > > > > > Srini,
> > > > > >
> > > > > > The eligible list of SGPs is all the SGPs belonging to the SG
> > > > > > that have connectivity to the AS and for which an ASP is in
> > > > > > the ASP-ACTIVE state for the AS.
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 18:09:16)
> > > > > > > Brian,
> > > > > > >
> > > > > > >      I feel once the eligible list of SGPs to reach the AS are found, you answer applies. But my doubt is How to find the
> > > > > > > eligible list of SGPs?.
> > > > > > >
> > > > > > > --Srini
> > > > > > >
> > > > > > > "Brian F. G. Bidulock" wrote:
> > > > > > >
> >
> > --
> > 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 mailnull@www1.ietf.org  Fri Jan 31 06:21: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 GAA03569
	for <sigtran-archive@odin.ietf.org>; Fri, 31 Jan 2003 06:21:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0VBOli19069
	for sigtran-archive@odin.ietf.org; Fri, 31 Jan 2003 06:24:47 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0VBO3J19041;
	Fri, 31 Jan 2003 06:24:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0VBMRJ19006
	for <sigtran@optimus.ietf.org>; Fri, 31 Jan 2003 06:22:27 -0500
Received: from auds952.usa.alcatel.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03526
	for <sigtran@ietf.org>; Fri, 31 Jan 2003 06:18:27 -0500 (EST)
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.6/8.12.6) with ESMTP id h0VBLsqe029342;
	Fri, 31 Jan 2003 05:21:55 -0600 (CST)
Received: from axes-mach01.usa.alcatel.com by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id PAA09023; Fri, 31 Jan 2003 15:50:52 -0500 (GMT)
Message-ID: <3E3A5C6A.869F01B4@axes-mach01.usa.alcatel.com>
Date: Fri, 31 Jan 2003 16:52:18 +0530
From: ksrinivas <ksrini@axes-mach01.usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: TOLGA ASVEREN <tolga.asveren@o2.com.tr>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: ASP to SGP communication
References: <20030130031827.B10733@openss7.org> <3E3904A4.7BDAFD7E@axes-mach01.usa.alcatel.com> <20030130052618.B21821@openss7.org> <3E391CF3.DC147530@axes-mach01.usa.alcatel.com> <20030130060118.A3822@openss7.org> <3E392731.A7431820@axes-mach01.usa.alcatel.com> <20030130070055.A11092@openss7.org> <3E393793.665779E5@axes-mach01.usa.alcatel.com> <20030130080427.A19032@openss7.org> <3E39F41A.D12E514E@axes-mach01.usa.alcatel.com> <20030130223122.A31688@openss7.org>
Content-Type: text/plain; charset=x-user-defined
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

Brian,

   I don't think that you have replied to what I have requested. Can you make be more clear?.

--Srini

"Brian F. G. Bidulock" wrote:

> Srini,
>
> Normally NI (and the identity of the link upon which the message was received)
> to identify the SS7 netowrk and routing, the DPC to identify the destination
> for the message, and the SI value to determine the MTP User at the desination
> signalling point.  That's about it.  Gateway screening might screen the source
> address and some elements of the MTP-User data but will not affect routing.
>
> --brian
>
> ksrinivas wrote:                                                                 (Fri, 31 Jan 2003 09:27:14)
> > Brian,
> >
> > Can you please tell me with what the RL is compared/matched with, in finding the MTP-SAP.
> >
> > --Srini
> >
> > "Brian F. G. Bidulock" wrote:
> >
> > > Srini,
> > >
> > > SS7 MTP Level 3 finds the MTP-SAP quite nicely today using
> > > the information from the RL.  The RL (NI/DPC/SI) is all that
> > > is required to locate the AS.
> > >
> > > --brian
> > >
> > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 20:02:51)
> > > > Brian,
> > > >
> > > >    Yes, I agree with you. Finding the eligible list of SGPs is the matter for MTP Level 3 SS7 stack / NIF. But IMO maintaining the
> > > > complete routing keys at the SG itself will enable us to select the eligible SGPs better. Because based on the PC of AS(i.e., DPC)
> > > > alone or any other info of routing label alone, will not suffice to select the SGP to reach the AS. Is my assumption right?.
> > > >
> > > > --Srini
> > > >
> > > > "Brian F. G. Bidulock" wrote:
> > > >
> > > > > Srini,
> > > > >
> > > > > If the AS corresponds to an MTP-SAP (MTP-User), all that the SGP need do is
> > > > > find the MTP-User.  How an MTP Level 3 SS7 stack finds the MTP-User is a
> > > > > matter for the MTP Level 3 SS7 stack.
> > > > >
> > > > > --brian
> > > > >
> > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 18:52:58)
> > > > > > Brian,
> > > > > >
> > > > > >   How the SGP connectivity to the AS is determined at the SG?. Do we have to have AS-SGPs list?. But in that case we need to look
> > > > > > at the complete routing key table at the SG before selecting the SGP from the AS(RK).
> > > > > >
> > > > > > --Srini
> > > > > >
> > > > > > "Brian F. G. Bidulock" wrote:
> > > > > >
> > > > > > > Srini,
> > > > > > >
> > > > > > > The eligible list of SGPs is all the SGPs belonging to the SG
> > > > > > > that have connectivity to the AS and for which an ASP is in
> > > > > > > the ASP-ACTIVE state for the AS.
> > > > > > >
> > > > > > > --brian
> > > > > > >
> > > > > > > ksrinivas wrote:                                                                 (Thu, 30 Jan 2003 18:09:16)
> > > > > > > > Brian,
> > > > > > > >
> > > > > > > >      I feel once the eligible list of SGPs to reach the AS are found, you answer applies. But my doubt is How to find the
> > > > > > > > eligible list of SGPs?.
> > > > > > > >
> > > > > > > > --Srini
> > > > > > > >
> > > > > > > > "Brian F. G. Bidulock" wrote:
> > > > > > > >
> > >
> > > --
> > > 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



