From exim@www1.ietf.org  Mon Jan  5 12:30:32 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25693
	for <sigtran-archive@odin.ietf.org>; Mon, 5 Jan 2004 12:30:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdYYH-0004sD-1P
	for sigtran-archive@odin.ietf.org; Mon, 05 Jan 2004 12:30:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i05HU5Z2018734
	for sigtran-archive@odin.ietf.org; Mon, 5 Jan 2004 12:30:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdYYF-0004rs-Gu; Mon, 05 Jan 2004 12:30:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdYXd-0004pQ-42
	for sigtran@optimus.ietf.org; Mon, 05 Jan 2004 12:29:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25637
	for <sigtran@ietf.org>; Mon, 5 Jan 2004 12:29:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdYXb-0004YG-00
	for sigtran@ietf.org; Mon, 05 Jan 2004 12:29:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdYVk-0004Qs-00
	for sigtran@ietf.org; Mon, 05 Jan 2004 12:27:29 -0500
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdYUE-0004GH-00
	for sigtran@ietf.org; Mon, 05 Jan 2004 12:25:54 -0500
Received: from alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i05HOnLS027986;
	Mon, 5 Jan 2004 11:24:50 -0600 (CST)
Message-ID: <3FF99DE1.306@alcatel.com>
Date: Mon, 05 Jan 2004 11:24:49 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: Franck Boesch <boesch@iphase.com>, sigtran@ietf.org
Subject: Re: [Sigtran] SIGTRAN - M2PA  draft 10 - T7 timer at  Busy End
References: <000001c3ca02$a6a14cc0$a81faf9d@BOESCH> <20031224202818.B3480@openss7.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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 et al,

Should I make that clear in the text when I get a chance to revise it?

tomG.

Brian F. G. Bidulock wrote:
> Franck,
> 
> T7 is never restarted.  It is only started or stopped (or expires).
> 
> Where it says start, read: "start for all outstanding messages".
> 
> Where it says stop, read: "stopped for all outstanding messages".
> 
> Where it says expires, read: "expires for any message".
> 
> --brian
> 
> Franck Boesch wrote:                                                                (Wed, 24 Dec 2003 10:45:22)
> 
>>Hello,
>>
>>M2PA Draft 10 says:
>>
>>--------------------------------------------------------------------------------
>>4.2.1  Sending and receiving messages::
>>...
>>Because propagation delays in IP networks are more variable than in
>>traditional SS7 networks, a single T7 timer (excessive delay of
>>acknowledgement) as in MTP2 is inadequate. If any message is
>>unacknowledged after a period equal to the T7 value, the T7 timer
>>SHALL expire.
>>
>>4.1.5 Level 2 Flow Control:
>>...
>>When the peer M2PA receives the first Link Status Busy message, it
>>SHALL start the Remote Congestion timer T6 if there are messages in
>>the retransmission buffer awaiting acknowledgement (i.e., T7 is
>>running).  In addition, M2PA SHALL stop the T7 timer if it is running.
>>Additional Link Status Busy messages received while T6 is running do
>>not cause T6 to be reset and do not cause T7 to be started.  Also,
>>while T6 is running, T7 SHALL NOT be started.
>>
>>When the peer M2PA receives the Link Status Busy Ended message and T6
>>has not expired, it SHALL stop T6 if T6 is running and start T7 if
>>there are messages awaiting acknowledgement in the retransmission
>>buffer.
>>...
>>--------------------------------------------------------------------------------
>>
>>
>>My question is the following:
>>
>>At the Busy End (Link Status Busy Ended message receive), we may have several messages transmitted but waiting for acknowledgement. These messages may have been transmitted at different times. How do we restart T7 for each message ?
>>
>>Should I understand that at the beginning of the busy condition (Link Status Busy message receive), T7 should be "suspended" (if running) and then "resumed" at Busy End  (for all transmitted but not acknowledged messages)?
>>
>>Thanks,
>>
>>Franck Boesch.
>>
>>
>>
>>_______________________________________________
>>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/  *
*   I actively disclaim speaking for Alcatel.  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 exim@www1.ietf.org  Mon Jan  5 20:10:34 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16747
	for <sigtran-archive@odin.ietf.org>; Mon, 5 Jan 2004 20:10:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdfjR-000861-KF
	for sigtran-archive@odin.ietf.org; Mon, 05 Jan 2004 20:10:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i061A5YI031115
	for sigtran-archive@odin.ietf.org; Mon, 5 Jan 2004 20:10:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdfjP-00085c-NX; Mon, 05 Jan 2004 20:10:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWynD-0003Xt-U1
	for sigtran@optimus.ietf.org; Thu, 18 Dec 2003 09:06:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22372
	for <sigtran@ietf.org>; Thu, 18 Dec 2003 09:06:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWynC-0002OJ-00
	for sigtran@ietf.org; Thu, 18 Dec 2003 09:06:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWyn7-0002OB-00
	for sigtran@ietf.org; Thu, 18 Dec 2003 09:06:14 -0500
Received: from mail4.telekom.de ([195.243.210.197])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWyn6-0002NG-00
	for sigtran@ietf.org; Thu, 18 Dec 2003 09:06:13 -0500
Received: from g8pbr.blf01.telekom.de by mail2.dmz.telekom.de with ESMTP; Thu, 18 Dec 2003 14:58:35 +0100
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <Y9CBD89Q>; Thu, 18 Dec 2003 14:58:34 +0100
Message-Id: <53CD1252F68ED61183F5000347AE5F550547BE22@G8PPZ.blf01.telekom.de>
From: "Poetzl, Joachim" <Joachim.Poetzl@t-com.net>
To: asveren@ulticom.com, sigtran@ietf.org
Subject: AW: [Sigtran] seeking for Draft
Date: Thu, 18 Dec 2003 14:58:29 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

thanks all,

it was just for curiosity - to know what has been written down and if =
zhe topic is still alive

I do not really need it

Joachim

-----Urspr=FCngliche Nachricht-----
Von: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]Im Auftrag
von Tolga Asveren
Gesendet: Donnerstag, 18. Dezember 2003 14:50
An: sigtran@ietf.org
Betreff: RE: [Sigtran] seeking for Draft


Joachim,

Long time -really long time- ago, there was a draft about performance
requirements on SIGTRAN. I found a link to the 00 version of it:
http://www.cs.columbia.edu/sip/drafts/draft-seth-sigtran-req-00.txt

Why do you need it? I would think using relevant SS7 specifications is =
the
way to go for performance requirements for SIGTRAN.

   Tolga



> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf =
Of
> Poetzl, Joachim
> Sent: Monday, December 15, 2003 7:33 AM
> To: Michael.Tuexen@lurchi.franken.de
> Cc: sigtran@ietf.org
> Subject: AW: [Sigtran] seeking for Draft
>
>
> Hi Michael,
>
> I=B4m myself not sure about that. It is mentioned as first item on
> the SIGTRAN Working Group Homepage und section Goals and milestones:
>
> Goals and Milestones:
> Done    Submit Initial draft of Signaling Architecture and
> Performance Requirements document as an Internet-Draft
>
> Regards
> Joachim
>
> -----Urspr=FCngliche Nachricht-----
> Von: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
> Gesendet: Samstag, 13. Dezember 2003 09:57
> An: Potzl, Joachim
> Cc: sigtran@ietf.org
> Betreff: Re: [Sigtran] seeking for Draft
>
>
> Joachim,
>
> I'm not sure which ID you are talking about. There are some
> applicability statements like
> draft-ietf-sigtran-signalling-over-sctp-applic-09.txt
> rfc3257.txt
> Or are you thinking about a different document?
> Best regards
> Michael
>
> On Dec 10, 2003, at 3:04 PM, Poetzl, Joachim wrote:
>
> > Hi all,
> >
> > what happened to and what is the status of the draft on Signaling
> > Architecture and Performance Requirements?
> >
> > Some help?
> >
> >
> >> Best Regards
> >>
> >> Joachim P=F6tzl
> > Deutsche Telekom AG
> > T-Com Zentrale
> > T332-4; Signalling, Gateways and Switching Systems
> > 64307 DARMSTADT, GERMANY
> > Phone:  +49 6151 83-2134
> > Fax:      +49 6151 83-4577
> > PCFax:  +49 521 52244 983
> >> mailto:joachim.poetzl@t-com.net
> >>
> >
> > _______________________________________________
> > 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 exim@www1.ietf.org  Wed Jan  7 10:49:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15996
	for <sigtran-archive@odin.ietf.org>; Wed, 7 Jan 2004 10:49:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeFvc-0001Go-2h
	for sigtran-archive@odin.ietf.org; Wed, 07 Jan 2004 10:49:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i07Fn4mj004863
	for sigtran-archive@odin.ietf.org; Wed, 7 Jan 2004 10:49:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeFvY-0001GF-Ra; Wed, 07 Jan 2004 10:49:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeFuz-0001EZ-Tw
	for sigtran@optimus.ietf.org; Wed, 07 Jan 2004 10:48:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15980
	for <sigtran@ietf.org>; Wed, 7 Jan 2004 10:48:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeFux-0001rW-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 10:48:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeFtd-0001lZ-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 10:47:02 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeFsE-0001a5-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 10:45:34 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i07FjXkH017175
	for <sigtran@ietf.org>; Wed, 7 Jan 2004 10:45:33 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Date: Wed, 7 Jan 2004 10:47:02 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOEEHOCDAA.barryn@adax.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
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M3UA: More redundant RKM error 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: 7bit

There is a redundant pair of REG REQ error codes in Section 4.4.1 of RFC
3332, for the case in which a reg req contains a routing key that already
exists at the SGP.

The 1st is from the original RFC:

"  If the SGP determines that a unique Routing Key cannot be created,
   the SGP returns a Registration Response message to the ASP, with a
   Registration Status of "Error - "Cannot Support Unique Routing". An
   incoming signalling message received at an SGP should not match
   against more than one Routing Key. "

The 2nd was added in the IG Rev 05:

"  If the SGP determines that the received RK was already registered,
   the SGP returns a Registration Response message to the ASP,
   containing a Registration Result "Error - Routing Key Already
   Registered". This error applies whether the Routing Key is Active or
   Inactive."

Perhaps the intention of IG Rev 05 was to distinguish between the event
where we have duplicate RKs, one of which was created statically and the
other dynamically (by using the 1st error code), and the event where we have
duplicate RKs, both of which were created dynamically (by using the 2nd
error code)?

If my guess is correct, then the description of the 1st error code must be
updated to reflect this restriction.

As it stands now, the SGP could correctly use either error code to describe
the case in which a reg req contains a routing key that already exists at
the SGP.



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



From exim@www1.ietf.org  Wed Jan  7 11:07:31 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16631
	for <sigtran-archive@odin.ietf.org>; Wed, 7 Jan 2004 11:07:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeGD2-0001pm-Q5
	for sigtran-archive@odin.ietf.org; Wed, 07 Jan 2004 11:07:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i07G74Pl007038
	for sigtran-archive@odin.ietf.org; Wed, 7 Jan 2004 11:07:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeGCz-0001oG-Jz; Wed, 07 Jan 2004 11:07:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeGC4-0001mU-IF
	for sigtran@optimus.ietf.org; Wed, 07 Jan 2004 11:06:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16560
	for <sigtran@ietf.org>; Wed, 7 Jan 2004 11:06:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeGC1-0002i4-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 11:06:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeGA8-0002ba-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 11:04:04 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeG8I-0002VX-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 11:02:10 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id LAA25992
	for <sigtran@ietf.org>; Wed, 7 Jan 2004 11:02:08 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Wed, 7 Jan 2004 11:01:19 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMCECFCDAA.asveren@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)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <JBECLENKLBCKAAKFGAJOEEHOCDAA.barryn@adax.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
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

Barry,

inline....
-Again as far as I remember ;) -

   Tolga

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> Barry Nagelberg
> Sent: Wednesday, January 07, 2004 10:47 AM
> To: SIGTRAN Mailing List
> Subject: [Sigtran] M3UA: More redundant RKM error codes
>
>
> There is a redundant pair of REG REQ error codes in Section 4.4.1 of RFC
> 3332, for the case in which a reg req contains a routing key that already
> exists at the SGP.
>
> The 1st is from the original RFC:
>
> "  If the SGP determines that a unique Routing Key cannot be created,
>    the SGP returns a Registration Response message to the ASP, with a
>    Registration Status of "Error - "Cannot Support Unique Routing". An
>    incoming signalling message received at an SGP should not match
>    against more than one Routing Key. "
[TOLGA] This I believe is mainly for the case, where the required RK
overlaps with an already existing one -but they are not the same, just
partially overlapping-.
>
> The 2nd was added in the IG Rev 05:
>
> "  If the SGP determines that the received RK was already registered,
>    the SGP returns a Registration Response message to the ASP,
>    containing a Registration Result "Error - Routing Key Already
>    Registered". This error applies whether the Routing Key is Active or
>    Inactive."
>
> Perhaps the intention of IG Rev 05 was to distinguish between the event
> where we have duplicate RKs, one of which was created statically and the
> other dynamically (by using the 1st error code), and the event
> where we have
> duplicate RKs, both of which were created dynamically (by using the 2nd
> error code)?
[TOLGA]I don't know, whether there is a real need to distinguish between
those two cases. But , as it is right know, I also would expect it to work
like you described. Maybe it is a better idea to use the second one, when
there isa full match -regardless dynamic or static- , and to use the first
one for partial overlapping -so, shall Ig be updated to make it work that
way, any ideas?-
>
> If my guess is correct, then the description of the 1st error code must be
> updated to reflect this restriction.
>
> As it stands now, the SGP could correctly use either error code
> to describe
> the case in which a reg req contains a routing key that already exists at
> the SGP.
>
>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


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



From exim@www1.ietf.org  Wed Jan  7 13:09:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22928
	for <sigtran-archive@odin.ietf.org>; Wed, 7 Jan 2004 13:09:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeI74-0000tV-MU
	for sigtran-archive@odin.ietf.org; Wed, 07 Jan 2004 13:09:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i07I92oq003431
	for sigtran-archive@odin.ietf.org; Wed, 7 Jan 2004 13:09:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeI73-0000t9-IU; Wed, 07 Jan 2004 13:09:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeI6A-0000oO-H2
	for sigtran@optimus.ietf.org; Wed, 07 Jan 2004 13:08:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22889
	for <sigtran@ietf.org>; Wed, 7 Jan 2004 13:08:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeI68-0003JX-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 13:08:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeI4I-0003Ev-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 13:06:11 -0500
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeI2a-00034x-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 13:04:24 -0500
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i07I3iOf006645;
	Wed, 7 Jan 2004 12:03:45 -0600 (CST)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id i07I3M1C024875;
	Wed, 7 Jan 2004 12:03:22 -0600 (CST)
Date: Wed, 7 Jan 2004 12:03:22 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: Tolga Asveren <asveren@ulticom.com>
cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
In-Reply-To: <GBEBKGPKHGPAOFCLBNAMCECFCDAA.asveren@ulticom.com>
Message-ID: <Pine.SOL.4.10.10401071057080.15162-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Tolga,

 Yes agree with you, Error - "Cannot Support Unique Routing" is used
 when there is a partial match and Error - "Routing Key Already
 Registered" is used when there is a full exact match irrespective of 
 static or dynamic registration.

 But there are some valid reasons for the introdcution of these 2nd
 error code.
 
 Scenario - Before introduction of Error - "Routing Key Already
                                                       Registered "
 -----------------------------------------------------------------
 Intially RFC supported only Error - "Cannot Support Unique Routing".
 Say an ASP1 registers RK1(OPC=*,DPC=x) with SGP1 then SS7 traffic
 is flowing between SGP1 and ASP1. Now same ASP1 further registers
 RK2(OPC=*,DPC=x,SI=ISUP) with same SGP1, but ASP1 receives the 
 Error - "Cannot Support Unique Routing" in the REG RESP message.
 The intention of RK2 is to support only ISUP ss7 traffic with DPC=x.

 But when ASP1 receives Error - "Cannot Support Unique Routing", 50%
 there is a possibility to assume that RK2 was already supported by
 SGP1 and it starts ss7 traffic assuming it is processing only ISUP
 traffic but that is totally false.

 So in order to avoid such confusions Error - "Routing Key Already
 Registered " was introduced which differentiates exact match and 
 partial match.

 This is what i understood.

--Samuel

 
 

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

On Wed, 7 Jan 2004, Tolga Asveren wrote:

> Barry,
> 
> inline....
> -Again as far as I remember ;) -
> 
>    Tolga
> 
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Barry Nagelberg
> > Sent: Wednesday, January 07, 2004 10:47 AM
> > To: SIGTRAN Mailing List
> > Subject: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > There is a redundant pair of REG REQ error codes in Section 4.4.1 of RFC
> > 3332, for the case in which a reg req contains a routing key that already
> > exists at the SGP.
> >
> > The 1st is from the original RFC:
> >
> > "  If the SGP determines that a unique Routing Key cannot be created,
> >    the SGP returns a Registration Response message to the ASP, with a
> >    Registration Status of "Error - "Cannot Support Unique Routing". An
> >    incoming signalling message received at an SGP should not match
> >    against more than one Routing Key. "
> [TOLGA] This I believe is mainly for the case, where the required RK
> overlaps with an already existing one -but they are not the same, just
> partially overlapping-.
> >
> > The 2nd was added in the IG Rev 05:
> >
> > "  If the SGP determines that the received RK was already registered,
> >    the SGP returns a Registration Response message to the ASP,
> >    containing a Registration Result "Error - Routing Key Already
> >    Registered". This error applies whether the Routing Key is Active or
> >    Inactive."
> >
> > Perhaps the intention of IG Rev 05 was to distinguish between the event
> > where we have duplicate RKs, one of which was created statically and the
> > other dynamically (by using the 1st error code), and the event
> > where we have
> > duplicate RKs, both of which were created dynamically (by using the 2nd
> > error code)?
> [TOLGA]I don't know, whether there is a real need to distinguish between
> those two cases. But , as it is right know, I also would expect it to work
> like you described. Maybe it is a better idea to use the second one, when
> there isa full match -regardless dynamic or static- , and to use the first
> one for partial overlapping -so, shall Ig be updated to make it work that
> way, any ideas?-
> >
> > If my guess is correct, then the description of the 1st error code must be
> > updated to reflect this restriction.
> >
> > As it stands now, the SGP could correctly use either error code
> > to describe
> > the case in which a reg req contains a routing key that already exists at
> > the SGP.
> >
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 


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



From exim@www1.ietf.org  Wed Jan  7 13:19:29 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23299
	for <sigtran-archive@odin.ietf.org>; Wed, 7 Jan 2004 13:19:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeIGk-0001Po-8m
	for sigtran-archive@odin.ietf.org; Wed, 07 Jan 2004 13:19:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i07IJ1jU005413
	for sigtran-archive@odin.ietf.org; Wed, 7 Jan 2004 13:19:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeIGj-0001Os-6G; Wed, 07 Jan 2004 13:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeIFx-0001O1-C4
	for sigtran@optimus.ietf.org; Wed, 07 Jan 2004 13:18:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23260
	for <sigtran@ietf.org>; Wed, 7 Jan 2004 13:18:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeIFl-0003ia-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 13:18:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeIC5-0003e4-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 13:14:14 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeIAZ-0003aS-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 13:12:39 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id NAA01806;
	Wed, 7 Jan 2004 13:12:32 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Wed, 7 Jan 2004 13:11:43 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMCECGCDAA.asveren@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)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <Pine.SOL.4.10.10401071057080.15162-100000@sun2685.ssd.usa.alcatel.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
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

Samuel,

> -----Original Message-----
> From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> Sent: Wednesday, January 07, 2004 1:03 PM
> To: Tolga Asveren
> Cc: SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
>
>
>
> Tolga,
>
>  Yes agree with you, Error - "Cannot Support Unique Routing" is used
>  when there is a partial match and Error - "Routing Key Already
>  Registered" is used when there is a full exact match irrespective of
>  static or dynamic registration.
>
>  But there are some valid reasons for the introdcution of these 2nd
>  error code.
[TOLGA] I don't propose to remove the second error code, just make it more
clear that it works like you also described above. Currently, IMO, it is not
very clear.
>
>  Scenario - Before introduction of Error - "Routing Key Already
>                                                        Registered "
>  -----------------------------------------------------------------
>  Intially RFC supported only Error - "Cannot Support Unique Routing".
>  Say an ASP1 registers RK1(OPC=*,DPC=x) with SGP1 then SS7 traffic
>  is flowing between SGP1 and ASP1. Now same ASP1 further registers
>  RK2(OPC=*,DPC=x,SI=ISUP) with same SGP1, but ASP1 receives the
>  Error - "Cannot Support Unique Routing" in the REG RESP message.
>  The intention of RK2 is to support only ISUP ss7 traffic with DPC=x.
>
>  But when ASP1 receives Error - "Cannot Support Unique Routing", 50%
>  there is a possibility to assume that RK2 was already supported by
>  SGP1 and it starts ss7 traffic assuming it is processing only ISUP
>  traffic but that is totally false.
[TOLGA]I would think, this is not a clever choice in any case. ASP1 does not
know the corresponding RC -REG RSP has RC=0, if the result is error-. So, it
can't activate RK, or can fill RC into DATA properly. So, from protocol
point of view, -at least for now- I can't see a direct use of distinguishing
between those two cases but from administration point of view, it makes
sense to me.
>
>  So in order to avoid such confusions Error - "Routing Key Already
>  Registered " was introduced which differentiates exact match and
>  partial match.
>
>  This is what i understood.
>
> --Samuel
>
>
>
>
>   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA,
> Inc. *******
>
> On Wed, 7 Jan 2004, Tolga Asveren wrote:
>
> > Barry,
> >
> > inline....
> > -Again as far as I remember ;) -
> >
> >    Tolga
> >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > Barry Nagelberg
> > > Sent: Wednesday, January 07, 2004 10:47 AM
> > > To: SIGTRAN Mailing List
> > > Subject: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > There is a redundant pair of REG REQ error codes in Section
> 4.4.1 of RFC
> > > 3332, for the case in which a reg req contains a routing key
> that already
> > > exists at the SGP.
> > >
> > > The 1st is from the original RFC:
> > >
> > > "  If the SGP determines that a unique Routing Key cannot be created,
> > >    the SGP returns a Registration Response message to the ASP, with a
> > >    Registration Status of "Error - "Cannot Support Unique Routing". An
> > >    incoming signalling message received at an SGP should not match
> > >    against more than one Routing Key. "
> > [TOLGA] This I believe is mainly for the case, where the required RK
> > overlaps with an already existing one -but they are not the same, just
> > partially overlapping-.
> > >
> > > The 2nd was added in the IG Rev 05:
> > >
> > > "  If the SGP determines that the received RK was already registered,
> > >    the SGP returns a Registration Response message to the ASP,
> > >    containing a Registration Result "Error - Routing Key Already
> > >    Registered". This error applies whether the Routing Key is
> Active or
> > >    Inactive."
> > >
> > > Perhaps the intention of IG Rev 05 was to distinguish between
> the event
> > > where we have duplicate RKs, one of which was created
> statically and the
> > > other dynamically (by using the 1st error code), and the event
> > > where we have
> > > duplicate RKs, both of which were created dynamically (by
> using the 2nd
> > > error code)?
> > [TOLGA]I don't know, whether there is a real need to distinguish between
> > those two cases. But , as it is right know, I also would expect
> it to work
> > like you described. Maybe it is a better idea to use the second
> one, when
> > there isa full match -regardless dynamic or static- , and to
> use the first
> > one for partial overlapping -so, shall Ig be updated to make it
> work that
> > way, any ideas?-
> > >
> > > If my guess is correct, then the description of the 1st error
> code must be
> > > updated to reflect this restriction.
> > >
> > > As it stands now, the SGP could correctly use either error code
> > > to describe
> > > the case in which a reg req contains a routing key that
> already exists at
> > > the SGP.
> > >
> > >
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >
>


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



From exim@www1.ietf.org  Wed Jan  7 13:57:33 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24614
	for <sigtran-archive@odin.ietf.org>; Wed, 7 Jan 2004 13:57:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeIrZ-0003a7-GA
	for sigtran-archive@odin.ietf.org; Wed, 07 Jan 2004 13:57:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i07Iv5sc013761
	for sigtran-archive@odin.ietf.org; Wed, 7 Jan 2004 13:57:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeIrV-0003ZN-GB; Wed, 07 Jan 2004 13:57:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeIqh-0003Ys-Uk
	for sigtran@optimus.ietf.org; Wed, 07 Jan 2004 13:56:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24600
	for <sigtran@ietf.org>; Wed, 7 Jan 2004 13:56:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeIqf-0005Ne-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 13:56:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeIot-0005Kd-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 13:54:20 -0500
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeInz-0005H8-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 13:53:23 -0500
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i07IqjOh013381;
	Wed, 7 Jan 2004 12:52:46 -0600 (CST)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id i07IqB1C004425;
	Wed, 7 Jan 2004 12:52:11 -0600 (CST)
Date: Wed, 7 Jan 2004 12:52:11 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: Tolga Asveren <asveren@ulticom.com>
cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
In-Reply-To: <GBEBKGPKHGPAOFCLBNAMCECGCDAA.asveren@ulticom.com>
Message-ID: <Pine.SOL.4.10.10401071248480.15162-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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,

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

On Wed, 7 Jan 2004, Tolga Asveren wrote:

> Samuel,
> 
> > -----Original Message-----
> > From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> > Sent: Wednesday, January 07, 2004 1:03 PM
> > To: Tolga Asveren
> > Cc: SIGTRAN Mailing List
> > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> >
> > Tolga,
> >
> >  Yes agree with you, Error - "Cannot Support Unique Routing" is used
> >  when there is a partial match and Error - "Routing Key Already
> >  Registered" is used when there is a full exact match irrespective of
> >  static or dynamic registration.
> >
> >  But there are some valid reasons for the introdcution of these 2nd
> >  error code.
> [TOLGA] I don't propose to remove the second error code, just make it more
> clear that it works like you also described above. Currently, IMO, it is not
> very clear.
> >
> >  Scenario - Before introduction of Error - "Routing Key Already
> >                                                        Registered "
> >  -----------------------------------------------------------------
> >  Intially RFC supported only Error - "Cannot Support Unique Routing".
> >  Say an ASP1 registers RK1(OPC=*,DPC=x) with SGP1 then SS7 traffic
> >  is flowing between SGP1 and ASP1. Now same ASP1 further registers
> >  RK2(OPC=*,DPC=x,SI=ISUP) with same SGP1, but ASP1 receives the
> >  Error - "Cannot Support Unique Routing" in the REG RESP message.
> >  The intention of RK2 is to support only ISUP ss7 traffic with DPC=x.
> >
> >  But when ASP1 receives Error - "Cannot Support Unique Routing", 50%
> >  there is a possibility to assume that RK2 was already supported by
> >  SGP1 and it starts ss7 traffic assuming it is processing only ISUP
> >  traffic but that is totally false.
> [TOLGA]I would think, this is not a clever choice in any case. ASP1 does not
> know the corresponding RC -REG RSP has RC=0, if the result is error-. So, it
> can't activate RK, or can fill RC into DATA properly. So, from protocol
> point of view, -at least for now- I can't see a direct use of distinguishing
> between those two cases but from administration point of view, it makes
> sense to me.
> >

If ASP1 does not know the RC, How is going to de-register RK1 to
register RK2?

--Samuel
> >  So in order to avoid such confusions Error - "Routing Key Already
> >  Registered " was introduced which differentiates exact match and
> >  partial match.
> >
> >  This is what i understood.
> >
> > --Samuel
> >
> >
> >
> >
> >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA,
> > Inc. *******
> >
> > On Wed, 7 Jan 2004, Tolga Asveren wrote:
> >
> > > Barry,
> > >
> > > inline....
> > > -Again as far as I remember ;) -
> > >
> > >    Tolga
> > >
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > Barry Nagelberg
> > > > Sent: Wednesday, January 07, 2004 10:47 AM
> > > > To: SIGTRAN Mailing List
> > > > Subject: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > There is a redundant pair of REG REQ error codes in Section
> > 4.4.1 of RFC
> > > > 3332, for the case in which a reg req contains a routing key
> > that already
> > > > exists at the SGP.
> > > >
> > > > The 1st is from the original RFC:
> > > >
> > > > "  If the SGP determines that a unique Routing Key cannot be created,
> > > >    the SGP returns a Registration Response message to the ASP, with a
> > > >    Registration Status of "Error - "Cannot Support Unique Routing". An
> > > >    incoming signalling message received at an SGP should not match
> > > >    against more than one Routing Key. "
> > > [TOLGA] This I believe is mainly for the case, where the required RK
> > > overlaps with an already existing one -but they are not the same, just
> > > partially overlapping-.
> > > >
> > > > The 2nd was added in the IG Rev 05:
> > > >
> > > > "  If the SGP determines that the received RK was already registered,
> > > >    the SGP returns a Registration Response message to the ASP,
> > > >    containing a Registration Result "Error - Routing Key Already
> > > >    Registered". This error applies whether the Routing Key is
> > Active or
> > > >    Inactive."
> > > >
> > > > Perhaps the intention of IG Rev 05 was to distinguish between
> > the event
> > > > where we have duplicate RKs, one of which was created
> > statically and the
> > > > other dynamically (by using the 1st error code), and the event
> > > > where we have
> > > > duplicate RKs, both of which were created dynamically (by
> > using the 2nd
> > > > error code)?
> > > [TOLGA]I don't know, whether there is a real need to distinguish between
> > > those two cases. But , as it is right know, I also would expect
> > it to work
> > > like you described. Maybe it is a better idea to use the second
> > one, when
> > > there isa full match -regardless dynamic or static- , and to
> > use the first
> > > one for partial overlapping -so, shall Ig be updated to make it
> > work that
> > > way, any ideas?-
> > > >
> > > > If my guess is correct, then the description of the 1st error
> > code must be
> > > > updated to reflect this restriction.
> > > >
> > > > As it stands now, the SGP could correctly use either error code
> > > > to describe
> > > > the case in which a reg req contains a routing key that
> > already exists at
> > > > the SGP.
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > 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 exim@www1.ietf.org  Wed Jan  7 14:03:29 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24766
	for <sigtran-archive@odin.ietf.org>; Wed, 7 Jan 2004 14:03:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeIxJ-0003mf-K3
	for sigtran-archive@odin.ietf.org; Wed, 07 Jan 2004 14:03:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i07J31KX014532
	for sigtran-archive@odin.ietf.org; Wed, 7 Jan 2004 14:03:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeIxJ-0003m0-2B; Wed, 07 Jan 2004 14:03:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeIwV-0003kc-PF
	for sigtran@optimus.ietf.org; Wed, 07 Jan 2004 14:02:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24746
	for <sigtran@ietf.org>; Wed, 7 Jan 2004 14:02:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeIwT-0005an-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 14:02:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeIue-0005XG-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 14:00:17 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeItk-0005TQ-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 13:59:20 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id NAA14291;
	Wed, 7 Jan 2004 13:59:17 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Wed, 7 Jan 2004 13:58:27 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMAECHCDAA.asveren@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)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <Pine.SOL.4.10.10401071248480.15162-100000@sun2685.ssd.usa.alcatel.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
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

inline....

> -----Original Message-----
> From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> Sent: Wednesday, January 07, 2004 1:52 PM
> To: Tolga Asveren
> Cc: SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
>
>
>
> 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 Wed, 7 Jan 2004, Tolga Asveren wrote:
>
> > Samuel,
> >
> > > -----Original Message-----
> > > From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> > > Sent: Wednesday, January 07, 2004 1:03 PM
> > > To: Tolga Asveren
> > > Cc: SIGTRAN Mailing List
> > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > >
> > > Tolga,
> > >
> > >  Yes agree with you, Error - "Cannot Support Unique Routing" is used
> > >  when there is a partial match and Error - "Routing Key Already
> > >  Registered" is used when there is a full exact match irrespective of
> > >  static or dynamic registration.
> > >
> > >  But there are some valid reasons for the introdcution of these 2nd
> > >  error code.
> > [TOLGA] I don't propose to remove the second error code, just
> make it more
> > clear that it works like you also described above. Currently,
> IMO, it is not
> > very clear.
> > >
> > >  Scenario - Before introduction of Error - "Routing Key Already
> > >                                                        Registered "
> > >  -----------------------------------------------------------------
> > >  Intially RFC supported only Error - "Cannot Support Unique Routing".
> > >  Say an ASP1 registers RK1(OPC=*,DPC=x) with SGP1 then SS7 traffic
> > >  is flowing between SGP1 and ASP1. Now same ASP1 further registers
> > >  RK2(OPC=*,DPC=x,SI=ISUP) with same SGP1, but ASP1 receives the
> > >  Error - "Cannot Support Unique Routing" in the REG RESP message.
> > >  The intention of RK2 is to support only ISUP ss7 traffic with DPC=x.
> > >
> > >  But when ASP1 receives Error - "Cannot Support Unique Routing", 50%
> > >  there is a possibility to assume that RK2 was already supported by
> > >  SGP1 and it starts ss7 traffic assuming it is processing only ISUP
> > >  traffic but that is totally false.
> > [TOLGA]I would think, this is not a clever choice in any case.
> ASP1 does not
> > know the corresponding RC -REG RSP has RC=0, if the result is
> error-. So, it
> > can't activate RK, or can fill RC into DATA properly. So, from protocol
> > point of view, -at least for now- I can't see a direct use of
> distinguishing
> > between those two cases but from administration point of view, it makes
> > sense to me.
> > >
>
> If ASP1 does not know the RC, How is going to de-register RK1 to
> register RK2?
[TOLGA]Yes, for the "already registered case" it should know this. In fact,
"already registered" case does not make sense at all, because it means ASP
already knows that it has registered for this RK, why should it need
asistance from SG?. "Overlap error" makes sense, because some other ASP
might have registered with an overlapping RK.
>
> --Samuel
> > >  So in order to avoid such confusions Error - "Routing Key Already
> > >  Registered " was introduced which differentiates exact match and
> > >  partial match.
> > >
> > >  This is what i understood.
> > >
> > > --Samuel
> > >
> > >
> > >
> > >
> > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA,
> > > Inc. *******
> > >
> > > On Wed, 7 Jan 2004, Tolga Asveren wrote:
> > >
> > > > Barry,
> > > >
> > > > inline....
> > > > -Again as far as I remember ;) -
> > > >
> > > >    Tolga
> > > >
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > Barry Nagelberg
> > > > > Sent: Wednesday, January 07, 2004 10:47 AM
> > > > > To: SIGTRAN Mailing List
> > > > > Subject: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > There is a redundant pair of REG REQ error codes in Section
> > > 4.4.1 of RFC
> > > > > 3332, for the case in which a reg req contains a routing key
> > > that already
> > > > > exists at the SGP.
> > > > >
> > > > > The 1st is from the original RFC:
> > > > >
> > > > > "  If the SGP determines that a unique Routing Key cannot
> be created,
> > > > >    the SGP returns a Registration Response message to the
> ASP, with a
> > > > >    Registration Status of "Error - "Cannot Support Unique
> Routing". An
> > > > >    incoming signalling message received at an SGP should not match
> > > > >    against more than one Routing Key. "
> > > > [TOLGA] This I believe is mainly for the case, where the required RK
> > > > overlaps with an already existing one -but they are not the
> same, just
> > > > partially overlapping-.
> > > > >
> > > > > The 2nd was added in the IG Rev 05:
> > > > >
> > > > > "  If the SGP determines that the received RK was already
> registered,
> > > > >    the SGP returns a Registration Response message to the ASP,
> > > > >    containing a Registration Result "Error - Routing Key Already
> > > > >    Registered". This error applies whether the Routing Key is
> > > Active or
> > > > >    Inactive."
> > > > >
> > > > > Perhaps the intention of IG Rev 05 was to distinguish between
> > > the event
> > > > > where we have duplicate RKs, one of which was created
> > > statically and the
> > > > > other dynamically (by using the 1st error code), and the event
> > > > > where we have
> > > > > duplicate RKs, both of which were created dynamically (by
> > > using the 2nd
> > > > > error code)?
> > > > [TOLGA]I don't know, whether there is a real need to
> distinguish between
> > > > those two cases. But , as it is right know, I also would expect
> > > it to work
> > > > like you described. Maybe it is a better idea to use the second
> > > one, when
> > > > there isa full match -regardless dynamic or static- , and to
> > > use the first
> > > > one for partial overlapping -so, shall Ig be updated to make it
> > > work that
> > > > way, any ideas?-
> > > > >
> > > > > If my guess is correct, then the description of the 1st error
> > > code must be
> > > > > updated to reflect this restriction.
> > > > >
> > > > > As it stands now, the SGP could correctly use either error code
> > > > > to describe
> > > > > the case in which a reg req contains a routing key that
> > > already exists at
> > > > > the SGP.
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > 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 exim@www1.ietf.org  Wed Jan  7 14:09:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25043
	for <sigtran-archive@odin.ietf.org>; Wed, 7 Jan 2004 14:09:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeJ38-0004Om-Kk
	for sigtran-archive@odin.ietf.org; Wed, 07 Jan 2004 14:09:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i07J92n4016889
	for sigtran-archive@odin.ietf.org; Wed, 7 Jan 2004 14:09:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeJ38-0004OD-2M; Wed, 07 Jan 2004 14:09:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeJ2P-0004KI-8V
	for sigtran@optimus.ietf.org; Wed, 07 Jan 2004 14:08:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24958
	for <sigtran@ietf.org>; Wed, 7 Jan 2004 14:08:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeJ2M-0005ul-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 14:08:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeJ0c-0005nP-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 14:06:27 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeIyh-0005iU-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 14:04:27 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i07J4QkH017731
	for <sigtran@ietf.org>; Wed, 7 Jan 2004 14:04:26 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Wed, 7 Jan 2004 14:05:55 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOAEICCDAA.barryn@adax.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)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <Pine.SOL.4.10.10401071057080.15162-100000@sun2685.ssd.usa.alcatel.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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

OK, I now understand the difference, and I agree with Tolga and Samuel.
But the text, as it is now, is confusing. I suggest the following changes:

1st error code:

"  If the SGP determines that the requested RK partially,
   but not exactly, matches an existing RK, and that an
   incoming signalling message received at an SGP could possibly match
   both the requested and the existing RK,
   the SGP returns a Registration Response message to the ASP, with a
   Registration Status of "Error - "Cannot Support Unique Routing"."

2nd error code:

"  If the SGP determines that the requested RK was already registered
   fully and exactly, either statically or dynamically, by the sending ASP,
   the SGP returns a Registration Response message to the ASP,
   containing a Registration Result "Error - Routing Key Already
   Registered ". This error applies whether the Routing Key is Active or
   Inactive."

Barry Nagelberg

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> Samuel Dur D. Jeyaseelan
> Sent: Wednesday, January 07, 2004 1:03 PM
> To: Tolga Asveren
> Cc: SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
>
>
>
> Tolga,
>
>  Yes agree with you, Error - "Cannot Support Unique Routing" is used
>  when there is a partial match and Error - "Routing Key Already
>  Registered" is used when there is a full exact match irrespective of
>  static or dynamic registration.
>
>  But there are some valid reasons for the introdcution of these 2nd
>  error code.
>
>  Scenario - Before introduction of Error - "Routing Key Already
>                                                        Registered "
>  -----------------------------------------------------------------
>  Intially RFC supported only Error - "Cannot Support Unique Routing".
>  Say an ASP1 registers RK1(OPC=*,DPC=x) with SGP1 then SS7 traffic
>  is flowing between SGP1 and ASP1. Now same ASP1 further registers
>  RK2(OPC=*,DPC=x,SI=ISUP) with same SGP1, but ASP1 receives the
>  Error - "Cannot Support Unique Routing" in the REG RESP message.
>  The intention of RK2 is to support only ISUP ss7 traffic with DPC=x.
>
>  But when ASP1 receives Error - "Cannot Support Unique Routing", 50%
>  there is a possibility to assume that RK2 was already supported by
>  SGP1 and it starts ss7 traffic assuming it is processing only ISUP
>  traffic but that is totally false.
>
>  So in order to avoid such confusions Error - "Routing Key Already
>  Registered " was introduced which differentiates exact match and
>  partial match.
>
>  This is what i understood.
>
> --Samuel
>
>
>
>
>   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA,
> Inc. *******
>
> On Wed, 7 Jan 2004, Tolga Asveren wrote:
>
> > Barry,
> >
> > inline....
> > -Again as far as I remember ;) -
> >
> >    Tolga
> >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > Barry Nagelberg
> > > Sent: Wednesday, January 07, 2004 10:47 AM
> > > To: SIGTRAN Mailing List
> > > Subject: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > There is a redundant pair of REG REQ error codes in Section
> 4.4.1 of RFC
> > > 3332, for the case in which a reg req contains a routing key
> that already
> > > exists at the SGP.
> > >
> > > The 1st is from the original RFC:
> > >
> > > "  If the SGP determines that a unique Routing Key cannot be created,
> > >    the SGP returns a Registration Response message to the ASP, with a
> > >    Registration Status of "Error - "Cannot Support Unique Routing". An
> > >    incoming signalling message received at an SGP should not match
> > >    against more than one Routing Key. "
> > [TOLGA] This I believe is mainly for the case, where the required RK
> > overlaps with an already existing one -but they are not the same, just
> > partially overlapping-.
> > >
> > > The 2nd was added in the IG Rev 05:
> > >
> > > "  If the SGP determines that the received RK was already registered,
> > >    the SGP returns a Registration Response message to the ASP,
> > >    containing a Registration Result "Error - Routing Key Already
> > >    Registered". This error applies whether the Routing Key is
> Active or
> > >    Inactive."
> > >
> > > Perhaps the intention of IG Rev 05 was to distinguish between
> the event
> > > where we have duplicate RKs, one of which was created
> statically and the
> > > other dynamically (by using the 1st error code), and the event
> > > where we have
> > > duplicate RKs, both of which were created dynamically (by
> using the 2nd
> > > error code)?
> > [TOLGA]I don't know, whether there is a real need to distinguish between
> > those two cases. But , as it is right know, I also would expect
> it to work
> > like you described. Maybe it is a better idea to use the second
> one, when
> > there isa full match -regardless dynamic or static- , and to
> use the first
> > one for partial overlapping -so, shall Ig be updated to make it
> work that
> > way, any ideas?-
> > >
> > > If my guess is correct, then the description of the 1st error
> code must be
> > > updated to reflect this restriction.
> > >
> > > As it stands now, the SGP could correctly use either error code
> > > to describe
> > > the case in which a reg req contains a routing key that
> already exists at
> > > the SGP.
> > >


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



From exim@www1.ietf.org  Wed Jan  7 15:43:33 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29993
	for <sigtran-archive@odin.ietf.org>; Wed, 7 Jan 2004 15:43:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeKW8-00089k-99
	for sigtran-archive@odin.ietf.org; Wed, 07 Jan 2004 15:43:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i07Kh4ZW031348
	for sigtran-archive@odin.ietf.org; Wed, 7 Jan 2004 15:43:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeKW6-00089P-7i; Wed, 07 Jan 2004 15:43:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeKVU-00088E-2G
	for sigtran@optimus.ietf.org; Wed, 07 Jan 2004 15:42:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29952
	for <sigtran@ietf.org>; Wed, 7 Jan 2004 15:42:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeKVS-0002NR-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 15:42:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeKTr-0002I0-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 15:40:44 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeKSq-00029n-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 15:39:40 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id PAA12731
	for <sigtran@ietf.org>; Wed, 7 Jan 2004 15:39:35 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Wed, 7 Jan 2004 15:38:44 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMIECHCDAA.asveren@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)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <JBECLENKLBCKAAKFGAJOAEICCDAA.barryn@adax.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
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

Just one more thought below...

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> Barry Nagelberg
> Sent: Wednesday, January 07, 2004 2:06 PM
> To: SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
>
>
> OK, I now understand the difference, and I agree with Tolga and Samuel.
> But the text, as it is now, is confusing. I suggest the following changes:
>
> 1st error code:
>
> "  If the SGP determines that the requested RK partially,
>    but not exactly, matches an existing RK, and that an
>    incoming signalling message received at an SGP could possibly match
>    both the requested and the existing RK,
>    the SGP returns a Registration Response message to the ASP, with a
>    Registration Status of "Error - "Cannot Support Unique Routing"."
>
> 2nd error code:
>
> "  If the SGP determines that the requested RK was already registered
>    fully and exactly, either statically or dynamically, by the
> sending ASP,
>    the SGP returns a Registration Response message to the ASP,
>    containing a Registration Result "Error - Routing Key Already
>    Registered ". This error applies whether the Routing Key is Active or
>    Inactive."
[TOLGA]Although I don't see significant practical use of this error code,
still if we want it then at least let's make it a bit more usefull -or maybe
just discard it?-, by including actual RC in the REG-RESP, so that ASP does
not need to figure it out by itself:
"For this error code, RC field in Registration REsponse message MUST be
populated with the actual value of RC in SGP corresponding to the specified
RK in Registration Request message"
>
> Barry Nagelberg
>
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Samuel Dur D. Jeyaseelan
> > Sent: Wednesday, January 07, 2004 1:03 PM
> > To: Tolga Asveren
> > Cc: SIGTRAN Mailing List
> > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> >
> > Tolga,
> >
> >  Yes agree with you, Error - "Cannot Support Unique Routing" is used
> >  when there is a partial match and Error - "Routing Key Already
> >  Registered" is used when there is a full exact match irrespective of
> >  static or dynamic registration.
> >
> >  But there are some valid reasons for the introdcution of these 2nd
> >  error code.
> >
> >  Scenario - Before introduction of Error - "Routing Key Already
> >                                                        Registered "
> >  -----------------------------------------------------------------
> >  Intially RFC supported only Error - "Cannot Support Unique Routing".
> >  Say an ASP1 registers RK1(OPC=*,DPC=x) with SGP1 then SS7 traffic
> >  is flowing between SGP1 and ASP1. Now same ASP1 further registers
> >  RK2(OPC=*,DPC=x,SI=ISUP) with same SGP1, but ASP1 receives the
> >  Error - "Cannot Support Unique Routing" in the REG RESP message.
> >  The intention of RK2 is to support only ISUP ss7 traffic with DPC=x.
> >
> >  But when ASP1 receives Error - "Cannot Support Unique Routing", 50%
> >  there is a possibility to assume that RK2 was already supported by
> >  SGP1 and it starts ss7 traffic assuming it is processing only ISUP
> >  traffic but that is totally false.
> >
> >  So in order to avoid such confusions Error - "Routing Key Already
> >  Registered " was introduced which differentiates exact match and
> >  partial match.
> >
> >  This is what i understood.
> >
> > --Samuel
> >
> >
> >
> >
> >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA,
> > Inc. *******
> >
> > On Wed, 7 Jan 2004, Tolga Asveren wrote:
> >
> > > Barry,
> > >
> > > inline....
> > > -Again as far as I remember ;) -
> > >
> > >    Tolga
> > >
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > Barry Nagelberg
> > > > Sent: Wednesday, January 07, 2004 10:47 AM
> > > > To: SIGTRAN Mailing List
> > > > Subject: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > There is a redundant pair of REG REQ error codes in Section
> > 4.4.1 of RFC
> > > > 3332, for the case in which a reg req contains a routing key
> > that already
> > > > exists at the SGP.
> > > >
> > > > The 1st is from the original RFC:
> > > >
> > > > "  If the SGP determines that a unique Routing Key cannot
> be created,
> > > >    the SGP returns a Registration Response message to the
> ASP, with a
> > > >    Registration Status of "Error - "Cannot Support Unique
> Routing". An
> > > >    incoming signalling message received at an SGP should not match
> > > >    against more than one Routing Key. "
> > > [TOLGA] This I believe is mainly for the case, where the required RK
> > > overlaps with an already existing one -but they are not the same, just
> > > partially overlapping-.
> > > >
> > > > The 2nd was added in the IG Rev 05:
> > > >
> > > > "  If the SGP determines that the received RK was already
> registered,
> > > >    the SGP returns a Registration Response message to the ASP,
> > > >    containing a Registration Result "Error - Routing Key Already
> > > >    Registered". This error applies whether the Routing Key is
> > Active or
> > > >    Inactive."
> > > >
> > > > Perhaps the intention of IG Rev 05 was to distinguish between
> > the event
> > > > where we have duplicate RKs, one of which was created
> > statically and the
> > > > other dynamically (by using the 1st error code), and the event
> > > > where we have
> > > > duplicate RKs, both of which were created dynamically (by
> > using the 2nd
> > > > error code)?
> > > [TOLGA]I don't know, whether there is a real need to
> distinguish between
> > > those two cases. But , as it is right know, I also would expect
> > it to work
> > > like you described. Maybe it is a better idea to use the second
> > one, when
> > > there isa full match -regardless dynamic or static- , and to
> > use the first
> > > one for partial overlapping -so, shall Ig be updated to make it
> > work that
> > > way, any ideas?-
> > > >
> > > > If my guess is correct, then the description of the 1st error
> > code must be
> > > > updated to reflect this restriction.
> > > >
> > > > As it stands now, the SGP could correctly use either error code
> > > > to describe
> > > > the case in which a reg req contains a routing key that
> > already exists at
> > > > the SGP.
> > > >
>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


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



From exim@www1.ietf.org  Wed Jan  7 15:57:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00939
	for <sigtran-archive@odin.ietf.org>; Wed, 7 Jan 2004 15:57:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeKje-0000RY-9f
	for sigtran-archive@odin.ietf.org; Wed, 07 Jan 2004 15:57:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i07Kv2qe001688
	for sigtran-archive@odin.ietf.org; Wed, 7 Jan 2004 15:57:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeKjd-0000R7-Of; Wed, 07 Jan 2004 15:57:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeKj2-0000Q4-9P
	for sigtran@optimus.ietf.org; Wed, 07 Jan 2004 15:56:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00889
	for <sigtran@ietf.org>; Wed, 7 Jan 2004 15:56:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeKj0-0003Fi-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 15:56:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeKhU-0003AV-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 15:54:49 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[BI0l32ldWMMmHiIyKx3ae/mO9gUaKpso])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeKfl-0002zx-00
	for sigtran@ietf.org; Wed, 07 Jan 2004 15:53:01 -0500
Received: from ns.pigworks.openss7.net (IDENT:cehtjT0Hra7gH+if6a8oC9+wxAnhRctQ@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i07KqtI03140;
	Wed, 7 Jan 2004 13:52:55 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i07Kqss27186;
	Wed, 7 Jan 2004 13:52:54 -0700
Date: Wed, 7 Jan 2004 13:52:54 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <asveren@ulticom.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
Message-ID: <20040107135254.A26539@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <asveren@ulticom.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <JBECLENKLBCKAAKFGAJOAEICCDAA.barryn@adax.com> <GBEBKGPKHGPAOFCLBNAMIECHCDAA.asveren@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: <GBEBKGPKHGPAOFCLBNAMIECHCDAA.asveren@ulticom.com>; from asveren@ulticom.com on Wed, Jan 07, 2004 at 03:38:44PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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,

IIRC it was for faulty implementations that lose the REG RESP.

--brian

Tolga Asveren wrote:                                                                 (Wed, 07 Jan 2004 15:38:44)
> Just one more thought below...
> 
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Barry Nagelberg
> > Sent: Wednesday, January 07, 2004 2:06 PM
> > To: SIGTRAN Mailing List
> > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > OK, I now understand the difference, and I agree with Tolga and Samuel.
> > But the text, as it is now, is confusing. I suggest the following changes:
> >
> > 1st error code:
> >
> > "  If the SGP determines that the requested RK partially,
> >    but not exactly, matches an existing RK, and that an
> >    incoming signalling message received at an SGP could possibly match
> >    both the requested and the existing RK,
> >    the SGP returns a Registration Response message to the ASP, with a
> >    Registration Status of "Error - "Cannot Support Unique Routing"."
> >
> > 2nd error code:
> >
> > "  If the SGP determines that the requested RK was already registered
> >    fully and exactly, either statically or dynamically, by the
> > sending ASP,
> >    the SGP returns a Registration Response message to the ASP,
> >    containing a Registration Result "Error - Routing Key Already
> >    Registered ". This error applies whether the Routing Key is Active or
> >    Inactive."
> [TOLGA]Although I don't see significant practical use of this error code,
> still if we want it then at least let's make it a bit more usefull -or maybe
> just discard it?-, by including actual RC in the REG-RESP, so that ASP does
> not need to figure it out by itself:
> "For this error code, RC field in Registration REsponse message MUST be
> populated with the actual value of RC in SGP corresponding to the specified
> RK in Registration Request message"
> >
> > Barry Nagelberg
> >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > Samuel Dur D. Jeyaseelan
> > > Sent: Wednesday, January 07, 2004 1:03 PM
> > > To: Tolga Asveren
> > > Cc: SIGTRAN Mailing List
> > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > >
> > > Tolga,
> > >
> > >  Yes agree with you, Error - "Cannot Support Unique Routing" is used
> > >  when there is a partial match and Error - "Routing Key Already
> > >  Registered" is used when there is a full exact match irrespective of
> > >  static or dynamic registration.
> > >
> > >  But there are some valid reasons for the introdcution of these 2nd
> > >  error code.
> > >
> > >  Scenario - Before introduction of Error - "Routing Key Already
> > >                                                        Registered "
> > >  -----------------------------------------------------------------
> > >  Intially RFC supported only Error - "Cannot Support Unique Routing".
> > >  Say an ASP1 registers RK1(OPC=*,DPC=x) with SGP1 then SS7 traffic
> > >  is flowing between SGP1 and ASP1. Now same ASP1 further registers
> > >  RK2(OPC=*,DPC=x,SI=ISUP) with same SGP1, but ASP1 receives the
> > >  Error - "Cannot Support Unique Routing" in the REG RESP message.
> > >  The intention of RK2 is to support only ISUP ss7 traffic with DPC=x.
> > >
> > >  But when ASP1 receives Error - "Cannot Support Unique Routing", 50%
> > >  there is a possibility to assume that RK2 was already supported by
> > >  SGP1 and it starts ss7 traffic assuming it is processing only ISUP
> > >  traffic but that is totally false.
> > >
> > >  So in order to avoid such confusions Error - "Routing Key Already
> > >  Registered " was introduced which differentiates exact match and
> > >  partial match.
> > >
> > >  This is what i understood.
> > >
> > > --Samuel
> > >
> > >
> > >
> > >
> > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA,
> > > Inc. *******
> > >
> > > On Wed, 7 Jan 2004, Tolga Asveren wrote:
> > >
> > > > Barry,
> > > >
> > > > inline....
> > > > -Again as far as I remember ;) -
> > > >
> > > >    Tolga
> > > >
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > Barry Nagelberg
> > > > > Sent: Wednesday, January 07, 2004 10:47 AM
> > > > > To: SIGTRAN Mailing List
> > > > > Subject: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > There is a redundant pair of REG REQ error codes in Section
> > > 4.4.1 of RFC
> > > > > 3332, for the case in which a reg req contains a routing key
> > > that already
> > > > > exists at the SGP.
> > > > >
> > > > > The 1st is from the original RFC:
> > > > >
> > > > > "  If the SGP determines that a unique Routing Key cannot
> > be created,
> > > > >    the SGP returns a Registration Response message to the
> > ASP, with a
> > > > >    Registration Status of "Error - "Cannot Support Unique
> > Routing". An
> > > > >    incoming signalling message received at an SGP should not match
> > > > >    against more than one Routing Key. "
> > > > [TOLGA] This I believe is mainly for the case, where the required RK
> > > > overlaps with an already existing one -but they are not the same, just
> > > > partially overlapping-.
> > > > >
> > > > > The 2nd was added in the IG Rev 05:
> > > > >
> > > > > "  If the SGP determines that the received RK was already
> > registered,
> > > > >    the SGP returns a Registration Response message to the ASP,
> > > > >    containing a Registration Result "Error - Routing Key Already
> > > > >    Registered". This error applies whether the Routing Key is
> > > Active or
> > > > >    Inactive."
> > > > >
> > > > > Perhaps the intention of IG Rev 05 was to distinguish between
> > > the event
> > > > > where we have duplicate RKs, one of which was created
> > > statically and the
> > > > > other dynamically (by using the 1st error code), and the event
> > > > > where we have
> > > > > duplicate RKs, both of which were created dynamically (by
> > > using the 2nd
> > > > > error code)?
> > > > [TOLGA]I don't know, whether there is a real need to
> > distinguish between
> > > > those two cases. But , as it is right know, I also would expect
> > > it to work
> > > > like you described. Maybe it is a better idea to use the second
> > > one, when
> > > > there isa full match -regardless dynamic or static- , and to
> > > use the first
> > > > one for partial overlapping -so, shall Ig be updated to make it
> > > work that
> > > > way, any ideas?-
> > > > >
> > > > > If my guess is correct, then the description of the 1st error
> > > code must be
> > > > > updated to reflect this restriction.
> > > > >
> > > > > As it stands now, the SGP could correctly use either error code
> > > > > to describe
> > > > > the case in which a reg req contains a routing key that
> > > already exists at
> > > > > the SGP.
> > > > >
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jan  8 12:26:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03147
	for <sigtran-archive@odin.ietf.org>; Thu, 8 Jan 2004 12:26:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aedv1-000409-90
	for sigtran-archive@odin.ietf.org; Thu, 08 Jan 2004 12:26:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i08HQ38j015372
	for sigtran-archive@odin.ietf.org; Thu, 8 Jan 2004 12:26:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aeduy-0003zO-K3; Thu, 08 Jan 2004 12:26:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aedum-0003zB-9I
	for sigtran@optimus.ietf.org; Thu, 08 Jan 2004 12:25:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03137
	for <sigtran@ietf.org>; Thu, 8 Jan 2004 12:25:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aeduf-0001VA-00
	for sigtran@ietf.org; Thu, 08 Jan 2004 12:25:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aedny-0001Jj-00
	for sigtran@ietf.org; Thu, 08 Jan 2004 12:18:47 -0500
Received: from goliath.siemens.de ([192.35.17.28])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AednT-0001DX-00
	for sigtran@ietf.org; Thu, 08 Jan 2004 12:18:15 -0500
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11])
	by goliath.siemens.de (8.11.7/8.11.7) with ESMTP id i08HHvr25520
	for <sigtran@ietf.org>; Thu, 8 Jan 2004 18:17:57 +0100 (MET)
Received: from moody.mchh.siemens.de (moody.mchh.siemens.de [139.21.205.85])
	by mail2.siemens.de (8.11.7/8.11.7) with ESMTP id i08HHtP24722
	for <sigtran@ietf.org>; Thu, 8 Jan 2004 18:17:55 +0100 (MET)
Received: from mchh253e.mchh.siemens.de (mchh253e.mchh.siemens.de [139.21.200.63])
	by moody.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id SAA28990
	for <sigtran@ietf.org>; Thu, 8 Jan 2004 18:17:54 +0100 (MET)
Received: by mchh253e.mchh.siemens.de with Internet Mail Service (5.5.2657.72)
	id <CFK1S869>; Thu, 8 Jan 2004 18:17:45 +0100
Message-ID: <99522F0FD7EFD611A47D0002A58EDAB7C84BAE@mchh2a8e.mchh.siemens.de>
From: Gaiser Franz <franz.gaiser@siemens.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: [Sigtran] M2PA draft 10 - Processor outage
Date: Thu, 8 Jan 2004 18:17:44 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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 All,

I have a question to figure 16: There is not mentioned the behavior of the messages in the retransmission buffer. Is it correct, when A flushes (request from MTP3) the incoming messages 14-16 (the messages that were buffered without acknowledgement) the messages 5-6 still stored in the retransmission buffer of A are to be discared too?  The same applies to side B: when flushing the incoming message 6, the messages 14-16 in the retransmission buffer are discarded. 


Thanks for clarification.


Best regards, Franz

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



From exim@www1.ietf.org  Fri Jan  9 12:50:36 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18020
	for <sigtran-archive@odin.ietf.org>; Fri, 9 Jan 2004 12:50:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af0lt-0007mO-0T
	for sigtran-archive@odin.ietf.org; Fri, 09 Jan 2004 12:50:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i09Ho8p2029890
	for sigtran-archive@odin.ietf.org; Fri, 9 Jan 2004 12:50:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af0ls-0007ly-Pg
	for sigtran-web-archive@optimus.ietf.org; Fri, 09 Jan 2004 12:50:08 -0500
Date: Fri, 09 Jan 2004 12:50:08 -0500
Message-ID: <20040109175008.9164.44150.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: sigtran-web-archive@optimus.ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, sigtran-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

***************************************************************************


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

   
***************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for sigtran-web-archive@optimus.ietf.org:

List                                     Password // URL
----                                     --------  
sigtran@ietf.org                         emupuc    
https://www1.ietf.org/mailman/options/sigtran/sigtran-web-archive%40optimus.ietf.org



From exim@www1.ietf.org  Fri Jan  9 16:04:33 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15395
	for <sigtran-archive@odin.ietf.org>; Fri, 9 Jan 2004 16:04:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af3nY-0006vX-Py
	for sigtran-archive@odin.ietf.org; Fri, 09 Jan 2004 16:04:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i09L44SK026608
	for sigtran-archive@odin.ietf.org; Fri, 9 Jan 2004 16:04:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af3nV-0006ul-7Y; Fri, 09 Jan 2004 16:04:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af3nK-0006uR-Qr
	for sigtran@optimus.ietf.org; Fri, 09 Jan 2004 16:03:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15354
	for <sigtran@ietf.org>; Fri, 9 Jan 2004 16:03:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af3nI-00065T-00
	for sigtran@ietf.org; Fri, 09 Jan 2004 16:03:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af3lb-0005tf-00
	for sigtran@ietf.org; Fri, 09 Jan 2004 16:02:04 -0500
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af3jt-0005ay-00
	for sigtran@ietf.org; Fri, 09 Jan 2004 16:00:17 -0500
Received: from alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i09KxjOf005114;
	Fri, 9 Jan 2004 14:59:45 -0600 (CST)
Message-ID: <3FFF1641.3030607@alcatel.com>
Date: Fri, 09 Jan 2004 14:59:45 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gaiser Franz <franz.gaiser@siemens.com>
CC: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M2PA draft 10 - Processor outage
References: <99522F0FD7EFD611A47D0002A58EDAB7C84BAE@mchh2a8e.mchh.siemens.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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

Franz,

I think you are right. That is implied by the example, though it is not 
stated explicitly.

tomG.

Gaiser Franz wrote:
 > Hi All,
 >
 > I have a question to figure 16: There is not mentioned the behavior
 > of the messages in the retransmission buffer. Is it correct, when A
 > flushes (request from MTP3) the incoming messages 14-16 (the messages
 > that were buffered without acknowledgement) the messages 5-6 still
 > stored in the retransmission buffer of A are to be discared too?  The
 > same applies to side B: when flushing the incoming message 6, the
 > messages 14-16 in the retransmission buffer are discarded.
 >
 >
 > Thanks for clarification.
 >
 >
 > Best regards, Franz


-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
*   I actively disclaim speaking for Alcatel.  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 exim@www1.ietf.org  Mon Jan 12 06:36:29 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22475
	for <sigtran-archive@odin.ietf.org>; Mon, 12 Jan 2004 06:36:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ag0MU-0007Tc-QW
	for sigtran-archive@odin.ietf.org; Mon, 12 Jan 2004 06:36:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0CBa2UO028739
	for sigtran-archive@odin.ietf.org; Mon, 12 Jan 2004 06:36:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ag0MT-0007T6-Dx; Mon, 12 Jan 2004 06:36:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ag0MK-0007Sl-FH
	for sigtran@optimus.ietf.org; Mon, 12 Jan 2004 06:35:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22468
	for <sigtran@ietf.org>; Mon, 12 Jan 2004 06:35:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag0M6-0004Kp-00
	for sigtran@ietf.org; Mon, 12 Jan 2004 06:35:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag0JV-0004G5-00
	for sigtran@ietf.org; Mon, 12 Jan 2004 06:32:58 -0500
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag0FB-00048o-00
	for sigtran@ietf.org; Mon, 12 Jan 2004 06:28:29 -0500
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by david.siemens.de (8.11.7/8.11.7) with ESMTP id i0CBRjr24353;
	Mon, 12 Jan 2004 12:27:46 +0100 (MET)
Received: from blues.mchh.siemens.de (blues.mchh.siemens.de [139.21.204.206])
	by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id i0CBRjj19891;
	Mon, 12 Jan 2004 12:27:45 +0100 (MET)
Received: from mchh248e.mchh.siemens.de (mchh248e.mchh.siemens.de [139.21.200.58])
	by blues.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id MAA14389;
	Mon, 12 Jan 2004 12:27:32 +0100 (MET)
Received: by mchh248e.mchh.siemens.de with Internet Mail Service (5.5.2657.72)
	id <CFJNG864>; Mon, 12 Jan 2004 12:27:43 +0100
Message-ID: <99522F0FD7EFD611A47D0002A58EDAB7C84BB1@mchh2a8e.mchh.siemens.de>
From: Gaiser Franz <franz.gaiser@siemens.com>
To: "'Tom George'" <Tom.George@alcatel.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: AW: [Sigtran] M2PA draft 10 - Processor outage
Date: Mon, 12 Jan 2004 12:27:42 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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,

there are two more questions about PO:
1.) If MTP3 decides to resume operation after LPO ends (by sending CONTINUE instead of FLUSH), shall M2PA also exchange LS 'Ready' messages between the peers before resuming operation ? 
2.) What happens when one side gets CONTINUE (e.g. after LPO ends), but the other side a FLUSH command from MTP3? 
3.) In chapter 4.1.4 it is written that when M2PA experiences local processor outage, it MAY put the link out of service ... . Does this imply that also the side receiving a LS 'processor outage' may put the link out of service by sending a LS 'OOS'?

Thanks & Best regards, Franz


-----Ursprungliche Nachricht-----
Von: Tom George [mailto:Tom.George@alcatel.com]
Gesendet: Freitag, 9. Januar 2004 22:00
An: Gaiser Franz
Cc: 'sigtran@ietf.org'
Betreff: Re: [Sigtran] M2PA draft 10 - Processor outage


Franz,

I think you are right. That is implied by the example, though it is not 
stated explicitly.

tomG.

Gaiser Franz wrote:
 > Hi All,
 >
 > I have a question to figure 16: There is not mentioned the behavior
 > of the messages in the retransmission buffer. Is it correct, when A
 > flushes (request from MTP3) the incoming messages 14-16 (the messages
 > that were buffered without acknowledgement) the messages 5-6 still
 > stored in the retransmission buffer of A are to be discared too?  The
 > same applies to side B: when flushing the incoming message 6, the
 > messages 14-16 in the retransmission buffer are discarded.
 >
 >
 > Thanks for clarification.
 >
 >
 > Best regards, Franz


-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
*   I actively disclaim speaking for Alcatel.  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 exim@www1.ietf.org  Mon Jan 12 12:30:37 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06870
	for <sigtran-archive@odin.ietf.org>; Mon, 12 Jan 2004 12:30:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ag5tA-0004nA-Dj
	for sigtran-archive@odin.ietf.org; Mon, 12 Jan 2004 12:30:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0CHU82r018413
	for sigtran-archive@odin.ietf.org; Mon, 12 Jan 2004 12:30:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ag5t6-0004m9-GQ; Mon, 12 Jan 2004 12:30:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ag5sL-0004jz-13
	for sigtran@optimus.ietf.org; Mon, 12 Jan 2004 12:29:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06849
	for <sigtran@ietf.org>; Mon, 12 Jan 2004 12:29:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag5sJ-0004of-00
	for sigtran@ietf.org; Mon, 12 Jan 2004 12:29:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag5qX-0004kv-00
	for sigtran@ietf.org; Mon, 12 Jan 2004 12:27:26 -0500
Received: from pecos2.iphase.com ([157.175.3.201] helo=iphase.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag5pt-0004gU-00
	for sigtran@ietf.org; Mon, 12 Jan 2004 12:26:46 -0500
Received: from france.iphase.com (ariane [157.175.31.1])
	by iphase.com (8.12.9+Sun/8.12.2) with ESMTP id i0CHQE6i016219
	for <sigtran@ietf.org>; Mon, 12 Jan 2004 11:26:15 -0600 (CST)
Received: from BOESCH by france.iphase.com
	with SMTP (MDaemon.PRO.v5.0.4.R)
	for <sigtran@ietf.org>; Mon, 12 Jan 2004 18:27:05 +0100
Reply-To: <boesch@iphase.com>
From: "Franck Boesch" <boesch@iphase.com>
To: <sigtran@ietf.org>
Date: Mon, 12 Jan 2004 18:24:31 +0100
Message-ID: <002601c3d930$f14abad0$a81faf9d@BOESCH>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Return-Path: boesch@iphase.com
X-MDaemon-Deliver-To: sigtran@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Subject: [Sigtran] M2PA - draft 10 - Link Status Ready received during T4 period
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hello,

I would like to know if we should ignore a received 'Link Status Ready' =
message during the proving period (T4) or memorize that the remote end =
is ready to skip T1 period (just send 'Link Status Ready') when T4 =
expires. Please find below a modified Figure 12 page 35 of M2PA draft 10 =
to explain what I am saying.

Thanks for the reply,
Regards,
Franck Boesch.

Internet Draft  SS7 MTP2-User Peer-to-Peer Adaptation Layer   Oct 2003


    MTP3        M2PA        SCTP        SCTP        M2PA        MTP3
    ----        ----        ----        ----        ----        ----
     .           .           .           .           .           .
     .           Start timer T3          .           .           .
     .           Link Status Proving     .           .           .
     .           ------------------------------------>           .
     .           .           .           .           .           .
     .           .           .     Link Status Proving           .
     .           <------------------------------------           .
     .           .           .           .           .           .
     .           Stop timer T3           .           .           .
     .           .           .           .           .           .
     .           Start timer T4          .           .           .
     .           Link Status Proving     .           .           .
     .           ------------------------------------>           .
     .           ------------------------------------>           .
     .           ------------------------------------>           .
     .           .           .       Link Status Ready           .
     .           <------------------------------------           .
     .           ------------------------------------>           .
     .           ------------------------------------>           .
     .           ------------------------------------>           .
     .           .           .           .           .           .
     .           Timer T4 expires        .           .           .
     .           .           .           .           .           .

     Send Link Status Ready (one or more)=20

     .           .           .           .           .           .
     .           Link Status Ready       .           .           .
     .           ------------------------------------>           .
     .           .           .           .           .           .
     In Service              .           .           In Service
     <------------           .           .           ------------>
     .           .           .           .           .           .

     MTP3 MAY begin sending data messages.



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



From exim@www1.ietf.org  Tue Jan 13 09:39:33 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14239
	for <sigtran-archive@odin.ietf.org>; Tue, 13 Jan 2004 09:39:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgPhA-0007XM-4U
	for sigtran-archive@odin.ietf.org; Tue, 13 Jan 2004 09:39:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0DEd4Fx028968
	for sigtran-archive@odin.ietf.org; Tue, 13 Jan 2004 09:39:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgPh6-0007Wy-Qk; Tue, 13 Jan 2004 09:39:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgPgV-0007Vb-8E
	for sigtran@optimus.ietf.org; Tue, 13 Jan 2004 09:38:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14193
	for <sigtran@ietf.org>; Tue, 13 Jan 2004 09:38:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgPgT-000237-00
	for sigtran@ietf.org; Tue, 13 Jan 2004 09:38:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgPed-00020J-00
	for sigtran@ietf.org; Tue, 13 Jan 2004 09:36:27 -0500
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgPcp-0001xd-00
	for sigtran@ietf.org; Tue, 13 Jan 2004 09:34:36 -0500
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11])
	by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id i0DEYQo16221;
	Tue, 13 Jan 2004 15:34:26 +0100 (MET)
Received: from blues.mchh.siemens.de (blues.mchh.siemens.de [139.21.204.206])
	by mail2.siemens.de (8.11.7/8.11.7) with ESMTP id i0DEYPP03750;
	Tue, 13 Jan 2004 15:34:25 +0100 (MET)
Received: from mchh248e.mchh.siemens.de (mchh248e.mchh.siemens.de [139.21.200.58])
	by blues.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id PAA22358;
	Tue, 13 Jan 2004 15:34:11 +0100 (MET)
Received: by mchh248e.mchh.siemens.de with Internet Mail Service (5.5.2657.72)
	id <CFJN2QX4>; Tue, 13 Jan 2004 15:34:22 +0100
Message-ID: <99522F0FD7EFD611A47D0002A58EDAB7C84BB7@mchh2a8e.mchh.siemens.de>
From: Gaiser Franz <franz.gaiser@siemens.com>
To: "'boesch@iphase.com'" <boesch@iphase.com>, sigtran@ietf.org
Subject: AW: [Sigtran] M2PA - draft 10 - Link Status Ready received during
	 T4 period
Date: Tue, 13 Jan 2004 15:34:20 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi Frank,

Follow MTP2 behavior: If M2PA has already received a LS 'ready' from =
its peer when its timer T4 expires, there is no need to start T1. M2PA =
can just send LS 'ready' to the peer and continue along.

regards, Franz

-----Urspr=FCngliche Nachricht-----
Von: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]Im Auftrag
von Franck Boesch
Gesendet: Montag, 12. Januar 2004 18:25
An: sigtran@ietf.org
Betreff: [Sigtran] M2PA - draft 10 - Link Status Ready received during
T4 period


Hello,

I would like to know if we should ignore a received 'Link Status Ready' =
message during the proving period (T4) or memorize that the remote end =
is ready to skip T1 period (just send 'Link Status Ready') when T4 =
expires. Please find below a modified Figure 12 page 35 of M2PA draft =
10 to explain what I am saying.

Thanks for the reply,
Regards,
Franck Boesch.

Internet Draft  SS7 MTP2-User Peer-to-Peer Adaptation Layer   Oct 2003


    MTP3        M2PA        SCTP        SCTP        M2PA        MTP3
    ----        ----        ----        ----        ----        ----
     .           .           .           .           .           .
     .           Start timer T3          .           .           .
     .           Link Status Proving     .           .           .
     .           ------------------------------------>           .
     .           .           .           .           .           .
     .           .           .     Link Status Proving           .
     .           <------------------------------------           .
     .           .           .           .           .           .
     .           Stop timer T3           .           .           .
     .           .           .           .           .           .
     .           Start timer T4          .           .           .
     .           Link Status Proving     .           .           .
     .           ------------------------------------>           .
     .           ------------------------------------>           .
     .           ------------------------------------>           .
     .           .           .       Link Status Ready           .
     .           <------------------------------------           .
     .           ------------------------------------>           .
     .           ------------------------------------>           .
     .           ------------------------------------>           .
     .           .           .           .           .           .
     .           Timer T4 expires        .           .           .
     .           .           .           .           .           .

     Send Link Status Ready (one or more)=20

     .           .           .           .           .           .
     .           Link Status Ready       .           .           .
     .           ------------------------------------>           .
     .           .           .           .           .           .
     In Service              .           .           In Service
     <------------           .           .           ------------>
     .           .           .           .           .           .

     MTP3 MAY begin sending data messages.



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

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



From exim@www1.ietf.org  Tue Jan 13 10:15:33 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17861
	for <sigtran-archive@odin.ietf.org>; Tue, 13 Jan 2004 10:15:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgQG2-00011b-4t
	for sigtran-archive@odin.ietf.org; Tue, 13 Jan 2004 10:15:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0DFF62Y003931
	for sigtran-archive@odin.ietf.org; Tue, 13 Jan 2004 10:15:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgQFz-00011B-Vo; Tue, 13 Jan 2004 10:15:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgQFK-000101-Ri
	for sigtran@optimus.ietf.org; Tue, 13 Jan 2004 10:14:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17765
	for <sigtran@ietf.org>; Tue, 13 Jan 2004 10:14:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgQFI-0005Pt-00
	for sigtran@ietf.org; Tue, 13 Jan 2004 10:14:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgQDY-0005NQ-00
	for sigtran@ietf.org; Tue, 13 Jan 2004 10:12:33 -0500
Received: from pecos2.iphase.com ([157.175.3.201] helo=iphase.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgQC6-0005HD-00
	for sigtran@ietf.org; Tue, 13 Jan 2004 10:11:02 -0500
Received: from france.iphase.com (ariane [157.175.31.1])
	by iphase.com (8.12.9+Sun/8.12.2) with ESMTP id i0DFAU6i002011
	for <sigtran@ietf.org>; Tue, 13 Jan 2004 09:10:30 -0600 (CST)
Received: from BOESCH by france.iphase.com
	with SMTP (MDaemon.PRO.v5.0.4.R)
	for <sigtran@ietf.org>; Tue, 13 Jan 2004 16:11:41 +0100
Reply-To: <boesch@iphase.com>
From: "Franck Boesch" <boesch@iphase.com>
To: "'Gaiser Franz'" <franz.gaiser@siemens.com>, <sigtran@ietf.org>
Subject: RE: [Sigtran] M2PA - draft 10 - Link Status Ready received during T4 period
Date: Tue, 13 Jan 2004 16:09:06 +0100
Message-ID: <002e01c3d9e7$310aa5c0$a81faf9d@BOESCH>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
In-Reply-To: <99522F0FD7EFD611A47D0002A58EDAB7C84BB7@mchh2a8e.mchh.siemens.de>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Return-Path: boesch@iphase.com
X-MDaemon-Deliver-To: sigtran@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Thank you Franz - our MTP2 layer ignores a FISU received during T4 =
period (we consider that FISUs received afterwards due to FISU permanent =
transmission from remote will end local T1 period) and that explains why =
I have met this problem on M2PA layer.
regards,
Franck Boesch.

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
Gaiser Franz
Sent: mardi 13 janvier 2004 15:34
To: 'boesch@iphase.com'; sigtran@ietf.org
Subject: AW: [Sigtran] M2PA - draft 10 - Link Status Ready received
during T4 period


Hi Frank,

Follow MTP2 behavior: If M2PA has already received a LS 'ready' from =3D
its peer when its timer T4 expires, there is no need to start T1. M2PA =
=3D
can just send LS 'ready' to the peer and continue along.

regards, Franz

-----Urspr=3DFCngliche Nachricht-----
Von: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]Im Auftrag
von Franck Boesch
Gesendet: Montag, 12. Januar 2004 18:25
An: sigtran@ietf.org
Betreff: [Sigtran] M2PA - draft 10 - Link Status Ready received during
T4 period


Hello,

I would like to know if we should ignore a received 'Link Status Ready' =
=3D
message during the proving period (T4) or memorize that the remote end =
=3D
is ready to skip T1 period (just send 'Link Status Ready') when T4 =3D
expires. Please find below a modified Figure 12 page 35 of M2PA draft =
=3D
10 to explain what I am saying.

Thanks for the reply,
Regards,
Franck Boesch.

Internet Draft  SS7 MTP2-User Peer-to-Peer Adaptation Layer   Oct 2003


    MTP3        M2PA        SCTP        SCTP        M2PA        MTP3
    ----        ----        ----        ----        ----        ----
     .           .           .           .           .           .
     .           Start timer T3          .           .           .
     .           Link Status Proving     .           .           .
     .           ------------------------------------>           .
     .           .           .           .           .           .
     .           .           .     Link Status Proving           .
     .           <------------------------------------           .
     .           .           .           .           .           .
     .           Stop timer T3           .           .           .
     .           .           .           .           .           .
     .           Start timer T4          .           .           .
     .           Link Status Proving     .           .           .
     .           ------------------------------------>           .
     .           ------------------------------------>           .
     .           ------------------------------------>           .
     .           .           .       Link Status Ready           .
     .           <------------------------------------           .
     .           ------------------------------------>           .
     .           ------------------------------------>           .
     .           ------------------------------------>           .
     .           .           .           .           .           .
     .           Timer T4 expires        .           .           .
     .           .           .           .           .           .

     Send Link Status Ready (one or more)=3D20

     .           .           .           .           .           .
     .           Link Status Ready       .           .           .
     .           ------------------------------------>           .
     .           .           .           .           .           .
     In Service              .           .           In Service
     <------------           .           .           ------------>
     .           .           .           .           .           .

     MTP3 MAY begin sending data messages.



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

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



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



From exim@www1.ietf.org  Wed Jan 14 06:51:33 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13514
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 06:51:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgjYA-0002Li-Bc
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 06:51:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0EBp6KH009021
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 06:51:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgjY8-0002L0-8E; Wed, 14 Jan 2004 06:51:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgjY3-0002JU-9r
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 06:50:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13393
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 06:50:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgjXz-0006Go-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 06:50:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgjUH-0005Xg-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 06:47:08 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgjMe-0004fg-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 06:39:12 -0500
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i0EBcdAh008664;
	Wed, 14 Jan 2004 12:38:39 +0100
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.2657.72)
	id CR3H3VL3; Wed, 14 Jan 2004 12:41:09 +0100
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <CRN65DCD>; Wed, 14 Jan 2004 12:38:41 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C0433199A@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: SIGTRAN Mailing List <sigtran@ietf.org>
Cc: "Ken Morneault (E-mail)" <kmorneau@cisco.com>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Wed, 14 Jan 2004 12:36:54 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi guys, 

Here we send the new text proposal to clarify this issue according your comments. 

Thanks // Javier.



3.6 Receiving REG for a RK already registered
                                                                      
3.6.1 Description of the problem

The RFC does not clearly specify what the SG should do when it receives a Registration Request for a Routing Key that has already been registered. There are two scenarios to consider: the registration request is a duplicate, it overlaps partially an already registered RK. Also there is a desire to include the possibility of modifying a registered  Routing Key.

3.6.2 Text changes to the document

---------
Old text: (Section 3.6.1)
---------

The format of the Routing Key parameter 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
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                       Local-RK-Identifier                     |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                  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)               |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

---------
New text: (Section 3.6.1)
---------

The format of the Routing Key parameter 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
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                       Local-RK-Identifier                     |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                   Routing Context (optional)                  |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                  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)               |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

---------
Old text: (Section 3.6.2)
---------

Registration Status: 32-bit integer

  The Registration Result Status field indicates the success or the
  reason for failure of a registration request.
  Its values may be:

     0           Successfully Registered
     1           Error - Unknown
     2           Error - Invalid DPC
     3           Error - Invalid Network Appearance
     4           Error - Invalid Routing Key
     5           Error - Permission Denied
     6           Error - Cannot Support Unique Routing
     7           Error - Routing Key not Currently Provisioned
     8           Error - Insufficient Resources
     9           Error - Unsupported RK parameter Field
     10          Error - Unsupported/Invalid Traffic Handling Mode

---------
New text: (Section 3.6.2)
---------

Registration Status: 32-bit integer

  The Registration Result Status field indicates the success or the
  reason for failure of a registration request.
  Its values may be:
     0           Successfully Registered
     1           Error - Unknown
     2           Error - Invalid DPC
     3           Error - Invalid Network Appearance
     4           Error - Invalid Routing Key
     5           Error - Permission Denied
     6           Error - Cannot Support Unique Routing
     7           Error - Routing Key not Currently Provisioned
     8           Error - Insufficient Resources
     9           Error - Unsupported RK parameter Field
     10          Error - Unsupported/Invalid Traffic Handling Mode
     11          Error - Routing Key Change Refused
     12          Error - Routing Key Already Registered


--------- 
Old text: (Section 4.4.1) 
---------

If the SGP determines that a unique Routing Key cannot be created, the SGP returns a Registration Response message to the ASP, with a Registration Status of "Error - "Cannot Support Unique Routing"  An incoming signalling message received at an SGP should not match against more than one Routing Key.

-------- 
New text: (Section 4.4.1) 
---------

If the SGP determines that the requested RK partially, but not exactly, matches an existing RK, and that an incoming signalling message received at an SGP could possibly match both the requested and the existing RK, the SGP returns a Registration Response message to the ASP, with a Registration Status of "Error - "Cannot Support Unique Routing. An incoming signalling message received at an SGP should not match against more than one Routing Key.

If the SGP determines that the received RK was already registered, fully and exactly, either statically or dynamically, by the sending ASP, the SGP returns a Registration Response message to the ASP, containing a Registration Result "Error - Routing Key Already Registered ". This error applies whether the Routing Key is Active or Inactive. For this error code, RC field in Registration Response message MUST be populated with the actual value of RC in SGP corresponding to the specified RK in Registration Request message.

An ASP MAY modify an existing Routing Key by including a Routing Context parameter in the REG REQ.  If the SGP determines that the Routing Context applies to an existing Routing Key the SG MAY adjust the existing Routing Key to match the new information provided in the Routing Key parameter.  A Registration Response "ERR - Routing Key Change Refused" is returned if the SGP does not accept the modification of the Routing Key due to either it does not support the re-registration procedure or the specific RC does not exist. Otherwise if the change is accepted, a Registration Response "Successfully Registered" is returned.

3.6.3 Solution description 

The two cases, RK overlap and RK duplication, have been differentiated and explained in detail. The latter will use a new specific Error Code as defined above. Also the possibility of modification to a Routing Key is included with the addition of a new parameter in the REG REQ message and the corresponding explanation in the procedures section.

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



From exim@www1.ietf.org  Wed Jan 14 07:12:28 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14902
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 07:12:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgjsO-0003mA-GE
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 07:12:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0ECC0im014508
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 07:12:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgjsP-0003ld-Fg; Wed, 14 Jan 2004 07:12:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgjrQ-0003kk-7v
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 07:11:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14858
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 07:10:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgjrG-0000Hq-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 07:10:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Agjp0-0000BM-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 07:08:31 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agjn4-00004T-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 07:06:30 -0500
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i0EC6RAh014065;
	Wed, 14 Jan 2004 13:06:31 +0100
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.2657.72)
	id CR3H37J2; Wed, 14 Jan 2004 13:08:58 +0100
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <VRLK905Y>; Wed, 14 Jan 2004 13:03:41 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C0433199B@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>,
        Tolga Asveren
	 <tolga_asveren@yahoo.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: Network Appearance in Routing Key parameter
Date: Wed, 14 Jan 2004 13:05:43 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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, 

Yes, although a "weak conditional", we should turn it into conditional to follow a consistent labeling. We'll make the change for the new version.

Regarding the last sentence Barry mentions, I think it is the use as a wildcard what is stated here, but for creating different ASes at the same time, one per available NA. Would this be acceptable?

Thanks // Javier.

> -----Original Message-----
> From: sigtran-admin@ietf.org 
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Brian F. G. Bidulock
> Sent: jueves, 25 de diciembre de 2003 4:25
> To: Tolga Asveren
> Cc: SIGTRAN Mailing List
> Subject: Re: [Sigtran] M3UA: Network Appearance in Routing 
> Key parameter
> 
> 
> Tolga,
> 
> It probably should be "conditional".   I think it
> is just one "optional" we missed in the change to
> "conditional".
> 
> I am quite sure that in dicussions we were not going
> to allow an AS to span NA.  It would not be terribly
> useful, anyway.
> 
> However, because registration must be provisioned at
> the SG, it is always possible to provision a per-ASP
> default, regardless of the fact that the SG may exist
> in more than on NA.  All that the SG needs to know is
> that this particular ASP only registers (or default
> registers) in a given NA.  So I would say, at most
> a "weak conditional".  Perhaps that's why we left it
> as optional.
> 
> --brian
> 
> 
> Tolga Asveren wrote:                                          
>                        (Wed, 24 Dec 2003 13:36:43)
> > No, no, that was not what I tried to say, I thought
> > creating multiple RKs, one for each network. But this
> > also won't work, because there will be only one
> > registration result per request, I missed that part.
> > Otherwise thinking to link one AS to multiple networks
> > will definitly violate the principle of not spanning
> > multiple SPMS in an AS, which definitly will break a
> > lot of mechanisms in the protocol.
> > 
> > So, seems I am remembering wrong, anybody any idea
> > about the original question? Now, seems to me
> > something to be corrected....
> > 
> >     Tolga
> > --- Barry Nagelberg <barryn@adax.com> wrote:
> > > Tolga,
> > > 
> > > Thanks, but I don't think that your interpretation
> > > below is useful.
> > > 
> > > Let's not forget that the Reg Req is, among other
> > > things, a request by the
> > > ASP to create a new AS. Your interpretation means
> > > that the SGP would be
> > > linking this single, newly-created AS to multiple
> > > SS7 networks. I don't
> > > think that this is practical. A given AS should be
> > > linked to exactly one SS7
> > > network.
> > > 
> > > Barry Nagelberg
> > > 
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > Tolga Asveren
> > > > Sent: Wednesday, December 24, 2003 3:28 PM
> > > > To: SIGTRAN Mailing List
> > > > Subject: Re: [Sigtran] M3UA: Network Appearance in
> > > Routing Key parameter
> > > >
> > > >
> > > > Hi Barry,
> > > >
> > > > As far as I remember -not 100% sure though- it
> > > means
> > > > the following:
> > > > If NA is not there, ASP wants to register for the
> > > > specified traffic range in every network on SG.
> > > So, it
> > > > really is optinal, because it is possible to
> > > operate
> > > > in that way, even if there are multiple networks.
> > > >
> > > > Whether this is really usefull or not is a
> > > different
> > > > issue. At least now, a conditional NA parameter,
> > > which
> > > > must be included in case of multiple networks
> > > sound
> > > > more logical and easier to understand. In such a
> > > case,
> > > > there will be a need of multiple registration for
> > > each
> > > > network, even if PC/traffic range of AS is the
> > > same in
> > > > each network, but practically I wouldn't think
> > > this as
> > > > a huge problem. On the other hand, I would think,
> > > as
> > > > it is right now, is alo not a huge problem.
> > > >
> > > >     Tolga
> > > > --- Barry Nagelberg <barryn@adax.com> wrote:
> > > > > RFC 3332, in section 3.6.1, states that the
> > > Network
> > > > > Appearance parameter is
> > > > > optional in the Routing Key parameter of a REG
> > > REQ
> > > > > msg:
> > > > >
> > > > > <snip>
> > > > > The optional Network Appearance parameter field
> > > > > identifies the SS7
> > > > > network context for the Routing Key, and has the
> > > > > same format as in
> > > > > the DATA message (See Section 3.3.1) with the
> > > > > exception that it
> > > > > does not have to be the first parameter in the
> > > > > message.  The
> > > > > absence of the Network Appearance parameter in
> > > the
> > > > > Routing Key
> > > > > indicates the use of any Network Appearance
> > > value.
> > > > > <snip>
> > > > >
> > > > > There are at least 2 problems here:
> > > > >
> > > > > 1. This parameter should be conditional, not
> > > > > optional. It should be
> > > > > conditional in the sense that it is required
> > > when
> > > > > the SGP is handling
> > > > > traffic for more than one SS7 network. If such
> > > an
> > > > > SGP receives a Routing Key
> > > > > from the ASP with no Network Appearance
> > > parameter,
> > > > > how can the SGP possibly
> > > > > know to which SS7 network to link the
> > > newly-created
> > > > > Routing Key/AS/Routing
> > > > > Context?
> > > > >
> > > > > 2. The last sentence is very confusing. What is
> > > > > meant by "indicates the use
> > > > > of any Network Appearance value."? Use where? To
> > > > > indicate what?
> > > > >
> > > > > Barry Nagelberg
> > > 
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > __________________________________
> > Do you Yahoo!?
> > Protect your identity with Yahoo! Mail AddressGuard
> > http://antispam.yahoo.com/whatsnewfree
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 

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



From exim@www1.ietf.org  Wed Jan 14 07:30:38 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15283
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 07:30:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Agk9s-0004Cw-9T
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 07:30:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0ECU4PE016156
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 07:30:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Agk9q-0004C7-PF; Wed, 14 Jan 2004 07:30:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Agk9o-0004Bp-Kw
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 07:30:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15278
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 07:29:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agk9j-0000pf-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 07:29:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Agk4X-0000gE-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 07:24:34 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[9uxclXZUJ+PUbMauEjieCe3LT47sbnV6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agk0k-0000XK-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 07:20:38 -0500
Received: from ns.pigworks.openss7.net (IDENT:HgwI9BFAsbc96D2cxDtu6NIQ3kv8J+0q@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0ECK5I03380;
	Wed, 14 Jan 2004 05:20:05 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0ECK5G07294;
	Wed, 14 Jan 2004 05:20:05 -0700
Date: Wed, 14 Jan 2004 05:20:04 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>,
        "Ken Morneault (E-mail)" <kmorneau@cisco.com>
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
Message-ID: <20040114052004.A7105@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>,
	"Ken Morneault (E-mail)" <kmorneau@cisco.com>
References: <1AB3D30B989BF141BBD5C70057B2EF7C0433199A@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: <1AB3D30B989BF141BBD5C70057B2EF7C0433199A@eestqnt105.es.eu.ericsson.se>; from j.javier.pastor@ericsson.com on Wed, Jan 14, 2004 at 12:36:54PM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

J.Javier,

J.Javier Pastor (ML/EEM) wrote:                                                   (Wed, 14 Jan 2004 12:36:54)

--snip--
> 
> -------- 
> New text: (Section 4.4.1) 
> ---------
> 
> If the SGP determines that the requested RK partially, but not exactly,
> matches an existing RK, and that an incoming signalling message received at
> an SGP could possibly match both the requested and the existing RK, the SGP
> returns a Registration Response message to the ASP, with a Registration
> Status of "Error - "Cannot Support Unique Routing. An incoming signalling
> message received at an SGP should not match against more than one Routing
> Key.
> 
--snip--

I think you mean for a given ASP (Association) in the above.  Correct?

It should be mentioned that the "matching" of RKs is done only against other
RKs belonging to the same ASP (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 exim@www1.ietf.org  Wed Jan 14 08:44:32 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17326
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 08:44:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AglJT-0007Sd-N7
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 08:44:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0EDi3e5028676
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 08:44:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AglJR-0007SH-2Y; Wed, 14 Jan 2004 08:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AglId-0007QS-Cl
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 08:43:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17311
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 08:43:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AglIc-0003C9-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 08:43:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AglH2-00035y-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 08:41:32 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AglFm-0002wt-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 08:40:14 -0500
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i0EDe8qY003455;
	Wed, 14 Jan 2004 14:40:08 +0100 (MET)
Received: from ESEALNT744.al.sw.ericsson.se ([153.88.251.4]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id CZDFNLL5; Wed, 14 Jan 2004 14:40:08 +0100
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <CRN651NF>; Wed, 14 Jan 2004 14:40:10 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C0433199C@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>,
        "Ken Morneault (E-mail)"
	 <kmorneau@cisco.com>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Wed, 14 Jan 2004 14:37:45 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Brian,=20

Tell me if the following is OK.=20

If the SGP determines that the requested RK partially, but not exactly,
matches an existing RK already registered for the sender ASP, and that =
an incoming signalling message received at
an SGP could possibly match both the requested and the existing RK, the =
SGP
returns a Registration Response message to the ASP, with a Registration
Status of "Error - "Cannot Support Unique Routing. An incoming =
signalling
message received at an SGP should not match against more than one =
Routing
Key.


THanks // JAvier.

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> To: J.Javier Pastor (ML/EEM)
> Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
>=20
>=20
> J.Javier,
>=20
> J.Javier Pastor (ML/EEM) wrote:                              =20
>                     (Wed, 14 Jan 2004 12:36:54)
>=20
> --snip--
> >=20
> > --------=20
> > New text: (Section 4.4.1)=20
> > ---------
> >=20
> > If the SGP determines that the requested RK partially, but=20
> not exactly,
> > matches an existing RK, and that an incoming signalling=20
> message received at
> > an SGP could possibly match both the requested and the=20
> existing RK, the SGP
> > returns a Registration Response message to the ASP, with a=20
> Registration
> > Status of "Error - "Cannot Support Unique Routing. An=20
> incoming signalling
> > message received at an SGP should not match against more=20
> than one Routing
> > Key.
> >=20
> --snip--
>=20
> I think you mean for a given ASP (Association) in the above.  =
Correct?
>=20
> It should be mentioned that the "matching" of RKs is done=20
> only against other
> RKs belonging to the same ASP (Association).
>=20
> --brian
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20

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



From exim@www1.ietf.org  Wed Jan 14 08:49:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17738
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 08:49:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AglOH-0007eT-6w
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 08:49:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0EDn1Dw029394
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 08:49:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AglOG-0007dr-RO; Wed, 14 Jan 2004 08:49:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AglNy-0007dW-Oq
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 08:48:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17558
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 08:48:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AglNx-0003Wd-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 08:48:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AglM1-0003Mx-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 08:46:42 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AglKM-0003Gq-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 08:44:58 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id IAA13989;
	Wed, 14 Jan 2004 08:44:39 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: "J.Javier Pastor \(ML/EEM\)" <j.javier.pastor@ericsson.com>,
        <bidulock@openss7.org>, "Tolga Asveren" <tolga_asveren@yahoo.com>
Cc: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: Network Appearance in Routing Key parameter
Date: Wed, 14 Jan 2004 08:43:03 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMCEEECDAA.asveren@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)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C0433199B@eestqnt105.es.eu.ericsson.se>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
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 Javier,

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> J.Javier Pastor (ML/EEM)
> Sent: Wednesday, January 14, 2004 7:06 AM
> To: 'bidulock@openss7.org'; Tolga Asveren
> Cc: SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: Network Appearance in Routing Key parameter
>
>
> Hi,
>
> Yes, although a "weak conditional", we should turn it into
> conditional to follow a consistent labeling. We'll make the
> change for the new version.
>
> Regarding the last sentence Barry mentions, I think it is the use
> as a wildcard what is stated here, but for creating different
> ASes at the same time, one per available NA. Would this be acceptable?
[TOLGA]I think, then we would have the problem of communicating RCs for
those multiple ASs back to ASP. In REGRSP we have only one RC parameter per
localRK identifier.
>
> Thanks // Javier.
>
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Brian F. G. Bidulock
> > Sent: jueves, 25 de diciembre de 2003 4:25
> > To: Tolga Asveren
> > Cc: SIGTRAN Mailing List
> > Subject: Re: [Sigtran] M3UA: Network Appearance in Routing
> > Key parameter
> >
> >
> > Tolga,
> >
> > It probably should be "conditional".   I think it
> > is just one "optional" we missed in the change to
> > "conditional".
> >
> > I am quite sure that in dicussions we were not going
> > to allow an AS to span NA.  It would not be terribly
> > useful, anyway.
> >
> > However, because registration must be provisioned at
> > the SG, it is always possible to provision a per-ASP
> > default, regardless of the fact that the SG may exist
> > in more than on NA.  All that the SG needs to know is
> > that this particular ASP only registers (or default
> > registers) in a given NA.  So I would say, at most
> > a "weak conditional".  Perhaps that's why we left it
> > as optional.
> >
> > --brian
> >
> >
> > Tolga Asveren wrote:
> >                        (Wed, 24 Dec 2003 13:36:43)
> > > No, no, that was not what I tried to say, I thought
> > > creating multiple RKs, one for each network. But this
> > > also won't work, because there will be only one
> > > registration result per request, I missed that part.
> > > Otherwise thinking to link one AS to multiple networks
> > > will definitly violate the principle of not spanning
> > > multiple SPMS in an AS, which definitly will break a
> > > lot of mechanisms in the protocol.
> > >
> > > So, seems I am remembering wrong, anybody any idea
> > > about the original question? Now, seems to me
> > > something to be corrected....
> > >
> > >     Tolga
> > > --- Barry Nagelberg <barryn@adax.com> wrote:
> > > > Tolga,
> > > >
> > > > Thanks, but I don't think that your interpretation
> > > > below is useful.
> > > >
> > > > Let's not forget that the Reg Req is, among other
> > > > things, a request by the
> > > > ASP to create a new AS. Your interpretation means
> > > > that the SGP would be
> > > > linking this single, newly-created AS to multiple
> > > > SS7 networks. I don't
> > > > think that this is practical. A given AS should be
> > > > linked to exactly one SS7
> > > > network.
> > > >
> > > > Barry Nagelberg
> > > >
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org
> > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > Tolga Asveren
> > > > > Sent: Wednesday, December 24, 2003 3:28 PM
> > > > > To: SIGTRAN Mailing List
> > > > > Subject: Re: [Sigtran] M3UA: Network Appearance in
> > > > Routing Key parameter
> > > > >
> > > > >
> > > > > Hi Barry,
> > > > >
> > > > > As far as I remember -not 100% sure though- it
> > > > means
> > > > > the following:
> > > > > If NA is not there, ASP wants to register for the
> > > > > specified traffic range in every network on SG.
> > > > So, it
> > > > > really is optinal, because it is possible to
> > > > operate
> > > > > in that way, even if there are multiple networks.
> > > > >
> > > > > Whether this is really usefull or not is a
> > > > different
> > > > > issue. At least now, a conditional NA parameter,
> > > > which
> > > > > must be included in case of multiple networks
> > > > sound
> > > > > more logical and easier to understand. In such a
> > > > case,
> > > > > there will be a need of multiple registration for
> > > > each
> > > > > network, even if PC/traffic range of AS is the
> > > > same in
> > > > > each network, but practically I wouldn't think
> > > > this as
> > > > > a huge problem. On the other hand, I would think,
> > > > as
> > > > > it is right now, is alo not a huge problem.
> > > > >
> > > > >     Tolga
> > > > > --- Barry Nagelberg <barryn@adax.com> wrote:
> > > > > > RFC 3332, in section 3.6.1, states that the
> > > > Network
> > > > > > Appearance parameter is
> > > > > > optional in the Routing Key parameter of a REG
> > > > REQ
> > > > > > msg:
> > > > > >
> > > > > > <snip>
> > > > > > The optional Network Appearance parameter field
> > > > > > identifies the SS7
> > > > > > network context for the Routing Key, and has the
> > > > > > same format as in
> > > > > > the DATA message (See Section 3.3.1) with the
> > > > > > exception that it
> > > > > > does not have to be the first parameter in the
> > > > > > message.  The
> > > > > > absence of the Network Appearance parameter in
> > > > the
> > > > > > Routing Key
> > > > > > indicates the use of any Network Appearance
> > > > value.
> > > > > > <snip>
> > > > > >
> > > > > > There are at least 2 problems here:
> > > > > >
> > > > > > 1. This parameter should be conditional, not
> > > > > > optional. It should be
> > > > > > conditional in the sense that it is required
> > > > when
> > > > > > the SGP is handling
> > > > > > traffic for more than one SS7 network. If such
> > > > an
> > > > > > SGP receives a Routing Key
> > > > > > from the ASP with no Network Appearance
> > > > parameter,
> > > > > > how can the SGP possibly
> > > > > > know to which SS7 network to link the
> > > > newly-created
> > > > > > Routing Key/AS/Routing
> > > > > > Context?
> > > > > >
> > > > > > 2. The last sentence is very confusing. What is
> > > > > > meant by "indicates the use
> > > > > > of any Network Appearance value."? Use where? To
> > > > > > indicate what?
> > > > > >
> > > > > > Barry Nagelberg
> > > >
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > Protect your identity with Yahoo! Mail AddressGuard
> > > http://antispam.yahoo.com/whatsnewfree
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >
> > --
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


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



From exim@www1.ietf.org  Wed Jan 14 08:50:31 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17761
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 08:50:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AglPH-0007ka-4m
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 08:50:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0EDo32W029769
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 08:50:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AglPG-0007jq-Jd; Wed, 14 Jan 2004 08:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AglOO-0007hB-2y
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 08:49:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17619
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 08:49:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AglOM-0003Zw-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 08:49:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AglMQ-0003Qf-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 08:47:06 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AglKm-0003K6-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 08:45:25 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i0EDjNkH012416
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 08:45:23 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Wed, 14 Jan 2004 08:46:52 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOCEKOCDAA.barryn@adax.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)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <20040114052004.A7105@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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,

No, your suggestion is not correct. Routing keys are independent of ASPs or
associations. I think perhaps you are thinking of the routing context, which
may be unique for each ASP or association.

Barry Nagelberg

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> Brian F. G. Bidulock
> Sent: Wednesday, January 14, 2004 7:20 AM
> To: J.Javier Pastor (ML/EEM)
> Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
>
>
> J.Javier,
>
> J.Javier Pastor (ML/EEM) wrote:
>                 (Wed, 14 Jan 2004 12:36:54)
>
> --snip--
> >
> > --------
> > New text: (Section 4.4.1)
> > ---------
> >
> > If the SGP determines that the requested RK partially, but not exactly,
> > matches an existing RK, and that an incoming signalling message
> received at
> > an SGP could possibly match both the requested and the existing
> RK, the SGP
> > returns a Registration Response message to the ASP, with a Registration
> > Status of "Error - "Cannot Support Unique Routing. An incoming
> signalling
> > message received at an SGP should not match against more than
> one Routing
> > Key.
> >
> --snip--
>
> I think you mean for a given ASP (Association) in the above.  Correct?
>
> It should be mentioned that the "matching" of RKs is done only
> against other
> RKs belonging to the same ASP (Association).
>
> --brian


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



From exim@www1.ietf.org  Wed Jan 14 08:51:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17852
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 08:51:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AglQD-0007s8-Om
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 08:51:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0EDp13i030236
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 08:51:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AglQD-0007rW-HM; Wed, 14 Jan 2004 08:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AglQ4-0007qc-UE
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 08:50:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17837
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 08:50:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AglQ3-0003gv-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 08:50:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AglOl-0003dS-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 08:49:32 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AglN1-0003VL-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 08:47:43 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i0EDlgkH012424
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 08:47:42 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Wed, 14 Jan 2004 08:49:12 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOGEKOCDAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C0433199C@eestqnt105.es.eu.ericsson.se>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by slink5.mtl-nj.adax id i0EDlgkH012424
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Javier,

No, Brian's suggestion is not correct, nor is this updated text. Routing
keys are independent of ASPs or associations. I think perhaps Brian is
thinking of the routing context, which may be unique for each ASP or
association.

Barry Nagelberg

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf O=
f
> J.Javier Pastor (ML/EEM)
> Sent: Wednesday, January 14, 2004 8:38 AM
> To: 'bidulock@openss7.org'
> Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
>
>
> Brian,
>
> Tell me if the following is OK.
>
> If the SGP determines that the requested RK partially, but not exactly,
> matches an existing RK already registered for the sender ASP, and
> that an incoming signalling message received at
> an SGP could possibly match both the requested and the existing
> RK, the SGP
> returns a Registration Response message to the ASP, with a Registration
> Status of "Error - "Cannot Support Unique Routing. An incoming signalli=
ng
> message received at an SGP should not match against more than one Routi=
ng
> Key.
>
>
> THanks // JAvier.
>
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > To: J.Javier Pastor (ML/EEM)
> > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > J.Javier,
> >
> > J.Javier Pastor (ML/EEM) wrote:
> >                     (Wed, 14 Jan 2004 12:36:54)
> >
> > --snip--
> > >
> > > --------
> > > New text: (Section 4.4.1)
> > > ---------
> > >
> > > If the SGP determines that the requested RK partially, but
> > not exactly,
> > > matches an existing RK, and that an incoming signalling
> > message received at
> > > an SGP could possibly match both the requested and the
> > existing RK, the SGP
> > > returns a Registration Response message to the ASP, with a
> > Registration
> > > Status of "Error - "Cannot Support Unique Routing. An
> > incoming signalling
> > > message received at an SGP should not match against more
> > than one Routing
> > > Key.
> > >
> > --snip--
> >
> > I think you mean for a given ASP (Association) in the above.  Correct=
?
> >
> > It should be mentioned that the "matching" of RKs is done
> > only against other
> > RKs belonging to the same ASP (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 exim@www1.ietf.org  Wed Jan 14 09:05:33 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18316
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 09:05:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Agldp-0008UV-77
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 09:05:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0EE55Yr032622
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 09:05:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Agldo-0008Tf-7z; Wed, 14 Jan 2004 09:05:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgldT-0008Rv-9z
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 09:04:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18282
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 09:04:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgldR-0004Ai-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:04:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aglbf-00048d-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:02:52 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aglb9-00045g-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:02:19 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i0EE2IkH012464
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 09:02:18 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Wed, 14 Jan 2004 09:03:47 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOEEKPCDAA.barryn@adax.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
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C0433199A@eestqnt105.es.eu.ericsson.se>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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

Javier,

Thanks. For the sake of clarity, I suggest the following changes:

<snip>

3.6.1 Description of the problem

The RFC does not clearly specify what the SG should do when it receives a
Registration Request for a Routing Key that has already been registered.
There are 3 scenarios to consider:

1. The registration request is an exact duplicate of a registered RK.
2. The registration request partially overlaps a registered RK.
3. The ASP is requesting to modify a registered RK.

<snip>

Barry Nagelberg

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> J.Javier Pastor (ML/EEM)
> Sent: Wednesday, January 14, 2004 6:37 AM
> To: SIGTRAN Mailing List
> Cc: Ken Morneault (E-mail)
> Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
>
>
> Hi guys,
>
> Here we send the new text proposal to clarify this issue
> according your comments.
>
> Thanks // Javier.
>
>
>
> 3.6 Receiving REG for a RK already registered
>
> 3.6.1 Description of the problem
>
> The RFC does not clearly specify what the SG should do when it
> receives a Registration Request for a Routing Key that has
> already been registered. There are two scenarios to consider: the
> registration request is a duplicate, it overlaps partially an
> already registered RK. Also there is a desire to include the
> possibility of modifying a registered  Routing Key.
>
> 3.6.2 Text changes to the document
>
> ---------
> Old text: (Section 3.6.1)
> ---------
>
> The format of the Routing Key parameter 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
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |                       Local-RK-Identifier                     |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |                  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)               |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> ---------
> New text: (Section 3.6.1)
> ---------
>
> The format of the Routing Key parameter 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
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |                       Local-RK-Identifier                     |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |                   Routing Context (optional)                  |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |                  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)               |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> ---------
> Old text: (Section 3.6.2)
> ---------
>
> Registration Status: 32-bit integer
>
>   The Registration Result Status field indicates the success or the
>   reason for failure of a registration request.
>   Its values may be:
>
>      0           Successfully Registered
>      1           Error - Unknown
>      2           Error - Invalid DPC
>      3           Error - Invalid Network Appearance
>      4           Error - Invalid Routing Key
>      5           Error - Permission Denied
>      6           Error - Cannot Support Unique Routing
>      7           Error - Routing Key not Currently Provisioned
>      8           Error - Insufficient Resources
>      9           Error - Unsupported RK parameter Field
>      10          Error - Unsupported/Invalid Traffic Handling Mode
>
> ---------
> New text: (Section 3.6.2)
> ---------
>
> Registration Status: 32-bit integer
>
>   The Registration Result Status field indicates the success or the
>   reason for failure of a registration request.
>   Its values may be:
>      0           Successfully Registered
>      1           Error - Unknown
>      2           Error - Invalid DPC
>      3           Error - Invalid Network Appearance
>      4           Error - Invalid Routing Key
>      5           Error - Permission Denied
>      6           Error - Cannot Support Unique Routing
>      7           Error - Routing Key not Currently Provisioned
>      8           Error - Insufficient Resources
>      9           Error - Unsupported RK parameter Field
>      10          Error - Unsupported/Invalid Traffic Handling Mode
>      11          Error - Routing Key Change Refused
>      12          Error - Routing Key Already Registered
>
>
> ---------
> Old text: (Section 4.4.1)
> ---------
>
> If the SGP determines that a unique Routing Key cannot be
> created, the SGP returns a Registration Response message to the
> ASP, with a Registration Status of "Error - "Cannot Support
> Unique Routing"  An incoming signalling message received at an
> SGP should not match against more than one Routing Key.
>
> --------
> New text: (Section 4.4.1)
> ---------
>
> If the SGP determines that the requested RK partially, but not
> exactly, matches an existing RK, and that an incoming signalling
> message received at an SGP could possibly match both the
> requested and the existing RK, the SGP returns a Registration
> Response message to the ASP, with a Registration Status of "Error
> - "Cannot Support Unique Routing. An incoming signalling message
> received at an SGP should not match against more than one Routing Key.
>
> If the SGP determines that the received RK was already
> registered, fully and exactly, either statically or dynamically,
> by the sending ASP, the SGP returns a Registration Response
> message to the ASP, containing a Registration Result "Error -
> Routing Key Already Registered ". This error applies whether the
> Routing Key is Active or Inactive. For this error code, RC field
> in Registration Response message MUST be populated with the
> actual value of RC in SGP corresponding to the specified RK in
> Registration Request message.
>
> An ASP MAY modify an existing Routing Key by including a Routing
> Context parameter in the REG REQ.  If the SGP determines that the
> Routing Context applies to an existing Routing Key the SG MAY
> adjust the existing Routing Key to match the new information
> provided in the Routing Key parameter.  A Registration Response
> "ERR - Routing Key Change Refused" is returned if the SGP does
> not accept the modification of the Routing Key due to either it
> does not support the re-registration procedure or the specific RC
> does not exist. Otherwise if the change is accepted, a
> Registration Response "Successfully Registered" is returned.
>
> 3.6.3 Solution description
>
> The two cases, RK overlap and RK duplication, have been
> differentiated and explained in detail. The latter will use a new
> specific Error Code as defined above. Also the possibility of
> modification to a Routing Key is included with the addition of a
> new parameter in the REG REQ message and the corresponding
> explanation in the procedures section.
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


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



From exim@www1.ietf.org  Wed Jan 14 09:17:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19727
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 09:17:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AglpO-0001GM-HD
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 09:17:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0EEH2vg004825
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 09:17:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AglpN-0001Fd-DQ; Wed, 14 Jan 2004 09:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aglol-0001Dv-S6
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 09:16:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19620
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 09:16:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agloh-0005SA-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:16:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgloD-0005N3-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:15:54 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AglnO-0005Ag-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:14:58 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i0EEEvkH012546
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 09:14:57 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: Network Appearance in Routing Key parameter
Date: Wed, 14 Jan 2004 09:16:27 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOEELACDAA.barryn@adax.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
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C0433199B@eestqnt105.es.eu.ericsson.se>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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

Javier,

Regarding the "last" sentence that I mentioned below, that is currently in
the RFC and is very confusing:

<snip>
The absence of the Network Appearance parameter in the Routing Key indicates
the use of any Network Appearance value.
<snip>

Your suggestion below -

"I think it is the use as a wildcard what is stated here, but for creating
different ASes at the same time, one per available NA."

- is not very helpful in relieving the confusion. I suggest that we stick
with the "conditional" parameter, which MUST be present if the SGP is
handling traffic for more than one SS7 network.

Barry Nagelberg

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> J.Javier Pastor (ML/EEM)
> Sent: Wednesday, January 14, 2004 7:06 AM
> To: 'bidulock@openss7.org'; Tolga Asveren
> Cc: SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: Network Appearance in Routing Key parameter
>
>
> Hi,
>
> Yes, although a "weak conditional", we should turn it into
> conditional to follow a consistent labeling. We'll make the
> change for the new version.
>
> Regarding the last sentence Barry mentions, I think it is the use
> as a wildcard what is stated here, but for creating different
> ASes at the same time, one per available NA. Would this be acceptable?
>
> Thanks // Javier.
>
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Brian F. G. Bidulock
> > Sent: jueves, 25 de diciembre de 2003 4:25
> > To: Tolga Asveren
> > Cc: SIGTRAN Mailing List
> > Subject: Re: [Sigtran] M3UA: Network Appearance in Routing
> > Key parameter
> >
> >
> > Tolga,
> >
> > It probably should be "conditional".   I think it
> > is just one "optional" we missed in the change to
> > "conditional".
> >
> > I am quite sure that in dicussions we were not going
> > to allow an AS to span NA.  It would not be terribly
> > useful, anyway.
> >
> > However, because registration must be provisioned at
> > the SG, it is always possible to provision a per-ASP
> > default, regardless of the fact that the SG may exist
> > in more than on NA.  All that the SG needs to know is
> > that this particular ASP only registers (or default
> > registers) in a given NA.  So I would say, at most
> > a "weak conditional".  Perhaps that's why we left it
> > as optional.
> >
> > --brian
> >
> >
> > Tolga Asveren wrote:
> >                        (Wed, 24 Dec 2003 13:36:43)
> > > No, no, that was not what I tried to say, I thought
> > > creating multiple RKs, one for each network. But this
> > > also won't work, because there will be only one
> > > registration result per request, I missed that part.
> > > Otherwise thinking to link one AS to multiple networks
> > > will definitly violate the principle of not spanning
> > > multiple SPMS in an AS, which definitly will break a
> > > lot of mechanisms in the protocol.
> > >
> > > So, seems I am remembering wrong, anybody any idea
> > > about the original question? Now, seems to me
> > > something to be corrected....
> > >
> > >     Tolga
> > > --- Barry Nagelberg <barryn@adax.com> wrote:
> > > > Tolga,
> > > >
> > > > Thanks, but I don't think that your interpretation
> > > > below is useful.
> > > >
> > > > Let's not forget that the Reg Req is, among other
> > > > things, a request by the
> > > > ASP to create a new AS. Your interpretation means
> > > > that the SGP would be
> > > > linking this single, newly-created AS to multiple
> > > > SS7 networks. I don't
> > > > think that this is practical. A given AS should be
> > > > linked to exactly one SS7
> > > > network.
> > > >
> > > > Barry Nagelberg
> > > >
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org
> > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > Tolga Asveren
> > > > > Sent: Wednesday, December 24, 2003 3:28 PM
> > > > > To: SIGTRAN Mailing List
> > > > > Subject: Re: [Sigtran] M3UA: Network Appearance in
> > > > Routing Key parameter
> > > > >
> > > > >
> > > > > Hi Barry,
> > > > >
> > > > > As far as I remember -not 100% sure though- it
> > > > means
> > > > > the following:
> > > > > If NA is not there, ASP wants to register for the
> > > > > specified traffic range in every network on SG.
> > > > So, it
> > > > > really is optinal, because it is possible to
> > > > operate
> > > > > in that way, even if there are multiple networks.
> > > > >
> > > > > Whether this is really usefull or not is a
> > > > different
> > > > > issue. At least now, a conditional NA parameter,
> > > > which
> > > > > must be included in case of multiple networks
> > > > sound
> > > > > more logical and easier to understand. In such a
> > > > case,
> > > > > there will be a need of multiple registration for
> > > > each
> > > > > network, even if PC/traffic range of AS is the
> > > > same in
> > > > > each network, but practically I wouldn't think
> > > > this as
> > > > > a huge problem. On the other hand, I would think,
> > > > as
> > > > > it is right now, is alo not a huge problem.
> > > > >
> > > > >     Tolga
> > > > > --- Barry Nagelberg <barryn@adax.com> wrote:
> > > > > > RFC 3332, in section 3.6.1, states that the
> > > > Network
> > > > > > Appearance parameter is
> > > > > > optional in the Routing Key parameter of a REG
> > > > REQ
> > > > > > msg:
> > > > > >
> > > > > > <snip>
> > > > > > The optional Network Appearance parameter field
> > > > > > identifies the SS7
> > > > > > network context for the Routing Key, and has the
> > > > > > same format as in
> > > > > > the DATA message (See Section 3.3.1) with the
> > > > > > exception that it
> > > > > > does not have to be the first parameter in the
> > > > > > message.  The
> > > > > > absence of the Network Appearance parameter in
> > > > the
> > > > > > Routing Key
> > > > > > indicates the use of any Network Appearance
> > > > value.
> > > > > > <snip>
> > > > > >
> > > > > > There are at least 2 problems here:
> > > > > >
> > > > > > 1. This parameter should be conditional, not
> > > > > > optional. It should be
> > > > > > conditional in the sense that it is required
> > > > when
> > > > > > the SGP is handling
> > > > > > traffic for more than one SS7 network. If such
> > > > an
> > > > > > SGP receives a Routing Key
> > > > > > from the ASP with no Network Appearance
> > > > parameter,
> > > > > > how can the SGP possibly
> > > > > > know to which SS7 network to link the
> > > > newly-created
> > > > > > Routing Key/AS/Routing
> > > > > > Context?
> > > > > >
> > > > > > 2. The last sentence is very confusing. What is
> > > > > > meant by "indicates the use
> > > > > > of any Network Appearance value."? Use where? To
> > > > > > indicate what?
> > > > > >
> > > > > > Barry Nagelberg


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



From exim@www1.ietf.org  Wed Jan 14 09:33:31 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20122
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 09:33:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Agm4t-0002Ay-Fs
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 09:33:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0EEX3e4008358
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 09:33:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Agm4r-0002AU-IL; Wed, 14 Jan 2004 09:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Agm4Y-0002AD-Fc
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 09:32:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20113
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 09:32:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agm4W-0005wF-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:32:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Agm3b-0005vg-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:31:44 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agm2s-0005v2-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:30:59 -0500
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i0EEUrAh013793;
	Wed, 14 Jan 2004 15:30:53 +0100
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id ZJBSJB6S; Wed, 14 Jan 2004 15:32:23 +0100
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <VRLK0BQ9>; Wed, 14 Jan 2004 15:28:07 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C0433199D@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "'Barry Nagelberg'" <barryn@adax.com>,
        SIGTRAN Mailing List
	 <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Wed, 14 Jan 2004 15:30:10 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Barry,=20

You are right. And that is valid only for the overlapping case. You can =
not create a new AS whose associated RK overlaps another existing =
registered RK. In the duplicate case it is already included that the =
check is against the RK previosly registered by the sending ASP. The =
latter makes sense but not the former.

Go back to my first proposal.

Thanks // Javier.

> -----Original Message-----
> From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Barry Nagelberg
> Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> To: SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
>=20
>=20
> Javier,
>=20
> No, Brian's suggestion is not correct, nor is this updated=20
> text. Routing
> keys are independent of ASPs or associations. I think perhaps Brian =
is
> thinking of the routing context, which may be unique for each ASP or
> association.
>=20
> Barry Nagelberg
>=20
> > -----Original Message-----
> > From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> > J.Javier Pastor (ML/EEM)
> > Sent: Wednesday, January 14, 2004 8:38 AM
> > To: 'bidulock@openss7.org'
> > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > Brian,
> >
> > Tell me if the following is OK.
> >
> > If the SGP determines that the requested RK partially, but=20
> not exactly,
> > matches an existing RK already registered for the sender ASP, and
> > that an incoming signalling message received at
> > an SGP could possibly match both the requested and the existing
> > RK, the SGP
> > returns a Registration Response message to the ASP, with a=20
> Registration
> > Status of "Error - "Cannot Support Unique Routing. An=20
> incoming signalling
> > message received at an SGP should not match against more=20
> than one Routing
> > Key.
> >
> >
> > THanks // JAvier.
> >
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > To: J.Javier Pastor (ML/EEM)
> > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > J.Javier,
> > >
> > > J.Javier Pastor (ML/EEM) wrote:
> > >                     (Wed, 14 Jan 2004 12:36:54)
> > >
> > > --snip--
> > > >
> > > > --------
> > > > New text: (Section 4.4.1)
> > > > ---------
> > > >
> > > > If the SGP determines that the requested RK partially, but
> > > not exactly,
> > > > matches an existing RK, and that an incoming signalling
> > > message received at
> > > > an SGP could possibly match both the requested and the
> > > existing RK, the SGP
> > > > returns a Registration Response message to the ASP, with a
> > > Registration
> > > > Status of "Error - "Cannot Support Unique Routing. An
> > > incoming signalling
> > > > message received at an SGP should not match against more
> > > than one Routing
> > > > Key.
> > > >
> > > --snip--
> > >
> > > I think you mean for a given ASP (Association) in the=20
> above.  Correct?
> > >
> > > It should be mentioned that the "matching" of RKs is done
> > > only against other
> > > RKs belonging to the same ASP (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
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20

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



From exim@www1.ietf.org  Wed Jan 14 09:43:31 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20633
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 09:43:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgmEZ-00035i-0r
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 09:43:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0EEh2Lj011876
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 09:43:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgmEX-00035A-Td; Wed, 14 Jan 2004 09:43:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgmEF-00034H-C6
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 09:42:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20616
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 09:42:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgmED-0006Tn-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:42:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgmDG-0006SM-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:41:43 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgmCK-0006QK-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:40:44 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id JAA00513;
	Wed, 14 Jan 2004 09:40:35 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: "J.Javier Pastor \(ML/EEM\)" <j.javier.pastor@ericsson.com>,
        "'Barry Nagelberg'" <barryn@adax.com>,
        "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Wed, 14 Jan 2004 09:38:59 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMIEEGCDAA.asveren@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C0433199D@eestqnt105.es.eu.ericsson.se>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by chuckie.dgms.com id JAA00513
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Just to refine it a bit more:
We should also mention about the case, where there is a full RK match, bu=
t
this RK is registered by another ASP (not by the ASP, which sent REGREQ).=
 In
such a case, SGP should assign a RC value for the RK/ASP and should fill =
the
RC value in REGRESP with it (if the RK was already registered by ASP send=
ing
REGREQ, SGP would have used the already allocated RC value).

   Tolga

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf O=
f
> J.Javier Pastor (ML/EEM)
> Sent: Wednesday, January 14, 2004 9:30 AM
> To: 'Barry Nagelberg'; SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
>
>
> Barry,
>
> You are right. And that is valid only for the overlapping case.
> You can not create a new AS whose associated RK overlaps another
> existing registered RK. In the duplicate case it is already
> included that the check is against the RK previosly registered by
> the sending ASP. The latter makes sense but not the former.
>
> Go back to my first proposal.
>
> Thanks // Javier.
>
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Barry Nagelberg
> > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > To: SIGTRAN Mailing List
> > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > Javier,
> >
> > No, Brian's suggestion is not correct, nor is this updated
> > text. Routing
> > keys are independent of ASPs or associations. I think perhaps Brian i=
s
> > thinking of the routing context, which may be unique for each ASP or
> > association.
> >
> > Barry Nagelberg
> >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > J.Javier Pastor (ML/EEM)
> > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > To: 'bidulock@openss7.org'
> > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > Brian,
> > >
> > > Tell me if the following is OK.
> > >
> > > If the SGP determines that the requested RK partially, but
> > not exactly,
> > > matches an existing RK already registered for the sender ASP, and
> > > that an incoming signalling message received at
> > > an SGP could possibly match both the requested and the existing
> > > RK, the SGP
> > > returns a Registration Response message to the ASP, with a
> > Registration
> > > Status of "Error - "Cannot Support Unique Routing. An
> > incoming signalling
> > > message received at an SGP should not match against more
> > than one Routing
> > > Key.
> > >
> > >
> > > THanks // JAvier.
> > >
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > To: J.Javier Pastor (ML/EEM)
> > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > J.Javier,
> > > >
> > > > J.Javier Pastor (ML/EEM) wrote:
> > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > >
> > > > --snip--
> > > > >
> > > > > --------
> > > > > New text: (Section 4.4.1)
> > > > > ---------
> > > > >
> > > > > If the SGP determines that the requested RK partially, but
> > > > not exactly,
> > > > > matches an existing RK, and that an incoming signalling
> > > > message received at
> > > > > an SGP could possibly match both the requested and the
> > > > existing RK, the SGP
> > > > > returns a Registration Response message to the ASP, with a
> > > > Registration
> > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > incoming signalling
> > > > > message received at an SGP should not match against more
> > > > than one Routing
> > > > > Key.
> > > > >
> > > > --snip--
> > > >
> > > > I think you mean for a given ASP (Association) in the
> > above.  Correct?
> > > >
> > > > It should be mentioned that the "matching" of RKs is done
> > > > only against other
> > > > RKs belonging to the same ASP (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
> >
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


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



From exim@www1.ietf.org  Wed Jan 14 09:50:35 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20881
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 09:50:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgmLP-0003NI-GB
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 09:50:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0EEo7dF012955
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 09:50:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgmLL-0003Md-DQ; Wed, 14 Jan 2004 09:50:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgmL6-0003LB-2Y
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 09:49:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20853
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 09:49:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgmL4-0006gT-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:49:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgmK8-0006ey-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:48:49 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgmJC-0006dg-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:47:51 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i0EElnkH012665
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 09:47:49 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Wed, 14 Jan 2004 09:49:18 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOOELBCDAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <GBEBKGPKHGPAOFCLBNAMIEEGCDAA.asveren@ulticom.com>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by slink5.mtl-nj.adax id i0EElnkH012665
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Tolga,

This is already covered in section 4.4.1:

<snip>

   If the received Routing Key matches an existing SGP Routing Key entry,
and
   the ASP is not currently included in the list of ASPs for the related
   Application Server, the SGP MAY authorize the ASP to be added to the
   AS.

<snip>

Barry Nagelberg

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf O=
f
> Tolga Asveren
> Sent: Wednesday, January 14, 2004 9:39 AM
> To: J.Javier Pastor (ML/EEM); 'Barry Nagelberg'; SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
>
>
> Just to refine it a bit more:
> We should also mention about the case, where there is a full RK match, =
but
> this RK is registered by another ASP (not by the ASP, which sent
> REGREQ). In
> such a case, SGP should assign a RC value for the RK/ASP and
> should fill the
> RC value in REGRESP with it (if the RK was already registered by
> ASP sending
> REGREQ, SGP would have used the already allocated RC value).
>
>    Tolga
>
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf=
 Of
> > J.Javier Pastor (ML/EEM)
> > Sent: Wednesday, January 14, 2004 9:30 AM
> > To: 'Barry Nagelberg'; SIGTRAN Mailing List
> > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > Barry,
> >
> > You are right. And that is valid only for the overlapping case.
> > You can not create a new AS whose associated RK overlaps another
> > existing registered RK. In the duplicate case it is already
> > included that the check is against the RK previosly registered by
> > the sending ASP. The latter makes sense but not the former.
> >
> > Go back to my first proposal.
> >
> > Thanks // Javier.
> >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > Barry Nagelberg
> > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > To: SIGTRAN Mailing List
> > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > Javier,
> > >
> > > No, Brian's suggestion is not correct, nor is this updated
> > > text. Routing
> > > keys are independent of ASPs or associations. I think perhaps Brian=
 is
> > > thinking of the routing context, which may be unique for each ASP o=
r
> > > association.
> > >
> > > Barry Nagelberg
> > >
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > J.Javier Pastor (ML/EEM)
> > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > To: 'bidulock@openss7.org'
> > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > Brian,
> > > >
> > > > Tell me if the following is OK.
> > > >
> > > > If the SGP determines that the requested RK partially, but
> > > not exactly,
> > > > matches an existing RK already registered for the sender ASP, and
> > > > that an incoming signalling message received at
> > > > an SGP could possibly match both the requested and the existing
> > > > RK, the SGP
> > > > returns a Registration Response message to the ASP, with a
> > > Registration
> > > > Status of "Error - "Cannot Support Unique Routing. An
> > > incoming signalling
> > > > message received at an SGP should not match against more
> > > than one Routing
> > > > Key.
> > > >
> > > >
> > > > THanks // JAvier.
> > > >
> > > > > -----Original Message-----
> > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > To: J.Javier Pastor (ML/EEM)
> > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > J.Javier,
> > > > >
> > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > >
> > > > > --snip--
> > > > > >
> > > > > > --------
> > > > > > New text: (Section 4.4.1)
> > > > > > ---------
> > > > > >
> > > > > > If the SGP determines that the requested RK partially, but
> > > > > not exactly,
> > > > > > matches an existing RK, and that an incoming signalling
> > > > > message received at
> > > > > > an SGP could possibly match both the requested and the
> > > > > existing RK, the SGP
> > > > > > returns a Registration Response message to the ASP, with a
> > > > > Registration
> > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > incoming signalling
> > > > > > message received at an SGP should not match against more
> > > > > than one Routing
> > > > > > Key.
> > > > > >
> > > > > --snip--
> > > > >
> > > > > I think you mean for a given ASP (Association) in the
> > > above.  Correct?
> > > > >
> > > > > It should be mentioned that the "matching" of RKs is done
> > > > > only against other
> > > > > RKs belonging to the same ASP (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
> > >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


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



From exim@www1.ietf.org  Wed Jan 14 09:59:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21142
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 09:59:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgmU2-0003g2-AC
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 09:59:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0EEx2LD014126
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 09:59:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgmU1-0003fe-3W; Wed, 14 Jan 2004 09:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgmTm-0003ew-65
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 09:58:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21125
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 09:58:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgmTk-0006uR-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:58:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgmSp-0006tQ-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:57:48 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgmS3-0006sN-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 09:56:59 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id JAA05156;
	Wed, 14 Jan 2004 09:56:54 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: "Barry Nagelberg" <barryn@adax.com>,
        "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Wed, 14 Jan 2004 09:55:17 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMCEEHCDAA.asveren@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <JBECLENKLBCKAAKFGAJOOELBCDAA.barryn@adax.com>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by chuckie.dgms.com id JAA05156
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Yes, you are right, my oversight.

  Tolga

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf O=
f
> Barry Nagelberg
> Sent: Wednesday, January 14, 2004 9:49 AM
> To: SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
>
>
> Tolga,
>
> This is already covered in section 4.4.1:
>
> <snip>
>
>    If the received Routing Key matches an existing SGP Routing Key entr=
y,
> and
>    the ASP is not currently included in the list of ASPs for the relate=
d
>    Application Server, the SGP MAY authorize the ASP to be added to the
>    AS.
>
> <snip>
>
> Barry Nagelberg
>
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf=
 Of
> > Tolga Asveren
> > Sent: Wednesday, January 14, 2004 9:39 AM
> > To: J.Javier Pastor (ML/EEM); 'Barry Nagelberg'; SIGTRAN Mailing List
> > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > Just to refine it a bit more:
> > We should also mention about the case, where there is a full RK
> match, but
> > this RK is registered by another ASP (not by the ASP, which sent
> > REGREQ). In
> > such a case, SGP should assign a RC value for the RK/ASP and
> > should fill the
> > RC value in REGRESP with it (if the RK was already registered by
> > ASP sending
> > REGREQ, SGP would have used the already allocated RC value).
> >
> >    Tolga
> >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > J.Javier Pastor (ML/EEM)
> > > Sent: Wednesday, January 14, 2004 9:30 AM
> > > To: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > Barry,
> > >
> > > You are right. And that is valid only for the overlapping case.
> > > You can not create a new AS whose associated RK overlaps another
> > > existing registered RK. In the duplicate case it is already
> > > included that the check is against the RK previosly registered by
> > > the sending ASP. The latter makes sense but not the former.
> > >
> > > Go back to my first proposal.
> > >
> > > Thanks // Javier.
> > >
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org
> > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > Barry Nagelberg
> > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > To: SIGTRAN Mailing List
> > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > Javier,
> > > >
> > > > No, Brian's suggestion is not correct, nor is this updated
> > > > text. Routing
> > > > keys are independent of ASPs or associations. I think
> perhaps Brian is
> > > > thinking of the routing context, which may be unique for each ASP=
 or
> > > > association.
> > > >
> > > > Barry Nagelberg
> > > >
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org
> > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > J.Javier Pastor (ML/EEM)
> > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > To: 'bidulock@openss7.org'
> > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > Brian,
> > > > >
> > > > > Tell me if the following is OK.
> > > > >
> > > > > If the SGP determines that the requested RK partially, but
> > > > not exactly,
> > > > > matches an existing RK already registered for the sender ASP, a=
nd
> > > > > that an incoming signalling message received at
> > > > > an SGP could possibly match both the requested and the existing
> > > > > RK, the SGP
> > > > > returns a Registration Response message to the ASP, with a
> > > > Registration
> > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > incoming signalling
> > > > > message received at an SGP should not match against more
> > > > than one Routing
> > > > > Key.
> > > > >
> > > > >
> > > > > THanks // JAvier.
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > > >
> > > > > >
> > > > > > J.Javier,
> > > > > >
> > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > >
> > > > > > --snip--
> > > > > > >
> > > > > > > --------
> > > > > > > New text: (Section 4.4.1)
> > > > > > > ---------
> > > > > > >
> > > > > > > If the SGP determines that the requested RK partially, but
> > > > > > not exactly,
> > > > > > > matches an existing RK, and that an incoming signalling
> > > > > > message received at
> > > > > > > an SGP could possibly match both the requested and the
> > > > > > existing RK, the SGP
> > > > > > > returns a Registration Response message to the ASP, with a
> > > > > > Registration
> > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > incoming signalling
> > > > > > > message received at an SGP should not match against more
> > > > > > than one Routing
> > > > > > > Key.
> > > > > > >
> > > > > > --snip--
> > > > > >
> > > > > > I think you mean for a given ASP (Association) in the
> > > > above.  Correct?
> > > > > >
> > > > > > It should be mentioned that the "matching" of RKs is done
> > > > > > only against other
> > > > > > RKs belonging to the same ASP (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
> > > >
> > >
> > > _______________________________________________
> > > 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 exim@www1.ietf.org  Wed Jan 14 13:09:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00987
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 13:09:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgpRv-0006QT-O8
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 13:09:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0EI93M1024695
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 13:09:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgpRt-0006Q7-U5; Wed, 14 Jan 2004 13:09:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgpRm-0006Pv-Kc
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 13:08:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00981
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 13:08:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgpRk-0000Pk-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 13:08:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgpQt-0000OQ-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 13:07:59 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[5XLaKwsvk+S2T3uAXG0IarW7il2tl73Q])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgpQD-0000MJ-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 13:07:18 -0500
Received: from ns.pigworks.openss7.net (IDENT:dfnAd++K03ahW8+JMV32WeQxQDvCYONO@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0EI79I08726;
	Wed, 14 Jan 2004 11:07:09 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0EI79C11854;
	Wed, 14 Jan 2004 11:07:09 -0700
Date: Wed, 14 Jan 2004 11:07:09 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>,
        "Ken Morneault (E-mail)" <kmorneau@cisco.com>
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
Message-ID: <20040114110709.C11446@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>,
	"Ken Morneault (E-mail)" <kmorneau@cisco.com>
References: <1AB3D30B989BF141BBD5C70057B2EF7C0433199C@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C0433199C@eestqnt105.es.eu.ericsson.se>; from j.javier.pastor@ericsson.com on Wed, Jan 14, 2004 at 02:37:45PM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i0EI79I08726
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

J.Javier,

Sounds good.

--brian

J.Javier Pastor (ML/EEM) wrote:                                          =
         (Wed, 14 Jan 2004 14:37:45)
> Brian,=20
>=20
> Tell me if the following is OK.=20
>=20
> If the SGP determines that the requested RK partially, but not exactly,
> matches an existing RK already registered for the sender ASP, and that =
an incoming signalling message received at
> an SGP could possibly match both the requested and the existing RK, the=
 SGP
> returns a Registration Response message to the ASP, with a Registration
> Status of "Error - "Cannot Support Unique Routing. An incoming signalli=
ng
> message received at an SGP should not match against more than one Routi=
ng
> Key.
>=20
>=20
> THanks // JAvier.
>=20
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > To: J.Javier Pastor (ML/EEM)
> > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> >=20
> >=20
> > J.Javier,
> >=20
> > J.Javier Pastor (ML/EEM) wrote:                              =20
> >                     (Wed, 14 Jan 2004 12:36:54)
> >=20
> > --snip--
> > >=20
> > > --------=20
> > > New text: (Section 4.4.1)=20
> > > ---------
> > >=20
> > > If the SGP determines that the requested RK partially, but=20
> > not exactly,
> > > matches an existing RK, and that an incoming signalling=20
> > message received at
> > > an SGP could possibly match both the requested and the=20
> > existing RK, the SGP
> > > returns a Registration Response message to the ASP, with a=20
> > Registration
> > > Status of "Error - "Cannot Support Unique Routing. An=20
> > incoming signalling
> > > message received at an SGP should not match against more=20
> > than one Routing
> > > Key.
> > >=20
> > --snip--
> >=20
> > I think you mean for a given ASP (Association) in the above.  Correct=
?
> >=20
> > It should be mentioned that the "matching" of RKs is done=20
> > only against other
> > RKs belonging to the same ASP (Association).
> >=20
> > --brian
> >=20
> > --=20
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >=20

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

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



From exim@www1.ietf.org  Wed Jan 14 13:18:28 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01394
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 13:18:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Agpab-0006sE-ST
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 13:18:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0EII1WS026398
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 13:18:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Agpab-0006rd-IG; Wed, 14 Jan 2004 13:18:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgpaP-0006rD-K4
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 13:17:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01354
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 13:17:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgpaN-0000qD-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 13:17:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgpZP-0000oF-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 13:16:47 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[kFyUE2uknqa/I/mcBMsPhxFeZY0XWXtU])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgpYQ-0000ld-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 13:15:47 -0500
Received: from ns.pigworks.openss7.net (IDENT:z6KWg/1ZzmGuvOIOVcJjejIefUHl9UoI@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0EIFkI08816;
	Wed, 14 Jan 2004 11:15:46 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0EIFkE11952;
	Wed, 14 Jan 2004 11:15:46 -0700
Date: Wed, 14 Jan 2004 11:15:45 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
Cc: "'Barry Nagelberg'" <barryn@adax.com>,
        SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
Message-ID: <20040114111545.D11446@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>,
	'Barry Nagelberg' <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <1AB3D30B989BF141BBD5C70057B2EF7C0433199D@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C0433199D@eestqnt105.es.eu.ericsson.se>; from j.javier.pastor@ericsson.com on Wed, Jan 14, 2004 at 03:30:10PM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i0EIFkI08816
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

J.Javier,

Just to clarify, there should be nothing stopping an implementation from
allowing ASP1 to register for, say, 5-5-5 (ISUP), ASP2 to register for
5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).

In this case, although ASP3 registers after ASP1 and ASP2, there is nothi=
ng
stopping an SG from assigining a RK and RC to 5-5-5(*) for ASP3.

An SG implementation could choose to refuse 5-5-5(*) and require ASP3
to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or it might not.
I don't think it is the RFC's place to require one or the other.  So,
for in the case where there is an overlap between "different" APSs, it
should be left up to the SG implementation as it is now.

Your additional text below, now clarifies that.  Thank you.

--brian


J.Javier Pastor (ML/EEM) wrote:                                          =
         (Wed, 14 Jan 2004 15:30:10)
> Barry,=20
>=20
> You are right. And that is valid only for the overlapping case. You can=
 not create a new AS whose associated RK overlaps another existing regist=
ered RK. In the duplicate case it is already included that the check is a=
gainst the RK previosly registered by the sending ASP. The latter makes s=
ense but not the former.
>=20
> Go back to my first proposal.
>=20
> Thanks // Javier.
>=20
> > -----Original Message-----
> > From: sigtran-admin@ietf.org=20
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Barry Nagelberg
> > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > To: SIGTRAN Mailing List
> > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> >=20
> >=20
> > Javier,
> >=20
> > No, Brian's suggestion is not correct, nor is this updated=20
> > text. Routing
> > keys are independent of ASPs or associations. I think perhaps Brian i=
s
> > thinking of the routing context, which may be unique for each ASP or
> > association.
> >=20
> > Barry Nagelberg
> >=20
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org=20
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > J.Javier Pastor (ML/EEM)
> > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > To: 'bidulock@openss7.org'
> > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > Brian,
> > >
> > > Tell me if the following is OK.
> > >
> > > If the SGP determines that the requested RK partially, but=20
> > not exactly,
> > > matches an existing RK already registered for the sender ASP, and
> > > that an incoming signalling message received at
> > > an SGP could possibly match both the requested and the existing
> > > RK, the SGP
> > > returns a Registration Response message to the ASP, with a=20
> > Registration
> > > Status of "Error - "Cannot Support Unique Routing. An=20
> > incoming signalling
> > > message received at an SGP should not match against more=20
> > than one Routing
> > > Key.
> > >
> > >
> > > THanks // JAvier.
> > >
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > To: J.Javier Pastor (ML/EEM)
> > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > J.Javier,
> > > >
> > > > J.Javier Pastor (ML/EEM) wrote:
> > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > >
> > > > --snip--
> > > > >
> > > > > --------
> > > > > New text: (Section 4.4.1)
> > > > > ---------
> > > > >
> > > > > If the SGP determines that the requested RK partially, but
> > > > not exactly,
> > > > > matches an existing RK, and that an incoming signalling
> > > > message received at
> > > > > an SGP could possibly match both the requested and the
> > > > existing RK, the SGP
> > > > > returns a Registration Response message to the ASP, with a
> > > > Registration
> > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > incoming signalling
> > > > > message received at an SGP should not match against more
> > > > than one Routing
> > > > > Key.
> > > > >
> > > > --snip--
> > > >
> > > > I think you mean for a given ASP (Association) in the=20
> > above.  Correct?
> > > >
> > > > It should be mentioned that the "matching" of RKs is done
> > > > only against other
> > > > RKs belonging to the same ASP (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
> >=20
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Wed Jan 14 13:24:27 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01639
	for <sigtran-archive@odin.ietf.org>; Wed, 14 Jan 2004 13:24:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgpgP-00075X-Fv
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 13:24:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0EIO1Pp027230
	for sigtran-archive@odin.ietf.org; Wed, 14 Jan 2004 13:24:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgpgO-00074v-SH; Wed, 14 Jan 2004 13:24:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgpgD-00074O-T5
	for sigtran@optimus.ietf.org; Wed, 14 Jan 2004 13:23:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01582
	for <sigtran@ietf.org>; Wed, 14 Jan 2004 13:23:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgpgB-00013T-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 13:23:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgpfE-00011e-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 13:22:49 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[KvEMFAmSsf2IEcjFknQCmUa8ztFaUuXi])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgpeN-00010Y-00
	for sigtran@ietf.org; Wed, 14 Jan 2004 13:21:55 -0500
Received: from ns.pigworks.openss7.net (IDENT:9u6jSy7CSRLT0yVyISWRzRPQfzqxwAAz@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0EILtI08879;
	Wed, 14 Jan 2004 11:21:55 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0EILtA12011;
	Wed, 14 Jan 2004 11:21:55 -0700
Date: Wed, 14 Jan 2004 11:21:54 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry Nagelberg <barryn@adax.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA: Network Appearance in Routing Key parameter
Message-ID: <20040114112154.E11446@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry Nagelberg <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <1AB3D30B989BF141BBD5C70057B2EF7C0433199B@eestqnt105.es.eu.ericsson.se> <JBECLENKLBCKAAKFGAJOEELACDAA.barryn@adax.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: <JBECLENKLBCKAAKFGAJOEELACDAA.barryn@adax.com>; from barryn@adax.com on Wed, Jan 14, 2004 at 09:16:27AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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,

I disagree.  That would impede the ability of an SG implementation to
rationally assign an NA where none is provided, relieving the ASP of
the need to provision NAs of which it has no knowledge.  An ASP that
operates in a single NA need not have to be provisioned with NA, nor
does it need to include it in the message, regardless of the number
of networks for which the SG is provisioned.

Besides, the "conditional" was never on the basis of the SG, but was
on the basis of the association.  If the association (i.e. SG-ASP tuple) is
provisioned to operate in more than one network then NA should be provided.
But how many networks an SGP operates in is of little moment.

--brian

Barry Nagelberg wrote:                                                               (Wed, 14 Jan 2004 09:16:27)
> Javier,
> 
> Regarding the "last" sentence that I mentioned below, that is currently in
> the RFC and is very confusing:
> 
> <snip>
> The absence of the Network Appearance parameter in the Routing Key indicates
> the use of any Network Appearance value.
> <snip>
> 
> Your suggestion below -
> 
> "I think it is the use as a wildcard what is stated here, but for creating
> different ASes at the same time, one per available NA."
> 
> - is not very helpful in relieving the confusion. I suggest that we stick
> with the "conditional" parameter, which MUST be present if the SGP is
> handling traffic for more than one SS7 network.
> 
> Barry Nagelberg
> 
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> > J.Javier Pastor (ML/EEM)
> > Sent: Wednesday, January 14, 2004 7:06 AM
> > To: 'bidulock@openss7.org'; Tolga Asveren
> > Cc: SIGTRAN Mailing List
> > Subject: RE: [Sigtran] M3UA: Network Appearance in Routing Key parameter
> >
> >
> > Hi,
> >
> > Yes, although a "weak conditional", we should turn it into
> > conditional to follow a consistent labeling. We'll make the
> > change for the new version.
> >
> > Regarding the last sentence Barry mentions, I think it is the use
> > as a wildcard what is stated here, but for creating different
> > ASes at the same time, one per available NA. Would this be acceptable?
> >
> > Thanks // Javier.
> >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > Brian F. G. Bidulock
> > > Sent: jueves, 25 de diciembre de 2003 4:25
> > > To: Tolga Asveren
> > > Cc: SIGTRAN Mailing List
> > > Subject: Re: [Sigtran] M3UA: Network Appearance in Routing
> > > Key parameter
> > >
> > >
> > > Tolga,
> > >
> > > It probably should be "conditional".   I think it
> > > is just one "optional" we missed in the change to
> > > "conditional".
> > >
> > > I am quite sure that in dicussions we were not going
> > > to allow an AS to span NA.  It would not be terribly
> > > useful, anyway.
> > >
> > > However, because registration must be provisioned at
> > > the SG, it is always possible to provision a per-ASP
> > > default, regardless of the fact that the SG may exist
> > > in more than on NA.  All that the SG needs to know is
> > > that this particular ASP only registers (or default
> > > registers) in a given NA.  So I would say, at most
> > > a "weak conditional".  Perhaps that's why we left it
> > > as optional.
> > >
> > > --brian
> > >
> > >
> > > Tolga Asveren wrote:
> > >                        (Wed, 24 Dec 2003 13:36:43)
> > > > No, no, that was not what I tried to say, I thought
> > > > creating multiple RKs, one for each network. But this
> > > > also won't work, because there will be only one
> > > > registration result per request, I missed that part.
> > > > Otherwise thinking to link one AS to multiple networks
> > > > will definitly violate the principle of not spanning
> > > > multiple SPMS in an AS, which definitly will break a
> > > > lot of mechanisms in the protocol.
> > > >
> > > > So, seems I am remembering wrong, anybody any idea
> > > > about the original question? Now, seems to me
> > > > something to be corrected....
> > > >
> > > >     Tolga
> > > > --- Barry Nagelberg <barryn@adax.com> wrote:
> > > > > Tolga,
> > > > >
> > > > > Thanks, but I don't think that your interpretation
> > > > > below is useful.
> > > > >
> > > > > Let's not forget that the Reg Req is, among other
> > > > > things, a request by the
> > > > > ASP to create a new AS. Your interpretation means
> > > > > that the SGP would be
> > > > > linking this single, newly-created AS to multiple
> > > > > SS7 networks. I don't
> > > > > think that this is practical. A given AS should be
> > > > > linked to exactly one SS7
> > > > > network.
> > > > >
> > > > > Barry Nagelberg
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: sigtran-admin@ietf.org
> > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > Tolga Asveren
> > > > > > Sent: Wednesday, December 24, 2003 3:28 PM
> > > > > > To: SIGTRAN Mailing List
> > > > > > Subject: Re: [Sigtran] M3UA: Network Appearance in
> > > > > Routing Key parameter
> > > > > >
> > > > > >
> > > > > > Hi Barry,
> > > > > >
> > > > > > As far as I remember -not 100% sure though- it
> > > > > means
> > > > > > the following:
> > > > > > If NA is not there, ASP wants to register for the
> > > > > > specified traffic range in every network on SG.
> > > > > So, it
> > > > > > really is optinal, because it is possible to
> > > > > operate
> > > > > > in that way, even if there are multiple networks.
> > > > > >
> > > > > > Whether this is really usefull or not is a
> > > > > different
> > > > > > issue. At least now, a conditional NA parameter,
> > > > > which
> > > > > > must be included in case of multiple networks
> > > > > sound
> > > > > > more logical and easier to understand. In such a
> > > > > case,
> > > > > > there will be a need of multiple registration for
> > > > > each
> > > > > > network, even if PC/traffic range of AS is the
> > > > > same in
> > > > > > each network, but practically I wouldn't think
> > > > > this as
> > > > > > a huge problem. On the other hand, I would think,
> > > > > as
> > > > > > it is right now, is alo not a huge problem.
> > > > > >
> > > > > >     Tolga
> > > > > > --- Barry Nagelberg <barryn@adax.com> wrote:
> > > > > > > RFC 3332, in section 3.6.1, states that the
> > > > > Network
> > > > > > > Appearance parameter is
> > > > > > > optional in the Routing Key parameter of a REG
> > > > > REQ
> > > > > > > msg:
> > > > > > >
> > > > > > > <snip>
> > > > > > > The optional Network Appearance parameter field
> > > > > > > identifies the SS7
> > > > > > > network context for the Routing Key, and has the
> > > > > > > same format as in
> > > > > > > the DATA message (See Section 3.3.1) with the
> > > > > > > exception that it
> > > > > > > does not have to be the first parameter in the
> > > > > > > message.  The
> > > > > > > absence of the Network Appearance parameter in
> > > > > the
> > > > > > > Routing Key
> > > > > > > indicates the use of any Network Appearance
> > > > > value.
> > > > > > > <snip>
> > > > > > >
> > > > > > > There are at least 2 problems here:
> > > > > > >
> > > > > > > 1. This parameter should be conditional, not
> > > > > > > optional. It should be
> > > > > > > conditional in the sense that it is required
> > > > > when
> > > > > > > the SGP is handling
> > > > > > > traffic for more than one SS7 network. If such
> > > > > an
> > > > > > > SGP receives a Routing Key
> > > > > > > from the ASP with no Network Appearance
> > > > > parameter,
> > > > > > > how can the SGP possibly
> > > > > > > know to which SS7 network to link the
> > > > > newly-created
> > > > > > > Routing Key/AS/Routing
> > > > > > > Context?
> > > > > > >
> > > > > > > 2. The last sentence is very confusing. What is
> > > > > > > meant by "indicates the use
> > > > > > > of any Network Appearance value."? Use where? To
> > > > > > > indicate what?
> > > > > > >
> > > > > > > Barry Nagelberg
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jan 15 04:43:31 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21621
	for <sigtran-archive@odin.ietf.org>; Thu, 15 Jan 2004 04:43:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah41n-0007uh-NY
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 04:43:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0F9h3eC030420
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 04:43:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah41l-0007u3-IN; Thu, 15 Jan 2004 04:43:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah41D-0007sa-Jr
	for sigtran@optimus.ietf.org; Thu, 15 Jan 2004 04:42:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21571
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 04:42:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah41A-0007FQ-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 04:42:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah40J-0007Bw-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 04:41:32 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah3zL-00078t-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 04:40:31 -0500
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i0F9eTYG015947;
	Thu, 15 Jan 2004 10:40:29 +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.2657.72)
	id ZJAJ2DSZ; Thu, 15 Jan 2004 10:40:29 +0100
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <CRN65JM6>; Thu, 15 Jan 2004 10:40:31 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C0433199F@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "'Barry Nagelberg'" <barryn@adax.com>,
        SIGTRAN Mailing List
	 <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Thu, 15 Jan 2004 10:39:47 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

It seems good to me.

Cheers // Javier.

> -----Original Message-----
> From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Barry Nagelberg
> Sent: mi=E9rcoles, 14 de enero de 2004 15:04
> To: SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
>=20
>=20
> Javier,
>=20
> Thanks. For the sake of clarity, I suggest the following changes:
>=20
> <snip>
>=20
> 3.6.1 Description of the problem
>=20
> The RFC does not clearly specify what the SG should do when=20
> it receives a
> Registration Request for a Routing Key that has already been=20
> registered.
> There are 3 scenarios to consider:
>=20
> 1. The registration request is an exact duplicate of a registered RK =
by the sending ASP.
> 2. The registration request partially overlaps a registered RK in the =
SGP.
> 3. The ASP is requesting to modify a registered RK.
>=20
> <snip>
>=20
> Barry Nagelberg
>=20
> > -----Original Message-----
> > From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> > J.Javier Pastor (ML/EEM)
> > Sent: Wednesday, January 14, 2004 6:37 AM
> > To: SIGTRAN Mailing List
> > Cc: Ken Morneault (E-mail)
> > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > Hi guys,
> >
> > Here we send the new text proposal to clarify this issue
> > according your comments.
> >
> > Thanks // Javier.
> >
> >
> >
> > 3.6 Receiving REG for a RK already registered
> >
> > 3.6.1 Description of the problem
> >
> > The RFC does not clearly specify what the SG should do when it
> > receives a Registration Request for a Routing Key that has
> > already been registered. There are two scenarios to consider: the
> > registration request is a duplicate, it overlaps partially an
> > already registered RK. Also there is a desire to include the
> > possibility of modifying a registered  Routing Key.
> >
> > 3.6.2 Text changes to the document
> >
> > ---------
> > Old text: (Section 3.6.1)
> > ---------
> >
> > The format of the Routing Key parameter 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
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |                       Local-RK-Identifier                     |
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |                  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)               |
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> > ---------
> > New text: (Section 3.6.1)
> > ---------
> >
> > The format of the Routing Key parameter 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
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |                       Local-RK-Identifier                     |
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |                   Routing Context (optional)                  |
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |                  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)               |
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> > ---------
> > Old text: (Section 3.6.2)
> > ---------
> >
> > Registration Status: 32-bit integer
> >
> >   The Registration Result Status field indicates the success or the
> >   reason for failure of a registration request.
> >   Its values may be:
> >
> >      0           Successfully Registered
> >      1           Error - Unknown
> >      2           Error - Invalid DPC
> >      3           Error - Invalid Network Appearance
> >      4           Error - Invalid Routing Key
> >      5           Error - Permission Denied
> >      6           Error - Cannot Support Unique Routing
> >      7           Error - Routing Key not Currently Provisioned
> >      8           Error - Insufficient Resources
> >      9           Error - Unsupported RK parameter Field
> >      10          Error - Unsupported/Invalid Traffic Handling Mode
> >
> > ---------
> > New text: (Section 3.6.2)
> > ---------
> >
> > Registration Status: 32-bit integer
> >
> >   The Registration Result Status field indicates the success or the
> >   reason for failure of a registration request.
> >   Its values may be:
> >      0           Successfully Registered
> >      1           Error - Unknown
> >      2           Error - Invalid DPC
> >      3           Error - Invalid Network Appearance
> >      4           Error - Invalid Routing Key
> >      5           Error - Permission Denied
> >      6           Error - Cannot Support Unique Routing
> >      7           Error - Routing Key not Currently Provisioned
> >      8           Error - Insufficient Resources
> >      9           Error - Unsupported RK parameter Field
> >      10          Error - Unsupported/Invalid Traffic Handling Mode
> >      11          Error - Routing Key Change Refused
> >      12          Error - Routing Key Already Registered
> >
> >
> > ---------
> > Old text: (Section 4.4.1)
> > ---------
> >
> > If the SGP determines that a unique Routing Key cannot be
> > created, the SGP returns a Registration Response message to the
> > ASP, with a Registration Status of "Error - "Cannot Support
> > Unique Routing"  An incoming signalling message received at an
> > SGP should not match against more than one Routing Key.
> >
> > --------
> > New text: (Section 4.4.1)
> > ---------
> >
> > If the SGP determines that the requested RK partially, but not
> > exactly, matches an existing RK, and that an incoming signalling
> > message received at an SGP could possibly match both the
> > requested and the existing RK, the SGP returns a Registration
> > Response message to the ASP, with a Registration Status of "Error
> > - "Cannot Support Unique Routing. An incoming signalling message
> > received at an SGP should not match against more than one=20
> Routing Key.
> >
> > If the SGP determines that the received RK was already
> > registered, fully and exactly, either statically or dynamically,
> > by the sending ASP, the SGP returns a Registration Response
> > message to the ASP, containing a Registration Result "Error -
> > Routing Key Already Registered ". This error applies whether the
> > Routing Key is Active or Inactive. For this error code, RC field
> > in Registration Response message MUST be populated with the
> > actual value of RC in SGP corresponding to the specified RK in
> > Registration Request message.
> >
> > An ASP MAY modify an existing Routing Key by including a Routing
> > Context parameter in the REG REQ.  If the SGP determines that the
> > Routing Context applies to an existing Routing Key the SG MAY
> > adjust the existing Routing Key to match the new information
> > provided in the Routing Key parameter.  A Registration Response
> > "ERR - Routing Key Change Refused" is returned if the SGP does
> > not accept the modification of the Routing Key due to either it
> > does not support the re-registration procedure or the specific RC
> > does not exist. Otherwise if the change is accepted, a
> > Registration Response "Successfully Registered" is returned.
> >
> > 3.6.3 Solution description
> >
> > The two cases, RK overlap and RK duplication, have been
> > differentiated and explained in detail. The latter will use a new
> > specific Error Code as defined above. Also the possibility of
> > modification to a Routing Key is included with the addition of a
> > new parameter in the REG REQ message and the corresponding
> > explanation in the procedures section.
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20

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



From exim@www1.ietf.org  Thu Jan 15 05:53:29 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26622
	for <sigtran-archive@odin.ietf.org>; Thu, 15 Jan 2004 05:53:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah57V-0004Ud-MG
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 05:53:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0FAr1W5017270
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 05:53:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah57U-0004UM-Gp; Thu, 15 Jan 2004 05:53:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah56s-0004U7-CC
	for sigtran@optimus.ietf.org; Thu, 15 Jan 2004 05:52:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26563
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 05:52:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah56o-0005Dy-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 05:52:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah55q-0005BW-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 05:51:19 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[sfAb4uO4263CGlqOhVpwva1OXy9u6k5z])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah54r-000585-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 05:50:18 -0500
Received: from ns.pigworks.openss7.net (IDENT:uJ88orca1CXFAYAnD7QWcgZ3OJVRk6fr@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0FAoHI24424;
	Thu, 15 Jan 2004 03:50:17 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0FAoH726369;
	Thu, 15 Jan 2004 03:50:17 -0700
Date: Thu, 15 Jan 2004 03:50:17 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
Cc: "'Barry Nagelberg'" <barryn@adax.com>,
        SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
Message-ID: <20040115035017.E22297@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>,
	'Barry Nagelberg' <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <1AB3D30B989BF141BBD5C70057B2EF7C0433199F@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C0433199F@eestqnt105.es.eu.ericsson.se>; from j.javier.pastor@ericsson.com on Thu, Jan 15, 2004 at 10:39:47AM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i0FAoHI24424
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

J.Javier,

Sure, just change to:

1. The registration request is an exact duplicate of a registered RK by t=
he sending ASP.
2. The registration request partially overlaps a registered RK in the SGP=
 for the sending ASP.
3. The ASP is requesting to modify a registered RK.

Thanks.

--brian

J.Javier Pastor (ML/EEM) wrote:                                          =
         (Thu, 15 Jan 2004 10:39:47)
> It seems good to me.
>=20
> Cheers // Javier.
>=20
> > -----Original Message-----
> > From: sigtran-admin@ietf.org=20
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Barry Nagelberg
> > Sent: mi=E9rcoles, 14 de enero de 2004 15:04
> > To: SIGTRAN Mailing List
> > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> >=20
> >=20
> > Javier,
> >=20
> > Thanks. For the sake of clarity, I suggest the following changes:
> >=20
> > <snip>
> >=20
> > 3.6.1 Description of the problem
> >=20
> > The RFC does not clearly specify what the SG should do when=20
> > it receives a
> > Registration Request for a Routing Key that has already been=20
> > registered.
> > There are 3 scenarios to consider:
> >=20
> > 1. The registration request is an exact duplicate of a registered RK =
by the sending ASP.
> > 2. The registration request partially overlaps a registered RK in the=
 SGP.
> > 3. The ASP is requesting to modify a registered RK.
> >=20
> > <snip>
> >=20
> > Barry Nagelberg
> >=20
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org=20
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > J.Javier Pastor (ML/EEM)
> > > Sent: Wednesday, January 14, 2004 6:37 AM
> > > To: SIGTRAN Mailing List
> > > Cc: Ken Morneault (E-mail)
> > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > Hi guys,
> > >
> > > Here we send the new text proposal to clarify this issue
> > > according your comments.
> > >
> > > Thanks // Javier.
> > >
> > >
> > >
> > > 3.6 Receiving REG for a RK already registered
> > >
> > > 3.6.1 Description of the problem
> > >
> > > The RFC does not clearly specify what the SG should do when it
> > > receives a Registration Request for a Routing Key that has
> > > already been registered. There are two scenarios to consider: the
> > > registration request is a duplicate, it overlaps partially an
> > > already registered RK. Also there is a desire to include the
> > > possibility of modifying a registered  Routing Key.
> > >
> > > 3.6.2 Text changes to the document
> > >
> > > ---------
> > > Old text: (Section 3.6.1)
> > > ---------
> > >
> > > The format of the Routing Key parameter 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
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                       Local-RK-Identifier                     |
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                  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)               |
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >
> > > ---------
> > > New text: (Section 3.6.1)
> > > ---------
> > >
> > > The format of the Routing Key parameter 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
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                       Local-RK-Identifier                     |
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                   Routing Context (optional)                  |
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                  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)               |
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >
> > > ---------
> > > Old text: (Section 3.6.2)
> > > ---------
> > >
> > > Registration Status: 32-bit integer
> > >
> > >   The Registration Result Status field indicates the success or the
> > >   reason for failure of a registration request.
> > >   Its values may be:
> > >
> > >      0           Successfully Registered
> > >      1           Error - Unknown
> > >      2           Error - Invalid DPC
> > >      3           Error - Invalid Network Appearance
> > >      4           Error - Invalid Routing Key
> > >      5           Error - Permission Denied
> > >      6           Error - Cannot Support Unique Routing
> > >      7           Error - Routing Key not Currently Provisioned
> > >      8           Error - Insufficient Resources
> > >      9           Error - Unsupported RK parameter Field
> > >      10          Error - Unsupported/Invalid Traffic Handling Mode
> > >
> > > ---------
> > > New text: (Section 3.6.2)
> > > ---------
> > >
> > > Registration Status: 32-bit integer
> > >
> > >   The Registration Result Status field indicates the success or the
> > >   reason for failure of a registration request.
> > >   Its values may be:
> > >      0           Successfully Registered
> > >      1           Error - Unknown
> > >      2           Error - Invalid DPC
> > >      3           Error - Invalid Network Appearance
> > >      4           Error - Invalid Routing Key
> > >      5           Error - Permission Denied
> > >      6           Error - Cannot Support Unique Routing
> > >      7           Error - Routing Key not Currently Provisioned
> > >      8           Error - Insufficient Resources
> > >      9           Error - Unsupported RK parameter Field
> > >      10          Error - Unsupported/Invalid Traffic Handling Mode
> > >      11          Error - Routing Key Change Refused
> > >      12          Error - Routing Key Already Registered
> > >
> > >
> > > ---------
> > > Old text: (Section 4.4.1)
> > > ---------
> > >
> > > If the SGP determines that a unique Routing Key cannot be
> > > created, the SGP returns a Registration Response message to the
> > > ASP, with a Registration Status of "Error - "Cannot Support
> > > Unique Routing"  An incoming signalling message received at an
> > > SGP should not match against more than one Routing Key.
> > >
> > > --------
> > > New text: (Section 4.4.1)
> > > ---------
> > >
> > > If the SGP determines that the requested RK partially, but not
> > > exactly, matches an existing RK, and that an incoming signalling
> > > message received at an SGP could possibly match both the
> > > requested and the existing RK, the SGP returns a Registration
> > > Response message to the ASP, with a Registration Status of "Error
> > > - "Cannot Support Unique Routing. An incoming signalling message
> > > received at an SGP should not match against more than one=20
> > Routing Key.
> > >
> > > If the SGP determines that the received RK was already
> > > registered, fully and exactly, either statically or dynamically,
> > > by the sending ASP, the SGP returns a Registration Response
> > > message to the ASP, containing a Registration Result "Error -
> > > Routing Key Already Registered ". This error applies whether the
> > > Routing Key is Active or Inactive. For this error code, RC field
> > > in Registration Response message MUST be populated with the
> > > actual value of RC in SGP corresponding to the specified RK in
> > > Registration Request message.
> > >
> > > An ASP MAY modify an existing Routing Key by including a Routing
> > > Context parameter in the REG REQ.  If the SGP determines that the
> > > Routing Context applies to an existing Routing Key the SG MAY
> > > adjust the existing Routing Key to match the new information
> > > provided in the Routing Key parameter.  A Registration Response
> > > "ERR - Routing Key Change Refused" is returned if the SGP does
> > > not accept the modification of the Routing Key due to either it
> > > does not support the re-registration procedure or the specific RC
> > > does not exist. Otherwise if the change is accepted, a
> > > Registration Response "Successfully Registered" is returned.
> > >
> > > 3.6.3 Solution description
> > >
> > > The two cases, RK overlap and RK duplication, have been
> > > differentiated and explained in detail. The latter will use a new
> > > specific Error Code as defined above. Also the possibility of
> > > modification to a Routing Key is included with the addition of a
> > > new parameter in the REG REQ message and the corresponding
> > > explanation in the procedures section.
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >=20
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jan 15 06:15:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27789
	for <sigtran-archive@odin.ietf.org>; Thu, 15 Jan 2004 06:15:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah5Sp-0006AJ-So
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 06:15:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0FBF3MD023680
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 06:15:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah5So-00069X-Tg; Thu, 15 Jan 2004 06:15:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah5SE-00068G-Ub
	for sigtran@optimus.ietf.org; Thu, 15 Jan 2004 06:14:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27714
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 06:14:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah5SB-0006e5-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 06:14:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah5RF-0006Z4-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 06:13:26 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah5QI-0006U5-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 06:12:26 -0500
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i0FBCPAh015967;
	Thu, 15 Jan 2004 12:12:25 +0100
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id CZDF4TW7; Thu, 15 Jan 2004 12:12:25 +0100
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <VRLK0H3V>; Thu, 15 Jan 2004 12:09:37 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C043319A9@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: "'Barry Nagelberg'" <barryn@adax.com>,
        SIGTRAN Mailing List
	 <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Thu, 15 Jan 2004 12:11:40 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Brian,=20

Why don't you take the following approach...

Define two different ASes:
- AS1 -> 5-5-5 (ISUP)
- AS2 -> 5-5-5 (SCCP)

ASP1 registers within AS1
ASP2 registers within AS2
ASP3 registers within both AS1 and AS2

It is important to keep one unique routing per AS. ASes MUST not =
overlap.

Cheers // Javier.

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> To: J.Javier Pastor (ML/EEM)
> Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
>=20
>=20
> J.Javier,
>=20
> Just to clarify, there should be nothing stopping an=20
> implementation from
> allowing ASP1 to register for, say, 5-5-5 (ISUP), ASP2 to register =
for
> 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
>=20
> In this case, although ASP3 registers after ASP1 and ASP2,=20
> there is nothing
> stopping an SG from assigining a RK and RC to 5-5-5(*) for ASP3.
>=20
> An SG implementation could choose to refuse 5-5-5(*) and require ASP3
> to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or it=20
> might not.
> I don't think it is the RFC's place to require one or the other.  So,
> for in the case where there is an overlap between "different" APSs, =
it
> should be left up to the SG implementation as it is now.
>=20
> Your additional text below, now clarifies that.  Thank you.
>=20
> --brian
>=20
>=20
> J.Javier Pastor (ML/EEM) wrote:                              =20
>                     (Wed, 14 Jan 2004 15:30:10)
> > Barry,=20
> >=20
> > You are right. And that is valid only for the overlapping=20
> case. You can not create a new AS whose associated RK=20
> overlaps another existing registered RK. In the duplicate=20
> case it is already included that the check is against the RK=20
> previosly registered by the sending ASP. The latter makes=20
> sense but not the former.
> >=20
> > Go back to my first proposal.
> >=20
> > Thanks // Javier.
> >=20
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org=20
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > Barry Nagelberg
> > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > To: SIGTRAN Mailing List
> > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > >=20
> > >=20
> > > Javier,
> > >=20
> > > No, Brian's suggestion is not correct, nor is this updated=20
> > > text. Routing
> > > keys are independent of ASPs or associations. I think=20
> perhaps Brian is
> > > thinking of the routing context, which may be unique for=20
> each ASP or
> > > association.
> > >=20
> > > Barry Nagelberg
> > >=20
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org=20
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > J.Javier Pastor (ML/EEM)
> > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > To: 'bidulock@openss7.org'
> > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > Brian,
> > > >
> > > > Tell me if the following is OK.
> > > >
> > > > If the SGP determines that the requested RK partially, but=20
> > > not exactly,
> > > > matches an existing RK already registered for the=20
> sender ASP, and
> > > > that an incoming signalling message received at
> > > > an SGP could possibly match both the requested and the existing
> > > > RK, the SGP
> > > > returns a Registration Response message to the ASP, with a=20
> > > Registration
> > > > Status of "Error - "Cannot Support Unique Routing. An=20
> > > incoming signalling
> > > > message received at an SGP should not match against more=20
> > > than one Routing
> > > > Key.
> > > >
> > > >
> > > > THanks // JAvier.
> > > >
> > > > > -----Original Message-----
> > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > To: J.Javier Pastor (ML/EEM)
> > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > J.Javier,
> > > > >
> > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > >
> > > > > --snip--
> > > > > >
> > > > > > --------
> > > > > > New text: (Section 4.4.1)
> > > > > > ---------
> > > > > >
> > > > > > If the SGP determines that the requested RK partially, but
> > > > > not exactly,
> > > > > > matches an existing RK, and that an incoming signalling
> > > > > message received at
> > > > > > an SGP could possibly match both the requested and the
> > > > > existing RK, the SGP
> > > > > > returns a Registration Response message to the ASP, with a
> > > > > Registration
> > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > incoming signalling
> > > > > > message received at an SGP should not match against more
> > > > > than one Routing
> > > > > > Key.
> > > > > >
> > > > > --snip--
> > > > >
> > > > > I think you mean for a given ASP (Association) in the=20
> > > above.  Correct?
> > > > >
> > > > > It should be mentioned that the "matching" of RKs is done
> > > > > only against other
> > > > > RKs belonging to the same ASP (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
> > >=20
> > >=20
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >=20
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20

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



From exim@www1.ietf.org  Thu Jan 15 07:17:31 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00837
	for <sigtran-archive@odin.ietf.org>; Thu, 15 Jan 2004 07:17:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah6Qn-0001bR-8n
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 07:17:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0FCH1bq006149
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 07:17:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah6Qm-0001aw-FO; Thu, 15 Jan 2004 07:17:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah6QD-0001a0-R9
	for sigtran@optimus.ietf.org; Thu, 15 Jan 2004 07:16:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00730
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 07:16:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah6QD-0002uc-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 07:16:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah6PM-0002s1-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 07:15:33 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[wL8MTn6JH3vzD6GNx00rRxFh84jJ68Kg])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah6OS-0002px-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 07:14:36 -0500
Received: from ns.pigworks.openss7.net (IDENT:srBblqoJ2/BPTN3sbDPP2BlZKbfR0JaD@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0FCEZI26126;
	Thu, 15 Jan 2004 05:14:35 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0FCEZk27951;
	Thu, 15 Jan 2004 05:14:35 -0700
Date: Thu, 15 Jan 2004 05:14:34 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
Cc: "'Barry Nagelberg'" <barryn@adax.com>,
        SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
Message-ID: <20040115051434.A27369@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>,
	'Barry Nagelberg' <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <1AB3D30B989BF141BBD5C70057B2EF7C043319A9@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C043319A9@eestqnt105.es.eu.ericsson.se>; from j.javier.pastor@ericsson.com on Thu, Jan 15, 2004 at 12:11:40PM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i0FCEZI26126
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

J.Javier,

Where does it say ASes must not overlap?  This is precisely
one of the example cases we used for IPSP discussions.
I certainly don't see where retricting this is necessary
for proper interworking or to protect the network.

The only problem case we had for "Unique Routing" was were
two RC's exist for the same traffic for the same ASP.  It is
then abivalent which RC the SG is to assign to the traffic.

In this example case, it is clear which RC value is to be
assigned to each message for each ASP.  There is no problem
of "Unique Routing".

The problem of "Unique Routing" exists where one attempt to
configure or register overlapping RKs for the same ASP.  So
if ASP4 tries to register for 5-5-5(ISUP) and 5-5-5(*) there
is a problem of unique routing.  To which RC is ISUP traffic
to go?

For the case of different ASPs, the SG can choose to support
it, if capable, or refuse it if not.  The IG need not attempt
to dictate a restriction to SG capabilities in this regard.

--brian

J.Javier Pastor (ML/EEM) wrote:                                          =
         (Thu, 15 Jan 2004 12:11:40)
> Brian,=20
>=20
> Why don't you take the following approach...
>=20
> Define two different ASes:
> - AS1 -> 5-5-5 (ISUP)
> - AS2 -> 5-5-5 (SCCP)
>=20
> ASP1 registers within AS1
> ASP2 registers within AS2
> ASP3 registers within both AS1 and AS2
>=20
> It is important to keep one unique routing per AS. ASes MUST not overla=
p.
>=20
> Cheers // Javier.
>=20
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > To: J.Javier Pastor (ML/EEM)
> > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> >=20
> >=20
> > J.Javier,
> >=20
> > Just to clarify, there should be nothing stopping an=20
> > implementation from
> > allowing ASP1 to register for, say, 5-5-5 (ISUP), ASP2 to register fo=
r
> > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> >=20
> > In this case, although ASP3 registers after ASP1 and ASP2,=20
> > there is nothing
> > stopping an SG from assigining a RK and RC to 5-5-5(*) for ASP3.
> >=20
> > An SG implementation could choose to refuse 5-5-5(*) and require ASP3
> > to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or it=20
> > might not.
> > I don't think it is the RFC's place to require one or the other.  So,
> > for in the case where there is an overlap between "different" APSs, i=
t
> > should be left up to the SG implementation as it is now.
> >=20
> > Your additional text below, now clarifies that.  Thank you.
> >=20
> > --brian
> >=20
> >=20
> > J.Javier Pastor (ML/EEM) wrote:                              =20
> >                     (Wed, 14 Jan 2004 15:30:10)
> > > Barry,=20
> > >=20
> > > You are right. And that is valid only for the overlapping=20
> > case. You can not create a new AS whose associated RK=20
> > overlaps another existing registered RK. In the duplicate=20
> > case it is already included that the check is against the RK=20
> > previosly registered by the sending ASP. The latter makes=20
> > sense but not the former.
> > >=20
> > > Go back to my first proposal.
> > >=20
> > > Thanks // Javier.
> > >=20
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org=20
> > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > Barry Nagelberg
> > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > To: SIGTRAN Mailing List
> > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > >=20
> > > >=20
> > > > Javier,
> > > >=20
> > > > No, Brian's suggestion is not correct, nor is this updated=20
> > > > text. Routing
> > > > keys are independent of ASPs or associations. I think=20
> > perhaps Brian is
> > > > thinking of the routing context, which may be unique for=20
> > each ASP or
> > > > association.
> > > >=20
> > > > Barry Nagelberg
> > > >=20
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org=20
> > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > J.Javier Pastor (ML/EEM)
> > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > To: 'bidulock@openss7.org'
> > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > Brian,
> > > > >
> > > > > Tell me if the following is OK.
> > > > >
> > > > > If the SGP determines that the requested RK partially, but=20
> > > > not exactly,
> > > > > matches an existing RK already registered for the=20
> > sender ASP, and
> > > > > that an incoming signalling message received at
> > > > > an SGP could possibly match both the requested and the existing
> > > > > RK, the SGP
> > > > > returns a Registration Response message to the ASP, with a=20
> > > > Registration
> > > > > Status of "Error - "Cannot Support Unique Routing. An=20
> > > > incoming signalling
> > > > > message received at an SGP should not match against more=20
> > > > than one Routing
> > > > > Key.
> > > > >
> > > > >
> > > > > THanks // JAvier.
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > > >
> > > > > >
> > > > > > J.Javier,
> > > > > >
> > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > >
> > > > > > --snip--
> > > > > > >
> > > > > > > --------
> > > > > > > New text: (Section 4.4.1)
> > > > > > > ---------
> > > > > > >
> > > > > > > If the SGP determines that the requested RK partially, but
> > > > > > not exactly,
> > > > > > > matches an existing RK, and that an incoming signalling
> > > > > > message received at
> > > > > > > an SGP could possibly match both the requested and the
> > > > > > existing RK, the SGP
> > > > > > > returns a Registration Response message to the ASP, with a
> > > > > > Registration
> > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > incoming signalling
> > > > > > > message received at an SGP should not match against more
> > > > > > than one Routing
> > > > > > > Key.
> > > > > > >
> > > > > > --snip--
> > > > > >
> > > > > > I think you mean for a given ASP (Association) in the=20
> > > > above.  Correct?
> > > > > >
> > > > > > It should be mentioned that the "matching" of RKs is done
> > > > > > only against other
> > > > > > RKs belonging to the same ASP (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
> > > >=20
> > > >=20
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >=20
> > >=20
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >=20
> > --=20
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >=20

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

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



From exim@www1.ietf.org  Thu Jan 15 09:00:42 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05690
	for <sigtran-archive@odin.ietf.org>; Thu, 15 Jan 2004 09:00:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah81W-0008RX-UF
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 08:59:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0FDx2b2032446
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 08:59:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah81V-0008R4-9h; Thu, 15 Jan 2004 08:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah80x-0008QJ-Oc
	for sigtran@optimus.ietf.org; Thu, 15 Jan 2004 08:58:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05549
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 08:58:25 -0500 (EST)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah80w-0001Wj-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 08:58:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah7zy-0001Tu-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 08:57:27 -0500
Received: from [203.200.71.140] (helo=spark.hss.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah7z2-0001FA-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 08:56:29 -0500
Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id i0FDquiB002535
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 19:22:56 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id i0FDsCY22630
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 19:24:12 +0530 (IST)
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
To: SIGTRAN Mailing List <sigtran@ietf.org>
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF8339CFE5.79D2FC84-ON65256E1C.004A8D40@hss.hns.com>
Date: Thu, 15 Jan 2004 19:17:06 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 15/01/2004
 07:14:26 PM
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.4 required=5.0 tests=EXCUSE_16,NO_REAL_NAME,
	ROUND_THE_WORLD_LOCAL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable






Hi,

I totally agree with Javier that there should be unique routing per AS'=
s ,
AS's must not overlap.
I am not able to understand how SG can handle overlapped AS's registere=
d by
different ASP's,
Brian can you explain it a little bit more.

I think SG should not be confused in selecting actual AS if AS's are
overlapped because first
thing what SG does is selecting of AS for given traffic received withou=
t
having any clue of ASP's.

Kamesh Kaul
www.hssworld.com
Hughes Software Systems




---------------------- Forwarded by Kamesh Kaul/HSS on 01/15/2004 07:04=
 PM
---------------------------


"Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on 01/15/2004
05:44:34 PM

Please respond to bidulock@openss7.org

Sent by:    sigtran-admin@ietf.org


To:    "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
cc:    "'Barry Nagelberg'" <barryn@adax.com>, SIGTRAN Mailing List
       <sigtran@ietf.org>

Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes


J.Javier,

Where does it say ASes must not overlap?  This is precisely
one of the example cases we used for IPSP discussions.
I certainly don't see where retricting this is necessary
for proper interworking or to protect the network.

The only problem case we had for "Unique Routing" was were
two RC's exist for the same traffic for the same ASP.  It is
then abivalent which RC the SG is to assign to the traffic.

In this example case, it is clear which RC value is to be
assigned to each message for each ASP.  There is no problem
of "Unique Routing".

The problem of "Unique Routing" exists where one attempt to
configure or register overlapping RKs for the same ASP.  So
if ASP4 tries to register for 5-5-5(ISUP) and 5-5-5(*) there
is a problem of unique routing.  To which RC is ISUP traffic
to go?

For the case of different ASPs, the SG can choose to support
it, if capable, or refuse it if not.  The IG need not attempt
to dictate a restriction to SG capabilities in this regard.

--brian

J.Javier Pastor (ML/EEM) wrote:
(Thu, 15 Jan 2004 12:11:40)
> Brian,
>
> Why don't you take the following approach...
>
> Define two different ASes:
> - AS1 -> 5-5-5 (ISUP)
> - AS2 -> 5-5-5 (SCCP)
>
> ASP1 registers within AS1
> ASP2 registers within AS2
> ASP3 registers within both AS1 and AS2
>
> It is important to keep one unique routing per AS. ASes MUST not over=
lap.
>
> Cheers // Javier.
>
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > To: J.Javier Pastor (ML/EEM)
> > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > J.Javier,
> >
> > Just to clarify, there should be nothing stopping an
> > implementation from
> > allowing ASP1 to register for, say, 5-5-5 (ISUP), ASP2 to register =
for
> > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> >
> > In this case, although ASP3 registers after ASP1 and ASP2,
> > there is nothing
> > stopping an SG from assigining a RK and RC to 5-5-5(*) for ASP3.
> >
> > An SG implementation could choose to refuse 5-5-5(*) and require AS=
P3
> > to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or it
> > might not.
> > I don't think it is the RFC's place to require one or the other.  S=
o,
> > for in the case where there is an overlap between "different" APSs,=
 it
> > should be left up to the SG implementation as it is now.
> >
> > Your additional text below, now clarifies that.  Thank you.
> >
> > --brian
> >
> >
> > J.Javier Pastor (ML/EEM) wrote:
> >                     (Wed, 14 Jan 2004 15:30:10)
> > > Barry,
> > >
> > > You are right. And that is valid only for the overlapping
> > case. You can not create a new AS whose associated RK
> > overlaps another existing registered RK. In the duplicate
> > case it is already included that the check is against the RK
> > previosly registered by the sending ASP. The latter makes
> > sense but not the former.
> > >
> > > Go back to my first proposal.
> > >
> > > Thanks // Javier.
> > >
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org
> > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > Barry Nagelberg
> > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > To: SIGTRAN Mailing List
> > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > Javier,
> > > >
> > > > No, Brian's suggestion is not correct, nor is this updated
> > > > text. Routing
> > > > keys are independent of ASPs or associations. I think
> > perhaps Brian is
> > > > thinking of the routing context, which may be unique for
> > each ASP or
> > > > association.
> > > >
> > > > Barry Nagelberg
> > > >
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org
> > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > J.Javier Pastor (ML/EEM)
> > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > To: 'bidulock@openss7.org'
> > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > Brian,
> > > > >
> > > > > Tell me if the following is OK.
> > > > >
> > > > > If the SGP determines that the requested RK partially, but
> > > > not exactly,
> > > > > matches an existing RK already registered for the
> > sender ASP, and
> > > > > that an incoming signalling message received at
> > > > > an SGP could possibly match both the requested and the existi=
ng
> > > > > RK, the SGP
> > > > > returns a Registration Response message to the ASP, with a
> > > > Registration
> > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > incoming signalling
> > > > > message received at an SGP should not match against more
> > > > than one Routing
> > > > > Key.
> > > > >
> > > > >
> > > > > THanks // JAvier.
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes=

> > > > > >
> > > > > >
> > > > > > J.Javier,
> > > > > >
> > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > >
> > > > > > --snip--
> > > > > > >
> > > > > > > --------
> > > > > > > New text: (Section 4.4.1)
> > > > > > > ---------
> > > > > > >
> > > > > > > If the SGP determines that the requested RK partially, bu=
t
> > > > > > not exactly,
> > > > > > > matches an existing RK, and that an incoming signalling
> > > > > > message received at
> > > > > > > an SGP could possibly match both the requested and the
> > > > > > existing RK, the SGP
> > > > > > > returns a Registration Response message to the ASP, with =
a
> > > > > > Registration
> > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > incoming signalling
> > > > > > > message received at an SGP should not match against more
> > > > > > than one Routing
> > > > > > > Key.
> > > > > > >
> > > > > > --snip--
> > > > > >
> > > > > > I think you mean for a given ASP (Association) in the
> > > > above.  Correct?
> > > > > >
> > > > > > It should be mentioned that the "matching" of RKs is done
> > > > > > only against other
> > > > > > RKs belonging to the same ASP (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
> > > >
> > >
> > > _______________________________________________
> > > 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 is proprietary to Hughes Software Systems Lim=
ited
(HSS) and is intended solely for the use of the individual to whom it i=
s
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 t=
his
email including damage from virus."=



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



From exim@www1.ietf.org  Thu Jan 15 09:29:32 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07958
	for <sigtran-archive@odin.ietf.org>; Thu, 15 Jan 2004 09:29:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah8UZ-0002FR-Tj
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 09:29:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0FET3N5008622
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 09:29:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah8UX-0002E0-P5; Thu, 15 Jan 2004 09:29:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah8U4-0002CM-H1
	for sigtran@optimus.ietf.org; Thu, 15 Jan 2004 09:28:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07857
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 09:28:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah8U2-0004Tl-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 09:28:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah8T6-0004MK-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 09:27:34 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah8SB-0004HP-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 09:26:35 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i0FEQYkH016801
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 09:26:34 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Thu, 15 Jan 2004 09:28:03 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOEELOCDAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C0433199F@eestqnt105.es.eu.ericsson.se>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by slink5.mtl-nj.adax id i0FEQYkH016801
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Javier,

Oops, sorry - some minor corrections:

1. The registration request is an exact duplicate of a registered RK.
2. The registration request partially overlaps a registered RK.
3. The ASP is requesting to modify a registered RK.

I agree with you and Kamesh (and apparently with everyone else except
Brian), that there SHOULD NOT be more than one RK match per AS. This is a=
lso
stated in section 1.4.2.2 of the RFC - Routing Key Limitations.

Barry Nagelberg

> -----Original Message-----
> From: J.Javier Pastor (ML/EEM) [mailto:j.javier.pastor@ericsson.com]
> Sent: Thursday, January 15, 2004 4:40 AM
> To: 'Barry Nagelberg'; SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
>
>
> It seems good to me.
>
> Cheers // Javier.
>
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Barry Nagelberg
> > Sent: mi=E9rcoles, 14 de enero de 2004 15:04
> > To: SIGTRAN Mailing List
> > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > Javier,
> >
> > Thanks. For the sake of clarity, I suggest the following changes:
> >
> > <snip>
> >
> > 3.6.1 Description of the problem
> >
> > The RFC does not clearly specify what the SG should do when
> > it receives a
> > Registration Request for a Routing Key that has already been
> > registered.
> > There are 3 scenarios to consider:
> >
> > 1. The registration request is an exact duplicate of a
> registered RK by the sending ASP.
> > 2. The registration request partially overlaps a registered RK
> in the SGP.
> > 3. The ASP is requesting to modify a registered RK.
> >
> > <snip>
> >
> > Barry Nagelberg
> >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > J.Javier Pastor (ML/EEM)
> > > Sent: Wednesday, January 14, 2004 6:37 AM
> > > To: SIGTRAN Mailing List
> > > Cc: Ken Morneault (E-mail)
> > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > Hi guys,
> > >
> > > Here we send the new text proposal to clarify this issue
> > > according your comments.
> > >
> > > Thanks // Javier.
> > >
> > >
> > >
> > > 3.6 Receiving REG for a RK already registered
> > >
> > > 3.6.1 Description of the problem
> > >
> > > The RFC does not clearly specify what the SG should do when it
> > > receives a Registration Request for a Routing Key that has
> > > already been registered. There are two scenarios to consider: the
> > > registration request is a duplicate, it overlaps partially an
> > > already registered RK. Also there is a desire to include the
> > > possibility of modifying a registered  Routing Key.
> > >
> > > 3.6.2 Text changes to the document
> > >
> > > ---------
> > > Old text: (Section 3.6.1)
> > > ---------
> > >
> > > The format of the Routing Key parameter 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
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                       Local-RK-Identifier                     |
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                  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)               |
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >
> > > ---------
> > > New text: (Section 3.6.1)
> > > ---------
> > >
> > > The format of the Routing Key parameter 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
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                       Local-RK-Identifier                     |
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                   Routing Context (optional)                  |
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                  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)               |
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >
> > > ---------
> > > Old text: (Section 3.6.2)
> > > ---------
> > >
> > > Registration Status: 32-bit integer
> > >
> > >   The Registration Result Status field indicates the success or the
> > >   reason for failure of a registration request.
> > >   Its values may be:
> > >
> > >      0           Successfully Registered
> > >      1           Error - Unknown
> > >      2           Error - Invalid DPC
> > >      3           Error - Invalid Network Appearance
> > >      4           Error - Invalid Routing Key
> > >      5           Error - Permission Denied
> > >      6           Error - Cannot Support Unique Routing
> > >      7           Error - Routing Key not Currently Provisioned
> > >      8           Error - Insufficient Resources
> > >      9           Error - Unsupported RK parameter Field
> > >      10          Error - Unsupported/Invalid Traffic Handling Mode
> > >
> > > ---------
> > > New text: (Section 3.6.2)
> > > ---------
> > >
> > > Registration Status: 32-bit integer
> > >
> > >   The Registration Result Status field indicates the success or the
> > >   reason for failure of a registration request.
> > >   Its values may be:
> > >      0           Successfully Registered
> > >      1           Error - Unknown
> > >      2           Error - Invalid DPC
> > >      3           Error - Invalid Network Appearance
> > >      4           Error - Invalid Routing Key
> > >      5           Error - Permission Denied
> > >      6           Error - Cannot Support Unique Routing
> > >      7           Error - Routing Key not Currently Provisioned
> > >      8           Error - Insufficient Resources
> > >      9           Error - Unsupported RK parameter Field
> > >      10          Error - Unsupported/Invalid Traffic Handling Mode
> > >      11          Error - Routing Key Change Refused
> > >      12          Error - Routing Key Already Registered
> > >
> > >
> > > ---------
> > > Old text: (Section 4.4.1)
> > > ---------
> > >
> > > If the SGP determines that a unique Routing Key cannot be
> > > created, the SGP returns a Registration Response message to the
> > > ASP, with a Registration Status of "Error - "Cannot Support
> > > Unique Routing"  An incoming signalling message received at an
> > > SGP should not match against more than one Routing Key.
> > >
> > > --------
> > > New text: (Section 4.4.1)
> > > ---------
> > >
> > > If the SGP determines that the requested RK partially, but not
> > > exactly, matches an existing RK, and that an incoming signalling
> > > message received at an SGP could possibly match both the
> > > requested and the existing RK, the SGP returns a Registration
> > > Response message to the ASP, with a Registration Status of "Error
> > > - "Cannot Support Unique Routing. An incoming signalling message
> > > received at an SGP should not match against more than one
> > Routing Key.
> > >
> > > If the SGP determines that the received RK was already
> > > registered, fully and exactly, either statically or dynamically,
> > > by the sending ASP, the SGP returns a Registration Response
> > > message to the ASP, containing a Registration Result "Error -
> > > Routing Key Already Registered ". This error applies whether the
> > > Routing Key is Active or Inactive. For this error code, RC field
> > > in Registration Response message MUST be populated with the
> > > actual value of RC in SGP corresponding to the specified RK in
> > > Registration Request message.
> > >
> > > An ASP MAY modify an existing Routing Key by including a Routing
> > > Context parameter in the REG REQ.  If the SGP determines that the
> > > Routing Context applies to an existing Routing Key the SG MAY
> > > adjust the existing Routing Key to match the new information
> > > provided in the Routing Key parameter.  A Registration Response
> > > "ERR - Routing Key Change Refused" is returned if the SGP does
> > > not accept the modification of the Routing Key due to either it
> > > does not support the re-registration procedure or the specific RC
> > > does not exist. Otherwise if the change is accepted, a
> > > Registration Response "Successfully Registered" is returned.
> > >
> > > 3.6.3 Solution description
> > >
> > > The two cases, RK overlap and RK duplication, have been
> > > differentiated and explained in detail. The latter will use a new
> > > specific Error Code as defined above. Also the possibility of
> > > modification to a Routing Key is included with the addition of a
> > > new parameter in the REG REQ message and the corresponding
> > > explanation in the procedures section.
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >


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



From exim@www1.ietf.org  Thu Jan 15 10:04:29 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09580
	for <sigtran-archive@odin.ietf.org>; Thu, 15 Jan 2004 10:04:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah92Q-0004oV-1l
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 10:04:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0FF42mM018502
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 10:04:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah92P-0004oE-5E; Thu, 15 Jan 2004 10:04:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah91u-0004nr-Eq
	for sigtran@optimus.ietf.org; Thu, 15 Jan 2004 10:03:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09559
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 10:03:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah91s-0006X3-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 10:03:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah90v-0006VD-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 10:02:30 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[y52wQCshTOkNSGYSDJUuFCWHuD0gn1fR])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah901-0006TD-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 10:01:33 -0500
Received: from ns.pigworks.openss7.net (IDENT:eax+UEt9zWRPaFlxqfQFlAHT1tJnbUXS@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0FF1UI28716;
	Thu, 15 Jan 2004 08:01:31 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0FF1U409501;
	Thu, 15 Jan 2004 08:01:30 -0700
Date: Thu, 15 Jan 2004 08:01:30 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: kakaul@hss.hns.com
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
Message-ID: <20040115080130.A9268@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: kakaul@hss.hns.com,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <OF8339CFE5.79D2FC84-ON65256E1C.004A8D40@hss.hns.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF8339CFE5.79D2FC84-ON65256E1C.004A8D40@hss.hns.com>; from kakaul@hss.hns.com on Thu, Jan 15, 2004 at 07:17:06PM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i0FF1UI28716
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,EXCUSE_16 autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

kakaul,

In the example:

            RK          ASP1   ASP2   ASP3
	-----------     ----   ----   ----
	5-5-5(ISUP)	RC1	-     RC3
	5-5-5(SCCP)	 -     RC2    RC3

Is that so difficult?

--brian

kakaul@hss.hns.com wrote:                                                =
           (Thu, 15 Jan 2004 19:17:06)
>=20
>=20
>=20
>=20
>=20
> Hi,
>=20
> I totally agree with Javier that there should be unique routing per AS'=
s ,
> AS's must not overlap.
> I am not able to understand how SG can handle overlapped AS's registere=
d by
> different ASP's,
> Brian can you explain it a little bit more.
>=20
> I think SG should not be confused in selecting actual AS if AS's are
> overlapped because first
> thing what SG does is selecting of AS for given traffic received withou=
t
> having any clue of ASP's.
>=20
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
>=20
>=20
>=20
>=20
> ---------------------- Forwarded by Kamesh Kaul/HSS on 01/15/2004 07:04=
 PM
> ---------------------------
>=20
>=20
> "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on 01/15/2004
> 05:44:34 PM
>=20
> Please respond to bidulock@openss7.org
>=20
> Sent by:    sigtran-admin@ietf.org
>=20
>=20
> To:    "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
> cc:    "'Barry Nagelberg'" <barryn@adax.com>, SIGTRAN Mailing List
>        <sigtran@ietf.org>
>=20
> Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
>=20
>=20
> J.Javier,
>=20
> Where does it say ASes must not overlap?  This is precisely
> one of the example cases we used for IPSP discussions.
> I certainly don't see where retricting this is necessary
> for proper interworking or to protect the network.
>=20
> The only problem case we had for "Unique Routing" was were
> two RC's exist for the same traffic for the same ASP.  It is
> then abivalent which RC the SG is to assign to the traffic.
>=20
> In this example case, it is clear which RC value is to be
> assigned to each message for each ASP.  There is no problem
> of "Unique Routing".
>=20
> The problem of "Unique Routing" exists where one attempt to
> configure or register overlapping RKs for the same ASP.  So
> if ASP4 tries to register for 5-5-5(ISUP) and 5-5-5(*) there
> is a problem of unique routing.  To which RC is ISUP traffic
> to go?
>=20
> For the case of different ASPs, the SG can choose to support
> it, if capable, or refuse it if not.  The IG need not attempt
> to dictate a restriction to SG capabilities in this regard.
>=20
> --brian
>=20
> J.Javier Pastor (ML/EEM) wrote:
> (Thu, 15 Jan 2004 12:11:40)
> > Brian,
> >
> > Why don't you take the following approach...
> >
> > Define two different ASes:
> > - AS1 -> 5-5-5 (ISUP)
> > - AS2 -> 5-5-5 (SCCP)
> >
> > ASP1 registers within AS1
> > ASP2 registers within AS2
> > ASP3 registers within both AS1 and AS2
> >
> > It is important to keep one unique routing per AS. ASes MUST not over=
lap.
> >
> > Cheers // Javier.
> >
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > > To: J.Javier Pastor (ML/EEM)
> > > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > J.Javier,
> > >
> > > Just to clarify, there should be nothing stopping an
> > > implementation from
> > > allowing ASP1 to register for, say, 5-5-5 (ISUP), ASP2 to register =
for
> > > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> > >
> > > In this case, although ASP3 registers after ASP1 and ASP2,
> > > there is nothing
> > > stopping an SG from assigining a RK and RC to 5-5-5(*) for ASP3.
> > >
> > > An SG implementation could choose to refuse 5-5-5(*) and require AS=
P3
> > > to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or it
> > > might not.
> > > I don't think it is the RFC's place to require one or the other.  S=
o,
> > > for in the case where there is an overlap between "different" APSs,=
 it
> > > should be left up to the SG implementation as it is now.
> > >
> > > Your additional text below, now clarifies that.  Thank you.
> > >
> > > --brian
> > >
> > >
> > > J.Javier Pastor (ML/EEM) wrote:
> > >                     (Wed, 14 Jan 2004 15:30:10)
> > > > Barry,
> > > >
> > > > You are right. And that is valid only for the overlapping
> > > case. You can not create a new AS whose associated RK
> > > overlaps another existing registered RK. In the duplicate
> > > case it is already included that the check is against the RK
> > > previosly registered by the sending ASP. The latter makes
> > > sense but not the former.
> > > >
> > > > Go back to my first proposal.
> > > >
> > > > Thanks // Javier.
> > > >
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org
> > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > Barry Nagelberg
> > > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > > To: SIGTRAN Mailing List
> > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > Javier,
> > > > >
> > > > > No, Brian's suggestion is not correct, nor is this updated
> > > > > text. Routing
> > > > > keys are independent of ASPs or associations. I think
> > > perhaps Brian is
> > > > > thinking of the routing context, which may be unique for
> > > each ASP or
> > > > > association.
> > > > >
> > > > > Barry Nagelberg
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: sigtran-admin@ietf.org
> > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > J.Javier Pastor (ML/EEM)
> > > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > > To: 'bidulock@openss7.org'
> > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > > >
> > > > > >
> > > > > > Brian,
> > > > > >
> > > > > > Tell me if the following is OK.
> > > > > >
> > > > > > If the SGP determines that the requested RK partially, but
> > > > > not exactly,
> > > > > > matches an existing RK already registered for the
> > > sender ASP, and
> > > > > > that an incoming signalling message received at
> > > > > > an SGP could possibly match both the requested and the existi=
ng
> > > > > > RK, the SGP
> > > > > > returns a Registration Response message to the ASP, with a
> > > > > Registration
> > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > incoming signalling
> > > > > > message received at an SGP should not match against more
> > > > > than one Routing
> > > > > > Key.
> > > > > >
> > > > > >
> > > > > > THanks // JAvier.
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > > > >
> > > > > > >
> > > > > > > J.Javier,
> > > > > > >
> > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > > >
> > > > > > > --snip--
> > > > > > > >
> > > > > > > > --------
> > > > > > > > New text: (Section 4.4.1)
> > > > > > > > ---------
> > > > > > > >
> > > > > > > > If the SGP determines that the requested RK partially, bu=
t
> > > > > > > not exactly,
> > > > > > > > matches an existing RK, and that an incoming signalling
> > > > > > > message received at
> > > > > > > > an SGP could possibly match both the requested and the
> > > > > > > existing RK, the SGP
> > > > > > > > returns a Registration Response message to the ASP, with =
a
> > > > > > > Registration
> > > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > > incoming signalling
> > > > > > > > message received at an SGP should not match against more
> > > > > > > than one Routing
> > > > > > > > Key.
> > > > > > > >
> > > > > > > --snip--
> > > > > > >
> > > > > > > I think you mean for a given ASP (Association) in the
> > > > > above.  Correct?
> > > > > > >
> > > > > > > It should be mentioned that the "matching" of RKs is done
> > > > > > > only against other
> > > > > > > RKs belonging to the same ASP (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
> > > > >
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >
> > > --
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >
>=20
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
>  https://www1.ietf.org/mailman/listinfo/sigtran
>=20
>=20
>=20
>=20
> "DISCLAIMER: This message is proprietary to Hughes Software Systems Lim=
ited
> (HSS) and is intended solely for the use of the individual to whom it i=
s
> 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 t=
his
> email including damage from virus."
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jan 15 10:09:29 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10069
	for <sigtran-archive@odin.ietf.org>; Thu, 15 Jan 2004 10:09:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah97F-0005Hf-Cr
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 10:09:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0FF91Od020290
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 10:09:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah97E-0005H8-Ud; Thu, 15 Jan 2004 10:09:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah96k-0005Fk-Kb
	for sigtran@optimus.ietf.org; Thu, 15 Jan 2004 10:08:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09964
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 10:08:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah96i-0006da-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 10:08:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah93r-0006Zm-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 10:05:32 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[3FPYNUve0yI8ppncrHVk7BEAT0VTVCFL])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah91W-0006WV-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 10:03:06 -0500
Received: from ns.pigworks.openss7.net (IDENT:i2DzpjkbrRPGFqw5vZ3hgltzZvtfRhuz@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0FF35I28736;
	Thu, 15 Jan 2004 08:03:05 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0FF35q09513;
	Thu, 15 Jan 2004 08:03:05 -0700
Date: Thu, 15 Jan 2004 08:03:05 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry Nagelberg <barryn@adax.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
Message-ID: <20040115080305.B9268@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry Nagelberg <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <1AB3D30B989BF141BBD5C70057B2EF7C0433199F@eestqnt105.es.eu.ericsson.se> <JBECLENKLBCKAAKFGAJOEELOCDAA.barryn@adax.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <JBECLENKLBCKAAKFGAJOEELOCDAA.barryn@adax.com>; from barryn@adax.com on Thu, Jan 15, 2004 at 09:28:03AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i0FF35I28736
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Barry,

Oh, so now you're going to send an error every time that an ASP
registers for an RK that another ASP has registered for?  Don't
be absurd.

--brian

Barry Nagelberg wrote:                                                   =
            (Thu, 15 Jan 2004 09:28:03)
> Javier,
>=20
> Oops, sorry - some minor corrections:
>=20
> 1. The registration request is an exact duplicate of a registered RK.
> 2. The registration request partially overlaps a registered RK.
> 3. The ASP is requesting to modify a registered RK.
>=20
> I agree with you and Kamesh (and apparently with everyone else except
> Brian), that there SHOULD NOT be more than one RK match per AS. This is=
 also
> stated in section 1.4.2.2 of the RFC - Routing Key Limitations.
>=20
> Barry Nagelberg
>=20
> > -----Original Message-----
> > From: J.Javier Pastor (ML/EEM) [mailto:j.javier.pastor@ericsson.com]
> > Sent: Thursday, January 15, 2004 4:40 AM
> > To: 'Barry Nagelberg'; SIGTRAN Mailing List
> > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > It seems good to me.
> >
> > Cheers // Javier.
> >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > Barry Nagelberg
> > > Sent: mi=E9rcoles, 14 de enero de 2004 15:04
> > > To: SIGTRAN Mailing List
> > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > Javier,
> > >
> > > Thanks. For the sake of clarity, I suggest the following changes:
> > >
> > > <snip>
> > >
> > > 3.6.1 Description of the problem
> > >
> > > The RFC does not clearly specify what the SG should do when
> > > it receives a
> > > Registration Request for a Routing Key that has already been
> > > registered.
> > > There are 3 scenarios to consider:
> > >
> > > 1. The registration request is an exact duplicate of a
> > registered RK by the sending ASP.
> > > 2. The registration request partially overlaps a registered RK
> > in the SGP.
> > > 3. The ASP is requesting to modify a registered RK.
> > >
> > > <snip>
> > >
> > > Barry Nagelberg
> > >
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > J.Javier Pastor (ML/EEM)
> > > > Sent: Wednesday, January 14, 2004 6:37 AM
> > > > To: SIGTRAN Mailing List
> > > > Cc: Ken Morneault (E-mail)
> > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > Hi guys,
> > > >
> > > > Here we send the new text proposal to clarify this issue
> > > > according your comments.
> > > >
> > > > Thanks // Javier.
> > > >
> > > >
> > > >
> > > > 3.6 Receiving REG for a RK already registered
> > > >
> > > > 3.6.1 Description of the problem
> > > >
> > > > The RFC does not clearly specify what the SG should do when it
> > > > receives a Registration Request for a Routing Key that has
> > > > already been registered. There are two scenarios to consider: the
> > > > registration request is a duplicate, it overlaps partially an
> > > > already registered RK. Also there is a desire to include the
> > > > possibility of modifying a registered  Routing Key.
> > > >
> > > > 3.6.2 Text changes to the document
> > > >
> > > > ---------
> > > > Old text: (Section 3.6.1)
> > > > ---------
> > > >
> > > > The format of the Routing Key parameter 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
> > > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+
> > > >   |                       Local-RK-Identifier                    =
 |
> > > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+
> > > >   |                  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)              =
 |
> > > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+
> > > >
> > > > ---------
> > > > New text: (Section 3.6.1)
> > > > ---------
> > > >
> > > > The format of the Routing Key parameter 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
> > > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+
> > > >   |                       Local-RK-Identifier                    =
 |
> > > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+
> > > >   |                   Routing Context (optional)                 =
 |
> > > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+
> > > >   |                  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)              =
 |
> > > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+
> > > >
> > > > ---------
> > > > Old text: (Section 3.6.2)
> > > > ---------
> > > >
> > > > Registration Status: 32-bit integer
> > > >
> > > >   The Registration Result Status field indicates the success or t=
he
> > > >   reason for failure of a registration request.
> > > >   Its values may be:
> > > >
> > > >      0           Successfully Registered
> > > >      1           Error - Unknown
> > > >      2           Error - Invalid DPC
> > > >      3           Error - Invalid Network Appearance
> > > >      4           Error - Invalid Routing Key
> > > >      5           Error - Permission Denied
> > > >      6           Error - Cannot Support Unique Routing
> > > >      7           Error - Routing Key not Currently Provisioned
> > > >      8           Error - Insufficient Resources
> > > >      9           Error - Unsupported RK parameter Field
> > > >      10          Error - Unsupported/Invalid Traffic Handling Mod=
e
> > > >
> > > > ---------
> > > > New text: (Section 3.6.2)
> > > > ---------
> > > >
> > > > Registration Status: 32-bit integer
> > > >
> > > >   The Registration Result Status field indicates the success or t=
he
> > > >   reason for failure of a registration request.
> > > >   Its values may be:
> > > >      0           Successfully Registered
> > > >      1           Error - Unknown
> > > >      2           Error - Invalid DPC
> > > >      3           Error - Invalid Network Appearance
> > > >      4           Error - Invalid Routing Key
> > > >      5           Error - Permission Denied
> > > >      6           Error - Cannot Support Unique Routing
> > > >      7           Error - Routing Key not Currently Provisioned
> > > >      8           Error - Insufficient Resources
> > > >      9           Error - Unsupported RK parameter Field
> > > >      10          Error - Unsupported/Invalid Traffic Handling Mod=
e
> > > >      11          Error - Routing Key Change Refused
> > > >      12          Error - Routing Key Already Registered
> > > >
> > > >
> > > > ---------
> > > > Old text: (Section 4.4.1)
> > > > ---------
> > > >
> > > > If the SGP determines that a unique Routing Key cannot be
> > > > created, the SGP returns a Registration Response message to the
> > > > ASP, with a Registration Status of "Error - "Cannot Support
> > > > Unique Routing"  An incoming signalling message received at an
> > > > SGP should not match against more than one Routing Key.
> > > >
> > > > --------
> > > > New text: (Section 4.4.1)
> > > > ---------
> > > >
> > > > If the SGP determines that the requested RK partially, but not
> > > > exactly, matches an existing RK, and that an incoming signalling
> > > > message received at an SGP could possibly match both the
> > > > requested and the existing RK, the SGP returns a Registration
> > > > Response message to the ASP, with a Registration Status of "Error
> > > > - "Cannot Support Unique Routing. An incoming signalling message
> > > > received at an SGP should not match against more than one
> > > Routing Key.
> > > >
> > > > If the SGP determines that the received RK was already
> > > > registered, fully and exactly, either statically or dynamically,
> > > > by the sending ASP, the SGP returns a Registration Response
> > > > message to the ASP, containing a Registration Result "Error -
> > > > Routing Key Already Registered ". This error applies whether the
> > > > Routing Key is Active or Inactive. For this error code, RC field
> > > > in Registration Response message MUST be populated with the
> > > > actual value of RC in SGP corresponding to the specified RK in
> > > > Registration Request message.
> > > >
> > > > An ASP MAY modify an existing Routing Key by including a Routing
> > > > Context parameter in the REG REQ.  If the SGP determines that the
> > > > Routing Context applies to an existing Routing Key the SG MAY
> > > > adjust the existing Routing Key to match the new information
> > > > provided in the Routing Key parameter.  A Registration Response
> > > > "ERR - Routing Key Change Refused" is returned if the SGP does
> > > > not accept the modification of the Routing Key due to either it
> > > > does not support the re-registration procedure or the specific RC
> > > > does not exist. Otherwise if the change is accepted, a
> > > > Registration Response "Successfully Registered" is returned.
> > > >
> > > > 3.6.3 Solution description
> > > >
> > > > The two cases, RK overlap and RK duplication, have been
> > > > differentiated and explained in detail. The latter will use a new
> > > > specific Error Code as defined above. Also the possibility of
> > > > modification to a Routing Key is included with the addition of a
> > > > new parameter in the REG REQ message and the corresponding
> > > > explanation in the procedures section.
> > > >
> > > > _______________________________________________
> > > > 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
> > >
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jan 15 10:13:28 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10506
	for <sigtran-archive@odin.ietf.org>; Thu, 15 Jan 2004 10:13:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah9B7-0005ZL-76
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 10:13:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0FFD1ev021388
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 10:13:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah9B6-0005Yr-Ta; Thu, 15 Jan 2004 10:13:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah9At-0005YE-Il
	for sigtran@optimus.ietf.org; Thu, 15 Jan 2004 10:12:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10442
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 10:12:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah9Ar-0006r6-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 10:12:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah99z-0006nn-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 10:11:52 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah98d-0006iY-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 10:10:27 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i0FFAPkH016919
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 10:10:26 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Thu, 15 Jan 2004 10:11:55 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOAELPCDAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <20040115080305.B9268@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by slink5.mtl-nj.adax id i0FFAPkH016919
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Javier,

Brian is correct. I am wrong. Please use my original suggestion from
yesterday, January 14.

Barry Nagelberg

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Thursday, January 15, 2004 10:03 AM
> To: Barry Nagelberg
> Cc: SIGTRAN Mailing List
> Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
>
>
> Barry,
>
> Oh, so now you're going to send an error every time that an ASP
> registers for an RK that another ASP has registered for?  Don't
> be absurd.
>
> --brian
>
> Barry Nagelberg wrote:
>                    (Thu, 15 Jan 2004 09:28:03)
> > Javier,
> >
> > Oops, sorry - some minor corrections:
> >
> > 1. The registration request is an exact duplicate of a registered RK.
> > 2. The registration request partially overlaps a registered RK.
> > 3. The ASP is requesting to modify a registered RK.
> >
> > I agree with you and Kamesh (and apparently with everyone else except
> > Brian), that there SHOULD NOT be more than one RK match per AS.
> This is also
> > stated in section 1.4.2.2 of the RFC - Routing Key Limitations.
> >
> > Barry Nagelberg
> >
> > > -----Original Message-----
> > > From: J.Javier Pastor (ML/EEM) [mailto:j.javier.pastor@ericsson.com=
]
> > > Sent: Thursday, January 15, 2004 4:40 AM
> > > To: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > It seems good to me.
> > >
> > > Cheers // Javier.
> > >
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org
> > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > Barry Nagelberg
> > > > Sent: mi=E9rcoles, 14 de enero de 2004 15:04
> > > > To: SIGTRAN Mailing List
> > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > Javier,
> > > >
> > > > Thanks. For the sake of clarity, I suggest the following changes:
> > > >
> > > > <snip>
> > > >
> > > > 3.6.1 Description of the problem
> > > >
> > > > The RFC does not clearly specify what the SG should do when
> > > > it receives a
> > > > Registration Request for a Routing Key that has already been
> > > > registered.
> > > > There are 3 scenarios to consider:
> > > >
> > > > 1. The registration request is an exact duplicate of a
> > > registered RK by the sending ASP.
> > > > 2. The registration request partially overlaps a registered RK
> > > in the SGP.
> > > > 3. The ASP is requesting to modify a registered RK.
> > > >
> > > > <snip>
> > > >
> > > > Barry Nagelberg
> > > >
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org
> > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > J.Javier Pastor (ML/EEM)
> > > > > Sent: Wednesday, January 14, 2004 6:37 AM
> > > > > To: SIGTRAN Mailing List
> > > > > Cc: Ken Morneault (E-mail)
> > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > Hi guys,
> > > > >
> > > > > Here we send the new text proposal to clarify this issue
> > > > > according your comments.
> > > > >
> > > > > Thanks // Javier.
> > > > >
> > > > >
> > > > >
> > > > > 3.6 Receiving REG for a RK already registered
> > > > >
> > > > > 3.6.1 Description of the problem
> > > > >
> > > > > The RFC does not clearly specify what the SG should do when it
> > > > > receives a Registration Request for a Routing Key that has
> > > > > already been registered. There are two scenarios to consider: t=
he
> > > > > registration request is a duplicate, it overlaps partially an
> > > > > already registered RK. Also there is a desire to include the
> > > > > possibility of modifying a registered  Routing Key.
> > > > >
> > > > > 3.6.2 Text changes to the document
> > > > >
> > > > > ---------
> > > > > Old text: (Section 3.6.1)
> > > > > ---------
> > > > >
> > > > > The format of the Routing Key parameter 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
> > > > >
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > > >   |                       Local-RK-Identifier
>         |
> > > > >
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > > >   |                  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)
>         |
> > > > >
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > > >
> > > > > ---------
> > > > > New text: (Section 3.6.1)
> > > > > ---------
> > > > >
> > > > > The format of the Routing Key parameter 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
> > > > >
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > > >   |                       Local-RK-Identifier
>         |
> > > > >
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > > >   |                   Routing Context (optional)
>         |
> > > > >
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > > >   |                  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)
>         |
> > > > >
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > > >
> > > > > ---------
> > > > > Old text: (Section 3.6.2)
> > > > > ---------
> > > > >
> > > > > Registration Status: 32-bit integer
> > > > >
> > > > >   The Registration Result Status field indicates the
> success or the
> > > > >   reason for failure of a registration request.
> > > > >   Its values may be:
> > > > >
> > > > >      0           Successfully Registered
> > > > >      1           Error - Unknown
> > > > >      2           Error - Invalid DPC
> > > > >      3           Error - Invalid Network Appearance
> > > > >      4           Error - Invalid Routing Key
> > > > >      5           Error - Permission Denied
> > > > >      6           Error - Cannot Support Unique Routing
> > > > >      7           Error - Routing Key not Currently Provisioned
> > > > >      8           Error - Insufficient Resources
> > > > >      9           Error - Unsupported RK parameter Field
> > > > >      10          Error - Unsupported/Invalid Traffic Handling M=
ode
> > > > >
> > > > > ---------
> > > > > New text: (Section 3.6.2)
> > > > > ---------
> > > > >
> > > > > Registration Status: 32-bit integer
> > > > >
> > > > >   The Registration Result Status field indicates the
> success or the
> > > > >   reason for failure of a registration request.
> > > > >   Its values may be:
> > > > >      0           Successfully Registered
> > > > >      1           Error - Unknown
> > > > >      2           Error - Invalid DPC
> > > > >      3           Error - Invalid Network Appearance
> > > > >      4           Error - Invalid Routing Key
> > > > >      5           Error - Permission Denied
> > > > >      6           Error - Cannot Support Unique Routing
> > > > >      7           Error - Routing Key not Currently Provisioned
> > > > >      8           Error - Insufficient Resources
> > > > >      9           Error - Unsupported RK parameter Field
> > > > >      10          Error - Unsupported/Invalid Traffic Handling M=
ode
> > > > >      11          Error - Routing Key Change Refused
> > > > >      12          Error - Routing Key Already Registered
> > > > >
> > > > >
> > > > > ---------
> > > > > Old text: (Section 4.4.1)
> > > > > ---------
> > > > >
> > > > > If the SGP determines that a unique Routing Key cannot be
> > > > > created, the SGP returns a Registration Response message to the
> > > > > ASP, with a Registration Status of "Error - "Cannot Support
> > > > > Unique Routing"  An incoming signalling message received at an
> > > > > SGP should not match against more than one Routing Key.
> > > > >
> > > > > --------
> > > > > New text: (Section 4.4.1)
> > > > > ---------
> > > > >
> > > > > If the SGP determines that the requested RK partially, but not
> > > > > exactly, matches an existing RK, and that an incoming signallin=
g
> > > > > message received at an SGP could possibly match both the
> > > > > requested and the existing RK, the SGP returns a Registration
> > > > > Response message to the ASP, with a Registration Status of "Err=
or
> > > > > - "Cannot Support Unique Routing. An incoming signalling messag=
e
> > > > > received at an SGP should not match against more than one
> > > > Routing Key.
> > > > >
> > > > > If the SGP determines that the received RK was already
> > > > > registered, fully and exactly, either statically or dynamically=
,
> > > > > by the sending ASP, the SGP returns a Registration Response
> > > > > message to the ASP, containing a Registration Result "Error -
> > > > > Routing Key Already Registered ". This error applies whether th=
e
> > > > > Routing Key is Active or Inactive. For this error code, RC fiel=
d
> > > > > in Registration Response message MUST be populated with the
> > > > > actual value of RC in SGP corresponding to the specified RK in
> > > > > Registration Request message.
> > > > >
> > > > > An ASP MAY modify an existing Routing Key by including a Routin=
g
> > > > > Context parameter in the REG REQ.  If the SGP determines that t=
he
> > > > > Routing Context applies to an existing Routing Key the SG MAY
> > > > > adjust the existing Routing Key to match the new information
> > > > > provided in the Routing Key parameter.  A Registration Response
> > > > > "ERR - Routing Key Change Refused" is returned if the SGP does
> > > > > not accept the modification of the Routing Key due to either it
> > > > > does not support the re-registration procedure or the specific =
RC
> > > > > does not exist. Otherwise if the change is accepted, a
> > > > > Registration Response "Successfully Registered" is returned.
> > > > >
> > > > > 3.6.3 Solution description
> > > > >
> > > > > The two cases, RK overlap and RK duplication, have been
> > > > > differentiated and explained in detail. The latter will use a n=
ew
> > > > > specific Error Code as defined above. Also the possibility of
> > > > > modification to a Routing Key is included with the addition of =
a
> > > > > new parameter in the REG REQ message and the corresponding
> > > > > explanation in the procedures section.
> > > > >
> > > > > _______________________________________________
> > > > > 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
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


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



From exim@www1.ietf.org  Thu Jan 15 10:24:29 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11291
	for <sigtran-archive@odin.ietf.org>; Thu, 15 Jan 2004 10:24:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah9Lm-00063a-0E
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 10:24:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0FFO1jN023280
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 10:24:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah9Ll-00063H-39; Thu, 15 Jan 2004 10:24:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah9LT-00062B-26
	for sigtran@optimus.ietf.org; Thu, 15 Jan 2004 10:23:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11277
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 10:23:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah9LQ-0007J4-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 10:23:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah9KT-0007Gq-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 10:22:42 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah9K7-0007EK-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 10:22:19 -0500
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i0FFMGYG005561;
	Thu, 15 Jan 2004 16:22:16 +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.2657.72)
	id ZJBSSFZ2; Thu, 15 Jan 2004 16:23:50 +0100
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <CRN65NXV>; Thu, 15 Jan 2004 16:22:18 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C043319B1@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "'Barry Nagelberg'" <barryn@adax.com>,
        SIGTRAN Mailing List
	 <sigtran@ietf.org>
Cc: "'bidulock@openss7.org'" <bidulock@openss7.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Thu, 15 Jan 2004 16:21:33 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

That's right.

As I explained in a previous mail, the duplicate RK case we are talking =
about makes sense when an ASP registers a RK that it has previously =
registered. On the other hand, the overlapping RK detection includes a =
comparison with all the routing keys that have been previously =
registered by any ASP including the sending one. The reason for the =
latter is per section 1.4.2.2 as Barry says: "each received SS7 message =
SHOULD have a full or partial match to a SINGLE routing result".=20

Cheers // Javier.


> -----Original Message-----
> From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Barry Nagelberg
> Sent: jueves, 15 de enero de 2004 16:12
> To: SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
>=20
>=20
> Javier,
>=20
> Brian is correct. I am wrong. Please use my original suggestion from
> yesterday, January 14.
>=20
> Barry Nagelberg
>=20
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Thursday, January 15, 2004 10:03 AM
> > To: Barry Nagelberg
> > Cc: SIGTRAN Mailing List
> > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > Barry,
> >
> > Oh, so now you're going to send an error every time that an ASP
> > registers for an RK that another ASP has registered for?  Don't
> > be absurd.
> >
> > --brian
> >
> > Barry Nagelberg wrote:
> >                    (Thu, 15 Jan 2004 09:28:03)
> > > Javier,
> > >
> > > Oops, sorry - some minor corrections:
> > >
> > > 1. The registration request is an exact duplicate of a=20
> registered RK.
> > > 2. The registration request partially overlaps a registered RK.
> > > 3. The ASP is requesting to modify a registered RK.
> > >
> > > I agree with you and Kamesh (and apparently with everyone=20
> else except
> > > Brian), that there SHOULD NOT be more than one RK match per AS.
> > This is also
> > > stated in section 1.4.2.2 of the RFC - Routing Key Limitations.
> > >
> > > Barry Nagelberg
> > >
> > > > -----Original Message-----
> > > > From: J.Javier Pastor (ML/EEM)=20
> [mailto:j.javier.pastor@ericsson.com]
> > > > Sent: Thursday, January 15, 2004 4:40 AM
> > > > To: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > It seems good to me.
> > > >
> > > > Cheers // Javier.
> > > >
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org
> > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > Barry Nagelberg
> > > > > Sent: mi=E9rcoles, 14 de enero de 2004 15:04
> > > > > To: SIGTRAN Mailing List
> > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > Javier,
> > > > >
> > > > > Thanks. For the sake of clarity, I suggest the=20
> following changes:
> > > > >
> > > > > <snip>
> > > > >
> > > > > 3.6.1 Description of the problem
> > > > >
> > > > > The RFC does not clearly specify what the SG should do when
> > > > > it receives a
> > > > > Registration Request for a Routing Key that has already been
> > > > > registered.
> > > > > There are 3 scenarios to consider:
> > > > >
> > > > > 1. The registration request is an exact duplicate of a
> > > > registered RK by the sending ASP.
> > > > > 2. The registration request partially overlaps a registered =
RK
> > > > in the SGP.
> > > > > 3. The ASP is requesting to modify a registered RK.
> > > > >
> > > > > <snip>
> > > > >
> > > > > Barry Nagelberg
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: sigtran-admin@ietf.org
> > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > J.Javier Pastor (ML/EEM)
> > > > > > Sent: Wednesday, January 14, 2004 6:37 AM
> > > > > > To: SIGTRAN Mailing List
> > > > > > Cc: Ken Morneault (E-mail)
> > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > > >
> > > > > >
> > > > > > Hi guys,
> > > > > >
> > > > > > Here we send the new text proposal to clarify this issue
> > > > > > according your comments.
> > > > > >
> > > > > > Thanks // Javier.
> > > > > >
> > > > > >
> > > > > >
> > > > > > 3.6 Receiving REG for a RK already registered
> > > > > >
> > > > > > 3.6.1 Description of the problem
> > > > > >
> > > > > > The RFC does not clearly specify what the SG should=20
> do when it
> > > > > > receives a Registration Request for a Routing Key that has
> > > > > > already been registered. There are two scenarios to=20
> consider: the
> > > > > > registration request is a duplicate, it overlaps=20
> partially an
> > > > > > already registered RK. Also there is a desire to include =
the
> > > > > > possibility of modifying a registered  Routing Key.
> > > > > >
> > > > > > 3.6.2 Text changes to the document
> > > > > >
> > > > > > ---------
> > > > > > Old text: (Section 3.6.1)
> > > > > > ---------
> > > > > >
> > > > > > The format of the Routing Key parameter is as follows.
> > > > > >
> > > > > >   0                   1                   2        =20
>           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=20
> 5 6 7 8 9 0 1
> > > > > >
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > > > >   |                       Local-RK-Identifier
> >         |
> > > > > >
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > > > >   |                  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)
> >         |
> > > > > >
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > > > >
> > > > > > ---------
> > > > > > New text: (Section 3.6.1)
> > > > > > ---------
> > > > > >
> > > > > > The format of the Routing Key parameter is as follows.
> > > > > >
> > > > > >   0                   1                   2        =20
>           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=20
> 5 6 7 8 9 0 1
> > > > > >
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > > > >   |                       Local-RK-Identifier
> >         |
> > > > > >
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > > > >   |                   Routing Context (optional)
> >         |
> > > > > >
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > > > >   |                  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)
> >         |
> > > > > >
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > > > >
> > > > > > ---------
> > > > > > Old text: (Section 3.6.2)
> > > > > > ---------
> > > > > >
> > > > > > Registration Status: 32-bit integer
> > > > > >
> > > > > >   The Registration Result Status field indicates the
> > success or the
> > > > > >   reason for failure of a registration request.
> > > > > >   Its values may be:
> > > > > >
> > > > > >      0           Successfully Registered
> > > > > >      1           Error - Unknown
> > > > > >      2           Error - Invalid DPC
> > > > > >      3           Error - Invalid Network Appearance
> > > > > >      4           Error - Invalid Routing Key
> > > > > >      5           Error - Permission Denied
> > > > > >      6           Error - Cannot Support Unique Routing
> > > > > >      7           Error - Routing Key not Currently=20
> Provisioned
> > > > > >      8           Error - Insufficient Resources
> > > > > >      9           Error - Unsupported RK parameter Field
> > > > > >      10          Error - Unsupported/Invalid=20
> Traffic Handling Mode
> > > > > >
> > > > > > ---------
> > > > > > New text: (Section 3.6.2)
> > > > > > ---------
> > > > > >
> > > > > > Registration Status: 32-bit integer
> > > > > >
> > > > > >   The Registration Result Status field indicates the
> > success or the
> > > > > >   reason for failure of a registration request.
> > > > > >   Its values may be:
> > > > > >      0           Successfully Registered
> > > > > >      1           Error - Unknown
> > > > > >      2           Error - Invalid DPC
> > > > > >      3           Error - Invalid Network Appearance
> > > > > >      4           Error - Invalid Routing Key
> > > > > >      5           Error - Permission Denied
> > > > > >      6           Error - Cannot Support Unique Routing
> > > > > >      7           Error - Routing Key not Currently=20
> Provisioned
> > > > > >      8           Error - Insufficient Resources
> > > > > >      9           Error - Unsupported RK parameter Field
> > > > > >      10          Error - Unsupported/Invalid=20
> Traffic Handling Mode
> > > > > >      11          Error - Routing Key Change Refused
> > > > > >      12          Error - Routing Key Already Registered
> > > > > >
> > > > > >
> > > > > > ---------
> > > > > > Old text: (Section 4.4.1)
> > > > > > ---------
> > > > > >
> > > > > > If the SGP determines that a unique Routing Key cannot be
> > > > > > created, the SGP returns a Registration Response=20
> message to the
> > > > > > ASP, with a Registration Status of "Error - "Cannot Support
> > > > > > Unique Routing"  An incoming signalling message=20
> received at an
> > > > > > SGP should not match against more than one Routing Key.
> > > > > >
> > > > > > --------
> > > > > > New text: (Section 4.4.1)
> > > > > > ---------
> > > > > >
> > > > > > If the SGP determines that the requested RK=20
> partially, but not
> > > > > > exactly, matches an existing RK, and that an=20
> incoming signalling
> > > > > > message received at an SGP could possibly match both the
> > > > > > requested and the existing RK, the SGP returns a=20
> Registration
> > > > > > Response message to the ASP, with a Registration=20
> Status of "Error
> > > > > > - "Cannot Support Unique Routing. An incoming=20
> signalling message
> > > > > > received at an SGP should not match against more than one
> > > > > Routing Key.
> > > > > >
> > > > > > If the SGP determines that the received RK was already
> > > > > > registered, fully and exactly, either statically or=20
> dynamically,
> > > > > > by the sending ASP, the SGP returns a Registration Response
> > > > > > message to the ASP, containing a Registration=20
> Result "Error -
> > > > > > Routing Key Already Registered ". This error=20
> applies whether the
> > > > > > Routing Key is Active or Inactive. For this error=20
> code, RC field
> > > > > > in Registration Response message MUST be populated with the
> > > > > > actual value of RC in SGP corresponding to the=20
> specified RK in
> > > > > > Registration Request message.
> > > > > >
> > > > > > An ASP MAY modify an existing Routing Key by=20
> including a Routing
> > > > > > Context parameter in the REG REQ.  If the SGP=20
> determines that the
> > > > > > Routing Context applies to an existing Routing Key=20
> the SG MAY
> > > > > > adjust the existing Routing Key to match the new =
information
> > > > > > provided in the Routing Key parameter.  A=20
> Registration Response
> > > > > > "ERR - Routing Key Change Refused" is returned if=20
> the SGP does
> > > > > > not accept the modification of the Routing Key due=20
> to either it
> > > > > > does not support the re-registration procedure or=20
> the specific RC
> > > > > > does not exist. Otherwise if the change is accepted, a
> > > > > > Registration Response "Successfully Registered" is =
returned.
> > > > > >
> > > > > > 3.6.3 Solution description
> > > > > >
> > > > > > The two cases, RK overlap and RK duplication, have been
> > > > > > differentiated and explained in detail. The latter=20
> will use a new
> > > > > > specific Error Code as defined above. Also the=20
> possibility of
> > > > > > modification to a Routing Key is included with the=20
> addition of a
> > > > > > new parameter in the REG REQ message and the corresponding
> > > > > > explanation in the procedures section.
> > > > > >
> > > > > > _______________________________________________
> > > > > > 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
> >
> > --
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20

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



From exim@www1.ietf.org  Thu Jan 15 10:44:04 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12092
	for <sigtran-archive@odin.ietf.org>; Thu, 15 Jan 2004 10:44:04 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah9eB-0007F9-0L
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 10:43:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0FFh2J3027840
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 10:43:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah9e9-0007Ep-4e; Thu, 15 Jan 2004 10:43:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah9dg-0007E8-Rz
	for sigtran@optimus.ietf.org; Thu, 15 Jan 2004 10:42:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12019
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 10:42:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah9de-00009c-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 10:42:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah9cj-00007v-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 10:41:34 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah9bp-00005s-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 10:40:37 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id KAA14928
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 10:40:36 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Thu, 15 Jan 2004 10:38:52 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMEEEPCDAA.asveren@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <OF8339CFE5.79D2FC84-ON65256E1C.004A8D40@hss.hns.com>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by chuckie.dgms.com id KAA14928
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,EXCUSE_16 autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Maybe we should look to this issue again in depth, because a few things h=
ave
changed in the last one year or so about the RKs.

Before we had CIC/SSN as possible parts of RKs. This could make hierarchi=
cal
routing almost impossible -or at least proprietary- in case of overlappin=
g
RKs. For example one has AS1:DPC=3D1-1-1/CIC=3D0-100 and
AS:DPC=3D1-1-1/CIC=3D50-150. Then for a message with DPC=3D1-1-1 and CIC=3D=
75, it is
not easy (or straighforward) to tell, which AS the message has to match.

Now the issue is a bit different considering that our RKs are limited to =
PC
and User Parts. For example if there is AS1:DPC1-1-1 and AS2:DPC=3D1-1-1/=
ISUP,
it is quite obvious (especially maybe with a small section about
hierarchical RKs in IG) that traffic for ISUP should go to AS2 and other
traffic for DPC=3D1-1-1 to AS1.

Currently related with RK overlapping we have:
RFC3332 1.4.2.2 Routing Key Limitations:
"Routing Keys SHOULD be unique in the sense that each received SS7 sgnall=
ing
message SHOULD have a full or partial match to a single routing result."

I also remember some people supporting hierarchical RKs based on that
"SHOULD" already.

In fact, once there is a well defined hieararchy among overlapping RKs, o=
ne
can even have them on the same ASP -with the drawback of receiving SSNM
separetly for them, but not big deal

Personally -at least for now- I don't think overlapping RKs is terribly
usefull (maybe for a "backup" node:

           AS2:1-1-1  AS3:1-1-1
 AS1:1-1-1  SCCP      ISUP
  +----+   +----+   +----+
  |ASP1|   |ASP2|   |ASP3|
  +--+-+   +--+-+   +--+-+
     |        |        |
     |        |        |
     |        |        |
  +--+--------+--------+-+
  |                      |
  |        SG1           |
  +----------------------+

Imagine that first AS1 comes up (takes all traffic for AS1), then AS2 and
AS3. Now, AS1 does not get any traffic. Now AS1 can serve as backup for b=
oth
AS2/AS3 -and will take some part of traffic as soon as any of them fails-.


Having said all of that, I think because of the "SHOULD" in 1.4.4.2, RFC3=
332
already allows such a configuration(and we can assume now hierarchy among
RKs is almost obvious)

    Tolga

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf O=
f
> kakaul@hss.hns.com
> Sent: Thursday, January 15, 2004 8:47 AM
> To: SIGTRAN Mailing List
> Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
>
>
>
>
>
>
>
> Hi,
>
> I totally agree with Javier that there should be unique routing per AS'=
s ,
> AS's must not overlap.
> I am not able to understand how SG can handle overlapped AS's
> registered by
> different ASP's,
> Brian can you explain it a little bit more.
>
> I think SG should not be confused in selecting actual AS if AS's are
> overlapped because first
> thing what SG does is selecting of AS for given traffic received withou=
t
> having any clue of ASP's.
>
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
>
>
>
>
> ---------------------- Forwarded by Kamesh Kaul/HSS on 01/15/2004 07:04=
 PM
> ---------------------------
>
>
> "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on 01/15/2004
> 05:44:34 PM
>
> Please respond to bidulock@openss7.org
>
> Sent by:    sigtran-admin@ietf.org
>
>
> To:    "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
> cc:    "'Barry Nagelberg'" <barryn@adax.com>, SIGTRAN Mailing List
>        <sigtran@ietf.org>
>
> Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
>
>
> J.Javier,
>
> Where does it say ASes must not overlap?  This is precisely
> one of the example cases we used for IPSP discussions.
> I certainly don't see where retricting this is necessary
> for proper interworking or to protect the network.
>
> The only problem case we had for "Unique Routing" was were
> two RC's exist for the same traffic for the same ASP.  It is
> then abivalent which RC the SG is to assign to the traffic.
>
> In this example case, it is clear which RC value is to be
> assigned to each message for each ASP.  There is no problem
> of "Unique Routing".
>
> The problem of "Unique Routing" exists where one attempt to
> configure or register overlapping RKs for the same ASP.  So
> if ASP4 tries to register for 5-5-5(ISUP) and 5-5-5(*) there
> is a problem of unique routing.  To which RC is ISUP traffic
> to go?
>
> For the case of different ASPs, the SG can choose to support
> it, if capable, or refuse it if not.  The IG need not attempt
> to dictate a restriction to SG capabilities in this regard.
>
> --brian
>
> J.Javier Pastor (ML/EEM) wrote:
> (Thu, 15 Jan 2004 12:11:40)
> > Brian,
> >
> > Why don't you take the following approach...
> >
> > Define two different ASes:
> > - AS1 -> 5-5-5 (ISUP)
> > - AS2 -> 5-5-5 (SCCP)
> >
> > ASP1 registers within AS1
> > ASP2 registers within AS2
> > ASP3 registers within both AS1 and AS2
> >
> > It is important to keep one unique routing per AS. ASes MUST
> not overlap.
> >
> > Cheers // Javier.
> >
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > > To: J.Javier Pastor (ML/EEM)
> > > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > J.Javier,
> > >
> > > Just to clarify, there should be nothing stopping an
> > > implementation from
> > > allowing ASP1 to register for, say, 5-5-5 (ISUP), ASP2 to register =
for
> > > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> > >
> > > In this case, although ASP3 registers after ASP1 and ASP2,
> > > there is nothing
> > > stopping an SG from assigining a RK and RC to 5-5-5(*) for ASP3.
> > >
> > > An SG implementation could choose to refuse 5-5-5(*) and require AS=
P3
> > > to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or it
> > > might not.
> > > I don't think it is the RFC's place to require one or the other.  S=
o,
> > > for in the case where there is an overlap between "different" APSs,=
 it
> > > should be left up to the SG implementation as it is now.
> > >
> > > Your additional text below, now clarifies that.  Thank you.
> > >
> > > --brian
> > >
> > >
> > > J.Javier Pastor (ML/EEM) wrote:
> > >                     (Wed, 14 Jan 2004 15:30:10)
> > > > Barry,
> > > >
> > > > You are right. And that is valid only for the overlapping
> > > case. You can not create a new AS whose associated RK
> > > overlaps another existing registered RK. In the duplicate
> > > case it is already included that the check is against the RK
> > > previosly registered by the sending ASP. The latter makes
> > > sense but not the former.
> > > >
> > > > Go back to my first proposal.
> > > >
> > > > Thanks // Javier.
> > > >
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org
> > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > Barry Nagelberg
> > > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > > To: SIGTRAN Mailing List
> > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > Javier,
> > > > >
> > > > > No, Brian's suggestion is not correct, nor is this updated
> > > > > text. Routing
> > > > > keys are independent of ASPs or associations. I think
> > > perhaps Brian is
> > > > > thinking of the routing context, which may be unique for
> > > each ASP or
> > > > > association.
> > > > >
> > > > > Barry Nagelberg
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: sigtran-admin@ietf.org
> > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > J.Javier Pastor (ML/EEM)
> > > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > > To: 'bidulock@openss7.org'
> > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > > >
> > > > > >
> > > > > > Brian,
> > > > > >
> > > > > > Tell me if the following is OK.
> > > > > >
> > > > > > If the SGP determines that the requested RK partially, but
> > > > > not exactly,
> > > > > > matches an existing RK already registered for the
> > > sender ASP, and
> > > > > > that an incoming signalling message received at
> > > > > > an SGP could possibly match both the requested and the existi=
ng
> > > > > > RK, the SGP
> > > > > > returns a Registration Response message to the ASP, with a
> > > > > Registration
> > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > incoming signalling
> > > > > > message received at an SGP should not match against more
> > > > > than one Routing
> > > > > > Key.
> > > > > >
> > > > > >
> > > > > > THanks // JAvier.
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > > > >
> > > > > > >
> > > > > > > J.Javier,
> > > > > > >
> > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > > >
> > > > > > > --snip--
> > > > > > > >
> > > > > > > > --------
> > > > > > > > New text: (Section 4.4.1)
> > > > > > > > ---------
> > > > > > > >
> > > > > > > > If the SGP determines that the requested RK partially, bu=
t
> > > > > > > not exactly,
> > > > > > > > matches an existing RK, and that an incoming signalling
> > > > > > > message received at
> > > > > > > > an SGP could possibly match both the requested and the
> > > > > > > existing RK, the SGP
> > > > > > > > returns a Registration Response message to the ASP, with =
a
> > > > > > > Registration
> > > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > > incoming signalling
> > > > > > > > message received at an SGP should not match against more
> > > > > > > than one Routing
> > > > > > > > Key.
> > > > > > > >
> > > > > > > --snip--
> > > > > > >
> > > > > > > I think you mean for a given ASP (Association) in the
> > > > > above.  Correct?
> > > > > > >
> > > > > > > It should be mentioned that the "matching" of RKs is done
> > > > > > > only against other
> > > > > > > RKs belonging to the same ASP (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
> > > > >
> > > >
> > > > _______________________________________________
> > > > 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 is proprietary to Hughes Software
> Systems Limited
> (HSS) and is intended solely for the use of the individual to whom it i=
s
> 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 t=
his
> email including damage from virus."
>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


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



From exim@www1.ietf.org  Thu Jan 15 11:03:34 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12938
	for <sigtran-archive@odin.ietf.org>; Thu, 15 Jan 2004 11:03:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah9xb-0007wb-4D
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 11:03:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0FG37EM030518
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 11:03:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah9xV-0007w1-FN; Thu, 15 Jan 2004 11:03:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah9x5-0007vN-Hc
	for sigtran@optimus.ietf.org; Thu, 15 Jan 2004 11:02:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12917
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 11:02:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah9x2-0001BA-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 11:02:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah9w7-0001A7-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 11:01:36 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah9vl-00018p-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 11:01:13 -0500
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i0FG1BAh021536;
	Thu, 15 Jan 2004 17:01:11 +0100
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id CZDFXDJK; Thu, 15 Jan 2004 17:01:11 +0100
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <VRLK0LJB>; Thu, 15 Jan 2004 16:58:23 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C043319B3@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "'Tolga Asveren'" <asveren@ulticom.com>,
        SIGTRAN Mailing List
	 <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Thu, 15 Jan 2004 17:00:27 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by eagle.ericsson.se id i0FG1BAh021536
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,EXCUSE_16 autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Tolga,=20

Pls, see my comments below...

> -----Original Message-----
> From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Tolga Asveren
> Sent: jueves, 15 de enero de 2004 16:39
> To: SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
>=20
>=20
> Maybe we should look to this issue again in depth, because a=20
> few things have
> changed in the last one year or so about the RKs.
>=20
> Before we had CIC/SSN as possible parts of RKs. This could=20
> make hierarchical
> routing almost impossible -or at least proprietary- in case=20
> of overlapping
> RKs. For example one has AS1:DPC=3D1-1-1/CIC=3D0-100 and
> AS:DPC=3D1-1-1/CIC=3D50-150. Then for a message with DPC=3D1-1-1=20
> and CIC=3D75, it is
> not easy (or straighforward) to tell, which AS the message=20
> has to match.
>=20
> Now the issue is a bit different considering that our RKs are=20
> limited to PC
> and User Parts. For example if there is AS1:DPC1-1-1 and=20
> AS2:DPC=3D1-1-1/ISUP,
> it is quite obvious (especially maybe with a small section about
> hierarchical RKs in IG) that traffic for ISUP should go to=20
> AS2 and other
> traffic for DPC=3D1-1-1 to AS1.
>=20

But why not using AS1:DPC=3D1-1-1/SI=3DSCCP ? This is inline to what you =
want to achieve and it would make no problems with the RFC..

Take into account that things like this, may move us to use precedence ru=
les in RKs... :-(. I think that is not really needed while you can get th=
e same effect with the already defined building blocks...


> Currently related with RK overlapping we have:
> RFC3332 1.4.2.2 Routing Key Limitations:
> "Routing Keys SHOULD be unique in the sense that each=20
> received SS7 sgnalling
> message SHOULD have a full or partial match to a single=20
> routing result."
>=20
> I also remember some people supporting hierarchical RKs based on that
> "SHOULD" already.
>=20
Maybe that was the reason to leave the SHOULD. But doing in other way and=
 being compliance with the standard, implies the need to demonstrate a ve=
ry good reasons to contradict the SHOULD. I would not see "another way of=
 doing things" as strong enough reasons for that.

> In fact, once there is a well defined hieararchy among=20
> overlapping RKs, one
> can even have them on the same ASP -with the drawback of=20
> receiving SSNM
> separetly for them, but not big deal
>=20
> Personally -at least for now- I don't think overlapping RKs=20
> is terribly
> usefull (maybe for a "backup" node:
>=20
>            AS2:1-1-1  AS3:1-1-1
>  AS1:1-1-1  SCCP      ISUP
>   +----+   +----+   +----+
>   |ASP1|   |ASP2|   |ASP3|
>   +--+-+   +--+-+   +--+-+
>      |        |        |
>      |        |        |
>      |        |        |
>   +--+--------+--------+-+
>   |                      |
>   |        SG1           |
>   +----------------------+
>=20
> Imagine that first AS1 comes up (takes all traffic for AS1),=20
> then AS2 and
> AS3. Now, AS1 does not get any traffic. Now AS1 can serve as=20
> backup for both
> AS2/AS3 -and will take some part of traffic as soon as any of=20
> them fails-.
>=20

You can reach the same behaviour including ASP1 in AS2 and AS3... An a si=
de advantage is that you need to define a smaller number of RKs... and AS=
es.

>=20
> Having said all of that, I think because of the "SHOULD" in=20
> 1.4.4.2, RFC3332
> already allows such a configuration(and we can assume now=20
> hierarchy among
> RKs is almost obvious)
>=20
>     Tolga
>=20

Summarizing, I think it is not needed to change the RFC regarding this co=
ncern (also, for the time being ;D), since the functionality you claim ca=
n be already got with the normal procedures.


Cheers // Javier.


> > -----Original Message-----
> > From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> > kakaul@hss.hns.com
> > Sent: Thursday, January 15, 2004 8:47 AM
> > To: SIGTRAN Mailing List
> > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> >
> >
> >
> >
> >
> > Hi,
> >
> > I totally agree with Javier that there should be unique=20
> routing per AS's ,
> > AS's must not overlap.
> > I am not able to understand how SG can handle overlapped AS's
> > registered by
> > different ASP's,
> > Brian can you explain it a little bit more.
> >
> > I think SG should not be confused in selecting actual AS if AS's are
> > overlapped because first
> > thing what SG does is selecting of AS for given traffic=20
> received without
> > having any clue of ASP's.
> >
> > Kamesh Kaul
> > www.hssworld.com
> > Hughes Software Systems
> >
> >
> >
> >
> > ---------------------- Forwarded by Kamesh Kaul/HSS on=20
> 01/15/2004 07:04 PM
> > ---------------------------
> >
> >
> > "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on 01/15/2004
> > 05:44:34 PM
> >
> > Please respond to bidulock@openss7.org
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
> > cc:    "'Barry Nagelberg'" <barryn@adax.com>, SIGTRAN Mailing List
> >        <sigtran@ietf.org>
> >
> > Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > J.Javier,
> >
> > Where does it say ASes must not overlap?  This is precisely
> > one of the example cases we used for IPSP discussions.
> > I certainly don't see where retricting this is necessary
> > for proper interworking or to protect the network.
> >
> > The only problem case we had for "Unique Routing" was were
> > two RC's exist for the same traffic for the same ASP.  It is
> > then abivalent which RC the SG is to assign to the traffic.
> >
> > In this example case, it is clear which RC value is to be
> > assigned to each message for each ASP.  There is no problem
> > of "Unique Routing".
> >
> > The problem of "Unique Routing" exists where one attempt to
> > configure or register overlapping RKs for the same ASP.  So
> > if ASP4 tries to register for 5-5-5(ISUP) and 5-5-5(*) there
> > is a problem of unique routing.  To which RC is ISUP traffic
> > to go?
> >
> > For the case of different ASPs, the SG can choose to support
> > it, if capable, or refuse it if not.  The IG need not attempt
> > to dictate a restriction to SG capabilities in this regard.
> >
> > --brian
> >
> > J.Javier Pastor (ML/EEM) wrote:
> > (Thu, 15 Jan 2004 12:11:40)
> > > Brian,
> > >
> > > Why don't you take the following approach...
> > >
> > > Define two different ASes:
> > > - AS1 -> 5-5-5 (ISUP)
> > > - AS2 -> 5-5-5 (SCCP)
> > >
> > > ASP1 registers within AS1
> > > ASP2 registers within AS2
> > > ASP3 registers within both AS1 and AS2
> > >
> > > It is important to keep one unique routing per AS. ASes MUST
> > not overlap.
> > >
> > > Cheers // Javier.
> > >
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > > > To: J.Javier Pastor (ML/EEM)
> > > > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > J.Javier,
> > > >
> > > > Just to clarify, there should be nothing stopping an
> > > > implementation from
> > > > allowing ASP1 to register for, say, 5-5-5 (ISUP), ASP2=20
> to register for
> > > > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> > > >
> > > > In this case, although ASP3 registers after ASP1 and ASP2,
> > > > there is nothing
> > > > stopping an SG from assigining a RK and RC to 5-5-5(*) for ASP3.
> > > >
> > > > An SG implementation could choose to refuse 5-5-5(*)=20
> and require ASP3
> > > > to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or it
> > > > might not.
> > > > I don't think it is the RFC's place to require one or=20
> the other.  So,
> > > > for in the case where there is an overlap between=20
> "different" APSs, it
> > > > should be left up to the SG implementation as it is now.
> > > >
> > > > Your additional text below, now clarifies that.  Thank you.
> > > >
> > > > --brian
> > > >
> > > >
> > > > J.Javier Pastor (ML/EEM) wrote:
> > > >                     (Wed, 14 Jan 2004 15:30:10)
> > > > > Barry,
> > > > >
> > > > > You are right. And that is valid only for the overlapping
> > > > case. You can not create a new AS whose associated RK
> > > > overlaps another existing registered RK. In the duplicate
> > > > case it is already included that the check is against the RK
> > > > previosly registered by the sending ASP. The latter makes
> > > > sense but not the former.
> > > > >
> > > > > Go back to my first proposal.
> > > > >
> > > > > Thanks // Javier.
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: sigtran-admin@ietf.org
> > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > Barry Nagelberg
> > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > > > To: SIGTRAN Mailing List
> > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > > >
> > > > > >
> > > > > > Javier,
> > > > > >
> > > > > > No, Brian's suggestion is not correct, nor is this updated
> > > > > > text. Routing
> > > > > > keys are independent of ASPs or associations. I think
> > > > perhaps Brian is
> > > > > > thinking of the routing context, which may be unique for
> > > > each ASP or
> > > > > > association.
> > > > > >
> > > > > > Barry Nagelberg
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: sigtran-admin@ietf.org
> > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > J.Javier Pastor (ML/EEM)
> > > > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > > > To: 'bidulock@openss7.org'
> > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM=20
> error codes
> > > > > > >
> > > > > > >
> > > > > > > Brian,
> > > > > > >
> > > > > > > Tell me if the following is OK.
> > > > > > >
> > > > > > > If the SGP determines that the requested RK partially, but
> > > > > > not exactly,
> > > > > > > matches an existing RK already registered for the
> > > > sender ASP, and
> > > > > > > that an incoming signalling message received at
> > > > > > > an SGP could possibly match both the requested=20
> and the existing
> > > > > > > RK, the SGP
> > > > > > > returns a Registration Response message to the ASP, with a
> > > > > > Registration
> > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > incoming signalling
> > > > > > > message received at an SGP should not match against more
> > > > > > than one Routing
> > > > > > > Key.
> > > > > > >
> > > > > > >
> > > > > > > THanks // JAvier.
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM=20
> error codes
> > > > > > > >
> > > > > > > >
> > > > > > > > J.Javier,
> > > > > > > >
> > > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > > > >
> > > > > > > > --snip--
> > > > > > > > >
> > > > > > > > > --------
> > > > > > > > > New text: (Section 4.4.1)
> > > > > > > > > ---------
> > > > > > > > >
> > > > > > > > > If the SGP determines that the requested RK=20
> partially, but
> > > > > > > > not exactly,
> > > > > > > > > matches an existing RK, and that an incoming=20
> signalling
> > > > > > > > message received at
> > > > > > > > > an SGP could possibly match both the requested and the
> > > > > > > > existing RK, the SGP
> > > > > > > > > returns a Registration Response message to=20
> the ASP, with a
> > > > > > > > Registration
> > > > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > > > incoming signalling
> > > > > > > > > message received at an SGP should not match=20
> against more
> > > > > > > > than one Routing
> > > > > > > > > Key.
> > > > > > > > >
> > > > > > > > --snip--
> > > > > > > >
> > > > > > > > I think you mean for a given ASP (Association) in the
> > > > > > above.  Correct?
> > > > > > > >
> > > > > > > > It should be mentioned that the "matching" of=20
> RKs is done
> > > > > > > > only against other
> > > > > > > > RKs belonging to the same ASP (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
> > > > > >
> > > > >
> > > > > _______________________________________________
> > > > > 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 is proprietary to Hughes Software
> > Systems Limited
> > (HSS) and is intended solely for the use of the individual=20
> to whom it is
> > addressed. It may contain  privileged or confidential=20
> information and
> > should not be circulated or used for any purpose other than=20
> for what it is
> > intended. If you have received this message in error,=20
> please notify the
> > originator immediately. If you are not the intended=20
> recipient, you are
> > notified that you are strictly prohibited from using, copying,
> > altering, or
> > disclosing the contents of this message. HSS accepts no=20
> responsibility for
> > loss or damage arising from the use of the information=20
> transmitted by this
> > email including damage from virus."
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20

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



From exim@www1.ietf.org  Thu Jan 15 11:08:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13139
	for <sigtran-archive@odin.ietf.org>; Thu, 15 Jan 2004 11:08:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhA2M-0008PC-UB
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 11:08:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0FG82CR032269
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 11:08:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhA2L-0008OG-SS; Thu, 15 Jan 2004 11:08:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhA1w-0008Iv-TV
	for sigtran@optimus.ietf.org; Thu, 15 Jan 2004 11:07:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13121
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 11:07:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhA1u-0001PS-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 11:07:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhA15-0001Nm-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 11:06:44 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhA0L-0001LY-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 11:05:58 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id LAA21695
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 11:05:56 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Thu, 15 Jan 2004 11:04:12 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMKEFACDAA.asveren@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C043319B3@eestqnt105.es.eu.ericsson.se>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by chuckie.dgms.com id LAA21695
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,EXCUSE_16 autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Javier,
> -----Original Message-----
> From: J.Javier Pastor (ML/EEM) [mailto:j.javier.pastor@ericsson.com]
> Sent: Thursday, January 15, 2004 11:00 AM
> To: 'Tolga Asveren'; SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
>
>
> Tolga,
>
> Pls, see my comments below...
>
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Tolga Asveren
> > Sent: jueves, 15 de enero de 2004 16:39
> > To: SIGTRAN Mailing List
> > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > Maybe we should look to this issue again in depth, because a
> > few things have
> > changed in the last one year or so about the RKs.
> >
> > Before we had CIC/SSN as possible parts of RKs. This could
> > make hierarchical
> > routing almost impossible -or at least proprietary- in case
> > of overlapping
> > RKs. For example one has AS1:DPC=3D1-1-1/CIC=3D0-100 and
> > AS:DPC=3D1-1-1/CIC=3D50-150. Then for a message with DPC=3D1-1-1
> > and CIC=3D75, it is
> > not easy (or straighforward) to tell, which AS the message
> > has to match.
> >
> > Now the issue is a bit different considering that our RKs are
> > limited to PC
> > and User Parts. For example if there is AS1:DPC1-1-1 and
> > AS2:DPC=3D1-1-1/ISUP,
> > it is quite obvious (especially maybe with a small section about
> > hierarchical RKs in IG) that traffic for ISUP should go to
> > AS2 and other
> > traffic for DPC=3D1-1-1 to AS1.
> >
>
> But why not using AS1:DPC=3D1-1-1/SI=3DSCCP ? This is inline to what
> you want to achieve and it would make no problems with the RFC..
>
> Take into account that things like this, may move us to use
> precedence rules in RKs... :-(. I think that is not really needed
> while you can get the same effect with the already defined
> building blocks...
>
>
> > Currently related with RK overlapping we have:
> > RFC3332 1.4.2.2 Routing Key Limitations:
> > "Routing Keys SHOULD be unique in the sense that each
> > received SS7 sgnalling
> > message SHOULD have a full or partial match to a single
> > routing result."
> >
> > I also remember some people supporting hierarchical RKs based on that
> > "SHOULD" already.
> >
> Maybe that was the reason to leave the SHOULD. But doing in other
> way and being compliance with the standard, implies the need to
> demonstrate a very good reasons to contradict the SHOULD. I would
> not see "another way of doing things" as strong enough reasons for that.
>
> > In fact, once there is a well defined hieararchy among
> > overlapping RKs, one
> > can even have them on the same ASP -with the drawback of
> > receiving SSNM
> > separetly for them, but not big deal
> >
> > Personally -at least for now- I don't think overlapping RKs
> > is terribly
> > usefull (maybe for a "backup" node:
> >
> >            AS2:1-1-1  AS3:1-1-1
> >  AS1:1-1-1  SCCP      ISUP
> >   +----+   +----+   +----+
> >   |ASP1|   |ASP2|   |ASP3|
> >   +--+-+   +--+-+   +--+-+
> >      |        |        |
> >      |        |        |
> >      |        |        |
> >   +--+--------+--------+-+
> >   |                      |
> >   |        SG1           |
> >   +----------------------+
> >
> > Imagine that first AS1 comes up (takes all traffic for AS1),
> > then AS2 and
> > AS3. Now, AS1 does not get any traffic. Now AS1 can serve as
> > backup for both
> > AS2/AS3 -and will take some part of traffic as soon as any of
> > them fails-.
> >
>
> You can reach the same behaviour including ASP1 in AS2 and AS3...
> An a side advantage is that you need to define a smaller number
> of RKs... and ASes.
[TOLGA]Yes, you are right. But the above configuration has a slight
advantage: no time is wasted NTFY/ASPAC/ASPAC-ACK (but no big deal, thi s=
is
supposed to finish quickly and SG can buffer)
>
> >
> > Having said all of that, I think because of the "SHOULD" in
> > 1.4.4.2, RFC3332
> > already allows such a configuration(and we can assume now
> > hierarchy among
> > RKs is almost obvious)
> >
> >     Tolga
> >
>
> Summarizing, I think it is not needed to change the RFC regarding
> this concern (also, for the time being ;D), since the
> functionality you claim can be already got with the normal procedures.
[TOLGA]Yes, this is also what I think.
>
>
> Cheers // Javier.
>
>
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > kakaul@hss.hns.com
> > > Sent: Thursday, January 15, 2004 8:47 AM
> > > To: SIGTRAN Mailing List
> > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Hi,
> > >
> > > I totally agree with Javier that there should be unique
> > routing per AS's ,
> > > AS's must not overlap.
> > > I am not able to understand how SG can handle overlapped AS's
> > > registered by
> > > different ASP's,
> > > Brian can you explain it a little bit more.
> > >
> > > I think SG should not be confused in selecting actual AS if AS's ar=
e
> > > overlapped because first
> > > thing what SG does is selecting of AS for given traffic
> > received without
> > > having any clue of ASP's.
> > >
> > > Kamesh Kaul
> > > www.hssworld.com
> > > Hughes Software Systems
> > >
> > >
> > >
> > >
> > > ---------------------- Forwarded by Kamesh Kaul/HSS on
> > 01/15/2004 07:04 PM
> > > ---------------------------
> > >
> > >
> > > "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on 01/15/200=
4
> > > 05:44:34 PM
> > >
> > > Please respond to bidulock@openss7.org
> > >
> > > Sent by:    sigtran-admin@ietf.org
> > >
> > >
> > > To:    "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
> > > cc:    "'Barry Nagelberg'" <barryn@adax.com>, SIGTRAN Mailing List
> > >        <sigtran@ietf.org>
> > >
> > > Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > J.Javier,
> > >
> > > Where does it say ASes must not overlap?  This is precisely
> > > one of the example cases we used for IPSP discussions.
> > > I certainly don't see where retricting this is necessary
> > > for proper interworking or to protect the network.
> > >
> > > The only problem case we had for "Unique Routing" was were
> > > two RC's exist for the same traffic for the same ASP.  It is
> > > then abivalent which RC the SG is to assign to the traffic.
> > >
> > > In this example case, it is clear which RC value is to be
> > > assigned to each message for each ASP.  There is no problem
> > > of "Unique Routing".
> > >
> > > The problem of "Unique Routing" exists where one attempt to
> > > configure or register overlapping RKs for the same ASP.  So
> > > if ASP4 tries to register for 5-5-5(ISUP) and 5-5-5(*) there
> > > is a problem of unique routing.  To which RC is ISUP traffic
> > > to go?
> > >
> > > For the case of different ASPs, the SG can choose to support
> > > it, if capable, or refuse it if not.  The IG need not attempt
> > > to dictate a restriction to SG capabilities in this regard.
> > >
> > > --brian
> > >
> > > J.Javier Pastor (ML/EEM) wrote:
> > > (Thu, 15 Jan 2004 12:11:40)
> > > > Brian,
> > > >
> > > > Why don't you take the following approach...
> > > >
> > > > Define two different ASes:
> > > > - AS1 -> 5-5-5 (ISUP)
> > > > - AS2 -> 5-5-5 (SCCP)
> > > >
> > > > ASP1 registers within AS1
> > > > ASP2 registers within AS2
> > > > ASP3 registers within both AS1 and AS2
> > > >
> > > > It is important to keep one unique routing per AS. ASes MUST
> > > not overlap.
> > > >
> > > > Cheers // Javier.
> > > >
> > > > > -----Original Message-----
> > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > > > > To: J.Javier Pastor (ML/EEM)
> > > > > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > J.Javier,
> > > > >
> > > > > Just to clarify, there should be nothing stopping an
> > > > > implementation from
> > > > > allowing ASP1 to register for, say, 5-5-5 (ISUP), ASP2
> > to register for
> > > > > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> > > > >
> > > > > In this case, although ASP3 registers after ASP1 and ASP2,
> > > > > there is nothing
> > > > > stopping an SG from assigining a RK and RC to 5-5-5(*) for ASP3.
> > > > >
> > > > > An SG implementation could choose to refuse 5-5-5(*)
> > and require ASP3
> > > > > to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or it
> > > > > might not.
> > > > > I don't think it is the RFC's place to require one or
> > the other.  So,
> > > > > for in the case where there is an overlap between
> > "different" APSs, it
> > > > > should be left up to the SG implementation as it is now.
> > > > >
> > > > > Your additional text below, now clarifies that.  Thank you.
> > > > >
> > > > > --brian
> > > > >
> > > > >
> > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > >                     (Wed, 14 Jan 2004 15:30:10)
> > > > > > Barry,
> > > > > >
> > > > > > You are right. And that is valid only for the overlapping
> > > > > case. You can not create a new AS whose associated RK
> > > > > overlaps another existing registered RK. In the duplicate
> > > > > case it is already included that the check is against the RK
> > > > > previosly registered by the sending ASP. The latter makes
> > > > > sense but not the former.
> > > > > >
> > > > > > Go back to my first proposal.
> > > > > >
> > > > > > Thanks // Javier.
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: sigtran-admin@ietf.org
> > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > Barry Nagelberg
> > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > > > > To: SIGTRAN Mailing List
> > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > > > >
> > > > > > >
> > > > > > > Javier,
> > > > > > >
> > > > > > > No, Brian's suggestion is not correct, nor is this updated
> > > > > > > text. Routing
> > > > > > > keys are independent of ASPs or associations. I think
> > > > > perhaps Brian is
> > > > > > > thinking of the routing context, which may be unique for
> > > > > each ASP or
> > > > > > > association.
> > > > > > >
> > > > > > > Barry Nagelberg
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: sigtran-admin@ietf.org
> > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > > J.Javier Pastor (ML/EEM)
> > > > > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > > > > To: 'bidulock@openss7.org'
> > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM
> > error codes
> > > > > > > >
> > > > > > > >
> > > > > > > > Brian,
> > > > > > > >
> > > > > > > > Tell me if the following is OK.
> > > > > > > >
> > > > > > > > If the SGP determines that the requested RK partially, bu=
t
> > > > > > > not exactly,
> > > > > > > > matches an existing RK already registered for the
> > > > > sender ASP, and
> > > > > > > > that an incoming signalling message received at
> > > > > > > > an SGP could possibly match both the requested
> > and the existing
> > > > > > > > RK, the SGP
> > > > > > > > returns a Registration Response message to the ASP, with =
a
> > > > > > > Registration
> > > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > > incoming signalling
> > > > > > > > message received at an SGP should not match against more
> > > > > > > than one Routing
> > > > > > > > Key.
> > > > > > > >
> > > > > > > >
> > > > > > > > THanks // JAvier.
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org=
]
> > > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM
> > error codes
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > J.Javier,
> > > > > > > > >
> > > > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > > > > >
> > > > > > > > > --snip--
> > > > > > > > > >
> > > > > > > > > > --------
> > > > > > > > > > New text: (Section 4.4.1)
> > > > > > > > > > ---------
> > > > > > > > > >
> > > > > > > > > > If the SGP determines that the requested RK
> > partially, but
> > > > > > > > > not exactly,
> > > > > > > > > > matches an existing RK, and that an incoming
> > signalling
> > > > > > > > > message received at
> > > > > > > > > > an SGP could possibly match both the requested and th=
e
> > > > > > > > > existing RK, the SGP
> > > > > > > > > > returns a Registration Response message to
> > the ASP, with a
> > > > > > > > > Registration
> > > > > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > > > > incoming signalling
> > > > > > > > > > message received at an SGP should not match
> > against more
> > > > > > > > > than one Routing
> > > > > > > > > > Key.
> > > > > > > > > >
> > > > > > > > > --snip--
> > > > > > > > >
> > > > > > > > > I think you mean for a given ASP (Association) in the
> > > > > > > above.  Correct?
> > > > > > > > >
> > > > > > > > > It should be mentioned that the "matching" of
> > RKs is done
> > > > > > > > > only against other
> > > > > > > > > RKs belonging to the same ASP (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
> > > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > 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 is proprietary to Hughes Software
> > > Systems Limited
> > > (HSS) and is intended solely for the use of the individual
> > to whom it is
> > > addressed. It may contain  privileged or confidential
> > information and
> > > should not be circulated or used for any purpose other than
> > for what it is
> > > intended. If you have received this message in error,
> > please notify the
> > > originator immediately. If you are not the intended
> > recipient, you are
> > > notified that you are strictly prohibited from using, copying,
> > > altering, or
> > > disclosing the contents of this message. HSS accepts no
> > responsibility for
> > > loss or damage arising from the use of the information
> > transmitted by this
> > > email including damage from virus."
> > >
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >


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



From exim@www1.ietf.org  Thu Jan 15 11:15:32 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13311
	for <sigtran-archive@odin.ietf.org>; Thu, 15 Jan 2004 11:15:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhA99-0000NJ-Vq
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 11:15:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0FGF3EW001424
	for sigtran-archive@odin.ietf.org; Thu, 15 Jan 2004 11:15:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhA99-0000Mo-5m; Thu, 15 Jan 2004 11:15:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhA8f-0000Lv-Mw
	for sigtran@optimus.ietf.org; Thu, 15 Jan 2004 11:14:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13284
	for <sigtran@ietf.org>; Thu, 15 Jan 2004 11:14:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhA8e-0001cC-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 11:14:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhA7j-0001af-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 11:13:36 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[tM9ABaxRnhsjX983Ag4t3k9yT7MIUUJO])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhA79-0001ZH-00
	for sigtran@ietf.org; Thu, 15 Jan 2004 11:12:59 -0500
Received: from ns.pigworks.openss7.net (IDENT:JAGSAtYHOOBPYPj1ZmljRzrzy+vk97R+@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0FGCvI29830;
	Thu, 15 Jan 2004 09:12:57 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0FGCvC10398;
	Thu, 15 Jan 2004 09:12:57 -0700
Date: Thu, 15 Jan 2004 09:12:57 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <asveren@ulticom.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
Message-ID: <20040115091257.D9585@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <asveren@ulticom.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <OF8339CFE5.79D2FC84-ON65256E1C.004A8D40@hss.hns.com> <GBEBKGPKHGPAOFCLBNAMEEEPCDAA.asveren@ulticom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <GBEBKGPKHGPAOFCLBNAMEEEPCDAA.asveren@ulticom.com>; from asveren@ulticom.com on Thu, Jan 15, 2004 at 10:38:52AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i0FGCvI29830
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,EXCUSE_16 autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Tolga,

An other reason was to permit an ASP that refuses to use SI granularity
(like John's) to interwork with one that does.  There is certainly no
reason to go restricting this, as it the restriction will result in reduc=
ed
interoperability.

--brian

Tolga Asveren wrote:                                                     =
            (Thu, 15 Jan 2004 10:38:52)
> Maybe we should look to this issue again in depth, because a few things=
 have
> changed in the last one year or so about the RKs.
>=20
> Before we had CIC/SSN as possible parts of RKs. This could make hierarc=
hical
> routing almost impossible -or at least proprietary- in case of overlapp=
ing
> RKs. For example one has AS1:DPC=3D1-1-1/CIC=3D0-100 and
> AS:DPC=3D1-1-1/CIC=3D50-150. Then for a message with DPC=3D1-1-1 and CI=
C=3D75, it is
> not easy (or straighforward) to tell, which AS the message has to match.
>=20
> Now the issue is a bit different considering that our RKs are limited t=
o PC
> and User Parts. For example if there is AS1:DPC1-1-1 and AS2:DPC=3D1-1-=
1/ISUP,
> it is quite obvious (especially maybe with a small section about
> hierarchical RKs in IG) that traffic for ISUP should go to AS2 and othe=
r
> traffic for DPC=3D1-1-1 to AS1.
>=20
> Currently related with RK overlapping we have:
> RFC3332 1.4.2.2 Routing Key Limitations:
> "Routing Keys SHOULD be unique in the sense that each received SS7 sgna=
lling
> message SHOULD have a full or partial match to a single routing result.=
"
>=20
> I also remember some people supporting hierarchical RKs based on that
> "SHOULD" already.
>=20
> In fact, once there is a well defined hieararchy among overlapping RKs,=
 one
> can even have them on the same ASP -with the drawback of receiving SSNM
> separetly for them, but not big deal
>=20
> Personally -at least for now- I don't think overlapping RKs is terribly
> usefull (maybe for a "backup" node:
>=20
>            AS2:1-1-1  AS3:1-1-1
>  AS1:1-1-1  SCCP      ISUP
>   +----+   +----+   +----+
>   |ASP1|   |ASP2|   |ASP3|
>   +--+-+   +--+-+   +--+-+
>      |        |        |
>      |        |        |
>      |        |        |
>   +--+--------+--------+-+
>   |                      |
>   |        SG1           |
>   +----------------------+
>=20
> Imagine that first AS1 comes up (takes all traffic for AS1), then AS2 a=
nd
> AS3. Now, AS1 does not get any traffic. Now AS1 can serve as backup for=
 both
> AS2/AS3 -and will take some part of traffic as soon as any of them fail=
s-.
>=20
>=20
> Having said all of that, I think because of the "SHOULD" in 1.4.4.2, RF=
C3332
> already allows such a configuration(and we can assume now hierarchy amo=
ng
> RKs is almost obvious)
>=20
>     Tolga
>=20
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf=
 Of
> > kakaul@hss.hns.com
> > Sent: Thursday, January 15, 2004 8:47 AM
> > To: SIGTRAN Mailing List
> > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> >
> >
> >
> >
> >
> > Hi,
> >
> > I totally agree with Javier that there should be unique routing per A=
S's ,
> > AS's must not overlap.
> > I am not able to understand how SG can handle overlapped AS's
> > registered by
> > different ASP's,
> > Brian can you explain it a little bit more.
> >
> > I think SG should not be confused in selecting actual AS if AS's are
> > overlapped because first
> > thing what SG does is selecting of AS for given traffic received with=
out
> > having any clue of ASP's.
> >
> > Kamesh Kaul
> > www.hssworld.com
> > Hughes Software Systems
> >
> >
> >
> >
> > ---------------------- Forwarded by Kamesh Kaul/HSS on 01/15/2004 07:=
04 PM
> > ---------------------------
> >
> >
> > "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on 01/15/2004
> > 05:44:34 PM
> >
> > Please respond to bidulock@openss7.org
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
> > cc:    "'Barry Nagelberg'" <barryn@adax.com>, SIGTRAN Mailing List
> >        <sigtran@ietf.org>
> >
> > Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > J.Javier,
> >
> > Where does it say ASes must not overlap?  This is precisely
> > one of the example cases we used for IPSP discussions.
> > I certainly don't see where retricting this is necessary
> > for proper interworking or to protect the network.
> >
> > The only problem case we had for "Unique Routing" was were
> > two RC's exist for the same traffic for the same ASP.  It is
> > then abivalent which RC the SG is to assign to the traffic.
> >
> > In this example case, it is clear which RC value is to be
> > assigned to each message for each ASP.  There is no problem
> > of "Unique Routing".
> >
> > The problem of "Unique Routing" exists where one attempt to
> > configure or register overlapping RKs for the same ASP.  So
> > if ASP4 tries to register for 5-5-5(ISUP) and 5-5-5(*) there
> > is a problem of unique routing.  To which RC is ISUP traffic
> > to go?
> >
> > For the case of different ASPs, the SG can choose to support
> > it, if capable, or refuse it if not.  The IG need not attempt
> > to dictate a restriction to SG capabilities in this regard.
> >
> > --brian
> >
> > J.Javier Pastor (ML/EEM) wrote:
> > (Thu, 15 Jan 2004 12:11:40)
> > > Brian,
> > >
> > > Why don't you take the following approach...
> > >
> > > Define two different ASes:
> > > - AS1 -> 5-5-5 (ISUP)
> > > - AS2 -> 5-5-5 (SCCP)
> > >
> > > ASP1 registers within AS1
> > > ASP2 registers within AS2
> > > ASP3 registers within both AS1 and AS2
> > >
> > > It is important to keep one unique routing per AS. ASes MUST
> > not overlap.
> > >
> > > Cheers // Javier.
> > >
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > > > To: J.Javier Pastor (ML/EEM)
> > > > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > J.Javier,
> > > >
> > > > Just to clarify, there should be nothing stopping an
> > > > implementation from
> > > > allowing ASP1 to register for, say, 5-5-5 (ISUP), ASP2 to registe=
r for
> > > > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> > > >
> > > > In this case, although ASP3 registers after ASP1 and ASP2,
> > > > there is nothing
> > > > stopping an SG from assigining a RK and RC to 5-5-5(*) for ASP3.
> > > >
> > > > An SG implementation could choose to refuse 5-5-5(*) and require =
ASP3
> > > > to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or it
> > > > might not.
> > > > I don't think it is the RFC's place to require one or the other. =
 So,
> > > > for in the case where there is an overlap between "different" APS=
s, it
> > > > should be left up to the SG implementation as it is now.
> > > >
> > > > Your additional text below, now clarifies that.  Thank you.
> > > >
> > > > --brian
> > > >
> > > >
> > > > J.Javier Pastor (ML/EEM) wrote:
> > > >                     (Wed, 14 Jan 2004 15:30:10)
> > > > > Barry,
> > > > >
> > > > > You are right. And that is valid only for the overlapping
> > > > case. You can not create a new AS whose associated RK
> > > > overlaps another existing registered RK. In the duplicate
> > > > case it is already included that the check is against the RK
> > > > previosly registered by the sending ASP. The latter makes
> > > > sense but not the former.
> > > > >
> > > > > Go back to my first proposal.
> > > > >
> > > > > Thanks // Javier.
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: sigtran-admin@ietf.org
> > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > Barry Nagelberg
> > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > > > To: SIGTRAN Mailing List
> > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > > >
> > > > > >
> > > > > > Javier,
> > > > > >
> > > > > > No, Brian's suggestion is not correct, nor is this updated
> > > > > > text. Routing
> > > > > > keys are independent of ASPs or associations. I think
> > > > perhaps Brian is
> > > > > > thinking of the routing context, which may be unique for
> > > > each ASP or
> > > > > > association.
> > > > > >
> > > > > > Barry Nagelberg
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: sigtran-admin@ietf.org
> > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > J.Javier Pastor (ML/EEM)
> > > > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > > > To: 'bidulock@openss7.org'
> > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > > > >
> > > > > > >
> > > > > > > Brian,
> > > > > > >
> > > > > > > Tell me if the following is OK.
> > > > > > >
> > > > > > > If the SGP determines that the requested RK partially, but
> > > > > > not exactly,
> > > > > > > matches an existing RK already registered for the
> > > > sender ASP, and
> > > > > > > that an incoming signalling message received at
> > > > > > > an SGP could possibly match both the requested and the exis=
ting
> > > > > > > RK, the SGP
> > > > > > > returns a Registration Response message to the ASP, with a
> > > > > > Registration
> > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > incoming signalling
> > > > > > > message received at an SGP should not match against more
> > > > > > than one Routing
> > > > > > > Key.
> > > > > > >
> > > > > > >
> > > > > > > THanks // JAvier.
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error cod=
es
> > > > > > > >
> > > > > > > >
> > > > > > > > J.Javier,
> > > > > > > >
> > > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > > > >
> > > > > > > > --snip--
> > > > > > > > >
> > > > > > > > > --------
> > > > > > > > > New text: (Section 4.4.1)
> > > > > > > > > ---------
> > > > > > > > >
> > > > > > > > > If the SGP determines that the requested RK partially, =
but
> > > > > > > > not exactly,
> > > > > > > > > matches an existing RK, and that an incoming signalling
> > > > > > > > message received at
> > > > > > > > > an SGP could possibly match both the requested and the
> > > > > > > > existing RK, the SGP
> > > > > > > > > returns a Registration Response message to the ASP, wit=
h a
> > > > > > > > Registration
> > > > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > > > incoming signalling
> > > > > > > > > message received at an SGP should not match against mor=
e
> > > > > > > > than one Routing
> > > > > > > > > Key.
> > > > > > > > >
> > > > > > > > --snip--
> > > > > > > >
> > > > > > > > I think you mean for a given ASP (Association) in the
> > > > > > above.  Correct?
> > > > > > > >
> > > > > > > > It should be mentioned that the "matching" of RKs is done
> > > > > > > > only against other
> > > > > > > > RKs belonging to the same ASP (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
> > > > > >
> > > > >
> > > > > _______________________________________________
> > > > > 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 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 t=
he
> > originator immediately. If you are not the intended recipient, you ar=
e
> > notified that you are strictly prohibited from using, copying,
> > altering, or
> > disclosing the contents of this message. HSS accepts no responsibilit=
y 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
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Fri Jan 16 00:39:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17988
	for <sigtran-archive@odin.ietf.org>; Fri, 16 Jan 2004 00:39:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhMhD-0002fa-88
	for sigtran-archive@odin.ietf.org; Fri, 16 Jan 2004 00:39:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0G5d3B2010256
	for sigtran-archive@odin.ietf.org; Fri, 16 Jan 2004 00:39:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhMhB-0002fA-Cq; Fri, 16 Jan 2004 00:39:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhMgI-0002dA-Sk
	for sigtran@optimus.ietf.org; Fri, 16 Jan 2004 00:38:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17959
	for <sigtran@ietf.org>; Fri, 16 Jan 2004 00:37:58 -0500 (EST)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhMgB-0003RV-00
	for sigtran@ietf.org; Fri, 16 Jan 2004 00:37:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhMfE-0003OZ-00
	for sigtran@ietf.org; Fri, 16 Jan 2004 00:37:02 -0500
Received: from [203.200.71.140] (helo=spark.hss.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhMeJ-000389-00
	for sigtran@ietf.org; Fri, 16 Jan 2004 00:36:07 -0500
Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id i0G5WRiB005960;
	Fri, 16 Jan 2004 11:02:28 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id i0G5Xh716743;
	Fri, 16 Jan 2004 11:03:43 +0530 (IST)
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
To: bidulock@openss7.org
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF55E0A461.CE746179-ON65256E1D.001D90BA@hss.hns.com>
Date: Fri, 16 Jan 2004 10:56:35 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 16/01/2004
 10:53:56 AM
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.4 required=5.0 tests=EXCUSE_16,NO_REAL_NAME,
	ROUND_THE_WORLD_LOCAL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable





Brian,

   How can ASP3 have same RC3 for two different AS's (5-5-5(ISUP),
5-5-5(SCCP)) registered with same SGP.How will ASP3 activate the two AS=
's.

Kamesh Kaul
www.hssworld.com
Hughes Software Systems






"Brian F. G. Bidulock" <bidulock@openss7.org> on 01/15/2004 08:31:30 PM=


Please respond to bidulock@openss7.org

To:    Kamesh Kaul/HSS@HSS
cc:    SIGTRAN Mailing List <sigtran@ietf.org>

Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes


kakaul,

In the example:

            RK          ASP1   ASP2   ASP3
 -----------     ----   ----   ----
 5-5-5(ISUP)      RC1   -     RC3
 5-5-5(SCCP)       -     RC2    RC3

Is that so difficult?

--brian

kakaul@hss.hns.com wrote:
(Thu, 15 Jan 2004 19:17:06)
>
>
>
>
>
> Hi,
>
> I totally agree with Javier that there should be unique routing per A=
S's
,
> AS's must not overlap.
> I am not able to understand how SG can handle overlapped AS's registe=
red
by
> different ASP's,
> Brian can you explain it a little bit more.
>
> I think SG should not be confused in selecting actual AS if AS's are
> overlapped because first
> thing what SG does is selecting of AS for given traffic received with=
out
> having any clue of ASP's.
>
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
>
>
>
>
> ---------------------- Forwarded by Kamesh Kaul/HSS on 01/15/2004 07:=
04
PM
> ---------------------------
>
>
> "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on 01/15/2004
> 05:44:34 PM
>
> Please respond to bidulock@openss7.org
>
> Sent by:    sigtran-admin@ietf.org
>
>
> To:    "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
> cc:    "'Barry Nagelberg'" <barryn@adax.com>, SIGTRAN Mailing List
>        <sigtran@ietf.org>
>
> Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
>
>
> J.Javier,
>
> Where does it say ASes must not overlap?  This is precisely
> one of the example cases we used for IPSP discussions.
> I certainly don't see where retricting this is necessary
> for proper interworking or to protect the network.
>
> The only problem case we had for "Unique Routing" was were
> two RC's exist for the same traffic for the same ASP.  It is
> then abivalent which RC the SG is to assign to the traffic.
>
> In this example case, it is clear which RC value is to be
> assigned to each message for each ASP.  There is no problem
> of "Unique Routing".
>
> The problem of "Unique Routing" exists where one attempt to
> configure or register overlapping RKs for the same ASP.  So
> if ASP4 tries to register for 5-5-5(ISUP) and 5-5-5(*) there
> is a problem of unique routing.  To which RC is ISUP traffic
> to go?
>
> For the case of different ASPs, the SG can choose to support
> it, if capable, or refuse it if not.  The IG need not attempt
> to dictate a restriction to SG capabilities in this regard.
>
> --brian
>
> J.Javier Pastor (ML/EEM) wrote:
> (Thu, 15 Jan 2004 12:11:40)
> > Brian,
> >
> > Why don't you take the following approach...
> >
> > Define two different ASes:
> > - AS1 -> 5-5-5 (ISUP)
> > - AS2 -> 5-5-5 (SCCP)
> >
> > ASP1 registers within AS1
> > ASP2 registers within AS2
> > ASP3 registers within both AS1 and AS2
> >
> > It is important to keep one unique routing per AS. ASes MUST not
overlap.
> >
> > Cheers // Javier.
> >
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > > To: J.Javier Pastor (ML/EEM)
> > > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > J.Javier,
> > >
> > > Just to clarify, there should be nothing stopping an
> > > implementation from
> > > allowing ASP1 to register for, say, 5-5-5 (ISUP), ASP2 to registe=
r
for
> > > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> > >
> > > In this case, although ASP3 registers after ASP1 and ASP2,
> > > there is nothing
> > > stopping an SG from assigining a RK and RC to 5-5-5(*) for ASP3.
> > >
> > > An SG implementation could choose to refuse 5-5-5(*) and require =
ASP3
> > > to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or it
> > > might not.
> > > I don't think it is the RFC's place to require one or the other. =
 So,
> > > for in the case where there is an overlap between "different" APS=
s,
it
> > > should be left up to the SG implementation as it is now.
> > >
> > > Your additional text below, now clarifies that.  Thank you.
> > >
> > > --brian
> > >
> > >
> > > J.Javier Pastor (ML/EEM) wrote:
> > >                     (Wed, 14 Jan 2004 15:30:10)
> > > > Barry,
> > > >
> > > > You are right. And that is valid only for the overlapping
> > > case. You can not create a new AS whose associated RK
> > > overlaps another existing registered RK. In the duplicate
> > > case it is already included that the check is against the RK
> > > previosly registered by the sending ASP. The latter makes
> > > sense but not the former.
> > > >
> > > > Go back to my first proposal.
> > > >
> > > > Thanks // Javier.
> > > >
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org
> > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > Barry Nagelberg
> > > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > > To: SIGTRAN Mailing List
> > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > Javier,
> > > > >
> > > > > No, Brian's suggestion is not correct, nor is this updated
> > > > > text. Routing
> > > > > keys are independent of ASPs or associations. I think
> > > perhaps Brian is
> > > > > thinking of the routing context, which may be unique for
> > > each ASP or
> > > > > association.
> > > > >
> > > > > Barry Nagelberg
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: sigtran-admin@ietf.org
> > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > J.Javier Pastor (ML/EEM)
> > > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > > To: 'bidulock@openss7.org'
> > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes=

> > > > > >
> > > > > >
> > > > > > Brian,
> > > > > >
> > > > > > Tell me if the following is OK.
> > > > > >
> > > > > > If the SGP determines that the requested RK partially, but
> > > > > not exactly,
> > > > > > matches an existing RK already registered for the
> > > sender ASP, and
> > > > > > that an incoming signalling message received at
> > > > > > an SGP could possibly match both the requested and the exis=
ting
> > > > > > RK, the SGP
> > > > > > returns a Registration Response message to the ASP, with a
> > > > > Registration
> > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > incoming signalling
> > > > > > message received at an SGP should not match against more
> > > > > than one Routing
> > > > > > Key.
> > > > > >
> > > > > >
> > > > > > THanks // JAvier.
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error cod=
es
> > > > > > >
> > > > > > >
> > > > > > > J.Javier,
> > > > > > >
> > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > > >
> > > > > > > --snip--
> > > > > > > >
> > > > > > > > --------
> > > > > > > > New text: (Section 4.4.1)
> > > > > > > > ---------
> > > > > > > >
> > > > > > > > If the SGP determines that the requested RK partially, =
but
> > > > > > > not exactly,
> > > > > > > > matches an existing RK, and that an incoming signalling=

> > > > > > > message received at
> > > > > > > > an SGP could possibly match both the requested and the
> > > > > > > existing RK, the SGP
> > > > > > > > returns a Registration Response message to the ASP, wit=
h a
> > > > > > > Registration
> > > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > > incoming signalling
> > > > > > > > message received at an SGP should not match against mor=
e
> > > > > > > than one Routing
> > > > > > > > Key.
> > > > > > > >
> > > > > > > --snip--
> > > > > > >
> > > > > > > I think you mean for a given ASP (Association) in the
> > > > > above.  Correct?
> > > > > > >
> > > > > > > It should be mentioned that the "matching" of RKs is done=

> > > > > > > only against other
> > > > > > > RKs belonging to the same ASP (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
> > > > >
> > > >
> > > > _______________________________________________
> > > > 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 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 t=
he
> originator immediately. If you are not the intended recipient, you ar=
e
> notified that you are strictly prohibited from using, copying, alteri=
ng,
or
> disclosing the contents of this message. HSS accepts no responsibilit=
y
for
> loss or damage arising from the use of the information transmitted by=

this
> email including damage from virus."
>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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



=



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



From exim@www1.ietf.org  Fri Jan 16 01:21:31 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19318
	for <sigtran-archive@odin.ietf.org>; Fri, 16 Jan 2004 01:21:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhNLr-0004er-An
	for sigtran-archive@odin.ietf.org; Fri, 16 Jan 2004 01:21:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0G6L35Q017888
	for sigtran-archive@odin.ietf.org; Fri, 16 Jan 2004 01:21:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhNLq-0004e8-0b; Fri, 16 Jan 2004 01:21:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhNKs-0004cb-B2
	for sigtran@optimus.ietf.org; Fri, 16 Jan 2004 01:20:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19303
	for <sigtran@ietf.org>; Fri, 16 Jan 2004 01:20:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhNKp-0005ZE-00
	for sigtran@ietf.org; Fri, 16 Jan 2004 01:19:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhNJv-0005Xb-00
	for sigtran@ietf.org; Fri, 16 Jan 2004 01:19:04 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[2dmIswi/Xepb3J4FO3ghIdVu30bHNyRS])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhNJl-0005VZ-00
	for sigtran@ietf.org; Fri, 16 Jan 2004 01:18:53 -0500
Received: from ns.pigworks.openss7.net (IDENT:r9cu5BRUhumsjhrX6QgZosViKf+y4kD5@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0G6IrI10900;
	Thu, 15 Jan 2004 23:18:53 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0G6IrG09056;
	Thu, 15 Jan 2004 23:18:53 -0700
Date: Thu, 15 Jan 2004 23:18:53 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: kakaul@hss.hns.com
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
Message-ID: <20040115231853.A9023@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: kakaul@hss.hns.com,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <OF55E0A461.CE746179-ON65256E1D.001D90BA@hss.hns.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF55E0A461.CE746179-ON65256E1D.001D90BA@hss.hns.com>; from kakaul@hss.hns.com on Fri, Jan 16, 2004 at 10:56:35AM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i0G6IrI10900
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,EXCUSE_16 autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

kakaul,

As far as ASP3 is concerned it is one AS.  It activates it
by sending ASPAC(RC3).  To the SG it is clear what traffic
is activated: 5-5-5(*), and it responds ASPAC Ack(RC3).

--brian

kakaul@hss.hns.com wrote:                                                =
           (Fri, 16 Jan 2004 10:56:35)
>=20
>=20
>=20
>=20
> Brian,
>=20
>    How can ASP3 have same RC3 for two different AS's (5-5-5(ISUP),
> 5-5-5(SCCP)) registered with same SGP.How will ASP3 activate the two AS=
's.
>=20
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
>=20
>=20
>=20
>=20
>=20
>=20
> "Brian F. G. Bidulock" <bidulock@openss7.org> on 01/15/2004 08:31:30 PM
>=20
> Please respond to bidulock@openss7.org
>=20
> To:    Kamesh Kaul/HSS@HSS
> cc:    SIGTRAN Mailing List <sigtran@ietf.org>
>=20
> Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
>=20
>=20
> kakaul,
>=20
> In the example:
>=20
>             RK          ASP1   ASP2   ASP3
>  -----------     ----   ----   ----
>  5-5-5(ISUP)      RC1   -     RC3
>  5-5-5(SCCP)       -     RC2    RC3
>=20
> Is that so difficult?
>=20
> --brian
>=20
> kakaul@hss.hns.com wrote:
> (Thu, 15 Jan 2004 19:17:06)
> >
> >
> >
> >
> >
> > Hi,
> >
> > I totally agree with Javier that there should be unique routing per A=
S's
> ,
> > AS's must not overlap.
> > I am not able to understand how SG can handle overlapped AS's registe=
red
> by
> > different ASP's,
> > Brian can you explain it a little bit more.
> >
> > I think SG should not be confused in selecting actual AS if AS's are
> > overlapped because first
> > thing what SG does is selecting of AS for given traffic received with=
out
> > having any clue of ASP's.
> >
> > Kamesh Kaul
> > www.hssworld.com
> > Hughes Software Systems
> >
> >
> >
> >
> > ---------------------- Forwarded by Kamesh Kaul/HSS on 01/15/2004 07:=
04
> PM
> > ---------------------------
> >
> >
> > "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on 01/15/2004
> > 05:44:34 PM
> >
> > Please respond to bidulock@openss7.org
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
> > cc:    "'Barry Nagelberg'" <barryn@adax.com>, SIGTRAN Mailing List
> >        <sigtran@ietf.org>
> >
> > Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > J.Javier,
> >
> > Where does it say ASes must not overlap?  This is precisely
> > one of the example cases we used for IPSP discussions.
> > I certainly don't see where retricting this is necessary
> > for proper interworking or to protect the network.
> >
> > The only problem case we had for "Unique Routing" was were
> > two RC's exist for the same traffic for the same ASP.  It is
> > then abivalent which RC the SG is to assign to the traffic.
> >
> > In this example case, it is clear which RC value is to be
> > assigned to each message for each ASP.  There is no problem
> > of "Unique Routing".
> >
> > The problem of "Unique Routing" exists where one attempt to
> > configure or register overlapping RKs for the same ASP.  So
> > if ASP4 tries to register for 5-5-5(ISUP) and 5-5-5(*) there
> > is a problem of unique routing.  To which RC is ISUP traffic
> > to go?
> >
> > For the case of different ASPs, the SG can choose to support
> > it, if capable, or refuse it if not.  The IG need not attempt
> > to dictate a restriction to SG capabilities in this regard.
> >
> > --brian
> >
> > J.Javier Pastor (ML/EEM) wrote:
> > (Thu, 15 Jan 2004 12:11:40)
> > > Brian,
> > >
> > > Why don't you take the following approach...
> > >
> > > Define two different ASes:
> > > - AS1 -> 5-5-5 (ISUP)
> > > - AS2 -> 5-5-5 (SCCP)
> > >
> > > ASP1 registers within AS1
> > > ASP2 registers within AS2
> > > ASP3 registers within both AS1 and AS2
> > >
> > > It is important to keep one unique routing per AS. ASes MUST not
> overlap.
> > >
> > > Cheers // Javier.
> > >
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > > > To: J.Javier Pastor (ML/EEM)
> > > > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > J.Javier,
> > > >
> > > > Just to clarify, there should be nothing stopping an
> > > > implementation from
> > > > allowing ASP1 to register for, say, 5-5-5 (ISUP), ASP2 to registe=
r
> for
> > > > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> > > >
> > > > In this case, although ASP3 registers after ASP1 and ASP2,
> > > > there is nothing
> > > > stopping an SG from assigining a RK and RC to 5-5-5(*) for ASP3.
> > > >
> > > > An SG implementation could choose to refuse 5-5-5(*) and require =
ASP3
> > > > to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or it
> > > > might not.
> > > > I don't think it is the RFC's place to require one or the other. =
 So,
> > > > for in the case where there is an overlap between "different" APS=
s,
> it
> > > > should be left up to the SG implementation as it is now.
> > > >
> > > > Your additional text below, now clarifies that.  Thank you.
> > > >
> > > > --brian
> > > >
> > > >
> > > > J.Javier Pastor (ML/EEM) wrote:
> > > >                     (Wed, 14 Jan 2004 15:30:10)
> > > > > Barry,
> > > > >
> > > > > You are right. And that is valid only for the overlapping
> > > > case. You can not create a new AS whose associated RK
> > > > overlaps another existing registered RK. In the duplicate
> > > > case it is already included that the check is against the RK
> > > > previosly registered by the sending ASP. The latter makes
> > > > sense but not the former.
> > > > >
> > > > > Go back to my first proposal.
> > > > >
> > > > > Thanks // Javier.
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: sigtran-admin@ietf.org
> > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > Barry Nagelberg
> > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > > > To: SIGTRAN Mailing List
> > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > > >
> > > > > >
> > > > > > Javier,
> > > > > >
> > > > > > No, Brian's suggestion is not correct, nor is this updated
> > > > > > text. Routing
> > > > > > keys are independent of ASPs or associations. I think
> > > > perhaps Brian is
> > > > > > thinking of the routing context, which may be unique for
> > > > each ASP or
> > > > > > association.
> > > > > >
> > > > > > Barry Nagelberg
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: sigtran-admin@ietf.org
> > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > J.Javier Pastor (ML/EEM)
> > > > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > > > To: 'bidulock@openss7.org'
> > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > > > >
> > > > > > >
> > > > > > > Brian,
> > > > > > >
> > > > > > > Tell me if the following is OK.
> > > > > > >
> > > > > > > If the SGP determines that the requested RK partially, but
> > > > > > not exactly,
> > > > > > > matches an existing RK already registered for the
> > > > sender ASP, and
> > > > > > > that an incoming signalling message received at
> > > > > > > an SGP could possibly match both the requested and the exis=
ting
> > > > > > > RK, the SGP
> > > > > > > returns a Registration Response message to the ASP, with a
> > > > > > Registration
> > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > incoming signalling
> > > > > > > message received at an SGP should not match against more
> > > > > > than one Routing
> > > > > > > Key.
> > > > > > >
> > > > > > >
> > > > > > > THanks // JAvier.
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error cod=
es
> > > > > > > >
> > > > > > > >
> > > > > > > > J.Javier,
> > > > > > > >
> > > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > > > >
> > > > > > > > --snip--
> > > > > > > > >
> > > > > > > > > --------
> > > > > > > > > New text: (Section 4.4.1)
> > > > > > > > > ---------
> > > > > > > > >
> > > > > > > > > If the SGP determines that the requested RK partially, =
but
> > > > > > > > not exactly,
> > > > > > > > > matches an existing RK, and that an incoming signalling
> > > > > > > > message received at
> > > > > > > > > an SGP could possibly match both the requested and the
> > > > > > > > existing RK, the SGP
> > > > > > > > > returns a Registration Response message to the ASP, wit=
h a
> > > > > > > > Registration
> > > > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > > > incoming signalling
> > > > > > > > > message received at an SGP should not match against mor=
e
> > > > > > > > than one Routing
> > > > > > > > > Key.
> > > > > > > > >
> > > > > > > > --snip--
> > > > > > > >
> > > > > > > > I think you mean for a given ASP (Association) in the
> > > > > > above.  Correct?
> > > > > > > >
> > > > > > > > It should be mentioned that the "matching" of RKs is done
> > > > > > > > only against other
> > > > > > > > RKs belonging to the same ASP (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
> > > > > >
> > > > >
> > > > > _______________________________________________
> > > > > 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 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 t=
he
> > originator immediately. If you are not the intended recipient, you ar=
e
> > notified that you are strictly prohibited from using, copying, alteri=
ng,
> or
> > disclosing the contents of this message. HSS accepts no responsibilit=
y
> 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
>=20
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
>  http://www.openss7.org/
>=20
>=20
>=20
>=20

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

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



From exim@www1.ietf.org  Fri Jan 16 09:39:33 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15662
	for <sigtran-archive@odin.ietf.org>; Fri, 16 Jan 2004 09:39:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhV7p-0004Tj-VA
	for sigtran-archive@odin.ietf.org; Fri, 16 Jan 2004 09:39:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0GEd5UY017211
	for sigtran-archive@odin.ietf.org; Fri, 16 Jan 2004 09:39:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhV7l-0004TU-FC; Fri, 16 Jan 2004 09:39:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhV75-0004OF-T1
	for sigtran@optimus.ietf.org; Fri, 16 Jan 2004 09:38:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15613
	for <sigtran@ietf.org>; Fri, 16 Jan 2004 09:38:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhV74-0007PS-00
	for sigtran@ietf.org; Fri, 16 Jan 2004 09:38:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhV6A-0007Lh-00
	for sigtran@ietf.org; Fri, 16 Jan 2004 09:37:23 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhV5O-0007Is-00
	for sigtran@ietf.org; Fri, 16 Jan 2004 09:36:35 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i0GEaXkH021020
	for <sigtran@ietf.org>; Fri, 16 Jan 2004 09:36:34 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Fri, 16 Jan 2004 09:38:03 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOOEMKCDAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <20040115231853.A9023@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by slink5.mtl-nj.adax id i0GEaXkH021020
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,EXCUSE_16 autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Brian,

I don't think that this configuration would be clear at all to the SGP. I=
n
fact, it is impossible to implement this configuration using an SGP that
complies with the RFC!

At both the SGP and the ASP, there must be a 1:1 correspondence between a
Routing Key and a Routing Context (please see Section 1.2 of the RFC). So=
 if
ASP3 tries to register 2 different routing keys, 5-5-5(SCCP) and
5-5-5(ISUP), the SGP will return 2 different routing context values. You
will never get RC3 for both routing keys at ASP3!

Barry Nagelberg

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf O=
f
> Brian F. G. Bidulock
> Sent: Friday, January 16, 2004 1:19 AM
> To: kakaul@hss.hns.com
> Cc: SIGTRAN Mailing List
> Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
>
>
> kakaul,
>
> As far as ASP3 is concerned it is one AS.  It activates it
> by sending ASPAC(RC3).  To the SG it is clear what traffic
> is activated: 5-5-5(*), and it responds ASPAC Ack(RC3).
>
> --brian
>
> kakaul@hss.hns.com wrote:
>                   (Fri, 16 Jan 2004 10:56:35)
> >
> >
> >
> >
> > Brian,
> >
> >    How can ASP3 have same RC3 for two different AS's (5-5-5(ISUP),
> > 5-5-5(SCCP)) registered with same SGP.How will ASP3 activate
> the two AS's.
> >
> > Kamesh Kaul
> > www.hssworld.com
> > Hughes Software Systems
> >
> >
> >
> >
> >
> >
> > "Brian F. G. Bidulock" <bidulock@openss7.org> on 01/15/2004 08:31:30 =
PM
> >
> > Please respond to bidulock@openss7.org
> >
> > To:    Kamesh Kaul/HSS@HSS
> > cc:    SIGTRAN Mailing List <sigtran@ietf.org>
> >
> > Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > kakaul,
> >
> > In the example:
> >
> >             RK          ASP1   ASP2   ASP3
> >  -----------     ----   ----   ----
> >  5-5-5(ISUP)      RC1   -     RC3
> >  5-5-5(SCCP)       -     RC2    RC3
> >
> > Is that so difficult?
> >
> > --brian
> >
> > kakaul@hss.hns.com wrote:
> > (Thu, 15 Jan 2004 19:17:06)
> > >
> > >
> > >
> > >
> > >
> > > Hi,
> > >
> > > I totally agree with Javier that there should be unique
> routing per AS's
> > ,
> > > AS's must not overlap.
> > > I am not able to understand how SG can handle overlapped AS's
> registered
> > by
> > > different ASP's,
> > > Brian can you explain it a little bit more.
> > >
> > > I think SG should not be confused in selecting actual AS if AS's ar=
e
> > > overlapped because first
> > > thing what SG does is selecting of AS for given traffic
> received without
> > > having any clue of ASP's.
> > >
> > > Kamesh Kaul
> > > www.hssworld.com
> > > Hughes Software Systems
> > >
> > >
> > >
> > >
> > > ---------------------- Forwarded by Kamesh Kaul/HSS on
> 01/15/2004 07:04
> > PM
> > > ---------------------------
> > >
> > >
> > > "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on 01/15/200=
4
> > > 05:44:34 PM
> > >
> > > Please respond to bidulock@openss7.org
> > >
> > > Sent by:    sigtran-admin@ietf.org
> > >
> > >
> > > To:    "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
> > > cc:    "'Barry Nagelberg'" <barryn@adax.com>, SIGTRAN Mailing List
> > >        <sigtran@ietf.org>
> > >
> > > Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > J.Javier,
> > >
> > > Where does it say ASes must not overlap?  This is precisely
> > > one of the example cases we used for IPSP discussions.
> > > I certainly don't see where retricting this is necessary
> > > for proper interworking or to protect the network.
> > >
> > > The only problem case we had for "Unique Routing" was were
> > > two RC's exist for the same traffic for the same ASP.  It is
> > > then abivalent which RC the SG is to assign to the traffic.
> > >
> > > In this example case, it is clear which RC value is to be
> > > assigned to each message for each ASP.  There is no problem
> > > of "Unique Routing".
> > >
> > > The problem of "Unique Routing" exists where one attempt to
> > > configure or register overlapping RKs for the same ASP.  So
> > > if ASP4 tries to register for 5-5-5(ISUP) and 5-5-5(*) there
> > > is a problem of unique routing.  To which RC is ISUP traffic
> > > to go?
> > >
> > > For the case of different ASPs, the SG can choose to support
> > > it, if capable, or refuse it if not.  The IG need not attempt
> > > to dictate a restriction to SG capabilities in this regard.
> > >
> > > --brian
> > >
> > > J.Javier Pastor (ML/EEM) wrote:
> > > (Thu, 15 Jan 2004 12:11:40)
> > > > Brian,
> > > >
> > > > Why don't you take the following approach...
> > > >
> > > > Define two different ASes:
> > > > - AS1 -> 5-5-5 (ISUP)
> > > > - AS2 -> 5-5-5 (SCCP)
> > > >
> > > > ASP1 registers within AS1
> > > > ASP2 registers within AS2
> > > > ASP3 registers within both AS1 and AS2
> > > >
> > > > It is important to keep one unique routing per AS. ASes MUST not
> > overlap.
> > > >
> > > > Cheers // Javier.
> > > >
> > > > > -----Original Message-----
> > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > > > > To: J.Javier Pastor (ML/EEM)
> > > > > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > J.Javier,
> > > > >
> > > > > Just to clarify, there should be nothing stopping an
> > > > > implementation from
> > > > > allowing ASP1 to register for, say, 5-5-5 (ISUP), ASP2 to regis=
ter
> > for
> > > > > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> > > > >
> > > > > In this case, although ASP3 registers after ASP1 and ASP2,
> > > > > there is nothing
> > > > > stopping an SG from assigining a RK and RC to 5-5-5(*) for ASP3.
> > > > >
> > > > > An SG implementation could choose to refuse 5-5-5(*) and
> require ASP3
> > > > > to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or it
> > > > > might not.
> > > > > I don't think it is the RFC's place to require one or the
> other.  So,
> > > > > for in the case where there is an overlap between
> "different" APSs,
> > it
> > > > > should be left up to the SG implementation as it is now.
> > > > >
> > > > > Your additional text below, now clarifies that.  Thank you.
> > > > >
> > > > > --brian
> > > > >
> > > > >
> > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > >                     (Wed, 14 Jan 2004 15:30:10)
> > > > > > Barry,
> > > > > >
> > > > > > You are right. And that is valid only for the overlapping
> > > > > case. You can not create a new AS whose associated RK
> > > > > overlaps another existing registered RK. In the duplicate
> > > > > case it is already included that the check is against the RK
> > > > > previosly registered by the sending ASP. The latter makes
> > > > > sense but not the former.
> > > > > >
> > > > > > Go back to my first proposal.
> > > > > >
> > > > > > Thanks // Javier.
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: sigtran-admin@ietf.org
> > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > Barry Nagelberg
> > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > > > > To: SIGTRAN Mailing List
> > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
> > > > > > >
> > > > > > >
> > > > > > > Javier,
> > > > > > >
> > > > > > > No, Brian's suggestion is not correct, nor is this updated
> > > > > > > text. Routing
> > > > > > > keys are independent of ASPs or associations. I think
> > > > > perhaps Brian is
> > > > > > > thinking of the routing context, which may be unique for
> > > > > each ASP or
> > > > > > > association.
> > > > > > >
> > > > > > > Barry Nagelberg
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: sigtran-admin@ietf.org
> > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > > J.Javier Pastor (ML/EEM)
> > > > > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > > > > To: 'bidulock@openss7.org'
> > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error cod=
es
> > > > > > > >
> > > > > > > >
> > > > > > > > Brian,
> > > > > > > >
> > > > > > > > Tell me if the following is OK.
> > > > > > > >
> > > > > > > > If the SGP determines that the requested RK partially, bu=
t
> > > > > > > not exactly,
> > > > > > > > matches an existing RK already registered for the
> > > > > sender ASP, and
> > > > > > > > that an incoming signalling message received at
> > > > > > > > an SGP could possibly match both the requested and
> the existing
> > > > > > > > RK, the SGP
> > > > > > > > returns a Registration Response message to the ASP, with =
a
> > > > > > > Registration
> > > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > > incoming signalling
> > > > > > > > message received at an SGP should not match against more
> > > > > > > than one Routing
> > > > > > > > Key.
> > > > > > > >
> > > > > > > >
> > > > > > > > THanks // JAvier.
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org=
]
> > > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM
> error codes
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > J.Javier,
> > > > > > > > >
> > > > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > > > > >
> > > > > > > > > --snip--
> > > > > > > > > >
> > > > > > > > > > --------
> > > > > > > > > > New text: (Section 4.4.1)
> > > > > > > > > > ---------
> > > > > > > > > >
> > > > > > > > > > If the SGP determines that the requested RK
> partially, but
> > > > > > > > > not exactly,
> > > > > > > > > > matches an existing RK, and that an incoming signalli=
ng
> > > > > > > > > message received at
> > > > > > > > > > an SGP could possibly match both the requested and th=
e
> > > > > > > > > existing RK, the SGP
> > > > > > > > > > returns a Registration Response message to the
> ASP, with a
> > > > > > > > > Registration
> > > > > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > > > > incoming signalling
> > > > > > > > > > message received at an SGP should not match against m=
ore
> > > > > > > > > than one Routing
> > > > > > > > > > Key.
> > > > > > > > > >
> > > > > > > > > --snip--
> > > > > > > > >
> > > > > > > > > I think you mean for a given ASP (Association) in the
> > > > > > > above.  Correct?
> > > > > > > > >
> > > > > > > > > It should be mentioned that the "matching" of RKs is do=
ne
> > > > > > > > > only against other
> > > > > > > > > RKs belonging to the same ASP (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
> > > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > 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 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 a=
nd
> > > 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 responsibil=
ity
> > for
> > > loss or damage arising from the use of the information transmitted =
by
> > this
> > > email including damage from virus."
> > >
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >
> > --
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> >  http://www.openss7.org/
> >
> >
> >
> >
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


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



From exim@www1.ietf.org  Fri Jan 16 16:29:04 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00021
	for <sigtran-archive@odin.ietf.org>; Fri, 16 Jan 2004 16:29:04 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhbVc-0003r2-IB
	for sigtran-archive@odin.ietf.org; Fri, 16 Jan 2004 16:28:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0GLS45T014810
	for sigtran-archive@odin.ietf.org; Fri, 16 Jan 2004 16:28:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhbVZ-0003pp-H6; Fri, 16 Jan 2004 16:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhbV9-0003ma-DE
	for sigtran@optimus.ietf.org; Fri, 16 Jan 2004 16:27:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29905
	for <sigtran@ietf.org>; Fri, 16 Jan 2004 16:27:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhbV7-0005uq-00
	for sigtran@ietf.org; Fri, 16 Jan 2004 16:27:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhbU9-0005rx-00
	for sigtran@ietf.org; Fri, 16 Jan 2004 16:26:34 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[RU3DAeJ1GN8jxpFl1zL3ljSN8Wrjh+oQ])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhbTW-0005pM-00
	for sigtran@ietf.org; Fri, 16 Jan 2004 16:25:54 -0500
Received: from ns.pigworks.openss7.net (IDENT:V5LBYFC1NZYeGns/jmED33gpL2Qfil+9@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0GLPnI26265;
	Fri, 16 Jan 2004 14:25:49 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0GLPmH20454;
	Fri, 16 Jan 2004 14:25:48 -0700
Date: Fri, 16 Jan 2004 14:25:48 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry Nagelberg <barryn@adax.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
Message-ID: <20040116142548.A20344@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry Nagelberg <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <20040115231853.A9023@openss7.org> <JBECLENKLBCKAAKFGAJOOEMKCDAA.barryn@adax.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <JBECLENKLBCKAAKFGAJOOEMKCDAA.barryn@adax.com>; from barryn@adax.com on Fri, Jan 16, 2004 at 09:38:03AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i0GLPnI26265
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,EXCUSE_16 autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Barry,

There is a 1:1 correspondence; they are:

  5-5-5(ISUP) RC1
  5-5-5(SCCP) RC2
  5-5-5(*)    RC3

--brian

Barry Nagelberg wrote:                                                   =
            (Fri, 16 Jan 2004 09:38:03)
> Brian,
>=20
> I don't think that this configuration would be clear at all to the SGP.=
 In
> fact, it is impossible to implement this configuration using an SGP tha=
t
> complies with the RFC!
>=20
> At both the SGP and the ASP, there must be a 1:1 correspondence between=
 a
> Routing Key and a Routing Context (please see Section 1.2 of the RFC). =
So if
> ASP3 tries to register 2 different routing keys, 5-5-5(SCCP) and
> 5-5-5(ISUP), the SGP will return 2 different routing context values. Yo=
u
> will never get RC3 for both routing keys at ASP3!
>=20
> Barry Nagelberg
>=20
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf=
 Of
> > Brian F. G. Bidulock
> > Sent: Friday, January 16, 2004 1:19 AM
> > To: kakaul@hss.hns.com
> > Cc: SIGTRAN Mailing List
> > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > kakaul,
> >
> > As far as ASP3 is concerned it is one AS.  It activates it
> > by sending ASPAC(RC3).  To the SG it is clear what traffic
> > is activated: 5-5-5(*), and it responds ASPAC Ack(RC3).
> >
> > --brian
> >
> > kakaul@hss.hns.com wrote:
> >                   (Fri, 16 Jan 2004 10:56:35)
> > >
> > >
> > >
> > >
> > > Brian,
> > >
> > >    How can ASP3 have same RC3 for two different AS's (5-5-5(ISUP),
> > > 5-5-5(SCCP)) registered with same SGP.How will ASP3 activate
> > the two AS's.
> > >
> > > Kamesh Kaul
> > > www.hssworld.com
> > > Hughes Software Systems
> > >
> > >
> > >
> > >
> > >
> > >
> > > "Brian F. G. Bidulock" <bidulock@openss7.org> on 01/15/2004 08:31:3=
0 PM
> > >
> > > Please respond to bidulock@openss7.org
> > >
> > > To:    Kamesh Kaul/HSS@HSS
> > > cc:    SIGTRAN Mailing List <sigtran@ietf.org>
> > >
> > > Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > kakaul,
> > >
> > > In the example:
> > >
> > >             RK          ASP1   ASP2   ASP3
> > >  -----------     ----   ----   ----
> > >  5-5-5(ISUP)      RC1   -     RC3
> > >  5-5-5(SCCP)       -     RC2    RC3
> > >
> > > Is that so difficult?
> > >
> > > --brian
> > >
> > > kakaul@hss.hns.com wrote:
> > > (Thu, 15 Jan 2004 19:17:06)
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > I totally agree with Javier that there should be unique
> > routing per AS's
> > > ,
> > > > AS's must not overlap.
> > > > I am not able to understand how SG can handle overlapped AS's
> > registered
> > > by
> > > > different ASP's,
> > > > Brian can you explain it a little bit more.
> > > >
> > > > I think SG should not be confused in selecting actual AS if AS's =
are
> > > > overlapped because first
> > > > thing what SG does is selecting of AS for given traffic
> > received without
> > > > having any clue of ASP's.
> > > >
> > > > Kamesh Kaul
> > > > www.hssworld.com
> > > > Hughes Software Systems
> > > >
> > > >
> > > >
> > > >
> > > > ---------------------- Forwarded by Kamesh Kaul/HSS on
> > 01/15/2004 07:04
> > > PM
> > > > ---------------------------
> > > >
> > > >
> > > > "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on 01/15/2=
004
> > > > 05:44:34 PM
> > > >
> > > > Please respond to bidulock@openss7.org
> > > >
> > > > Sent by:    sigtran-admin@ietf.org
> > > >
> > > >
> > > > To:    "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
> > > > cc:    "'Barry Nagelberg'" <barryn@adax.com>, SIGTRAN Mailing Lis=
t
> > > >        <sigtran@ietf.org>
> > > >
> > > > Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > J.Javier,
> > > >
> > > > Where does it say ASes must not overlap?  This is precisely
> > > > one of the example cases we used for IPSP discussions.
> > > > I certainly don't see where retricting this is necessary
> > > > for proper interworking or to protect the network.
> > > >
> > > > The only problem case we had for "Unique Routing" was were
> > > > two RC's exist for the same traffic for the same ASP.  It is
> > > > then abivalent which RC the SG is to assign to the traffic.
> > > >
> > > > In this example case, it is clear which RC value is to be
> > > > assigned to each message for each ASP.  There is no problem
> > > > of "Unique Routing".
> > > >
> > > > The problem of "Unique Routing" exists where one attempt to
> > > > configure or register overlapping RKs for the same ASP.  So
> > > > if ASP4 tries to register for 5-5-5(ISUP) and 5-5-5(*) there
> > > > is a problem of unique routing.  To which RC is ISUP traffic
> > > > to go?
> > > >
> > > > For the case of different ASPs, the SG can choose to support
> > > > it, if capable, or refuse it if not.  The IG need not attempt
> > > > to dictate a restriction to SG capabilities in this regard.
> > > >
> > > > --brian
> > > >
> > > > J.Javier Pastor (ML/EEM) wrote:
> > > > (Thu, 15 Jan 2004 12:11:40)
> > > > > Brian,
> > > > >
> > > > > Why don't you take the following approach...
> > > > >
> > > > > Define two different ASes:
> > > > > - AS1 -> 5-5-5 (ISUP)
> > > > > - AS2 -> 5-5-5 (SCCP)
> > > > >
> > > > > ASP1 registers within AS1
> > > > > ASP2 registers within AS2
> > > > > ASP3 registers within both AS1 and AS2
> > > > >
> > > > > It is important to keep one unique routing per AS. ASes MUST no=
t
> > > overlap.
> > > > >
> > > > > Cheers // Javier.
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > > >
> > > > > >
> > > > > > J.Javier,
> > > > > >
> > > > > > Just to clarify, there should be nothing stopping an
> > > > > > implementation from
> > > > > > allowing ASP1 to register for, say, 5-5-5 (ISUP), ASP2 to reg=
ister
> > > for
> > > > > > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> > > > > >
> > > > > > In this case, although ASP3 registers after ASP1 and ASP2,
> > > > > > there is nothing
> > > > > > stopping an SG from assigining a RK and RC to 5-5-5(*) for AS=
P3.
> > > > > >
> > > > > > An SG implementation could choose to refuse 5-5-5(*) and
> > require ASP3
> > > > > > to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or it
> > > > > > might not.
> > > > > > I don't think it is the RFC's place to require one or the
> > other.  So,
> > > > > > for in the case where there is an overlap between
> > "different" APSs,
> > > it
> > > > > > should be left up to the SG implementation as it is now.
> > > > > >
> > > > > > Your additional text below, now clarifies that.  Thank you.
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > >
> > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > >                     (Wed, 14 Jan 2004 15:30:10)
> > > > > > > Barry,
> > > > > > >
> > > > > > > You are right. And that is valid only for the overlapping
> > > > > > case. You can not create a new AS whose associated RK
> > > > > > overlaps another existing registered RK. In the duplicate
> > > > > > case it is already included that the check is against the RK
> > > > > > previosly registered by the sending ASP. The latter makes
> > > > > > sense but not the former.
> > > > > > >
> > > > > > > Go back to my first proposal.
> > > > > > >
> > > > > > > Thanks // Javier.
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: sigtran-admin@ietf.org
> > > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > > Barry Nagelberg
> > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > > > > > To: SIGTRAN Mailing List
> > > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error cod=
es
> > > > > > > >
> > > > > > > >
> > > > > > > > Javier,
> > > > > > > >
> > > > > > > > No, Brian's suggestion is not correct, nor is this update=
d
> > > > > > > > text. Routing
> > > > > > > > keys are independent of ASPs or associations. I think
> > > > > > perhaps Brian is
> > > > > > > > thinking of the routing context, which may be unique for
> > > > > > each ASP or
> > > > > > > > association.
> > > > > > > >
> > > > > > > > Barry Nagelberg
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: sigtran-admin@ietf.org
> > > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > > > J.Javier Pastor (ML/EEM)
> > > > > > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > > > > > To: 'bidulock@openss7.org'
> > > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error c=
odes
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Brian,
> > > > > > > > >
> > > > > > > > > Tell me if the following is OK.
> > > > > > > > >
> > > > > > > > > If the SGP determines that the requested RK partially, =
but
> > > > > > > > not exactly,
> > > > > > > > > matches an existing RK already registered for the
> > > > > > sender ASP, and
> > > > > > > > > that an incoming signalling message received at
> > > > > > > > > an SGP could possibly match both the requested and
> > the existing
> > > > > > > > > RK, the SGP
> > > > > > > > > returns a Registration Response message to the ASP, wit=
h a
> > > > > > > > Registration
> > > > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > > > incoming signalling
> > > > > > > > > message received at an SGP should not match against mor=
e
> > > > > > > > than one Routing
> > > > > > > > > Key.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > THanks // JAvier.
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.o=
rg]
> > > > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM
> > error codes
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > J.Javier,
> > > > > > > > > >
> > > > > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > > > > > >
> > > > > > > > > > --snip--
> > > > > > > > > > >
> > > > > > > > > > > --------
> > > > > > > > > > > New text: (Section 4.4.1)
> > > > > > > > > > > ---------
> > > > > > > > > > >
> > > > > > > > > > > If the SGP determines that the requested RK
> > partially, but
> > > > > > > > > > not exactly,
> > > > > > > > > > > matches an existing RK, and that an incoming signal=
ling
> > > > > > > > > > message received at
> > > > > > > > > > > an SGP could possibly match both the requested and =
the
> > > > > > > > > > existing RK, the SGP
> > > > > > > > > > > returns a Registration Response message to the
> > ASP, with a
> > > > > > > > > > Registration
> > > > > > > > > > > Status of "Error - "Cannot Support Unique Routing. =
An
> > > > > > > > > > incoming signalling
> > > > > > > > > > > message received at an SGP should not match against=
 more
> > > > > > > > > > than one Routing
> > > > > > > > > > > Key.
> > > > > > > > > > >
> > > > > > > > > > --snip--
> > > > > > > > > >
> > > > > > > > > > I think you mean for a given ASP (Association) in the
> > > > > > > > above.  Correct?
> > > > > > > > > >
> > > > > > > > > > It should be mentioned that the "matching" of RKs is =
done
> > > > > > > > > > only against other
> > > > > > > > > > RKs belonging to the same ASP (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
> > > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > 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 is proprietary to Hughes Software Syste=
ms
> > > 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, yo=
u are
> > > > notified that you are strictly prohibited from using,
> > copying, altering,
> > > or
> > > > disclosing the contents of this message. HSS accepts no responsib=
ility
> > > for
> > > > loss or damage arising from the use of the information transmitte=
d by
> > > this
> > > > email including damage from virus."
> > > >
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >
> > > --
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > >  http://www.openss7.org/
> > >
> > >
> > >
> > >
> >
> > --
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Sat Jan 17 02:18:36 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28450
	for <sigtran-archive@odin.ietf.org>; Sat, 17 Jan 2004 02:18:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ahkie-0007mn-8S
	for sigtran-archive@odin.ietf.org; Sat, 17 Jan 2004 02:18:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0H7I8Ym029928
	for sigtran-archive@odin.ietf.org; Sat, 17 Jan 2004 02:18:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhkiY-0007kk-N5; Sat, 17 Jan 2004 02:18:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ahkhq-0007Xf-BW
	for sigtran@optimus.ietf.org; Sat, 17 Jan 2004 02:17:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28250
	for <sigtran@ietf.org>; Sat, 17 Jan 2004 02:17:15 -0500 (EST)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ahkhm-0001b3-00
	for sigtran@ietf.org; Sat, 17 Jan 2004 02:17:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ahkf8-0001NS-00
	for sigtran@ietf.org; Sat, 17 Jan 2004 02:14:32 -0500
Received: from [203.200.71.140] (helo=spark.hss.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhkZj-0000kX-00
	for sigtran@ietf.org; Sat, 17 Jan 2004 02:08:55 -0500
Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id i0H753iB008272;
	Sat, 17 Jan 2004 12:35:03 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id i0H76Hi03910;
	Sat, 17 Jan 2004 12:36:17 +0530 (IST)
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
To: bidulock@openss7.org
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OFD85D456A.007B140C-ON65256E1E.0025C492@hss.hns.com>
Date: Sat, 17 Jan 2004 12:29:12 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 17/01/2004
 12:26:31 PM
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.4 required=5.0 tests=EXCUSE_16,NO_REAL_NAME,
	ROUND_THE_WORLD_LOCAL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable






Brian,

Apologies for responding so late.
Can you please explain this with a figure such that we are clear that A=
SP3
is ultimately serving how many AS's and to which SGP it is associated. =
I am
not able to understand the configuration you are talking about.

Kamesh Kaul
www.hssworld.com
Hughes Software Systems


"Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on 01/17/2004
02:55:48 AM

Please respond to bidulock@openss7.org

Sent by:    sigtran-admin@ietf.org


To:    Barry Nagelberg <barryn@adax.com>
cc:    SIGTRAN Mailing List <sigtran@ietf.org>

Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes


Barry,

There is a 1:1 correspondence; they are:

  5-5-5(ISUP) RC1
  5-5-5(SCCP) RC2
  5-5-5(*)    RC3

--brian

Barry Nagelberg wrote:
(Fri, 16 Jan 2004 09:38:03)
> Brian,
>
> I don't think that this configuration would be clear at all to the SG=
P.
In
> fact, it is impossible to implement this configuration using an SGP t=
hat
> complies with the RFC!
>
> At both the SGP and the ASP, there must be a 1:1 correspondence betwe=
en a
> Routing Key and a Routing Context (please see Section 1.2 of the RFC)=
. So
if
> ASP3 tries to register 2 different routing keys, 5-5-5(SCCP) and
> 5-5-5(ISUP), the SGP will return 2 different routing context values. =
You
> will never get RC3 for both routing keys at ASP3!
>
> Barry Nagelberg
>
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Beha=
lf
Of
> > Brian F. G. Bidulock
> > Sent: Friday, January 16, 2004 1:19 AM
> > To: kakaul@hss.hns.com
> > Cc: SIGTRAN Mailing List
> > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > kakaul,
> >
> > As far as ASP3 is concerned it is one AS.  It activates it
> > by sending ASPAC(RC3).  To the SG it is clear what traffic
> > is activated: 5-5-5(*), and it responds ASPAC Ack(RC3).
> >
> > --brian
> >
> > kakaul@hss.hns.com wrote:
> >                   (Fri, 16 Jan 2004 10:56:35)
> > >
> > >
> > >
> > >
> > > Brian,
> > >
> > >    How can ASP3 have same RC3 for two different AS's (5-5-5(ISUP)=
,
> > > 5-5-5(SCCP)) registered with same SGP.How will ASP3 activate
> > the two AS's.
> > >
> > > Kamesh Kaul
> > > www.hssworld.com
> > > Hughes Software Systems
> > >
> > >
> > >
> > >
> > >
> > >
> > > "Brian F. G. Bidulock" <bidulock@openss7.org> on 01/15/2004 08:31=
:30
PM
> > >
> > > Please respond to bidulock@openss7.org
> > >
> > > To:    Kamesh Kaul/HSS@HSS
> > > cc:    SIGTRAN Mailing List <sigtran@ietf.org>
> > >
> > > Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > kakaul,
> > >
> > > In the example:
> > >
> > >             RK          ASP1   ASP2   ASP3
> > >  -----------     ----   ----   ----
> > >  5-5-5(ISUP)      RC1   -     RC3
> > >  5-5-5(SCCP)       -     RC2    RC3
> > >
> > > Is that so difficult?
> > >
> > > --brian
> > >
> > > kakaul@hss.hns.com wrote:
> > > (Thu, 15 Jan 2004 19:17:06)
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > I totally agree with Javier that there should be unique
> > routing per AS's
> > > ,
> > > > AS's must not overlap.
> > > > I am not able to understand how SG can handle overlapped AS's
> > registered
> > > by
> > > > different ASP's,
> > > > Brian can you explain it a little bit more.
> > > >
> > > > I think SG should not be confused in selecting actual AS if AS'=
s
are
> > > > overlapped because first
> > > > thing what SG does is selecting of AS for given traffic
> > received without
> > > > having any clue of ASP's.
> > > >
> > > > Kamesh Kaul
> > > > www.hssworld.com
> > > > Hughes Software Systems
> > > >
> > > >
> > > >
> > > >
> > > > ---------------------- Forwarded by Kamesh Kaul/HSS on
> > 01/15/2004 07:04
> > > PM
> > > > ---------------------------
> > > >
> > > >
> > > > "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on
01/15/2004
> > > > 05:44:34 PM
> > > >
> > > > Please respond to bidulock@openss7.org
> > > >
> > > > Sent by:    sigtran-admin@ietf.org
> > > >
> > > >
> > > > To:    "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com=
>
> > > > cc:    "'Barry Nagelberg'" <barryn@adax.com>, SIGTRAN Mailing L=
ist
> > > >        <sigtran@ietf.org>
> > > >
> > > > Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > J.Javier,
> > > >
> > > > Where does it say ASes must not overlap?  This is precisely
> > > > one of the example cases we used for IPSP discussions.
> > > > I certainly don't see where retricting this is necessary
> > > > for proper interworking or to protect the network.
> > > >
> > > > The only problem case we had for "Unique Routing" was were
> > > > two RC's exist for the same traffic for the same ASP.  It is
> > > > then abivalent which RC the SG is to assign to the traffic.
> > > >
> > > > In this example case, it is clear which RC value is to be
> > > > assigned to each message for each ASP.  There is no problem
> > > > of "Unique Routing".
> > > >
> > > > The problem of "Unique Routing" exists where one attempt to
> > > > configure or register overlapping RKs for the same ASP.  So
> > > > if ASP4 tries to register for 5-5-5(ISUP) and 5-5-5(*) there
> > > > is a problem of unique routing.  To which RC is ISUP traffic
> > > > to go?
> > > >
> > > > For the case of different ASPs, the SG can choose to support
> > > > it, if capable, or refuse it if not.  The IG need not attempt
> > > > to dictate a restriction to SG capabilities in this regard.
> > > >
> > > > --brian
> > > >
> > > > J.Javier Pastor (ML/EEM) wrote:
> > > > (Thu, 15 Jan 2004 12:11:40)
> > > > > Brian,
> > > > >
> > > > > Why don't you take the following approach...
> > > > >
> > > > > Define two different ASes:
> > > > > - AS1 -> 5-5-5 (ISUP)
> > > > > - AS2 -> 5-5-5 (SCCP)
> > > > >
> > > > > ASP1 registers within AS1
> > > > > ASP2 registers within AS2
> > > > > ASP3 registers within both AS1 and AS2
> > > > >
> > > > > It is important to keep one unique routing per AS. ASes MUST =
not
> > > overlap.
> > > > >
> > > > > Cheers // Javier.
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes=

> > > > > >
> > > > > >
> > > > > > J.Javier,
> > > > > >
> > > > > > Just to clarify, there should be nothing stopping an
> > > > > > implementation from
> > > > > > allowing ASP1 to register for, say, 5-5-5 (ISUP), ASP2 to
register
> > > for
> > > > > > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> > > > > >
> > > > > > In this case, although ASP3 registers after ASP1 and ASP2,
> > > > > > there is nothing
> > > > > > stopping an SG from assigining a RK and RC to 5-5-5(*) for
ASP3.
> > > > > >
> > > > > > An SG implementation could choose to refuse 5-5-5(*) and
> > require ASP3
> > > > > > to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or =
it
> > > > > > might not.
> > > > > > I don't think it is the RFC's place to require one or the
> > other.  So,
> > > > > > for in the case where there is an overlap between
> > "different" APSs,
> > > it
> > > > > > should be left up to the SG implementation as it is now.
> > > > > >
> > > > > > Your additional text below, now clarifies that.  Thank you.=

> > > > > >
> > > > > > --brian
> > > > > >
> > > > > >
> > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > >                     (Wed, 14 Jan 2004 15:30:10)
> > > > > > > Barry,
> > > > > > >
> > > > > > > You are right. And that is valid only for the overlapping=

> > > > > > case. You can not create a new AS whose associated RK
> > > > > > overlaps another existing registered RK. In the duplicate
> > > > > > case it is already included that the check is against the R=
K
> > > > > > previosly registered by the sending ASP. The latter makes
> > > > > > sense but not the former.
> > > > > > >
> > > > > > > Go back to my first proposal.
> > > > > > >
> > > > > > > Thanks // Javier.
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: sigtran-admin@ietf.org
> > > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > > Barry Nagelberg
> > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > > > > > To: SIGTRAN Mailing List
> > > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error c=
odes
> > > > > > > >
> > > > > > > >
> > > > > > > > Javier,
> > > > > > > >
> > > > > > > > No, Brian's suggestion is not correct, nor is this upda=
ted
> > > > > > > > text. Routing
> > > > > > > > keys are independent of ASPs or associations. I think
> > > > > > perhaps Brian is
> > > > > > > > thinking of the routing context, which may be unique fo=
r
> > > > > > each ASP or
> > > > > > > > association.
> > > > > > > >
> > > > > > > > Barry Nagelberg
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: sigtran-admin@ietf.org
> > > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > > > J.Javier Pastor (ML/EEM)
> > > > > > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > > > > > To: 'bidulock@openss7.org'
> > > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM error=

codes
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Brian,
> > > > > > > > >
> > > > > > > > > Tell me if the following is OK.
> > > > > > > > >
> > > > > > > > > If the SGP determines that the requested RK partially=
,
but
> > > > > > > > not exactly,
> > > > > > > > > matches an existing RK already registered for the
> > > > > > sender ASP, and
> > > > > > > > > that an incoming signalling message received at
> > > > > > > > > an SGP could possibly match both the requested and
> > the existing
> > > > > > > > > RK, the SGP
> > > > > > > > > returns a Registration Response message to the ASP, w=
ith
a
> > > > > > > > Registration
> > > > > > > > > Status of "Error - "Cannot Support Unique Routing. An=

> > > > > > > > incoming signalling
> > > > > > > > > message received at an SGP should not match against m=
ore
> > > > > > > > than one Routing
> > > > > > > > > Key.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > THanks // JAvier.
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Brian F. G. Bidulock
[mailto:bidulock@openss7.org]
> > > > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM
> > error codes
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > J.Javier,
> > > > > > > > > >
> > > > > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > > > > > >
> > > > > > > > > > --snip--
> > > > > > > > > > >
> > > > > > > > > > > --------
> > > > > > > > > > > New text: (Section 4.4.1)
> > > > > > > > > > > ---------
> > > > > > > > > > >
> > > > > > > > > > > If the SGP determines that the requested RK
> > partially, but
> > > > > > > > > > not exactly,
> > > > > > > > > > > matches an existing RK, and that an incoming
signalling
> > > > > > > > > > message received at
> > > > > > > > > > > an SGP could possibly match both the requested an=
d
the
> > > > > > > > > > existing RK, the SGP
> > > > > > > > > > > returns a Registration Response message to the
> > ASP, with a
> > > > > > > > > > Registration
> > > > > > > > > > > Status of "Error - "Cannot Support Unique Routing=
. An
> > > > > > > > > > incoming signalling
> > > > > > > > > > > message received at an SGP should not match again=
st
more
> > > > > > > > > > than one Routing
> > > > > > > > > > > Key.
> > > > > > > > > > >
> > > > > > > > > > --snip--
> > > > > > > > > >
> > > > > > > > > > I think you mean for a given ASP (Association) in t=
he
> > > > > > > > above.  Correct?
> > > > > > > > > >
> > > > > > > > > > It should be mentioned that the "matching" of RKs i=
s
done
> > > > > > > > > > only against other
> > > > > > > > > > RKs belonging to the same ASP (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
> > > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > 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 is proprietary to Hughes Software Sys=
tems
> > > Limited
> > > > (HSS) and is intended solely for the use of the individual to
> > whom it is
> > > > addressed. It may contain  privileged or confidential informati=
on
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 transmit=
ted
by
> > > this
> > > > email including damage from virus."
> > > >
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >
> > > --
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > >  http://www.openss7.org/
> > >
> > >
> > >
> > >
> >
> > --
> > 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




"DISCLAIMER: This message is proprietary to Hughes Software Systems Lim=
ited
(HSS) and is intended solely for the use of the individual to whom it i=
s
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 t=
his
email including damage from virus."=



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



From exim@www1.ietf.org  Mon Jan 19 04:13:32 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07740
	for <sigtran-archive@odin.ietf.org>; Mon, 19 Jan 2004 04:13:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiVSx-0004lk-Nu
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 04:13:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0J9D3CT018315
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 04:13:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiVSv-0004kN-Hk; Mon, 19 Jan 2004 04:13:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiVSJ-0004j0-0b
	for sigtran@optimus.ietf.org; Mon, 19 Jan 2004 04:12:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07718
	for <sigtran@ietf.org>; Mon, 19 Jan 2004 04:12:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiVSG-0005P5-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 04:12:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiVRJ-0005Lf-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 04:11:21 -0500
Received: from zdemail04.zdem.compaq.com ([161.114.112.28])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiVQO-0005F4-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 04:10:25 -0500
Received: from demexg11.emea.cpqcorp.net (demexg11.emea.cpqcorp.net [16.41.86.63])
	by zdemail04.zdem.compaq.com (Postfix) with ESMTP
	id 69D6BE74; Mon, 19 Jan 2004 10:09:54 +0100 (CET)
Received: from vbeexc02.emea.cpqcorp.net ([16.188.146.229]) by demexg11.emea.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.6673);
	 Mon, 19 Jan 2004 10:09:52 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sigtran] SUA v14 doubt in SCON
Date: Mon, 19 Jan 2004 10:08:58 +0100
Message-ID: <06CAA4D3753C53408D2CE6340B6844420348FF52@vbeexc02.emea.cpqcorp.net>
Thread-Topic: [Sigtran] SUA v14 doubt in SCON
Thread-Index: AcJbPUwHN4hdDQ0DSx6ovFtdKvDJZGBE2wSA
From: "Zannin, Francois" <francois.zannin@hp.com>
To: "Tolga Asveren" <tolga.asveren@ss8.com>, <sigtran@ietf.org>
X-OriginalArrivalTime: 19 Jan 2004 09:09:52.0688 (UTC) FILETIME=[FF8E2B00:01C3DE6B]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi,

In the SUA network, I was wondering what could be the message send by an
ASP congested for one (and only one) of it's hosted AS.

The SCON sent by an ASP to the originator of the message (like # ss7 TFC
or SSC) could be a solution, But this SCON do not include any affected
PC like in M3UA.=20

When an ASP receive a message for a congested AS, it can return a
congestion indication to the originator of the message (Ref: Q714
5.2.7.1). Then, the ASP sends a SCON to the SG for the "originator of
the message". But with no concerned PC in the SCON, the SG cannot
identify the addressee of the SCON.

If we are handling the congestion in "International mode", no congestion
state must be kept in the message path, so the SG do not need any
processing other then forwarding the SCON as a TFC.

Could we add a concerned DPC in the SCON as it exist in the M3UA SCON?

Francois,


-----Original Message-----
From: Tolga Asveren [mailto:tolga.asveren@ss8.com]=20
Sent: Friday, September 13, 2002 5:58 PM
To: sigtran@ietf.org
Subject: RE: [Sigtran] SUA v14 doubt in SCON


Brian,

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Friday, September 13, 2002 11:10 AM
> To: ygahlaut@hss.hns.com
> Cc: john.loughney@nokia.com; tolga.asveren@ss8.com; sigtran@ietf.org
> Subject: Re: [Sigtran] SUA v14 doubt in SCON
>
>
> Yogesh,
>
> SCON is used to indicate SS7 network congestion only.  It is not=20
> useful in the IPSP case.  In the IPSP case, IETF mechanisms are more=20
> applicable: such as ECN.
[TOLGA] For SUA-IPSP case, aren't we allowed to use SCON to inform the
peer about local subsystem congestion? Because there is no 1:1:1
relationship between AS,SCTP associations and an IP address, I wouldn't
think ECN or SCTP congestion mechanisms can do, what SCON is intended to
do.

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

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



From exim@www1.ietf.org  Mon Jan 19 05:23:31 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10873
	for <sigtran-archive@odin.ietf.org>; Mon, 19 Jan 2004 05:23:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiWYi-0000YE-3W
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 05:23:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0JAN4GI002118
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 05:23:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiWYf-0000Xr-OU; Mon, 19 Jan 2004 05:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiWY5-0000Vz-SH
	for sigtran@optimus.ietf.org; Mon, 19 Jan 2004 05:22:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10850
	for <sigtran@ietf.org>; Mon, 19 Jan 2004 05:22:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiWY2-0001oM-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 05:22:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiWXA-0001mU-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 05:21:29 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[DDWH1GIIXZLqqWZyN91sJWbmU5TVrD3C])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiWWH-0001iA-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 05:20:33 -0500
Received: from ns.pigworks.openss7.net (IDENT:HiSOPosdMzcgD++3T/GE329HbuULb5Zf@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0JAKWI15508;
	Mon, 19 Jan 2004 03:20:32 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0JAKVf10590;
	Mon, 19 Jan 2004 03:20:31 -0700
Date: Mon, 19 Jan 2004 03:20:31 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Zannin, Francois" <francois.zannin@hp.com>
Cc: Tolga Asveren <tolga.asveren@ss8.com>, sigtran@ietf.org
Subject: Re: [Sigtran] SUA v14 doubt in SCON
Message-ID: <20040119032031.A9930@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Zannin, Francois" <francois.zannin@hp.com>,
	Tolga Asveren <tolga.asveren@ss8.com>, sigtran@ietf.org
References: <06CAA4D3753C53408D2CE6340B6844420348FF52@vbeexc02.emea.cpqcorp.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: <06CAA4D3753C53408D2CE6340B6844420348FF52@vbeexc02.emea.cpqcorp.net>; from francois.zannin@hp.com on Mon, Jan 19, 2004 at 10:08:58AM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Francois,

SUA does not support this (nor does it need to).  We only put it
in M3UA for so-called "nodal" congestion, and it has questionable
utility there.

--brian

Zannin, Francois wrote:                                                            (Mon, 19 Jan 2004 10:08:58)
> Hi,
> 
> In the SUA network, I was wondering what could be the message send by an
> ASP congested for one (and only one) of it's hosted AS.
> 
> The SCON sent by an ASP to the originator of the message (like # ss7 TFC
> or SSC) could be a solution, But this SCON do not include any affected
> PC like in M3UA. 
> 
> When an ASP receive a message for a congested AS, it can return a
> congestion indication to the originator of the message (Ref: Q714
> 5.2.7.1). Then, the ASP sends a SCON to the SG for the "originator of
> the message". But with no concerned PC in the SCON, the SG cannot
> identify the addressee of the SCON.
> 
> If we are handling the congestion in "International mode", no congestion
> state must be kept in the message path, so the SG do not need any
> processing other then forwarding the SCON as a TFC.
> 
> Could we add a concerned DPC in the SCON as it exist in the M3UA SCON?
> 
> Francois,
> 
> 
> -----Original Message-----
> From: Tolga Asveren [mailto:tolga.asveren@ss8.com] 
> Sent: Friday, September 13, 2002 5:58 PM
> To: sigtran@ietf.org
> Subject: RE: [Sigtran] SUA v14 doubt in SCON
> 
> 
> Brian,
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Friday, September 13, 2002 11:10 AM
> > To: ygahlaut@hss.hns.com
> > Cc: john.loughney@nokia.com; tolga.asveren@ss8.com; sigtran@ietf.org
> > Subject: Re: [Sigtran] SUA v14 doubt in SCON
> >
> >
> > Yogesh,
> >
> > SCON is used to indicate SS7 network congestion only.  It is not 
> > useful in the IPSP case.  In the IPSP case, IETF mechanisms are more 
> > applicable: such as ECN.
> [TOLGA] For SUA-IPSP case, aren't we allowed to use SCON to inform the
> peer about local subsystem congestion? Because there is no 1:1:1
> relationship between AS,SCTP associations and an IP address, I wouldn't
> think ECN or SCTP congestion mechanisms can do, what SCON is intended to
> do.
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Mon Jan 19 05:38:33 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11172
	for <sigtran-archive@odin.ietf.org>; Mon, 19 Jan 2004 05:38:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiWnF-0001K8-FZ
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 05:38:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0JAc5st005053
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 05:38:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiWnC-0001In-HV; Mon, 19 Jan 2004 05:38:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiWmt-0001CY-TU
	for sigtran@optimus.ietf.org; Mon, 19 Jan 2004 05:37:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11017
	for <sigtran@ietf.org>; Mon, 19 Jan 2004 05:37:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiWmq-0002S6-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 05:37:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiWlh-0002Fn-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 05:36:30 -0500
Received: from zdemail03.zdem.compaq.com ([161.114.112.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiWke-0002B5-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 05:35:24 -0500
Received: from demexg11.emea.cpqcorp.net (demexg11.emea.cpqcorp.net [16.41.86.63])
	by zdemail03.zdem.compaq.com (Postfix) with ESMTP
	id 31B0E1373; Mon, 19 Jan 2004 11:34:54 +0100 (CET)
Received: from vbeexc02.emea.cpqcorp.net ([16.188.146.229]) by demexg11.emea.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.6673);
	 Mon, 19 Jan 2004 11:34:54 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sigtran] SUA v14 doubt in SCON
Date: Mon, 19 Jan 2004 11:34:49 +0100
Message-ID: <06CAA4D3753C53408D2CE6340B6844420348FF55@vbeexc02.emea.cpqcorp.net>
Thread-Topic: [Sigtran] SUA v14 doubt in SCON
Thread-Index: AcPedmVrHhYoNoM1Toa6uCwKDTsNGwAAPMHg
From: "Zannin, Francois" <francois.zannin@hp.com>
To: <bidulock@openss7.org>
Cc: "Tolga Asveren" <tolga.asveren@ss8.com>, <sigtran@ietf.org>
X-OriginalArrivalTime: 19 Jan 2004 10:34:54.0744 (UTC) FILETIME=[E09E2180:01C3DE77]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Brian,

When a SUA End point is connected to two or more SG and the ASP is
congestionned for only one AS served by the ASP (this case exist), how
can the ASP inform the originator of the message that the AS (SCCP user)
is congestioned?

When you think that SCON is not needed for SUA, how can you replace this
functionnality?

Francois,

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]=20
Sent: Monday, January 19, 2004 11:21 AM
To: Zannin, Francois
Cc: Tolga Asveren; sigtran@ietf.org
Subject: Re: [Sigtran] SUA v14 doubt in SCON


Francois,

SUA does not support this (nor does it need to).  We only put it in M3UA
for so-called "nodal" congestion, and it has questionable utility there.

--brian

Zannin, Francois wrote:
(Mon, 19 Jan 2004 10:08:58)
> Hi,
>=20
> In the SUA network, I was wondering what could be the message send by=20
> an ASP congested for one (and only one) of it's hosted AS.
>=20
> The SCON sent by an ASP to the originator of the message (like # ss7=20
> TFC or SSC) could be a solution, But this SCON do not include any=20
> affected PC like in M3UA.
>=20
> When an ASP receive a message for a congested AS, it can return a=20
> congestion indication to the originator of the message (Ref: Q714=20
> 5.2.7.1). Then, the ASP sends a SCON to the SG for the "originator of=20
> the message". But with no concerned PC in the SCON, the SG cannot=20
> identify the addressee of the SCON.
>=20
> If we are handling the congestion in "International mode", no=20
> congestion state must be kept in the message path, so the SG do not=20
> need any processing other then forwarding the SCON as a TFC.
>=20
> Could we add a concerned DPC in the SCON as it exist in the M3UA SCON?
>=20
> Francois,
>=20
>=20
> -----Original Message-----
> From: Tolga Asveren [mailto:tolga.asveren@ss8.com]
> Sent: Friday, September 13, 2002 5:58 PM
> To: sigtran@ietf.org
> Subject: RE: [Sigtran] SUA v14 doubt in SCON
>=20
>=20
> Brian,
>=20
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Friday, September 13, 2002 11:10 AM
> > To: ygahlaut@hss.hns.com
> > Cc: john.loughney@nokia.com; tolga.asveren@ss8.com; sigtran@ietf.org
> > Subject: Re: [Sigtran] SUA v14 doubt in SCON
> >
> >
> > Yogesh,
> >
> > SCON is used to indicate SS7 network congestion only.  It is not
> > useful in the IPSP case.  In the IPSP case, IETF mechanisms are more

> > applicable: such as ECN.
> [TOLGA] For SUA-IPSP case, aren't we allowed to use SCON to inform the

> peer about local subsystem congestion? Because there is no 1:1:1=20
> relationship between AS,SCTP associations and an IP address, I=20
> wouldn't think ECN or SCTP congestion mechanisms can do, what SCON is=20
> intended to do.
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org https://www1.ietf.org/mailman/listinfo/sigtran
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Mon Jan 19 05:55:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11785
	for <sigtran-archive@odin.ietf.org>; Mon, 19 Jan 2004 05:55:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiX3f-0002Js-ER
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 05:55:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0JAt3lp008899
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 05:55:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiX3e-0002JN-IM; Mon, 19 Jan 2004 05:55:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiX3D-0002I8-6E
	for sigtran@optimus.ietf.org; Mon, 19 Jan 2004 05:54:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11755
	for <sigtran@ietf.org>; Mon, 19 Jan 2004 05:54:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiX39-0003iA-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 05:54:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiX2G-0003fA-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 05:53:37 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[8dUxCtoxJ5ZENPTGBwVeOxxK5ccmCWOt])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiX1x-0003cB-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 05:53:17 -0500
Received: from ns.pigworks.openss7.net (IDENT:zGLqeCDfKDY4yyoP/fIuUV4XKbhLM9mF@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0JArII16246;
	Mon, 19 Jan 2004 03:53:18 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0JArHH10931;
	Mon, 19 Jan 2004 03:53:17 -0700
Date: Mon, 19 Jan 2004 03:53:17 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Zannin, Francois" <francois.zannin@hp.com>
Cc: Tolga Asveren <tolga.asveren@ss8.com>, sigtran@ietf.org
Subject: Re: [Sigtran] SUA v14 doubt in SCON
Message-ID: <20040119035317.A10882@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Zannin, Francois" <francois.zannin@hp.com>,
	Tolga Asveren <tolga.asveren@ss8.com>, sigtran@ietf.org
References: <06CAA4D3753C53408D2CE6340B6844420348FF55@vbeexc02.emea.cpqcorp.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: <06CAA4D3753C53408D2CE6340B6844420348FF55@vbeexc02.emea.cpqcorp.net>; from francois.zannin@hp.com on Mon, Jan 19, 2004 at 11:34:49AM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Francois,

I did not say that SCON was not needed for SUA.  Concerned destination
is not needed.  When an SCCP user (subsystem) becomes congested, it SCCP
management signals same to the SCCP with the N-STATE request primitive.
This is the SCON message from ASP to SG.

What it does not require is a concerned destination.  N-STATE request
primitives and SUA SCON do only contain the affected node.  It is SCCP's
responsibility to send SSC every Pth message and only in response to the
necessary messages.  SCCP messages that encounter congestion are not
delivered to the SCCP user.

This is, in fact, also the situation for M3UA, and the SG is permitted to
ignore SCON sent from ASP to SG, and is permitted to also ignore the
concerned destination in the SCON send from ASP to SG.  That is why the
field (and message from ASP to SG) is of questionable utility in M3UA.

Do you understand now?

--brian


Zannin, Francois wrote:                                                            (Mon, 19 Jan 2004 11:34:49)
> Brian,
> 
> When a SUA End point is connected to two or more SG and the ASP is
> congestionned for only one AS served by the ASP (this case exist), how
> can the ASP inform the originator of the message that the AS (SCCP user)
> is congestioned?
> 
> When you think that SCON is not needed for SUA, how can you replace this
> functionnality?
> 
> Francois,
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org] 
> Sent: Monday, January 19, 2004 11:21 AM
> To: Zannin, Francois
> Cc: Tolga Asveren; sigtran@ietf.org
> Subject: Re: [Sigtran] SUA v14 doubt in SCON
> 
> 
> Francois,
> 
> SUA does not support this (nor does it need to).  We only put it in M3UA
> for so-called "nodal" congestion, and it has questionable utility there.
> 
> --brian
> 
> Zannin, Francois wrote:
> (Mon, 19 Jan 2004 10:08:58)
> > Hi,
> > 
> > In the SUA network, I was wondering what could be the message send by 
> > an ASP congested for one (and only one) of it's hosted AS.
> > 
> > The SCON sent by an ASP to the originator of the message (like # ss7 
> > TFC or SSC) could be a solution, But this SCON do not include any 
> > affected PC like in M3UA.
> > 
> > When an ASP receive a message for a congested AS, it can return a 
> > congestion indication to the originator of the message (Ref: Q714 
> > 5.2.7.1). Then, the ASP sends a SCON to the SG for the "originator of 
> > the message". But with no concerned PC in the SCON, the SG cannot 
> > identify the addressee of the SCON.
> > 
> > If we are handling the congestion in "International mode", no 
> > congestion state must be kept in the message path, so the SG do not 
> > need any processing other then forwarding the SCON as a TFC.
> > 
> > Could we add a concerned DPC in the SCON as it exist in the M3UA SCON?
> > 
> > Francois,
> > 
> > 
> > -----Original Message-----
> > From: Tolga Asveren [mailto:tolga.asveren@ss8.com]
> > Sent: Friday, September 13, 2002 5:58 PM
> > To: sigtran@ietf.org
> > Subject: RE: [Sigtran] SUA v14 doubt in SCON
> > 
> > 
> > Brian,
> > 
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: Friday, September 13, 2002 11:10 AM
> > > To: ygahlaut@hss.hns.com
> > > Cc: john.loughney@nokia.com; tolga.asveren@ss8.com; sigtran@ietf.org
> > > Subject: Re: [Sigtran] SUA v14 doubt in SCON
> > >
> > >
> > > Yogesh,
> > >
> > > SCON is used to indicate SS7 network congestion only.  It is not
> > > useful in the IPSP case.  In the IPSP case, IETF mechanisms are more
> 
> > > applicable: such as ECN.
> > [TOLGA] For SUA-IPSP case, aren't we allowed to use SCON to inform the
> 
> > peer about local subsystem congestion? Because there is no 1:1:1 
> > relationship between AS,SCTP associations and an IP address, I 
> > wouldn't think ECN or SCTP congestion mechanisms can do, what SCON is 
> > intended to do.
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/

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

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



From exim@www1.ietf.org  Mon Jan 19 09:48:35 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18690
	for <sigtran-archive@odin.ietf.org>; Mon, 19 Jan 2004 09:48:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiahD-0007n9-Dq
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 09:48:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0JEm7Yc029945
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 09:48:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aiah7-0007mm-VV; Mon, 19 Jan 2004 09:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiagC-0007kY-L6
	for sigtran@optimus.ietf.org; Mon, 19 Jan 2004 09:47:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18513
	for <sigtran@ietf.org>; Mon, 19 Jan 2004 09:47:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiagA-0000xE-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 09:47:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiafF-0000nm-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 09:46:06 -0500
Received: from zdemail03.zdem.compaq.com ([161.114.112.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiaeC-0000Xk-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 09:45:00 -0500
Received: from demexg11.emea.cpqcorp.net (demexg11.emea.cpqcorp.net [16.41.86.63])
	by zdemail03.zdem.compaq.com (Postfix) with ESMTP
	id 1AD74125A; Mon, 19 Jan 2004 15:44:26 +0100 (CET)
Received: from vbeexc02.emea.cpqcorp.net ([16.188.146.229]) by demexg11.emea.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.6673);
	 Mon, 19 Jan 2004 15:44:26 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sigtran] SUA v14 doubt in SCON
Date: Mon, 19 Jan 2004 15:44:23 +0100
Message-ID: <06CAA4D3753C53408D2CE6340B6844420348FF58@vbeexc02.emea.cpqcorp.net>
Thread-Topic: [Sigtran] SUA v14 doubt in SCON
Thread-Index: AcPeepVo09jggmqoRDODAQs1Pn4/ewAIB3UQ
From: "Zannin, Francois" <francois.zannin@hp.com>
To: <bidulock@openss7.org>
Cc: <sigtran@ietf.org>
X-OriginalArrivalTime: 19 Jan 2004 14:44:26.0252 (UTC) FILETIME=[BC54F4C0:01C3DE9A]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Brian,

Your view of the problem is that all SG connected to ASP must locally
handle the congestion for national and international mode.

For national Congestion with level, the good approach is to handle the
congestion action (messages discard, TFC) in the SG in order to minimize
useless traffic (because discarded) on the IP network. Then, the ASP
notify all the SG(p) of it's current congestion level per AS. A timer
procedure can be used on the SG in addition to the last SCON received.

But for international congestion with no systematic discard, isn't the
relay of the SCON enough to inform the originator of the message of the
congestion of the AS. There is no need to keep the congestion in the SG!


=20

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]=20
Sent: Monday, January 19, 2004 11:53 AM
To: Zannin, Francois
Cc: Tolga Asveren; sigtran@ietf.org
Subject: Re: [Sigtran] SUA v14 doubt in SCON


Francois,

I did not say that SCON was not needed for SUA.  Concerned destination
is not needed.  When an SCCP user (subsystem) becomes congested, it SCCP
management signals same to the SCCP with the N-STATE request primitive.
This is the SCON message from ASP to SG.

What it does not require is a concerned destination.  N-STATE request
primitives and SUA SCON do only contain the affected node.  It is SCCP's
responsibility to send SSC every Pth message and only in response to the
necessary messages.  SCCP messages that encounter congestion are not
delivered to the SCCP user.

This is, in fact, also the situation for M3UA, and the SG is permitted
to ignore SCON sent from ASP to SG, and is permitted to also ignore the
concerned destination in the SCON send from ASP to SG.  That is why the
field (and message from ASP to SG) is of questionable utility in M3UA.

Do you understand now?

--brian


Zannin, Francois wrote:
(Mon, 19 Jan 2004 11:34:49)
> Brian,
>=20
> When a SUA End point is connected to two or more SG and the ASP is=20
> congestionned for only one AS served by the ASP (this case exist), how

> can the ASP inform the originator of the message that the AS (SCCP=20
> user) is congestioned?
>=20
> When you think that SCON is not needed for SUA, how can you replace=20
> this functionnality?
>=20
> Francois,
>=20
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Monday, January 19, 2004 11:21 AM
> To: Zannin, Francois
> Cc: Tolga Asveren; sigtran@ietf.org
> Subject: Re: [Sigtran] SUA v14 doubt in SCON
>=20
>=20
> Francois,
>=20
> SUA does not support this (nor does it need to).  We only put it in=20
> M3UA for so-called "nodal" congestion, and it has questionable utility

> there.
>=20
> --brian
>=20
> Zannin, Francois wrote:
> (Mon, 19 Jan 2004 10:08:58)
> > Hi,
> >=20
> > In the SUA network, I was wondering what could be the message send=20
> > by
> > an ASP congested for one (and only one) of it's hosted AS.
> >=20
> > The SCON sent by an ASP to the originator of the message (like # ss7
> > TFC or SSC) could be a solution, But this SCON do not include any=20
> > affected PC like in M3UA.
> >=20
> > When an ASP receive a message for a congested AS, it can return a
> > congestion indication to the originator of the message (Ref: Q714=20
> > 5.2.7.1). Then, the ASP sends a SCON to the SG for the "originator
of=20
> > the message". But with no concerned PC in the SCON, the SG cannot=20
> > identify the addressee of the SCON.
> >=20
> > If we are handling the congestion in "International mode", no
> > congestion state must be kept in the message path, so the SG do not=20
> > need any processing other then forwarding the SCON as a TFC.
> >=20
> > Could we add a concerned DPC in the SCON as it exist in the M3UA=20
> > SCON?
> >=20
> > Francois,
> >=20
> >=20
> > -----Original Message-----
> > From: Tolga Asveren [mailto:tolga.asveren@ss8.com]
> > Sent: Friday, September 13, 2002 5:58 PM
> > To: sigtran@ietf.org
> > Subject: RE: [Sigtran] SUA v14 doubt in SCON
> >=20
> >=20
> > Brian,
> >=20
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: Friday, September 13, 2002 11:10 AM
> > > To: ygahlaut@hss.hns.com
> > > Cc: john.loughney@nokia.com; tolga.asveren@ss8.com;=20
> > > sigtran@ietf.org
> > > Subject: Re: [Sigtran] SUA v14 doubt in SCON
> > >
> > >
> > > Yogesh,
> > >
> > > SCON is used to indicate SS7 network congestion only.  It is not=20
> > > useful in the IPSP case.  In the IPSP case, IETF mechanisms are=20
> > > more
>=20
> > > applicable: such as ECN.
> > [TOLGA] For SUA-IPSP case, aren't we allowed to use SCON to inform=20
> > the
>=20
> > peer about local subsystem congestion? Because there is no 1:1:1
> > relationship between AS,SCTP associations and an IP address, I=20
> > wouldn't think ECN or SCTP congestion mechanisms can do, what SCON
is=20
> > intended to do.
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org https://www1.ietf.org/mailman/listinfo/sigtran
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org https://www1.ietf.org/mailman/listinfo/sigtran
>=20
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/

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

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



From exim@www1.ietf.org  Mon Jan 19 11:07:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23504
	for <sigtran-archive@odin.ietf.org>; Mon, 19 Jan 2004 11:07:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aibvc-0001fX-9A
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 11:07:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0JG74e1006396
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 11:07:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AibvY-0001da-O5; Mon, 19 Jan 2004 11:07:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aibuh-0001bT-LX
	for sigtran@optimus.ietf.org; Mon, 19 Jan 2004 11:06:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23473
	for <sigtran@ietf.org>; Mon, 19 Jan 2004 11:05:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AibuV-0006En-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 11:05:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AibrO-00069Z-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 11:02:43 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aibr3-000677-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 11:02:21 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i0JG1skH002022
	for <sigtran@ietf.org>; Mon, 19 Jan 2004 11:01:55 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Mon, 19 Jan 2004 11:03:23 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOKENFCDAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <20040116142548.A20344@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by slink5.mtl-nj.adax id i0JG1skH002022
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,EXCUSE_16 autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Brian,

ASP3 will not be able to register 5-5-5(*). The SGP will return the
following error code, as described in Javier's new text:

If the SGP determines that the requested RK partially, but not
exactly, matches an existing RK, and that an
incoming signalling message received at an SGP could possibly match
both the requested and the existing RK, the SGP returns a
Registration Response message to the ASP, with a Registration
Status of "Error - "Cannot Support Unique Routing. An incoming
signalling message received at an SGP should not match against more
than one Routing Key.

Barry Nagelberg

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Friday, January 16, 2004 4:26 PM
> To: Barry Nagelberg
> Cc: SIGTRAN Mailing List
> Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
>
>
> Barry,
>
> There is a 1:1 correspondence; they are:
>
>   5-5-5(ISUP) RC1
>   5-5-5(SCCP) RC2
>   5-5-5(*)    RC3
>
> --brian
>
> Barry Nagelberg wrote:
>                    (Fri, 16 Jan 2004 09:38:03)
> > Brian,
> >
> > I don't think that this configuration would be clear at all to
> the SGP. In
> > fact, it is impossible to implement this configuration using an SGP t=
hat
> > complies with the RFC!
> >
> > At both the SGP and the ASP, there must be a 1:1 correspondence
> between a
> > Routing Key and a Routing Context (please see Section 1.2 of
> the RFC). So if
> > ASP3 tries to register 2 different routing keys, 5-5-5(SCCP) and
> > 5-5-5(ISUP), the SGP will return 2 different routing context values. =
You
> > will never get RC3 for both routing keys at ASP3!
> >
> > Barry Nagelberg
> >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > Brian F. G. Bidulock
> > > Sent: Friday, January 16, 2004 1:19 AM
> > > To: kakaul@hss.hns.com
> > > Cc: SIGTRAN Mailing List
> > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > kakaul,
> > >
> > > As far as ASP3 is concerned it is one AS.  It activates it
> > > by sending ASPAC(RC3).  To the SG it is clear what traffic
> > > is activated: 5-5-5(*), and it responds ASPAC Ack(RC3).
> > >
> > > --brian
> > >
> > > kakaul@hss.hns.com wrote:
> > >                   (Fri, 16 Jan 2004 10:56:35)
> > > >
> > > >
> > > >
> > > >
> > > > Brian,
> > > >
> > > >    How can ASP3 have same RC3 for two different AS's (5-5-5(ISUP)=
,
> > > > 5-5-5(SCCP)) registered with same SGP.How will ASP3 activate
> > > the two AS's.
> > > >
> > > > Kamesh Kaul
> > > > www.hssworld.com
> > > > Hughes Software Systems
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > "Brian F. G. Bidulock" <bidulock@openss7.org> on 01/15/2004
> 08:31:30 PM
> > > >
> > > > Please respond to bidulock@openss7.org
> > > >
> > > > To:    Kamesh Kaul/HSS@HSS
> > > > cc:    SIGTRAN Mailing List <sigtran@ietf.org>
> > > >
> > > > Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > kakaul,
> > > >
> > > > In the example:
> > > >
> > > >             RK          ASP1   ASP2   ASP3
> > > >  -----------     ----   ----   ----
> > > >  5-5-5(ISUP)      RC1   -     RC3
> > > >  5-5-5(SCCP)       -     RC2    RC3
> > > >
> > > > Is that so difficult?
> > > >
> > > > --brian
> > > >
> > > > kakaul@hss.hns.com wrote:
> > > > (Thu, 15 Jan 2004 19:17:06)
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > I totally agree with Javier that there should be unique
> > > routing per AS's
> > > > ,
> > > > > AS's must not overlap.
> > > > > I am not able to understand how SG can handle overlapped AS's
> > > registered
> > > > by
> > > > > different ASP's,
> > > > > Brian can you explain it a little bit more.
> > > > >
> > > > > I think SG should not be confused in selecting actual AS
> if AS's are
> > > > > overlapped because first
> > > > > thing what SG does is selecting of AS for given traffic
> > > received without
> > > > > having any clue of ASP's.
> > > > >
> > > > > Kamesh Kaul
> > > > > www.hssworld.com
> > > > > Hughes Software Systems
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ---------------------- Forwarded by Kamesh Kaul/HSS on
> > > 01/15/2004 07:04
> > > > PM
> > > > > ---------------------------
> > > > >
> > > > >
> > > > > "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on
> 01/15/2004
> > > > > 05:44:34 PM
> > > > >
> > > > > Please respond to bidulock@openss7.org
> > > > >
> > > > > Sent by:    sigtran-admin@ietf.org
> > > > >
> > > > >
> > > > > To:    "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com=
>
> > > > > cc:    "'Barry Nagelberg'" <barryn@adax.com>, SIGTRAN Mailing L=
ist
> > > > >        <sigtran@ietf.org>
> > > > >
> > > > > Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > J.Javier,
> > > > >
> > > > > Where does it say ASes must not overlap?  This is precisely
> > > > > one of the example cases we used for IPSP discussions.
> > > > > I certainly don't see where retricting this is necessary
> > > > > for proper interworking or to protect the network.
> > > > >
> > > > > The only problem case we had for "Unique Routing" was were
> > > > > two RC's exist for the same traffic for the same ASP.  It is
> > > > > then abivalent which RC the SG is to assign to the traffic.
> > > > >
> > > > > In this example case, it is clear which RC value is to be
> > > > > assigned to each message for each ASP.  There is no problem
> > > > > of "Unique Routing".
> > > > >
> > > > > The problem of "Unique Routing" exists where one attempt to
> > > > > configure or register overlapping RKs for the same ASP.  So
> > > > > if ASP4 tries to register for 5-5-5(ISUP) and 5-5-5(*) there
> > > > > is a problem of unique routing.  To which RC is ISUP traffic
> > > > > to go?
> > > > >
> > > > > For the case of different ASPs, the SG can choose to support
> > > > > it, if capable, or refuse it if not.  The IG need not attempt
> > > > > to dictate a restriction to SG capabilities in this regard.
> > > > >
> > > > > --brian
> > > > >
> > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > (Thu, 15 Jan 2004 12:11:40)
> > > > > > Brian,
> > > > > >
> > > > > > Why don't you take the following approach...
> > > > > >
> > > > > > Define two different ASes:
> > > > > > - AS1 -> 5-5-5 (ISUP)
> > > > > > - AS2 -> 5-5-5 (SCCP)
> > > > > >
> > > > > > ASP1 registers within AS1
> > > > > > ASP2 registers within AS2
> > > > > > ASP3 registers within both AS1 and AS2
> > > > > >
> > > > > > It is important to keep one unique routing per AS. ASes MUST =
not
> > > > overlap.
> > > > > >
> > > > > > Cheers // Javier.
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > > > >
> > > > > > >
> > > > > > > J.Javier,
> > > > > > >
> > > > > > > Just to clarify, there should be nothing stopping an
> > > > > > > implementation from
> > > > > > > allowing ASP1 to register for, say, 5-5-5 (ISUP),
> ASP2 to register
> > > > for
> > > > > > > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> > > > > > >
> > > > > > > In this case, although ASP3 registers after ASP1 and ASP2,
> > > > > > > there is nothing
> > > > > > > stopping an SG from assigining a RK and RC to
> 5-5-5(*) for ASP3.
> > > > > > >
> > > > > > > An SG implementation could choose to refuse 5-5-5(*) and
> > > require ASP3
> > > > > > > to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or =
it
> > > > > > > might not.
> > > > > > > I don't think it is the RFC's place to require one or the
> > > other.  So,
> > > > > > > for in the case where there is an overlap between
> > > "different" APSs,
> > > > it
> > > > > > > should be left up to the SG implementation as it is now.
> > > > > > >
> > > > > > > Your additional text below, now clarifies that.  Thank you.
> > > > > > >
> > > > > > > --brian
> > > > > > >
> > > > > > >
> > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > >                     (Wed, 14 Jan 2004 15:30:10)
> > > > > > > > Barry,
> > > > > > > >
> > > > > > > > You are right. And that is valid only for the overlapping
> > > > > > > case. You can not create a new AS whose associated RK
> > > > > > > overlaps another existing registered RK. In the duplicate
> > > > > > > case it is already included that the check is against the R=
K
> > > > > > > previosly registered by the sending ASP. The latter makes
> > > > > > > sense but not the former.
> > > > > > > >
> > > > > > > > Go back to my first proposal.
> > > > > > > >
> > > > > > > > Thanks // Javier.
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: sigtran-admin@ietf.org
> > > > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > > > Barry Nagelberg
> > > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > > > > > > To: SIGTRAN Mailing List
> > > > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM
> error codes
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Javier,
> > > > > > > > >
> > > > > > > > > No, Brian's suggestion is not correct, nor is this upda=
ted
> > > > > > > > > text. Routing
> > > > > > > > > keys are independent of ASPs or associations. I think
> > > > > > > perhaps Brian is
> > > > > > > > > thinking of the routing context, which may be unique fo=
r
> > > > > > > each ASP or
> > > > > > > > > association.
> > > > > > > > >
> > > > > > > > > Barry Nagelberg
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: sigtran-admin@ietf.org
> > > > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > > > > J.Javier Pastor (ML/EEM)
> > > > > > > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > > > > > > To: 'bidulock@openss7.org'
> > > > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM
> error codes
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Brian,
> > > > > > > > > >
> > > > > > > > > > Tell me if the following is OK.
> > > > > > > > > >
> > > > > > > > > > If the SGP determines that the requested RK
> partially, but
> > > > > > > > > not exactly,
> > > > > > > > > > matches an existing RK already registered for the
> > > > > > > sender ASP, and
> > > > > > > > > > that an incoming signalling message received at
> > > > > > > > > > an SGP could possibly match both the requested and
> > > the existing
> > > > > > > > > > RK, the SGP
> > > > > > > > > > returns a Registration Response message to the
> ASP, with a
> > > > > > > > > Registration
> > > > > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > > > > incoming signalling
> > > > > > > > > > message received at an SGP should not match against m=
ore
> > > > > > > > > than one Routing
> > > > > > > > > > Key.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > THanks // JAvier.
> > > > > > > > > >
> > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > From: Brian F. G. Bidulock
> [mailto:bidulock@openss7.org]
> > > > > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM
> > > error codes
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > J.Javier,
> > > > > > > > > > >
> > > > > > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > > > > > > >
> > > > > > > > > > > --snip--
> > > > > > > > > > > >
> > > > > > > > > > > > --------
> > > > > > > > > > > > New text: (Section 4.4.1)
> > > > > > > > > > > > ---------
> > > > > > > > > > > >
> > > > > > > > > > > > If the SGP determines that the requested RK
> > > partially, but
> > > > > > > > > > > not exactly,
> > > > > > > > > > > > matches an existing RK, and that an
> incoming signalling
> > > > > > > > > > > message received at
> > > > > > > > > > > > an SGP could possibly match both the
> requested and the
> > > > > > > > > > > existing RK, the SGP
> > > > > > > > > > > > returns a Registration Response message to the
> > > ASP, with a
> > > > > > > > > > > Registration
> > > > > > > > > > > > Status of "Error - "Cannot Support Unique
> Routing. An
> > > > > > > > > > > incoming signalling
> > > > > > > > > > > > message received at an SGP should not match
> against more
> > > > > > > > > > > than one Routing
> > > > > > > > > > > > Key.
> > > > > > > > > > > >
> > > > > > > > > > > --snip--
> > > > > > > > > > >
> > > > > > > > > > > I think you mean for a given ASP (Association) in t=
he
> > > > > > > > > above.  Correct?
> > > > > > > > > > >
> > > > > > > > > > > It should be mentioned that the "matching" of
> RKs is done
> > > > > > > > > > > only against other
> > > > > > > > > > > RKs belonging to the same ASP (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
> > > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > 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 is proprietary to Hughes
> Software Systems
> > > > Limited
> > > > > (HSS) and is intended solely for the use of the individual to
> > > whom it is
> > > > > addressed. It may contain  privileged or confidential
> information and
> > > > > should not be circulated or used for any purpose other than
> > > for what it
> > > > is
> > > > > intended. If you have received this message in error, please
> > > notify the
> > > > > originator immediately. If you are not the intended
> recipient, you are
> > > > > notified that you are strictly prohibited from using,
> > > copying, altering,
> > > > or
> > > > > disclosing the contents of this message. HSS accepts no
> responsibility
> > > > for
> > > > > loss or damage arising from the use of the information
> transmitted by
> > > > this
> > > > > email including damage from virus."
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >
> > > > --
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > >  http://www.openss7.org/
> > > >
> > > >
> > > >
> > > >
> > >
> > > --
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


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



From exim@www1.ietf.org  Mon Jan 19 15:33:33 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07684
	for <sigtran-archive@odin.ietf.org>; Mon, 19 Jan 2004 15:33:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aig53-00005a-6q
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 15:33:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0JKX5E1000336
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 15:33:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aig4z-000057-Go; Mon, 19 Jan 2004 15:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aig4p-0008WA-1I
	for sigtran@optimus.ietf.org; Mon, 19 Jan 2004 15:32:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07672
	for <sigtran@ietf.org>; Mon, 19 Jan 2004 15:32:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aig4n-0003MD-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 15:32:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aig3s-0003J1-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 15:31:53 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[XMkFAHZ9eJqPsd7pYO/CRLvBmhoEqo2F])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aig33-0003G3-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 15:31:02 -0500
Received: from ns.pigworks.openss7.net (IDENT:wBlBdkHkxVWb0/XE9cnoW8xE2q0kRmf/@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0JKUwI28383;
	Mon, 19 Jan 2004 13:30:59 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0JKUw319080;
	Mon, 19 Jan 2004 13:30:58 -0700
Date: Mon, 19 Jan 2004 13:30:58 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry Nagelberg <barryn@adax.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
Message-ID: <20040119133057.A18788@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry Nagelberg <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <20040116142548.A20344@openss7.org> <JBECLENKLBCKAAKFGAJOKENFCDAA.barryn@adax.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <JBECLENKLBCKAAKFGAJOKENFCDAA.barryn@adax.com>; from barryn@adax.com on Mon, Jan 19, 2004 at 11:03:23AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i0JKUwI28383
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,EXCUSE_16 autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Barry,

Javier's new text needs to be changed to allow what
was already allowed by the RFC.

--brian

Barry Nagelberg wrote:                                                   =
            (Mon, 19 Jan 2004 11:03:23)
> Brian,
>=20
> ASP3 will not be able to register 5-5-5(*). The SGP will return the
> following error code, as described in Javier's new text:
>=20
> If the SGP determines that the requested RK partially, but not
> exactly, matches an existing RK, and that an
> incoming signalling message received at an SGP could possibly match
> both the requested and the existing RK, the SGP returns a
> Registration Response message to the ASP, with a Registration
> Status of "Error - "Cannot Support Unique Routing. An incoming
> signalling message received at an SGP should not match against more
> than one Routing Key.
>=20
> Barry Nagelberg
>=20
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Friday, January 16, 2004 4:26 PM
> > To: Barry Nagelberg
> > Cc: SIGTRAN Mailing List
> > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > Barry,
> >
> > There is a 1:1 correspondence; they are:
> >
> >   5-5-5(ISUP) RC1
> >   5-5-5(SCCP) RC2
> >   5-5-5(*)    RC3
> >
> > --brian
> >
> > Barry Nagelberg wrote:
> >                    (Fri, 16 Jan 2004 09:38:03)
> > > Brian,
> > >
> > > I don't think that this configuration would be clear at all to
> > the SGP. In
> > > fact, it is impossible to implement this configuration using an SGP=
 that
> > > complies with the RFC!
> > >
> > > At both the SGP and the ASP, there must be a 1:1 correspondence
> > between a
> > > Routing Key and a Routing Context (please see Section 1.2 of
> > the RFC). So if
> > > ASP3 tries to register 2 different routing keys, 5-5-5(SCCP) and
> > > 5-5-5(ISUP), the SGP will return 2 different routing context values=
. You
> > > will never get RC3 for both routing keys at ASP3!
> > >
> > > Barry Nagelberg
> > >
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > Brian F. G. Bidulock
> > > > Sent: Friday, January 16, 2004 1:19 AM
> > > > To: kakaul@hss.hns.com
> > > > Cc: SIGTRAN Mailing List
> > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > kakaul,
> > > >
> > > > As far as ASP3 is concerned it is one AS.  It activates it
> > > > by sending ASPAC(RC3).  To the SG it is clear what traffic
> > > > is activated: 5-5-5(*), and it responds ASPAC Ack(RC3).
> > > >
> > > > --brian
> > > >
> > > > kakaul@hss.hns.com wrote:
> > > >                   (Fri, 16 Jan 2004 10:56:35)
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Brian,
> > > > >
> > > > >    How can ASP3 have same RC3 for two different AS's (5-5-5(ISU=
P),
> > > > > 5-5-5(SCCP)) registered with same SGP.How will ASP3 activate
> > > > the two AS's.
> > > > >
> > > > > Kamesh Kaul
> > > > > www.hssworld.com
> > > > > Hughes Software Systems
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "Brian F. G. Bidulock" <bidulock@openss7.org> on 01/15/2004
> > 08:31:30 PM
> > > > >
> > > > > Please respond to bidulock@openss7.org
> > > > >
> > > > > To:    Kamesh Kaul/HSS@HSS
> > > > > cc:    SIGTRAN Mailing List <sigtran@ietf.org>
> > > > >
> > > > > Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > kakaul,
> > > > >
> > > > > In the example:
> > > > >
> > > > >             RK          ASP1   ASP2   ASP3
> > > > >  -----------     ----   ----   ----
> > > > >  5-5-5(ISUP)      RC1   -     RC3
> > > > >  5-5-5(SCCP)       -     RC2    RC3
> > > > >
> > > > > Is that so difficult?
> > > > >
> > > > > --brian
> > > > >
> > > > > kakaul@hss.hns.com wrote:
> > > > > (Thu, 15 Jan 2004 19:17:06)
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I totally agree with Javier that there should be unique
> > > > routing per AS's
> > > > > ,
> > > > > > AS's must not overlap.
> > > > > > I am not able to understand how SG can handle overlapped AS's
> > > > registered
> > > > > by
> > > > > > different ASP's,
> > > > > > Brian can you explain it a little bit more.
> > > > > >
> > > > > > I think SG should not be confused in selecting actual AS
> > if AS's are
> > > > > > overlapped because first
> > > > > > thing what SG does is selecting of AS for given traffic
> > > > received without
> > > > > > having any clue of ASP's.
> > > > > >
> > > > > > Kamesh Kaul
> > > > > > www.hssworld.com
> > > > > > Hughes Software Systems
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ---------------------- Forwarded by Kamesh Kaul/HSS on
> > > > 01/15/2004 07:04
> > > > > PM
> > > > > > ---------------------------
> > > > > >
> > > > > >
> > > > > > "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on
> > 01/15/2004
> > > > > > 05:44:34 PM
> > > > > >
> > > > > > Please respond to bidulock@openss7.org
> > > > > >
> > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > >
> > > > > >
> > > > > > To:    "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.c=
om>
> > > > > > cc:    "'Barry Nagelberg'" <barryn@adax.com>, SIGTRAN Mailing=
 List
> > > > > >        <sigtran@ietf.org>
> > > > > >
> > > > > > Subject:    Re: [Sigtran] M3UA: More redundant RKM error code=
s
> > > > > >
> > > > > >
> > > > > > J.Javier,
> > > > > >
> > > > > > Where does it say ASes must not overlap?  This is precisely
> > > > > > one of the example cases we used for IPSP discussions.
> > > > > > I certainly don't see where retricting this is necessary
> > > > > > for proper interworking or to protect the network.
> > > > > >
> > > > > > The only problem case we had for "Unique Routing" was were
> > > > > > two RC's exist for the same traffic for the same ASP.  It is
> > > > > > then abivalent which RC the SG is to assign to the traffic.
> > > > > >
> > > > > > In this example case, it is clear which RC value is to be
> > > > > > assigned to each message for each ASP.  There is no problem
> > > > > > of "Unique Routing".
> > > > > >
> > > > > > The problem of "Unique Routing" exists where one attempt to
> > > > > > configure or register overlapping RKs for the same ASP.  So
> > > > > > if ASP4 tries to register for 5-5-5(ISUP) and 5-5-5(*) there
> > > > > > is a problem of unique routing.  To which RC is ISUP traffic
> > > > > > to go?
> > > > > >
> > > > > > For the case of different ASPs, the SG can choose to support
> > > > > > it, if capable, or refuse it if not.  The IG need not attempt
> > > > > > to dictate a restriction to SG capabilities in this regard.
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > (Thu, 15 Jan 2004 12:11:40)
> > > > > > > Brian,
> > > > > > >
> > > > > > > Why don't you take the following approach...
> > > > > > >
> > > > > > > Define two different ASes:
> > > > > > > - AS1 -> 5-5-5 (ISUP)
> > > > > > > - AS2 -> 5-5-5 (SCCP)
> > > > > > >
> > > > > > > ASP1 registers within AS1
> > > > > > > ASP2 registers within AS2
> > > > > > > ASP3 registers within both AS1 and AS2
> > > > > > >
> > > > > > > It is important to keep one unique routing per AS. ASes MUS=
T not
> > > > > overlap.
> > > > > > >
> > > > > > > Cheers // Javier.
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error cod=
es
> > > > > > > >
> > > > > > > >
> > > > > > > > J.Javier,
> > > > > > > >
> > > > > > > > Just to clarify, there should be nothing stopping an
> > > > > > > > implementation from
> > > > > > > > allowing ASP1 to register for, say, 5-5-5 (ISUP),
> > ASP2 to register
> > > > > for
> > > > > > > > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> > > > > > > >
> > > > > > > > In this case, although ASP3 registers after ASP1 and ASP2=
,
> > > > > > > > there is nothing
> > > > > > > > stopping an SG from assigining a RK and RC to
> > 5-5-5(*) for ASP3.
> > > > > > > >
> > > > > > > > An SG implementation could choose to refuse 5-5-5(*) and
> > > > require ASP3
> > > > > > > > to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), o=
r it
> > > > > > > > might not.
> > > > > > > > I don't think it is the RFC's place to require one or the
> > > > other.  So,
> > > > > > > > for in the case where there is an overlap between
> > > > "different" APSs,
> > > > > it
> > > > > > > > should be left up to the SG implementation as it is now.
> > > > > > > >
> > > > > > > > Your additional text below, now clarifies that.  Thank yo=
u.
> > > > > > > >
> > > > > > > > --brian
> > > > > > > >
> > > > > > > >
> > > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > > >                     (Wed, 14 Jan 2004 15:30:10)
> > > > > > > > > Barry,
> > > > > > > > >
> > > > > > > > > You are right. And that is valid only for the overlappi=
ng
> > > > > > > > case. You can not create a new AS whose associated RK
> > > > > > > > overlaps another existing registered RK. In the duplicate
> > > > > > > > case it is already included that the check is against the=
 RK
> > > > > > > > previosly registered by the sending ASP. The latter makes
> > > > > > > > sense but not the former.
> > > > > > > > >
> > > > > > > > > Go back to my first proposal.
> > > > > > > > >
> > > > > > > > > Thanks // Javier.
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: sigtran-admin@ietf.org
> > > > > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > > > > Barry Nagelberg
> > > > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > > > > > > > To: SIGTRAN Mailing List
> > > > > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM
> > error codes
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Javier,
> > > > > > > > > >
> > > > > > > > > > No, Brian's suggestion is not correct, nor is this up=
dated
> > > > > > > > > > text. Routing
> > > > > > > > > > keys are independent of ASPs or associations. I think
> > > > > > > > perhaps Brian is
> > > > > > > > > > thinking of the routing context, which may be unique =
for
> > > > > > > > each ASP or
> > > > > > > > > > association.
> > > > > > > > > >
> > > > > > > > > > Barry Nagelberg
> > > > > > > > > >
> > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > From: sigtran-admin@ietf.org
> > > > > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > > > > > J.Javier Pastor (ML/EEM)
> > > > > > > > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > > > > > > > To: 'bidulock@openss7.org'
> > > > > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM
> > error codes
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Brian,
> > > > > > > > > > >
> > > > > > > > > > > Tell me if the following is OK.
> > > > > > > > > > >
> > > > > > > > > > > If the SGP determines that the requested RK
> > partially, but
> > > > > > > > > > not exactly,
> > > > > > > > > > > matches an existing RK already registered for the
> > > > > > > > sender ASP, and
> > > > > > > > > > > that an incoming signalling message received at
> > > > > > > > > > > an SGP could possibly match both the requested and
> > > > the existing
> > > > > > > > > > > RK, the SGP
> > > > > > > > > > > returns a Registration Response message to the
> > ASP, with a
> > > > > > > > > > Registration
> > > > > > > > > > > Status of "Error - "Cannot Support Unique Routing. =
An
> > > > > > > > > > incoming signalling
> > > > > > > > > > > message received at an SGP should not match against=
 more
> > > > > > > > > > than one Routing
> > > > > > > > > > > Key.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > THanks // JAvier.
> > > > > > > > > > >
> > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > From: Brian F. G. Bidulock
> > [mailto:bidulock@openss7.org]
> > > > > > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM
> > > > error codes
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > J.Javier,
> > > > > > > > > > > >
> > > > > > > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > > > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > > > > > > > >
> > > > > > > > > > > > --snip--
> > > > > > > > > > > > >
> > > > > > > > > > > > > --------
> > > > > > > > > > > > > New text: (Section 4.4.1)
> > > > > > > > > > > > > ---------
> > > > > > > > > > > > >
> > > > > > > > > > > > > If the SGP determines that the requested RK
> > > > partially, but
> > > > > > > > > > > > not exactly,
> > > > > > > > > > > > > matches an existing RK, and that an
> > incoming signalling
> > > > > > > > > > > > message received at
> > > > > > > > > > > > > an SGP could possibly match both the
> > requested and the
> > > > > > > > > > > > existing RK, the SGP
> > > > > > > > > > > > > returns a Registration Response message to the
> > > > ASP, with a
> > > > > > > > > > > > Registration
> > > > > > > > > > > > > Status of "Error - "Cannot Support Unique
> > Routing. An
> > > > > > > > > > > > incoming signalling
> > > > > > > > > > > > > message received at an SGP should not match
> > against more
> > > > > > > > > > > > than one Routing
> > > > > > > > > > > > > Key.
> > > > > > > > > > > > >
> > > > > > > > > > > > --snip--
> > > > > > > > > > > >
> > > > > > > > > > > > I think you mean for a given ASP (Association) in=
 the
> > > > > > > > > > above.  Correct?
> > > > > > > > > > > >
> > > > > > > > > > > > It should be mentioned that the "matching" of
> > RKs is done
> > > > > > > > > > > > only against other
> > > > > > > > > > > > RKs belonging to the same ASP (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
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > _______________________________________________
> > > > > > > > > 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 is proprietary to Hughes
> > Software Systems
> > > > > Limited
> > > > > > (HSS) and is intended solely for the use of the individual to
> > > > whom it is
> > > > > > addressed. It may contain  privileged or confidential
> > information and
> > > > > > should not be circulated or used for any purpose other than
> > > > for what it
> > > > > is
> > > > > > intended. If you have received this message in error, please
> > > > notify the
> > > > > > originator immediately. If you are not the intended
> > recipient, you are
> > > > > > notified that you are strictly prohibited from using,
> > > > copying, altering,
> > > > > or
> > > > > > disclosing the contents of this message. HSS accepts no
> > responsibility
> > > > > for
> > > > > > loss or damage arising from the use of the information
> > transmitted by
> > > > > this
> > > > > > email including damage from virus."
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Sigtran mailing list
> > > > > > Sigtran@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >
> > > > > --
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > >  http://www.openss7.org/
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > 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/
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Mon Jan 19 15:40:33 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07976
	for <sigtran-archive@odin.ietf.org>; Mon, 19 Jan 2004 15:40:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AigBp-0000oe-33
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 15:40:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0JKe4Pe003051
	for sigtran-archive@odin.ietf.org; Mon, 19 Jan 2004 15:40:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AigBm-0000mn-Ji; Mon, 19 Jan 2004 15:40:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AigBW-0000lX-IF
	for sigtran@optimus.ietf.org; Mon, 19 Jan 2004 15:39:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07960
	for <sigtran@ietf.org>; Mon, 19 Jan 2004 15:39:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AigBV-0003rz-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 15:39:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AigAc-0003og-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 15:38:51 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[ar+Qy1FXb7kMgJ9G/9rOOyOWRY3nXqUC])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aig9g-0003kW-00
	for sigtran@ietf.org; Mon, 19 Jan 2004 15:37:52 -0500
Received: from ns.pigworks.openss7.net (IDENT:9GxV4WH19LVW/UNKvm3+NJ8pwGy1m7fT@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0JKbpI28485;
	Mon, 19 Jan 2004 13:37:51 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0JKbos19193;
	Mon, 19 Jan 2004 13:37:50 -0700
Date: Mon, 19 Jan 2004 13:37:50 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Zannin, Francois" <francois.zannin@hp.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] SUA v14 doubt in SCON
Message-ID: <20040119133750.B18788@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Zannin, Francois" <francois.zannin@hp.com>,
	sigtran@ietf.org
References: <06CAA4D3753C53408D2CE6340B6844420348FF58@vbeexc02.emea.cpqcorp.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: <06CAA4D3753C53408D2CE6340B6844420348FF58@vbeexc02.emea.cpqcorp.net>; from francois.zannin@hp.com on Mon, Jan 19, 2004 at 03:44:23PM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Francois,

No.  The single ASP has no knowledge of the congestion of an AS (which
comprises multiple ASP).  The SG and SG alone is responsible for the
status of the SPMC/Subsystem as reflected to the SS7 network.  In both
the national and international mode, messages are discarded/retrned
*before* delivery to the SCCP user (AS).  Therefore, only the SG
determines to which destinations congestion messages are sent.  The ASP
does not even see the message.

I certainliy disagree with making an SUA message mimic a useless M3UA one.

--brian


Zannin, Francois wrote:                                                            (Mon, 19 Jan 2004 15:44:23)
> Brian,
> 
> Your view of the problem is that all SG connected to ASP must locally
> handle the congestion for national and international mode.
> 
> For national Congestion with level, the good approach is to handle the
> congestion action (messages discard, TFC) in the SG in order to minimize
> useless traffic (because discarded) on the IP network. Then, the ASP
> notify all the SG(p) of it's current congestion level per AS. A timer
> procedure can be used on the SG in addition to the last SCON received.
> 
> But for international congestion with no systematic discard, isn't the
> relay of the SCON enough to inform the originator of the message of the
> congestion of the AS. There is no need to keep the congestion in the SG!
> 
> 
>  
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org] 
> Sent: Monday, January 19, 2004 11:53 AM
> To: Zannin, Francois
> Cc: Tolga Asveren; sigtran@ietf.org
> Subject: Re: [Sigtran] SUA v14 doubt in SCON
> 
> 
> Francois,
> 
> I did not say that SCON was not needed for SUA.  Concerned destination
> is not needed.  When an SCCP user (subsystem) becomes congested, it SCCP
> management signals same to the SCCP with the N-STATE request primitive.
> This is the SCON message from ASP to SG.
> 
> What it does not require is a concerned destination.  N-STATE request
> primitives and SUA SCON do only contain the affected node.  It is SCCP's
> responsibility to send SSC every Pth message and only in response to the
> necessary messages.  SCCP messages that encounter congestion are not
> delivered to the SCCP user.
> 
> This is, in fact, also the situation for M3UA, and the SG is permitted
> to ignore SCON sent from ASP to SG, and is permitted to also ignore the
> concerned destination in the SCON send from ASP to SG.  That is why the
> field (and message from ASP to SG) is of questionable utility in M3UA.
> 
> Do you understand now?
> 
> --brian
> 
> 
> Zannin, Francois wrote:
> (Mon, 19 Jan 2004 11:34:49)
> > Brian,
> > 
> > When a SUA End point is connected to two or more SG and the ASP is 
> > congestionned for only one AS served by the ASP (this case exist), how
> 
> > can the ASP inform the originator of the message that the AS (SCCP 
> > user) is congestioned?
> > 
> > When you think that SCON is not needed for SUA, how can you replace 
> > this functionnality?
> > 
> > Francois,
> > 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Monday, January 19, 2004 11:21 AM
> > To: Zannin, Francois
> > Cc: Tolga Asveren; sigtran@ietf.org
> > Subject: Re: [Sigtran] SUA v14 doubt in SCON
> > 
> > 
> > Francois,
> > 
> > SUA does not support this (nor does it need to).  We only put it in 
> > M3UA for so-called "nodal" congestion, and it has questionable utility
> 
> > there.
> > 
> > --brian
> > 
> > Zannin, Francois wrote:
> > (Mon, 19 Jan 2004 10:08:58)
> > > Hi,
> > > 
> > > In the SUA network, I was wondering what could be the message send 
> > > by
> > > an ASP congested for one (and only one) of it's hosted AS.
> > > 
> > > The SCON sent by an ASP to the originator of the message (like # ss7
> > > TFC or SSC) could be a solution, But this SCON do not include any 
> > > affected PC like in M3UA.
> > > 
> > > When an ASP receive a message for a congested AS, it can return a
> > > congestion indication to the originator of the message (Ref: Q714 
> > > 5.2.7.1). Then, the ASP sends a SCON to the SG for the "originator
> of 
> > > the message". But with no concerned PC in the SCON, the SG cannot 
> > > identify the addressee of the SCON.
> > > 
> > > If we are handling the congestion in "International mode", no
> > > congestion state must be kept in the message path, so the SG do not 
> > > need any processing other then forwarding the SCON as a TFC.
> > > 
> > > Could we add a concerned DPC in the SCON as it exist in the M3UA 
> > > SCON?
> > > 
> > > Francois,
> > > 
> > > 
> > > -----Original Message-----
> > > From: Tolga Asveren [mailto:tolga.asveren@ss8.com]
> > > Sent: Friday, September 13, 2002 5:58 PM
> > > To: sigtran@ietf.org
> > > Subject: RE: [Sigtran] SUA v14 doubt in SCON
> > > 
> > > 
> > > Brian,
> > > 
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: Friday, September 13, 2002 11:10 AM
> > > > To: ygahlaut@hss.hns.com
> > > > Cc: john.loughney@nokia.com; tolga.asveren@ss8.com; 
> > > > sigtran@ietf.org
> > > > Subject: Re: [Sigtran] SUA v14 doubt in SCON
> > > >
> > > >
> > > > Yogesh,
> > > >
> > > > SCON is used to indicate SS7 network congestion only.  It is not 
> > > > useful in the IPSP case.  In the IPSP case, IETF mechanisms are 
> > > > more
> > 
> > > > applicable: such as ECN.
> > > [TOLGA] For SUA-IPSP case, aren't we allowed to use SCON to inform 
> > > the
> > 
> > > peer about local subsystem congestion? Because there is no 1:1:1
> > > relationship between AS,SCTP associations and an IP address, I 
> > > wouldn't think ECN or SCTP congestion mechanisms can do, what SCON
> is 
> > > intended to do.
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > --
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/

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

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



From exim@www1.ietf.org  Tue Jan 20 02:35:34 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17304
	for <sigtran-archive@odin.ietf.org>; Tue, 20 Jan 2004 02:35:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiqPi-0000mp-3s
	for sigtran-archive@odin.ietf.org; Tue, 20 Jan 2004 02:35:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0K7Z5Ki003010
	for sigtran-archive@odin.ietf.org; Tue, 20 Jan 2004 02:35:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiqPe-0000m8-GF; Tue, 20 Jan 2004 02:35:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiqPZ-0000lg-JE
	for sigtran@optimus.ietf.org; Tue, 20 Jan 2004 02:34:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17269
	for <sigtran@ietf.org>; Tue, 20 Jan 2004 02:34:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiqPL-0004Is-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 02:34:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiqNU-0004FU-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 02:32:50 -0500
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiqMP-0004Bl-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 02:31:41 -0500
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i0K7Ukwi024417
	for <sigtran@ietf.org>; Tue, 20 Jan 2004 01:30:46 -0600 (CST)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id i0K7UD1C026104
	for <sigtran@ietf.org>; Tue, 20 Jan 2004 01:30:13 -0600 (CST)
Date: Tue, 20 Jan 2004 01:30:13 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
In-Reply-To: <JBECLENKLBCKAAKFGAJOKENFCDAA.barryn@adax.com>
Message-ID: <Pine.SOL.4.10.10401200030460.17587-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,EXCUSE_16 autolearn=no 
	version=2.60
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: QUOTED-PRINTABLE


The intention of ASP3 to register 5-5-5(*) is to allow all MSUs
irrespective of SI value, it even includes MTP management messages.
I assume that SGP should send DEREG-RESP
with RCs of 5-5-5(ISUP) and 5-5-5(SCCP) , whenever SGP receives
REG message with a super-set value like 5-5-5(*), it should=20
send DEREG-RESP for all its sub-set values like 5-5-5(ISUP) and
5-5-5(SCCP) if they have been already registered.

When ASP3 decided to regsiter 5-5-5(*) then it has to de-register
5-5-5(ISUP) and 5-5-5(SCCP) but this can be avoided if SGP sends
DEREG-RESP with RCs of 5-5-5(ISUP) and 5-5-5(SCCP).

In this way IG can be kept un-altered.

--Samuel

On Mon, 19 Jan 2004, Barry Nagelberg wrote:

> Brian,
>=20
> ASP3 will not be able to register 5-5-5(*). The SGP will return the
> following error code, as described in Javier's new text:
>=20
> If the SGP determines that the requested RK partially, but not
> exactly, matches an existing RK, and that an
> incoming signalling message received at an SGP could possibly match
> both the requested and the existing RK, the SGP returns a
> Registration Response message to the ASP, with a Registration
> Status of "Error - "Cannot Support Unique Routing. An incoming
> signalling message received at an SGP should not match against more
> than one Routing Key.
>=20
> Barry Nagelberg
>=20
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Friday, January 16, 2004 4:26 PM
> > To: Barry Nagelberg
> > Cc: SIGTRAN Mailing List
> > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> >
> >
> > Barry,
> >
> > There is a 1:1 correspondence; they are:
> >
> >   5-5-5(ISUP) RC1
> >   5-5-5(SCCP) RC2
> >   5-5-5(*)    RC3
> >
> > --brian
> >
> > Barry Nagelberg wrote:
> >                    (Fri, 16 Jan 2004 09:38:03)
> > > Brian,
> > >
> > > I don't think that this configuration would be clear at all to
> > the SGP. In
> > > fact, it is impossible to implement this configuration using an SGP t=
hat
> > > complies with the RFC!
> > >
> > > At both the SGP and the ASP, there must be a 1:1 correspondence
> > between a
> > > Routing Key and a Routing Context (please see Section 1.2 of
> > the RFC). So if
> > > ASP3 tries to register 2 different routing keys, 5-5-5(SCCP) and
> > > 5-5-5(ISUP), the SGP will return 2 different routing context values. =
You
> > > will never get RC3 for both routing keys at ASP3!
> > >
> > > Barry Nagelberg
> > >
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > Brian F. G. Bidulock
> > > > Sent: Friday, January 16, 2004 1:19 AM
> > > > To: kakaul@hss.hns.com
> > > > Cc: SIGTRAN Mailing List
> > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > >
> > > >
> > > > kakaul,
> > > >
> > > > As far as ASP3 is concerned it is one AS.  It activates it
> > > > by sending ASPAC(RC3).  To the SG it is clear what traffic
> > > > is activated: 5-5-5(*), and it responds ASPAC Ack(RC3).
> > > >
> > > > --brian
> > > >
> > > > kakaul@hss.hns.com wrote:
> > > >                   (Fri, 16 Jan 2004 10:56:35)
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Brian,
> > > > >
> > > > >    How can ASP3 have same RC3 for two different AS's (5-5-5(ISUP)=
,
> > > > > 5-5-5(SCCP)) registered with same SGP.How will ASP3 activate
> > > > the two AS's.
> > > > >
> > > > > Kamesh Kaul
> > > > > www.hssworld.com
> > > > > Hughes Software Systems
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "Brian F. G. Bidulock" <bidulock@openss7.org> on 01/15/2004
> > 08:31:30 PM
> > > > >
> > > > > Please respond to bidulock@openss7.org
> > > > >
> > > > > To:    Kamesh Kaul/HSS@HSS
> > > > > cc:    SIGTRAN Mailing List <sigtran@ietf.org>
> > > > >
> > > > > Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > kakaul,
> > > > >
> > > > > In the example:
> > > > >
> > > > >             RK          ASP1   ASP2   ASP3
> > > > >  -----------     ----   ----   ----
> > > > >  5-5-5(ISUP)      RC1   -     RC3
> > > > >  5-5-5(SCCP)       -     RC2    RC3
> > > > >
> > > > > Is that so difficult?
> > > > >
> > > > > --brian
> > > > >
> > > > > kakaul@hss.hns.com wrote:
> > > > > (Thu, 15 Jan 2004 19:17:06)
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I totally agree with Javier that there should be unique
> > > > routing per AS's
> > > > > ,
> > > > > > AS's must not overlap.
> > > > > > I am not able to understand how SG can handle overlapped AS's
> > > > registered
> > > > > by
> > > > > > different ASP's,
> > > > > > Brian can you explain it a little bit more.
> > > > > >
> > > > > > I think SG should not be confused in selecting actual AS
> > if AS's are
> > > > > > overlapped because first
> > > > > > thing what SG does is selecting of AS for given traffic
> > > > received without
> > > > > > having any clue of ASP's.
> > > > > >
> > > > > > Kamesh Kaul
> > > > > > www.hssworld.com
> > > > > > Hughes Software Systems
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ---------------------- Forwarded by Kamesh Kaul/HSS on
> > > > 01/15/2004 07:04
> > > > > PM
> > > > > > ---------------------------
> > > > > >
> > > > > >
> > > > > > "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on
> > 01/15/2004
> > > > > > 05:44:34 PM
> > > > > >
> > > > > > Please respond to bidulock@openss7.org
> > > > > >
> > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > >
> > > > > >
> > > > > > To:    "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com=
>
> > > > > > cc:    "'Barry Nagelberg'" <barryn@adax.com>, SIGTRAN Mailing L=
ist
> > > > > >        <sigtran@ietf.org>
> > > > > >
> > > > > > Subject:    Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > > >
> > > > > >
> > > > > > J.Javier,
> > > > > >
> > > > > > Where does it say ASes must not overlap?  This is precisely
> > > > > > one of the example cases we used for IPSP discussions.
> > > > > > I certainly don't see where retricting this is necessary
> > > > > > for proper interworking or to protect the network.
> > > > > >
> > > > > > The only problem case we had for "Unique Routing" was were
> > > > > > two RC's exist for the same traffic for the same ASP.  It is
> > > > > > then abivalent which RC the SG is to assign to the traffic.
> > > > > >
> > > > > > In this example case, it is clear which RC value is to be
> > > > > > assigned to each message for each ASP.  There is no problem
> > > > > > of "Unique Routing".
> > > > > >
> > > > > > The problem of "Unique Routing" exists where one attempt to
> > > > > > configure or register overlapping RKs for the same ASP.  So
> > > > > > if ASP4 tries to register for 5-5-5(ISUP) and 5-5-5(*) there
> > > > > > is a problem of unique routing.  To which RC is ISUP traffic
> > > > > > to go?
> > > > > >
> > > > > > For the case of different ASPs, the SG can choose to support
> > > > > > it, if capable, or refuse it if not.  The IG need not attempt
> > > > > > to dictate a restriction to SG capabilities in this regard.
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > (Thu, 15 Jan 2004 12:11:40)
> > > > > > > Brian,
> > > > > > >
> > > > > > > Why don't you take the following approach...
> > > > > > >
> > > > > > > Define two different ASes:
> > > > > > > - AS1 -> 5-5-5 (ISUP)
> > > > > > > - AS2 -> 5-5-5 (SCCP)
> > > > > > >
> > > > > > > ASP1 registers within AS1
> > > > > > > ASP2 registers within AS2
> > > > > > > ASP3 registers within both AS1 and AS2
> > > > > > >
> > > > > > > It is important to keep one unique routing per AS. ASes MUST =
not
> > > > > overlap.
> > > > > > >
> > > > > > > Cheers // Javier.
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > > > > >
> > > > > > > >
> > > > > > > > J.Javier,
> > > > > > > >
> > > > > > > > Just to clarify, there should be nothing stopping an
> > > > > > > > implementation from
> > > > > > > > allowing ASP1 to register for, say, 5-5-5 (ISUP),
> > ASP2 to register
> > > > > for
> > > > > > > > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> > > > > > > >
> > > > > > > > In this case, although ASP3 registers after ASP1 and ASP2,
> > > > > > > > there is nothing
> > > > > > > > stopping an SG from assigining a RK and RC to
> > 5-5-5(*) for ASP3.
> > > > > > > >
> > > > > > > > An SG implementation could choose to refuse 5-5-5(*) and
> > > > require ASP3
> > > > > > > > to register separately for 5-5-5(ISUP) and 5-5-5(SCCP), or =
it
> > > > > > > > might not.
> > > > > > > > I don't think it is the RFC's place to require one or the
> > > > other.  So,
> > > > > > > > for in the case where there is an overlap between
> > > > "different" APSs,
> > > > > it
> > > > > > > > should be left up to the SG implementation as it is now.
> > > > > > > >
> > > > > > > > Your additional text below, now clarifies that.  Thank you.
> > > > > > > >
> > > > > > > > --brian
> > > > > > > >
> > > > > > > >
> > > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > > >                     (Wed, 14 Jan 2004 15:30:10)
> > > > > > > > > Barry,
> > > > > > > > >
> > > > > > > > > You are right. And that is valid only for the overlapping
> > > > > > > > case. You can not create a new AS whose associated RK
> > > > > > > > overlaps another existing registered RK. In the duplicate
> > > > > > > > case it is already included that the check is against the R=
K
> > > > > > > > previosly registered by the sending ASP. The latter makes
> > > > > > > > sense but not the former.
> > > > > > > > >
> > > > > > > > > Go back to my first proposal.
> > > > > > > > >
> > > > > > > > > Thanks // Javier.
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: sigtran-admin@ietf.org
> > > > > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > > > > Barry Nagelberg
> > > > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > > > > > > > To: SIGTRAN Mailing List
> > > > > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM
> > error codes
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Javier,
> > > > > > > > > >
> > > > > > > > > > No, Brian's suggestion is not correct, nor is this upda=
ted
> > > > > > > > > > text. Routing
> > > > > > > > > > keys are independent of ASPs or associations. I think
> > > > > > > > perhaps Brian is
> > > > > > > > > > thinking of the routing context, which may be unique fo=
r
> > > > > > > > each ASP or
> > > > > > > > > > association.
> > > > > > > > > >
> > > > > > > > > > Barry Nagelberg
> > > > > > > > > >
> > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > From: sigtran-admin@ietf.org
> > > > > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > > > > > J.Javier Pastor (ML/EEM)
> > > > > > > > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > > > > > > > To: 'bidulock@openss7.org'
> > > > > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM
> > error codes
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Brian,
> > > > > > > > > > >
> > > > > > > > > > > Tell me if the following is OK.
> > > > > > > > > > >
> > > > > > > > > > > If the SGP determines that the requested RK
> > partially, but
> > > > > > > > > > not exactly,
> > > > > > > > > > > matches an existing RK already registered for the
> > > > > > > > sender ASP, and
> > > > > > > > > > > that an incoming signalling message received at
> > > > > > > > > > > an SGP could possibly match both the requested and
> > > > the existing
> > > > > > > > > > > RK, the SGP
> > > > > > > > > > > returns a Registration Response message to the
> > ASP, with a
> > > > > > > > > > Registration
> > > > > > > > > > > Status of "Error - "Cannot Support Unique Routing. An
> > > > > > > > > > incoming signalling
> > > > > > > > > > > message received at an SGP should not match against m=
ore
> > > > > > > > > > than one Routing
> > > > > > > > > > > Key.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > THanks // JAvier.
> > > > > > > > > > >
> > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > From: Brian F. G. Bidulock
> > [mailto:bidulock@openss7.org]
> > > > > > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM
> > > > error codes
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > J.Javier,
> > > > > > > > > > > >
> > > > > > > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > > > > > > >                     (Wed, 14 Jan 2004 12:36:54)
> > > > > > > > > > > >
> > > > > > > > > > > > --snip--
> > > > > > > > > > > > >
> > > > > > > > > > > > > --------
> > > > > > > > > > > > > New text: (Section 4.4.1)
> > > > > > > > > > > > > ---------
> > > > > > > > > > > > >
> > > > > > > > > > > > > If the SGP determines that the requested RK
> > > > partially, but
> > > > > > > > > > > > not exactly,
> > > > > > > > > > > > > matches an existing RK, and that an
> > incoming signalling
> > > > > > > > > > > > message received at
> > > > > > > > > > > > > an SGP could possibly match both the
> > requested and the
> > > > > > > > > > > > existing RK, the SGP
> > > > > > > > > > > > > returns a Registration Response message to the
> > > > ASP, with a
> > > > > > > > > > > > Registration
> > > > > > > > > > > > > Status of "Error - "Cannot Support Unique
> > Routing. An
> > > > > > > > > > > > incoming signalling
> > > > > > > > > > > > > message received at an SGP should not match
> > against more
> > > > > > > > > > > > than one Routing
> > > > > > > > > > > > > Key.
> > > > > > > > > > > > >
> > > > > > > > > > > > --snip--
> > > > > > > > > > > >
> > > > > > > > > > > > I think you mean for a given ASP (Association) in t=
he
> > > > > > > > > > above.  Correct?
> > > > > > > > > > > >
> > > > > > > > > > > > It should be mentioned that the "matching" of
> > RKs is done
> > > > > > > > > > > > only against other
> > > > > > > > > > > > RKs belonging to the same ASP (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
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > _______________________________________________
> > > > > > > > > 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 is proprietary to Hughes
> > Software Systems
> > > > > Limited
> > > > > > (HSS) and is intended solely for the use of the individual to
> > > > whom it is
> > > > > > addressed. It may contain  privileged or confidential
> > information and
> > > > > > should not be circulated or used for any purpose other than
> > > > for what it
> > > > > is
> > > > > > intended. If you have received this message in error, please
> > > > notify the
> > > > > > originator immediately. If you are not the intended
> > recipient, you are
> > > > > > notified that you are strictly prohibited from using,
> > > > copying, altering,
> > > > > or
> > > > > > disclosing the contents of this message. HSS accepts no
> > responsibility
> > > > > for
> > > > > > loss or damage arising from the use of the information
> > transmitted by
> > > > > this
> > > > > > email including damage from virus."
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Sigtran mailing list
> > > > > > Sigtran@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >
> > > > > --
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > >  http://www.openss7.org/
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > 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/
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20
>=20


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



From exim@www1.ietf.org  Tue Jan 20 02:46:38 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17535
	for <sigtran-archive@odin.ietf.org>; Tue, 20 Jan 2004 02:46:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiqaK-0001nX-Nd
	for sigtran-archive@odin.ietf.org; Tue, 20 Jan 2004 02:46:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0K7k4PE006910
	for sigtran-archive@odin.ietf.org; Tue, 20 Jan 2004 02:46:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiqaI-0001n9-RM; Tue, 20 Jan 2004 02:46:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiqZh-0001ls-6Y
	for sigtran@optimus.ietf.org; Tue, 20 Jan 2004 02:45:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17484
	for <sigtran@ietf.org>; Tue, 20 Jan 2004 02:45:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiqZY-0004k8-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 02:45:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiqWp-0004bk-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 02:42:29 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiqUW-0004Un-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 02:40:04 -0500
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i0K7dqqY014714;
	Tue, 20 Jan 2004 08:39:52 +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.2657.72)
	id ZJBTXXZZ; Tue, 20 Jan 2004 08:41:43 +0100
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <CRN66CJP>; Tue, 20 Jan 2004 08:39:54 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C043319D5@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>,
        Barry Nagelberg
	 <barryn@adax.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA: More redundant RKM error codes
Date: Tue, 20 Jan 2004 08:39:08 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by albatross-ext.wise.edt.ericsson.se id i0K7dqqY014714
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Brian,=20

Pls check the following:

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

- RFC2119: "SHOULD   This word, or the adjective "RECOMMENDED", mean that=
 there may exist valid reasons in particular circumstances to ignore a pa=
rticular item, but the full implications must be understood and carefully=
 weighed before choosing a different course."

Although the guide is not to do what you are proposing, whenever you have=
 the particular circumstance of talking to John's implementation you woul=
d say that you have your valid reasons and then you would say the "SHOULD=
" allows them. Of course those valid reasons would need to be discussed b=
etween the two parties and agreed.=20

In order to get the consensus that SHOULD will also be moved to the new t=
ext in the following way:

If the SGP determines that the requested RK partially, but not
exactly, matches an existing RK, and that an
incoming signalling message received at an SGP could possibly match
both the requested and the existing RK, the SGP SHOULD return a
Registration Response message to the ASP, with a Registration
Status of "Error - "Cannot Support Unique Routing. An incoming
signalling message received at an SGP SHOULD NOT match against more
than one Routing Key.

Hopefully we are all happy.

Cheers // Javier.


> -----Original Message-----
> From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Brian F. G. Bidulock
> Sent: lunes, 19 de enero de 2004 21:31
> To: Barry Nagelberg
> Cc: SIGTRAN Mailing List
> Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
>=20
>=20
> Barry,
>=20
> Javier's new text needs to be changed to allow what
> was already allowed by the RFC.
>=20
> --brian
>=20
> Barry Nagelberg wrote:                                       =20
>                        (Mon, 19 Jan 2004 11:03:23)
> > Brian,
> >=20
> > ASP3 will not be able to register 5-5-5(*). The SGP will return the
> > following error code, as described in Javier's new text:
> >=20
> > If the SGP determines that the requested RK partially, but not
> > exactly, matches an existing RK, and that an
> > incoming signalling message received at an SGP could possibly match
> > both the requested and the existing RK, the SGP returns a
> > Registration Response message to the ASP, with a Registration
> > Status of "Error - "Cannot Support Unique Routing. An incoming
> > signalling message received at an SGP should not match against more
> > than one Routing Key.
> >=20
> > Barry Nagelberg
> >=20
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: Friday, January 16, 2004 4:26 PM
> > > To: Barry Nagelberg
> > > Cc: SIGTRAN Mailing List
> > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > >
> > >
> > > Barry,
> > >
> > > There is a 1:1 correspondence; they are:
> > >
> > >   5-5-5(ISUP) RC1
> > >   5-5-5(SCCP) RC2
> > >   5-5-5(*)    RC3
> > >
> > > --brian
> > >
> > > Barry Nagelberg wrote:
> > >                    (Fri, 16 Jan 2004 09:38:03)
> > > > Brian,
> > > >
> > > > I don't think that this configuration would be clear at all to
> > > the SGP. In
> > > > fact, it is impossible to implement this configuration=20
> using an SGP that
> > > > complies with the RFC!
> > > >
> > > > At both the SGP and the ASP, there must be a 1:1 correspondence
> > > between a
> > > > Routing Key and a Routing Context (please see Section 1.2 of
> > > the RFC). So if
> > > > ASP3 tries to register 2 different routing keys, 5-5-5(SCCP) and
> > > > 5-5-5(ISUP), the SGP will return 2 different routing=20
> context values. You
> > > > will never get RC3 for both routing keys at ASP3!
> > > >
> > > > Barry Nagelberg
> > > >
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > Brian F. G. Bidulock
> > > > > Sent: Friday, January 16, 2004 1:19 AM
> > > > > To: kakaul@hss.hns.com
> > > > > Cc: SIGTRAN Mailing List
> > > > > Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
> > > > >
> > > > >
> > > > > kakaul,
> > > > >
> > > > > As far as ASP3 is concerned it is one AS.  It activates it
> > > > > by sending ASPAC(RC3).  To the SG it is clear what traffic
> > > > > is activated: 5-5-5(*), and it responds ASPAC Ack(RC3).
> > > > >
> > > > > --brian
> > > > >
> > > > > kakaul@hss.hns.com wrote:
> > > > >                   (Fri, 16 Jan 2004 10:56:35)
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Brian,
> > > > > >
> > > > > >    How can ASP3 have same RC3 for two different=20
> AS's (5-5-5(ISUP),
> > > > > > 5-5-5(SCCP)) registered with same SGP.How will ASP3 activate
> > > > > the two AS's.
> > > > > >
> > > > > > Kamesh Kaul
> > > > > > www.hssworld.com
> > > > > > Hughes Software Systems
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > "Brian F. G. Bidulock" <bidulock@openss7.org> on 01/15/2004
> > > 08:31:30 PM
> > > > > >
> > > > > > Please respond to bidulock@openss7.org
> > > > > >
> > > > > > To:    Kamesh Kaul/HSS@HSS
> > > > > > cc:    SIGTRAN Mailing List <sigtran@ietf.org>
> > > > > >
> > > > > > Subject:    Re: [Sigtran] M3UA: More redundant RKM=20
> error codes
> > > > > >
> > > > > >
> > > > > > kakaul,
> > > > > >
> > > > > > In the example:
> > > > > >
> > > > > >             RK          ASP1   ASP2   ASP3
> > > > > >  -----------     ----   ----   ----
> > > > > >  5-5-5(ISUP)      RC1   -     RC3
> > > > > >  5-5-5(SCCP)       -     RC2    RC3
> > > > > >
> > > > > > Is that so difficult?
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > > kakaul@hss.hns.com wrote:
> > > > > > (Thu, 15 Jan 2004 19:17:06)
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > I totally agree with Javier that there should be unique
> > > > > routing per AS's
> > > > > > ,
> > > > > > > AS's must not overlap.
> > > > > > > I am not able to understand how SG can handle=20
> overlapped AS's
> > > > > registered
> > > > > > by
> > > > > > > different ASP's,
> > > > > > > Brian can you explain it a little bit more.
> > > > > > >
> > > > > > > I think SG should not be confused in selecting actual AS
> > > if AS's are
> > > > > > > overlapped because first
> > > > > > > thing what SG does is selecting of AS for given traffic
> > > > > received without
> > > > > > > having any clue of ASP's.
> > > > > > >
> > > > > > > Kamesh Kaul
> > > > > > > www.hssworld.com
> > > > > > > Hughes Software Systems
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ---------------------- Forwarded by Kamesh Kaul/HSS on
> > > > > 01/15/2004 07:04
> > > > > > PM
> > > > > > > ---------------------------
> > > > > > >
> > > > > > >
> > > > > > > "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on
> > > 01/15/2004
> > > > > > > 05:44:34 PM
> > > > > > >
> > > > > > > Please respond to bidulock@openss7.org
> > > > > > >
> > > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > > >
> > > > > > >
> > > > > > > To:    "J.Javier Pastor (ML/EEM)"=20
> <j.javier.pastor@ericsson.com>
> > > > > > > cc:    "'Barry Nagelberg'" <barryn@adax.com>,=20
> SIGTRAN Mailing List
> > > > > > >        <sigtran@ietf.org>
> > > > > > >
> > > > > > > Subject:    Re: [Sigtran] M3UA: More redundant=20
> RKM error codes
> > > > > > >
> > > > > > >
> > > > > > > J.Javier,
> > > > > > >
> > > > > > > Where does it say ASes must not overlap?  This is=20
> precisely
> > > > > > > one of the example cases we used for IPSP discussions.
> > > > > > > I certainly don't see where retricting this is necessary
> > > > > > > for proper interworking or to protect the network.
> > > > > > >
> > > > > > > The only problem case we had for "Unique Routing" was were
> > > > > > > two RC's exist for the same traffic for the same=20
> ASP.  It is
> > > > > > > then abivalent which RC the SG is to assign to=20
> the traffic.
> > > > > > >
> > > > > > > In this example case, it is clear which RC value is to be
> > > > > > > assigned to each message for each ASP.  There is=20
> no problem
> > > > > > > of "Unique Routing".
> > > > > > >
> > > > > > > The problem of "Unique Routing" exists where one=20
> attempt to
> > > > > > > configure or register overlapping RKs for the=20
> same ASP.  So
> > > > > > > if ASP4 tries to register for 5-5-5(ISUP) and=20
> 5-5-5(*) there
> > > > > > > is a problem of unique routing.  To which RC is=20
> ISUP traffic
> > > > > > > to go?
> > > > > > >
> > > > > > > For the case of different ASPs, the SG can choose=20
> to support
> > > > > > > it, if capable, or refuse it if not.  The IG need=20
> not attempt
> > > > > > > to dictate a restriction to SG capabilities in=20
> this regard.
> > > > > > >
> > > > > > > --brian
> > > > > > >
> > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > > (Thu, 15 Jan 2004 12:11:40)
> > > > > > > > Brian,
> > > > > > > >
> > > > > > > > Why don't you take the following approach...
> > > > > > > >
> > > > > > > > Define two different ASes:
> > > > > > > > - AS1 -> 5-5-5 (ISUP)
> > > > > > > > - AS2 -> 5-5-5 (SCCP)
> > > > > > > >
> > > > > > > > ASP1 registers within AS1
> > > > > > > > ASP2 registers within AS2
> > > > > > > > ASP3 registers within both AS1 and AS2
> > > > > > > >
> > > > > > > > It is important to keep one unique routing per=20
> AS. ASes MUST not
> > > > > > overlap.
> > > > > > > >
> > > > > > > > Cheers // Javier.
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Brian F. G. Bidulock=20
> [mailto:bidulock@openss7.org]
> > > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 19:16
> > > > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > > > Cc: 'Barry Nagelberg'; SIGTRAN Mailing List
> > > > > > > > > Subject: Re: [Sigtran] M3UA: More redundant=20
> RKM error codes
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > J.Javier,
> > > > > > > > >
> > > > > > > > > Just to clarify, there should be nothing stopping an
> > > > > > > > > implementation from
> > > > > > > > > allowing ASP1 to register for, say, 5-5-5 (ISUP),
> > > ASP2 to register
> > > > > > for
> > > > > > > > > 5-5-5 (SCCP) and ASP3 to register for 5-5-5(*).
> > > > > > > > >
> > > > > > > > > In this case, although ASP3 registers after=20
> ASP1 and ASP2,
> > > > > > > > > there is nothing
> > > > > > > > > stopping an SG from assigining a RK and RC to
> > > 5-5-5(*) for ASP3.
> > > > > > > > >
> > > > > > > > > An SG implementation could choose to refuse=20
> 5-5-5(*) and
> > > > > require ASP3
> > > > > > > > > to register separately for 5-5-5(ISUP) and=20
> 5-5-5(SCCP), or it
> > > > > > > > > might not.
> > > > > > > > > I don't think it is the RFC's place to=20
> require one or the
> > > > > other.  So,
> > > > > > > > > for in the case where there is an overlap between
> > > > > "different" APSs,
> > > > > > it
> > > > > > > > > should be left up to the SG implementation as=20
> it is now.
> > > > > > > > >
> > > > > > > > > Your additional text below, now clarifies=20
> that.  Thank you.
> > > > > > > > >
> > > > > > > > > --brian
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > > > >                     (Wed, 14 Jan 2004 15:30:10)
> > > > > > > > > > Barry,
> > > > > > > > > >
> > > > > > > > > > You are right. And that is valid only for=20
> the overlapping
> > > > > > > > > case. You can not create a new AS whose associated RK
> > > > > > > > > overlaps another existing registered RK. In=20
> the duplicate
> > > > > > > > > case it is already included that the check is=20
> against the RK
> > > > > > > > > previosly registered by the sending ASP. The=20
> latter makes
> > > > > > > > > sense but not the former.
> > > > > > > > > >
> > > > > > > > > > Go back to my first proposal.
> > > > > > > > > >
> > > > > > > > > > Thanks // Javier.
> > > > > > > > > >
> > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > From: sigtran-admin@ietf.org
> > > > > > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > > > > > Barry Nagelberg
> > > > > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 14:49
> > > > > > > > > > > To: SIGTRAN Mailing List
> > > > > > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM
> > > error codes
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Javier,
> > > > > > > > > > >
> > > > > > > > > > > No, Brian's suggestion is not correct,=20
> nor is this updated
> > > > > > > > > > > text. Routing
> > > > > > > > > > > keys are independent of ASPs or=20
> associations. I think
> > > > > > > > > perhaps Brian is
> > > > > > > > > > > thinking of the routing context, which=20
> may be unique for
> > > > > > > > > each ASP or
> > > > > > > > > > > association.
> > > > > > > > > > >
> > > > > > > > > > > Barry Nagelberg
> > > > > > > > > > >
> > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > From: sigtran-admin@ietf.org
> > > > > > > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > > > > > > J.Javier Pastor (ML/EEM)
> > > > > > > > > > > > Sent: Wednesday, January 14, 2004 8:38 AM
> > > > > > > > > > > > To: 'bidulock@openss7.org'
> > > > > > > > > > > > Cc: SIGTRAN Mailing List; Ken Morneault (E-mail)
> > > > > > > > > > > > Subject: RE: [Sigtran] M3UA: More redundant RKM
> > > error codes
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Brian,
> > > > > > > > > > > >
> > > > > > > > > > > > Tell me if the following is OK.
> > > > > > > > > > > >
> > > > > > > > > > > > If the SGP determines that the requested RK
> > > partially, but
> > > > > > > > > > > not exactly,
> > > > > > > > > > > > matches an existing RK already=20
> registered for the
> > > > > > > > > sender ASP, and
> > > > > > > > > > > > that an incoming signalling message received at
> > > > > > > > > > > > an SGP could possibly match both the=20
> requested and
> > > > > the existing
> > > > > > > > > > > > RK, the SGP
> > > > > > > > > > > > returns a Registration Response message to the
> > > ASP, with a
> > > > > > > > > > > Registration
> > > > > > > > > > > > Status of "Error - "Cannot Support=20
> Unique Routing. An
> > > > > > > > > > > incoming signalling
> > > > > > > > > > > > message received at an SGP should not=20
> match against more
> > > > > > > > > > > than one Routing
> > > > > > > > > > > > Key.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > THanks // JAvier.
> > > > > > > > > > > >
> > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > From: Brian F. G. Bidulock
> > > [mailto:bidulock@openss7.org]
> > > > > > > > > > > > > Sent: mi=E9rcoles, 14 de enero de 2004 13:20
> > > > > > > > > > > > > To: J.Javier Pastor (ML/EEM)
> > > > > > > > > > > > > Cc: SIGTRAN Mailing List; Ken=20
> Morneault (E-mail)
> > > > > > > > > > > > > Subject: Re: [Sigtran] M3UA: More=20
> redundant RKM
> > > > > error codes
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > J.Javier,
> > > > > > > > > > > > >
> > > > > > > > > > > > > J.Javier Pastor (ML/EEM) wrote:
> > > > > > > > > > > > >                     (Wed, 14 Jan 2004=20
> 12:36:54)
> > > > > > > > > > > > >
> > > > > > > > > > > > > --snip--
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --------
> > > > > > > > > > > > > > New text: (Section 4.4.1)
> > > > > > > > > > > > > > ---------
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > If the SGP determines that the requested RK
> > > > > partially, but
> > > > > > > > > > > > > not exactly,
> > > > > > > > > > > > > > matches an existing RK, and that an
> > > incoming signalling
> > > > > > > > > > > > > message received at
> > > > > > > > > > > > > > an SGP could possibly match both the
> > > requested and the
> > > > > > > > > > > > > existing RK, the SGP
> > > > > > > > > > > > > > returns a Registration Response=20
> message to the
> > > > > ASP, with a
> > > > > > > > > > > > > Registration
> > > > > > > > > > > > > > Status of "Error - "Cannot Support Unique
> > > Routing. An
> > > > > > > > > > > > > incoming signalling
> > > > > > > > > > > > > > message received at an SGP should not match
> > > against more
> > > > > > > > > > > > > than one Routing
> > > > > > > > > > > > > > Key.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > --snip--
> > > > > > > > > > > > >
> > > > > > > > > > > > > I think you mean for a given ASP=20
> (Association) in the
> > > > > > > > > > > above.  Correct?
> > > > > > > > > > > > >
> > > > > > > > > > > > > It should be mentioned that the "matching" of
> > > RKs is done
> > > > > > > > > > > > > only against other
> > > > > > > > > > > > > RKs belonging to the same ASP (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
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > _______________________________________________
> > > > > > > > > > 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 is proprietary to Hughes
> > > Software Systems
> > > > > > Limited
> > > > > > > (HSS) and is intended solely for the use of the=20
> individual to
> > > > > whom it is
> > > > > > > addressed. It may contain  privileged or confidential
> > > information and
> > > > > > > should not be circulated or used for any purpose=20
> other than
> > > > > for what it
> > > > > > is
> > > > > > > intended. If you have received this message in=20
> error, please
> > > > > notify the
> > > > > > > originator immediately. If you are not the intended
> > > recipient, you are
> > > > > > > notified that you are strictly prohibited from using,
> > > > > copying, altering,
> > > > > > or
> > > > > > > disclosing the contents of this message. HSS accepts no
> > > responsibility
> > > > > > for
> > > > > > > loss or damage arising from the use of the information
> > > transmitted by
> > > > > > this
> > > > > > > email including damage from virus."
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > Sigtran mailing list
> > > > > > > Sigtran@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > >
> > > > > > --
> > > > > > Brian F. G. Bidulock
> > > > > > bidulock@openss7.org
> > > > > >  http://www.openss7.org/
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > 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/
> >=20
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20

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



From exim@www1.ietf.org  Tue Jan 20 03:43:34 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18949
	for <sigtran-archive@odin.ietf.org>; Tue, 20 Jan 2004 03:43:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AirTV-0004fx-0P
	for sigtran-archive@odin.ietf.org; Tue, 20 Jan 2004 03:43:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0K8h4Mf017954
	for sigtran-archive@odin.ietf.org; Tue, 20 Jan 2004 03:43:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AirTS-0004fT-5g; Tue, 20 Jan 2004 03:43:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AirTB-0004eP-1z
	for sigtran@optimus.ietf.org; Tue, 20 Jan 2004 03:42:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18938
	for <sigtran@ietf.org>; Tue, 20 Jan 2004 03:42:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AirSy-0007ND-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 03:42:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AirQa-0007Ik-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 03:40:05 -0500
Received: from zdemail04.zdem.compaq.com ([161.114.112.28])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AirPS-0007Ca-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 03:38:54 -0500
Received: from demexg11.emea.cpqcorp.net (demexg11.emea.cpqcorp.net [16.41.86.63])
	by zdemail04.zdem.compaq.com (Postfix) with ESMTP
	id 0119EDA7; Tue, 20 Jan 2004 09:37:55 +0100 (CET)
Received: from vbeexc02.emea.cpqcorp.net ([16.188.146.229]) by demexg11.emea.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.6673);
	 Tue, 20 Jan 2004 09:37:54 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sigtran] SUA v14 doubt in SCON
Date: Tue, 20 Jan 2004 09:37:52 +0100
Message-ID: <06CAA4D3753C53408D2CE6340B68444214C4CE@vbeexc02.emea.cpqcorp.net>
Thread-Topic: [Sigtran] SUA v14 doubt in SCON
Thread-Index: AcPezFlXoUU8uJvLTROyXCa4w8MPjAAYRFag
From: "Zannin, Francois" <francois.zannin@hp.com>
To: <bidulock@openss7.org>
Cc: <sigtran@ietf.org>
X-OriginalArrivalTime: 20 Jan 2004 08:37:54.0758 (UTC) FILETIME=[B2CB0660:01C3DF30]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Brian,

I think that "simple ASP s no knowledge of the congestion of an AS" is
your implementation.
Some other can have a more task distributed implementation of the ASP.

My concern is about International mode only.

What can make a SG decide to discard a message for a specific AS? The
solution to allow a SG to fully handle congestion for an AS is to block
the read on SCTP association, action that block read for all AS served
by the ASP. If the SCTP stack API is not stream oriented, then you block
ALL messages (ASPTM, SSNM ...).
The congestion implementation is to inform the messages originators that
the "SCCP user" is congested (the number of messages buffered
increased), NOT that messages are systematically discarded.=20

DO we have to create SG that discards ALL messages as soon as an AS
sends a SCON? Maybe some people want to handle congestion in a different
way; this other solution needs a "concerned PC" in the SCON.
If some other doesn't need the SCON, they just can ignore it and force
the ASP implementation to block associations as soon as one AS on an ASP
enters in congestion!

Francois,

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]=20
Sent: Monday, January 19, 2004 9:38 PM
To: Zannin, Francois
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] SUA v14 doubt in SCON


Francois,

No.  The single ASP has no knowledge of the congestion of an AS (which
comprises multiple ASP).  The SG and SG alone is responsible for the
status of the SPMC/Subsystem as reflected to the SS7 network.  In both
the national and international mode, messages are discarded/retrned
*before* delivery to the SCCP user (AS).  Therefore, only the SG
determines to which destinations congestion messages are sent.  The ASP
does not even see the message.

I certainliy disagree with making an SUA message mimic a useless M3UA
one.

--brian


Zannin, Francois wrote:
(Mon, 19 Jan 2004 15:44:23)
> Brian,
>=20
> Your view of the problem is that all SG connected to ASP must locally=20
> handle the congestion for national and international mode.
>=20
> For national Congestion with level, the good approach is to handle the

> congestion action (messages discard, TFC) in the SG in order to=20
> minimize useless traffic (because discarded) on the IP network. Then,=20
> the ASP notify all the SG(p) of it's current congestion level per AS.=20
> A timer procedure can be used on the SG in addition to the last SCON=20
> received.
>=20
> But for international congestion with no systematic discard, isn't the

> relay of the SCON enough to inform the originator of the message of=20
> the congestion of the AS. There is no need to keep the congestion in=20
> the SG!
>=20
>=20
> =20
>=20
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Monday, January 19, 2004 11:53 AM
> To: Zannin, Francois
> Cc: Tolga Asveren; sigtran@ietf.org
> Subject: Re: [Sigtran] SUA v14 doubt in SCON
>=20
>=20
> Francois,
>=20
> I did not say that SCON was not needed for SUA.  Concerned destination

> is not needed.  When an SCCP user (subsystem) becomes congested, it=20
> SCCP management signals same to the SCCP with the N-STATE request=20
> primitive. This is the SCON message from ASP to SG.
>=20
> What it does not require is a concerned destination.  N-STATE request=20
> primitives and SUA SCON do only contain the affected node.  It is=20
> SCCP's responsibility to send SSC every Pth message and only in=20
> response to the necessary messages.  SCCP messages that encounter=20
> congestion are not delivered to the SCCP user.
>=20
> This is, in fact, also the situation for M3UA, and the SG is permitted

> to ignore SCON sent from ASP to SG, and is permitted to also ignore=20
> the concerned destination in the SCON send from ASP to SG.  That is=20
> why the field (and message from ASP to SG) is of questionable utility=20
> in M3UA.
>=20
> Do you understand now?
>=20
> --brian
>=20
>=20
> Zannin, Francois wrote:
> (Mon, 19 Jan 2004 11:34:49)
> > Brian,
> >=20
> > When a SUA End point is connected to two or more SG and the ASP is
> > congestionned for only one AS served by the ASP (this case exist),
how
>=20
> > can the ASP inform the originator of the message that the AS (SCCP
> > user) is congestioned?
> >=20
> > When you think that SCON is not needed for SUA, how can you replace
> > this functionnality?
> >=20
> > Francois,
> >=20
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Monday, January 19, 2004 11:21 AM
> > To: Zannin, Francois
> > Cc: Tolga Asveren; sigtran@ietf.org
> > Subject: Re: [Sigtran] SUA v14 doubt in SCON
> >=20
> >=20
> > Francois,
> >=20
> > SUA does not support this (nor does it need to).  We only put it in
> > M3UA for so-called "nodal" congestion, and it has questionable
utility
>=20
> > there.
> >=20
> > --brian
> >=20
> > Zannin, Francois wrote:
> > (Mon, 19 Jan 2004 10:08:58)
> > > Hi,
> > >=20
> > > In the SUA network, I was wondering what could be the message send
> > > by
> > > an ASP congested for one (and only one) of it's hosted AS.
> > >=20
> > > The SCON sent by an ASP to the originator of the message (like #=20
> > > ss7 TFC or SSC) could be a solution, But this SCON do not include=20
> > > any affected PC like in M3UA.
> > >=20
> > > When an ASP receive a message for a congested AS, it can return a=20
> > > congestion indication to the originator of the message (Ref: Q714=20
> > > 5.2.7.1). Then, the ASP sends a SCON to the SG for the "originator
> of
> > > the message". But with no concerned PC in the SCON, the SG cannot
> > > identify the addressee of the SCON.
> > >=20
> > > If we are handling the congestion in "International mode", no=20
> > > congestion state must be kept in the message path, so the SG do=20
> > > not need any processing other then forwarding the SCON as a TFC.
> > >=20
> > > Could we add a concerned DPC in the SCON as it exist in the M3UA
> > > SCON?
> > >=20
> > > Francois,
> > >=20
> > >=20
> > > -----Original Message-----
> > > From: Tolga Asveren [mailto:tolga.asveren@ss8.com]
> > > Sent: Friday, September 13, 2002 5:58 PM
> > > To: sigtran@ietf.org
> > > Subject: RE: [Sigtran] SUA v14 doubt in SCON
> > >=20
> > >=20
> > > Brian,
> > >=20
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: Friday, September 13, 2002 11:10 AM
> > > > To: ygahlaut@hss.hns.com
> > > > Cc: john.loughney@nokia.com; tolga.asveren@ss8.com;
> > > > sigtran@ietf.org
> > > > Subject: Re: [Sigtran] SUA v14 doubt in SCON
> > > >
> > > >
> > > > Yogesh,
> > > >
> > > > SCON is used to indicate SS7 network congestion only.  It is not
> > > > useful in the IPSP case.  In the IPSP case, IETF mechanisms are=20
> > > > more
> >=20
> > > > applicable: such as ECN.
> > > [TOLGA] For SUA-IPSP case, aren't we allowed to use SCON to inform
> > > the
> >=20
> > > peer about local subsystem congestion? Because there is no 1:1:1=20
> > > relationship between AS,SCTP associations and an IP address, I=20
> > > wouldn't think ECN or SCTP congestion mechanisms can do, what SCON
> is
> > > intended to do.
> > >=20
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org https://www1.ietf.org/mailman/listinfo/sigtran
> > >=20
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org https://www1.ietf.org/mailman/listinfo/sigtran
> >=20
> > --
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
>=20
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/

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

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



From exim@www1.ietf.org  Tue Jan 20 04:41:34 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20501
	for <sigtran-archive@odin.ietf.org>; Tue, 20 Jan 2004 04:41:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AisNd-00085Y-PL
	for sigtran-archive@odin.ietf.org; Tue, 20 Jan 2004 04:41:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0K9f5ao031091
	for sigtran-archive@odin.ietf.org; Tue, 20 Jan 2004 04:41:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AisNc-00085A-0m; Tue, 20 Jan 2004 04:41:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AisNT-00084p-RE
	for sigtran@optimus.ietf.org; Tue, 20 Jan 2004 04:40:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20487
	for <sigtran@ietf.org>; Tue, 20 Jan 2004 04:40:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AisNL-0002Bo-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 04:40:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AisL4-000287-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 04:38:27 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[x0BUCLNZQv0f6yDUdvvrtdbLHW3zdZf9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AisJK-00022R-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 04:36:38 -0500
Received: from ns.pigworks.openss7.net (IDENT:pGjiAkkpwl58bwVyUNcNkkx2EHEAKHxG@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0K9aBI30617;
	Tue, 20 Jan 2004 02:36:11 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0K8BAd27395;
	Tue, 20 Jan 2004 01:11:10 -0700
Date: Tue, 20 Jan 2004 01:11:10 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
Cc: Barry Nagelberg <barryn@adax.com>, SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA: More redundant RKM error codes
Message-ID: <20040120011110.A27087@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>,
	Barry Nagelberg <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <1AB3D30B989BF141BBD5C70057B2EF7C043319D5@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: <1AB3D30B989BF141BBD5C70057B2EF7C043319D5@eestqnt105.es.eu.ericsson.se>; from j.javier.pastor@ericsson.com on Tue, Jan 20, 2004 at 08:39:08AM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

J.Javier,

I have no problem with SHOULD, just with Barry's MUST.

I can agree with your text as worded below.


(However, note that RFC2119 does not require a bilateral agreement
to deviate from a SHOULD, as you seem to imply in your note.)

--brian

J.Javier Pastor (ML/EEM) wrote:                                                   (Tue, 20 Jan 2004 08:39:08)
> Brian, 
> 
> Pls check the following:
> 
> - RFC3332 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."
> 
> - RFC2119: "SHOULD   This word, or the adjective "RECOMMENDED", mean that
> there may exist valid reasons in particular circumstances to ignore a
> particular item, but the full implications must be understood and carefully
> weighed before choosing a different course."
> 
> Although the guide is not to do what you are proposing, whenever you have
> the particular circumstance of talking to John's implementation you would
> say that you have your valid reasons and then you would say the "SHOULD"
> allows them. Of course those valid reasons would need to be discussed
> between the two parties and agreed. 
> 
> In order to get the consensus that SHOULD will also be moved to the new text
> in the following way:
> 
> If the SGP determines that the requested RK partially, but not
> exactly, matches an existing RK, and that an
> incoming signalling message received at an SGP could possibly match
> both the requested and the existing RK, the SGP SHOULD return a
> Registration Response message to the ASP, with a Registration
> Status of "Error - "Cannot Support Unique Routing. An incoming
> signalling message received at an SGP SHOULD NOT match against more
> than one Routing Key.
> 
> Hopefully we are all happy.
> 
> Cheers // Javier.
> 

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

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



From exim@www1.ietf.org  Tue Jan 20 04:56:35 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20925
	for <sigtran-archive@odin.ietf.org>; Tue, 20 Jan 2004 04:56:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aisc9-0000FN-4t
	for sigtran-archive@odin.ietf.org; Tue, 20 Jan 2004 04:56:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0K9u4Qx000915
	for sigtran-archive@odin.ietf.org; Tue, 20 Jan 2004 04:56:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aisc6-0000EQ-Ni; Tue, 20 Jan 2004 04:56:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AisbR-0000DG-ME
	for sigtran@optimus.ietf.org; Tue, 20 Jan 2004 04:55:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20865
	for <sigtran@ietf.org>; Tue, 20 Jan 2004 04:55:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AisbO-0002sV-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 04:55:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AisaT-0002oM-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 04:54:22 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[6qm0+dYfHEe9sbG8rqRwY7yyRVrjdZEt])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AisZt-0002hO-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 04:53:45 -0500
Received: from ns.pigworks.openss7.net (IDENT:W0137/lCrOx6q7nrdZTb/wvCpJy2uKlu@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0K9reI30924;
	Tue, 20 Jan 2004 02:53:40 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0K9rdd28630;
	Tue, 20 Jan 2004 02:53:39 -0700
Date: Tue, 20 Jan 2004 02:53:39 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Zannin, Francois" <francois.zannin@hp.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] SUA v14 doubt in SCON
Message-ID: <20040120025339.A27818@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Zannin, Francois" <francois.zannin@hp.com>,
	sigtran@ietf.org
References: <06CAA4D3753C53408D2CE6340B68444214C4CE@vbeexc02.emea.cpqcorp.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: <06CAA4D3753C53408D2CE6340B68444214C4CE@vbeexc02.emea.cpqcorp.net>; from francois.zannin@hp.com on Tue, Jan 20, 2004 at 09:37:52AM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Francois,

The decision is made within SCCP, that resides at the SG.   The decision
is made by the SCCP by comparing the importance of the message with the
restricted importance level of the subsystem.  The SCCP also counts the
Pth message.   Although SCCP Management (distinct from the SCCP User) can
indicate its congestion to SCCP using the N-STATE request primitive, the
N-STATE request primitive (defined in Q.711), does not contain a concerned
point code, only an affected user.  Thus SCON sent from ASP to SG, does
not contain a concerned point code.

SUA transport the SCCP/SCCP-User and SCCP/SCCP Management interface from
the SG to the ASP.  The decision being within the SCCP layer, without
requiring concerned destinations from SCCP management, means that there
is no purpose to including it in the SCON, because the SCCP conforming
SG implementation has no use for it, because it has at its disposal the
OPC of the Pth message used to trigger SSC and does not send the message
that triggered the sending of SSC to the AS.  SCCP Management either at
the SG or at the AS may indicate via N-STATE request the congestion level
of the subsystem.  This congestion level is for all received messages and
does not pertain to a specific triggering message.  SCCP at the SG determines
which is the Pth message to trigger sending of SSC given the current RIL
communicated by SCCP management, and the origin or relay of that messsage
determines the concern SCCP node(s) for the SSC.

Note also that the node to which the SSC is sent is not necessarily the
originating SCCP.  The SCCP uses the OPC of the MTP portion of the message
to determine the concerned node for the SSC.  This can be an STP or other
relay point.  The point code of the relay is NOT communciated to the AS
in CL or CO messages.  Note that the Source Address in the CLDT and the
CORE messages is the originating SCCP node.  For proper congestion, the
SSC must also be sent to messages arriving from relay nodes that is only
contained in the OPC of the MTP-TRANSFER Indication primitive which is at
SCCP's disposal at the SG, and is NOT communicated by SCCP to the AS.
Therefore, for proper congestion operation, the AS cannot know the correct
target of the SSC, only the SG can.

SSC is distincly different from TFC.  TFC is always address to the originator
of the MTP message.  SSC is sent for every Pth message to the originator of
the MTP portion of the message (not the same as the SCCP originator) and is
either the originating SCCP node or a relay SCCP node (when an STP or relay
node relays a message it recreates the MTP envelope because the message
passes up to SCCP in MTP-TRANSFER Ind and then back down to MTP in a new
and, as far as MTP knows, unrelated, MTP-TRANSFER Request primitive.

In the case where the SUA ASP is connected to multiple SGs acting as STPs,
the SG itself might be the concerned relay point (or might not, depending on
whether the specific message was relayed at SCCP or transferred at MTP).

Therefore, I say again, there is no purpose or use to adding concerned
destination to SCON.  The ASP cannot properly populate the parameter, and
the SG does not require any information from the ASP to perform proper
SCCP congestion procedures within the SCCP layer.  The SCON message as
defined in the draft that was advanced to IESG, which contains the
affected user and is analogous to the N-STATE request, N-STATE indication
and N-PCSTATE indication primitives are both necessary and sufficient.

Do you now understand SCCP congestion procedures?  If not, I suggest that
you read the pertinent passages of the Q.71x series of specifications.

Perhaps you are making the mistake often made on this list of confusing
user-level flow controls with protocol layer flow controls.  Do not attempt
to make an SG perform flow control at the SCCP layer when it is more properly
addressed by flow controls within the SCCP-user.  For example, some TCAP
user parts perform Automatic Code Gapping to throttle overload.  SCP overload
controls are available for most TCAP protocols.  Non-TCAP SCCP users have
similar mechanisms.

Ultimately if the SCCP-user is not servicing its read queue for the SCTP
association, the SG needs to invoke SCCP congestion procedures independent
of receiving even N-STATE Request from the ASP for proper congestion
operation.  It cannot even rely on the ASP to be able to send a message when
either the ASP or the intervening network is suffering congestion.

Either way, there is no need for concerned DPC in the ASP->SG SCON for SUA.

If you choose to persist in along these lines, perhaps you can point to a
procedure that the SG, having a fully functional SCCP, is incapable of
performing without such a parameter.

--brian

Zannin, Francois wrote:                                                            (Tue, 20 Jan 2004 09:37:52)
> Brian,
> 
> I think that "simple ASP s no knowledge of the congestion of an AS" is
> your implementation.
> Some other can have a more task distributed implementation of the ASP.
> 
> My concern is about International mode only.
> 
> What can make a SG decide to discard a message for a specific AS? The
> solution to allow a SG to fully handle congestion for an AS is to block
> the read on SCTP association, action that block read for all AS served
> by the ASP. If the SCTP stack API is not stream oriented, then you block
> ALL messages (ASPTM, SSNM ...).
> The congestion implementation is to inform the messages originators that
> the "SCCP user" is congested (the number of messages buffered
> increased), NOT that messages are systematically discarded. 
> 
> DO we have to create SG that discards ALL messages as soon as an AS
> sends a SCON? Maybe some people want to handle congestion in a different
> way; this other solution needs a "concerned PC" in the SCON.
> If some other doesn't need the SCON, they just can ignore it and force
> the ASP implementation to block associations as soon as one AS on an ASP
> enters in congestion!
> 
> Francois,
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org] 
> Sent: Monday, January 19, 2004 9:38 PM
> To: Zannin, Francois
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] SUA v14 doubt in SCON
> 
> 
> Francois,
> 
> No.  The single ASP has no knowledge of the congestion of an AS (which
> comprises multiple ASP).  The SG and SG alone is responsible for the
> status of the SPMC/Subsystem as reflected to the SS7 network.  In both
> the national and international mode, messages are discarded/retrned
> *before* delivery to the SCCP user (AS).  Therefore, only the SG
> determines to which destinations congestion messages are sent.  The ASP
> does not even see the message.
> 
> I certainliy disagree with making an SUA message mimic a useless M3UA
> one.
> 
> --brian
> 
> 

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

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



From exim@www1.ietf.org  Tue Jan 20 08:59:32 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29695
	for <sigtran-archive@odin.ietf.org>; Tue, 20 Jan 2004 08:59:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiwPI-0005gJ-ES
	for sigtran-archive@odin.ietf.org; Tue, 20 Jan 2004 08:59:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0KDx4HD021814
	for sigtran-archive@odin.ietf.org; Tue, 20 Jan 2004 08:59:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiwPF-0005ea-Pg; Tue, 20 Jan 2004 08:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiwOd-0005Xm-54
	for sigtran@optimus.ietf.org; Tue, 20 Jan 2004 08:58:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29430
	for <sigtran@ietf.org>; Tue, 20 Jan 2004 08:58:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiwOb-0000j6-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 08:58:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiwNK-0000Sr-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 08:57:03 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiwJ0-00002x-00
	for sigtran@ietf.org; Tue, 20 Jan 2004 08:52:34 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id IAA05012
	for <sigtran@ietf.org>; Tue, 20 Jan 2004 08:52:08 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: <sigtran@ietf.org>
Subject: RE: [Sigtran] SUA v14 doubt in SCON
Date: Tue, 20 Jan 2004 08:50:51 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMKEGFCDAA.asveren@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)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <20040120025339.A27818@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,UPPERCASE_25_50 
	autolearn=no version=2.60
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

[..snip..]
> Either way, there is no need for concerned DPC in the ASP->SG
> SCON for SUA.
[TOLGA]I agree. Lets' keep it similar to SCCP/SCCP-User interface -as it is
right now-.



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



From exim@www1.ietf.org  Thu Jan 22 14:52:31 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06680
	for <sigtran-archive@odin.ietf.org>; Thu, 22 Jan 2004 14:52:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajks0-0004RA-0x
	for sigtran-archive@odin.ietf.org; Thu, 22 Jan 2004 14:52:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0MJq3NA017034
	for sigtran-archive@odin.ietf.org; Thu, 22 Jan 2004 14:52:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajkrx-0004QB-Dq; Thu, 22 Jan 2004 14:52:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajkr1-0004Ou-BS
	for sigtran@optimus.ietf.org; Thu, 22 Jan 2004 14:51:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06635
	for <sigtran@ietf.org>; Thu, 22 Jan 2004 14:50:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajkqy-0006Og-00
	for sigtran@ietf.org; Thu, 22 Jan 2004 14:51:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ajkq0-00056b-00
	for sigtran@ietf.org; Thu, 22 Jan 2004 14:50:01 -0500
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajkpf-0004aJ-00; Thu, 22 Jan 2004 14:49:39 -0500
Received: from [10.0.1.3] (p5089DD04.dip.t-dialin.net [80.137.221.4])
	by mail-n.franken.de (Postfix) with ESMTP
	id 466EC2462D; Thu, 22 Jan 2004 20:48:59 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v609)
Content-Transfer-Encoding: 7bit
Message-Id: <D699939C-4D13-11D8-8713-000A95C37894@lurchi.franken.de>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: sigtran@ietf.org, tsvwg@ietf.org
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Date: Thu, 22 Jan 2004 20:47:40 +0100
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] 7th SCTP Interop
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Dear all,

the 7th SCTP Interop will be hosted by the University of Applied 
Sciences
in Muenster, Germany. It will start on July 25th and will end on July 
30th.
It is the week before the summer IETF.

In addition to the testbed we have used in previous Interops (support of
dual homed hosts, IPv4 and IPv6, delay, loss, jitter) we will also 
provide
a switched GBit Ethernet network for performance testing and a simulated
satellite link with middle boxes generating packet drop reports.

Tested specifications include RFC 2960 with RFC 3309, SCTP-IG, PR-SCTP,
ADD-IP, PKT-DRP-REP and possibly more.

I would like to know who is interested in attending the Interop to 
finalize
my planning  because we have to charge some money to cover the costs.
We also have to make sure that we have enough electric power in the 
room.

Therefore I would like to know
- which companies would like to attend
- the number of participants of each company
- how many computers (laptop, desktop, ...) and switches / hubs
   each company will bring in.

Please send your response to tuexen@fh-muenster.de

After having an initial guess about the number of participants I will 
set up a
website with the information regarding registration, fee, hotel, 
traveling, ...
you need.

If you have any questions do not hesitate to contact me.

Thank you very much for your cooperation.

Best regards
Michael



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



From exim@www1.ietf.org  Thu Jan 22 17:06:36 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15071
	for <sigtran-archive@odin.ietf.org>; Thu, 22 Jan 2004 17:06:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajmxg-0006r3-IY
	for sigtran-archive@odin.ietf.org; Thu, 22 Jan 2004 17:06:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0MM64MQ026329
	for sigtran-archive@odin.ietf.org; Thu, 22 Jan 2004 17:06:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajmxe-0006qD-Ij; Thu, 22 Jan 2004 17:06:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjmxE-0006pH-Kn
	for sigtran@optimus.ietf.org; Thu, 22 Jan 2004 17:05:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15042
	for <sigtran@ietf.org>; Thu, 22 Jan 2004 17:05:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajmx7-0007Sc-00
	for sigtran@ietf.org; Thu, 22 Jan 2004 17:05:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ajmul-0007DK-00
	for sigtran@ietf.org; Thu, 22 Jan 2004 17:03:04 -0500
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajmr1-00076v-00
	for sigtran@ietf.org; Thu, 22 Jan 2004 16:59:11 -0500
Received: from [10.0.1.3] (p5089DD04.dip.t-dialin.net [80.137.221.4])
	by mail-n.franken.de (Postfix) with ESMTP id E2D692465F
	for <sigtran@ietf.org>; Thu, 22 Jan 2004 22:58:02 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v609)
Content-Transfer-Encoding: 7bit
Message-Id: <DE1D27D2-4D25-11D8-8713-000A95C37894@lurchi.franken.de>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: sigtran@ietf.org
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Date: Thu, 22 Jan 2004 22:56:44 +0100
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] SIGTRAN Interop
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Dear all,

there is the possibility to have a SIGTRAN Interop at ETSI premises in 
Nice, France,
from September 6th to September 10th. We would test all SIGTRAN 
adaptation layers.

I would like to know who is interested in attending that Interop.

Please send your answer to tuexen@fh-muenster.de

Thank you very much for your cooperation.

Best regards
Michael


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



From exim@www1.ietf.org  Thu Jan 22 17:43:35 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16667
	for <sigtran-archive@odin.ietf.org>; Thu, 22 Jan 2004 17:43:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjnXX-0001cD-1M
	for sigtran-archive@odin.ietf.org; Thu, 22 Jan 2004 17:43:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0MMh7Ah006203
	for sigtran-archive@odin.ietf.org; Thu, 22 Jan 2004 17:43:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjnXR-0001Yu-Q2; Thu, 22 Jan 2004 17:43:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjnWv-0001NM-TT
	for sigtran@optimus.ietf.org; Thu, 22 Jan 2004 17:42:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16522
	for <sigtran@ietf.org>; Thu, 22 Jan 2004 17:42:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjnWs-00030w-00
	for sigtran@ietf.org; Thu, 22 Jan 2004 17:42:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjnSz-00028a-00
	for sigtran@ietf.org; Thu, 22 Jan 2004 17:38:26 -0500
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjnIh-0000tD-00
	for sigtran@ietf.org; Thu, 22 Jan 2004 17:27:47 -0500
Received: from alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i0MMQmwi027153;
	Thu, 22 Jan 2004 16:26:48 -0600 (CST)
Message-ID: <40104E28.8000308@alcatel.com>
Date: Thu, 22 Jan 2004 16:26:48 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
CC: sigtran@ietf.org
Subject: Re: AW: [Sigtran] M2PA - draft 10 - Link Status Ready received during
  T4 period
References: <99522F0FD7EFD611A47D0002A58EDAB7C84BB7@mchh2a8e.mchh.siemens.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by auds951.usa.alcatel.com id i0MMQmwi027153
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Yes, follow the MTP2 behavior. In an earlier draft of M2PA, I had said=20
this explicitly. I decided to remove it as one of those items that=20
duplicated MTP2.

tomG.

Gaiser Franz wrote:
> Hi Frank,
>=20
> Follow MTP2 behavior: If M2PA has already received a LS 'ready' from it=
s peer when its timer T4 expires, there is no need to start T1. M2PA can =
just send LS 'ready' to the peer and continue along.
>=20
> regards, Franz
>=20
> -----Urspr=FCngliche Nachricht-----
> Von: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]Im Auftrag
> von Franck Boesch
> Gesendet: Montag, 12. Januar 2004 18:25
> An: sigtran@ietf.org
> Betreff: [Sigtran] M2PA - draft 10 - Link Status Ready received during
> T4 period
>=20
>=20
> Hello,
>=20
> I would like to know if we should ignore a received 'Link Status Ready'=
 message during the proving period (T4) or memorize that the remote end i=
s ready to skip T1 period (just send 'Link Status Ready') when T4 expires=
. Please find below a modified Figure 12 page 35 of M2PA draft 10 to expl=
ain what I am saying.
>=20
> Thanks for the reply,
> Regards,
> Franck Boesch.
>=20
> Internet Draft  SS7 MTP2-User Peer-to-Peer Adaptation Layer   Oct 2003
>=20
>=20
>     MTP3        M2PA        SCTP        SCTP        M2PA        MTP3
>     ----        ----        ----        ----        ----        ----
>      .           .           .           .           .           .
>      .           Start timer T3          .           .           .
>      .           Link Status Proving     .           .           .
>      .           ------------------------------------>           .
>      .           .           .           .           .           .
>      .           .           .     Link Status Proving           .
>      .           <------------------------------------           .
>      .           .           .           .           .           .
>      .           Stop timer T3           .           .           .
>      .           .           .           .           .           .
>      .           Start timer T4          .           .           .
>      .           Link Status Proving     .           .           .
>      .           ------------------------------------>           .
>      .           ------------------------------------>           .
>      .           ------------------------------------>           .
>      .           .           .       Link Status Ready           .
>      .           <------------------------------------           .
>      .           ------------------------------------>           .
>      .           ------------------------------------>           .
>      .           ------------------------------------>           .
>      .           .           .           .           .           .
>      .           Timer T4 expires        .           .           .
>      .           .           .           .           .           .
>=20
>      Send Link Status Ready (one or more)=20
>=20
>      .           .           .           .           .           .
>      .           Link Status Ready       .           .           .
>      .           ------------------------------------>           .
>      .           .           .           .           .           .
>      In Service              .           .           In Service
>      <------------           .           .           ------------>
>      .           .           .           .           .           .
>=20
>      MTP3 MAY begin sending data messages.
>=20
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20


--=20
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
*   I actively disclaim speaking for Alcatel.  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 exim@www1.ietf.org  Thu Jan 22 17:47:28 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17133
	for <sigtran-archive@odin.ietf.org>; Thu, 22 Jan 2004 17:47:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjnbJ-0001yq-Rq
	for sigtran-archive@odin.ietf.org; Thu, 22 Jan 2004 17:47:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0MMl1hZ007593
	for sigtran-archive@odin.ietf.org; Thu, 22 Jan 2004 17:47:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjnbJ-0001yM-Lk; Thu, 22 Jan 2004 17:47:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajnb8-0001xo-L2
	for sigtran@optimus.ietf.org; Thu, 22 Jan 2004 17:46:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16995
	for <sigtran@ietf.org>; Thu, 22 Jan 2004 17:46:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajnb5-0003yv-00
	for sigtran@ietf.org; Thu, 22 Jan 2004 17:46:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjnXM-000382-00
	for sigtran@ietf.org; Thu, 22 Jan 2004 17:42:58 -0500
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjnTX-00029c-00
	for sigtran@ietf.org; Thu, 22 Jan 2004 17:39:00 -0500
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i0MMcSfn010583;
	Thu, 22 Jan 2004 16:38:29 -0600 (CST)
Message-ID: <401050E4.5090906@alcatel.com>
Date: Thu, 22 Jan 2004 16:38:28 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
CC: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: AW: [Sigtran] M2PA draft 10 - Processor outage
References: <99522F0FD7EFD611A47D0002A58EDAB7C84BB1@mchh2a8e.mchh.siemens.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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

Franz,

Replies are below.

tomG.

Gaiser Franz wrote:
 > Tom,
 >
 > there are two more questions about PO:

 > 1.) If MTP3 decides to resume operation after LPO ends (by sending
 > CONTINUE instead of FLUSH), shall M2PA also exchange LS 'Ready'
 > messages between the peers before resuming operation ?

Yes.


 > 2.) What happens when one side gets CONTINUE (e.g. after LPO ends),
 > but the other side a FLUSH command from MTP3?

I think everything still works OK. The LS Ready messages help them get 
their sequence numbers OK.


 > 3.) In chapter 4.1.4 it is written that when M2PA experiences local
 > processor outage, it MAY put the link out of service ... . Does this
 > imply that also the side receiving a LS 'processor outage' may put
 > the link out of service by sending a LS 'OOS'?

Only if it is allowed by the applicable MTP2 standard. I am not aware of 
any that do, but I have not researched it.


 >
 > Thanks & Best regards, Franz
   [...]

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
*   I actively disclaim speaking for Alcatel.  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 exim@www1.ietf.org  Thu Jan 22 20:16:32 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22731
	for <sigtran-archive@odin.ietf.org>; Thu, 22 Jan 2004 20:16:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjpvX-0001RT-K5
	for sigtran-archive@odin.ietf.org; Thu, 22 Jan 2004 20:16:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0N1G3PW005537
	for sigtran-archive@odin.ietf.org; Thu, 22 Jan 2004 20:16:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjpvV-0001R9-Mh; Thu, 22 Jan 2004 20:16:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajpui-0001Pf-99
	for sigtran@optimus.ietf.org; Thu, 22 Jan 2004 20:15:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22690
	for <sigtran@ietf.org>; Thu, 22 Jan 2004 20:15:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjpuW-00024H-00
	for sigtran@ietf.org; Thu, 22 Jan 2004 20:15:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ajps1-0001xG-00
	for sigtran@ietf.org; Thu, 22 Jan 2004 20:12:25 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[qsrhZ3SoJOme9r8hLNGzNuvqdFRYVlCE])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajpo8-0001mp-00
	for sigtran@ietf.org; Thu, 22 Jan 2004 20:08:24 -0500
Received: from ns.pigworks.openss7.net (IDENT:DLKxMp0zgSkCDKMafEhFbcFZGmQJQta9@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0N17xI15052;
	Thu, 22 Jan 2004 18:07:59 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0N17wB13209;
	Thu, 22 Jan 2004 18:07:58 -0700
Date: Thu, 22 Jan 2004 18:07:58 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tom George <Tom.George@alcatel.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M2PA draft 10 - Processor outage
Message-ID: <20040122180758.A13182@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tom George <Tom.George@alcatel.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <99522F0FD7EFD611A47D0002A58EDAB7C84BB1@mchh2a8e.mchh.siemens.de> <401050E4.5090906@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: <401050E4.5090906@alcatel.com>; from Tom.George@alcatel.com on Thu, Jan 22, 2004 at 04:38:28PM -0600
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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,

Tom George wrote:                                                                      (Thu, 22 Jan 2004 16:38:28)
> Franz,
> 
> Replies are below.
> 
> tomG.
> 
> Gaiser Franz wrote:
>  > Tom,
>  >
>  > there are two more questions about PO:
> 
>  > 1.) If MTP3 decides to resume operation after LPO ends (by sending
>  > CONTINUE instead of FLUSH), shall M2PA also exchange LS 'Ready'
>  > messages between the peers before resuming operation ?
> 
> Yes.
> 
> 
>  > 2.) What happens when one side gets CONTINUE (e.g. after LPO ends),
>  > but the other side a FLUSH command from MTP3?
> 
> I think everything still works OK. The LS Ready messages help them get 
> their sequence numbers OK.
> 
> 
>  > 3.) In chapter 4.1.4 it is written that when M2PA experiences local
>  > processor outage, it MAY put the link out of service ... . Does this
>  > imply that also the side receiving a LS 'processor outage' may put
>  > the link out of service by sending a LS 'OOS'?
> 
> Only if it is allowed by the applicable MTP2 standard. I am not aware of 
> any that do, but I have not researched it.

MTP3b does.


--brian

> 
> 
>  >
>  > Thanks & Best regards, Franz
>    [...]
> 
> -- 
> * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> *   I actively disclaim speaking for Alcatel.  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 exim@www1.ietf.org  Fri Jan 23 09:52:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02965
	for <sigtran-archive@odin.ietf.org>; Fri, 23 Jan 2004 09:52:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ak2fD-0001Fw-Dx
	for sigtran-archive@odin.ietf.org; Fri, 23 Jan 2004 09:52:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0NEq3CJ004808
	for sigtran-archive@odin.ietf.org; Fri, 23 Jan 2004 09:52:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ak2fA-0001FO-Q4; Fri, 23 Jan 2004 09:52:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ak2er-0001EK-FN
	for sigtran@optimus.ietf.org; Fri, 23 Jan 2004 09:51:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02914
	for <sigtran@ietf.org>; Fri, 23 Jan 2004 09:51:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ak2ep-0001Jz-00
	for sigtran@ietf.org; Fri, 23 Jan 2004 09:51:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ak2dr-0001Id-00
	for sigtran@ietf.org; Fri, 23 Jan 2004 09:50:40 -0500
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ak2cy-0001H4-00
	for sigtran@ietf.org; Fri, 23 Jan 2004 09:49:44 -0500
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i0NEn7fn007178;
	Fri, 23 Jan 2004 08:49:07 -0600 (CST)
Message-ID: <40113462.3000602@alcatel.com>
Date: Fri, 23 Jan 2004 08:49:06 -0600
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
CC: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M2PA draft 10 - Processor outage
References: <99522F0FD7EFD611A47D0002A58EDAB7C84BB1@mchh2a8e.mchh.siemens.de> <401050E4.5090906@alcatel.com> <20040122180758.A13182@openss7.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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 forgot to mention that section 4.1.6 covers this case.

Brian F. G. Bidulock wrote:
   [...]
>> > 3.) In chapter 4.1.4 it is written that when M2PA experiences local
>> > processor outage, it MAY put the link out of service ... . Does this
>> > imply that also the side receiving a LS 'processor outage' may put
>> > the link out of service by sending a LS 'OOS'?
>>
>>Only if it is allowed by the applicable MTP2 standard. I am not aware of 
>>any that do, but I have not researched it.
> 
> 
> MTP3b does.
> 
> --brian
   [...]

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
*   I actively disclaim speaking for Alcatel.  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 exim@www1.ietf.org  Fri Jan 23 19:49:33 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05397
	for <sigtran-archive@odin.ietf.org>; Fri, 23 Jan 2004 19:49:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkByy-0003U2-Bd
	for sigtran-archive@odin.ietf.org; Fri, 23 Jan 2004 19:49:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0O0n4kT013370
	for sigtran-archive@odin.ietf.org; Fri, 23 Jan 2004 19:49:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkByu-0003TX-Jt; Fri, 23 Jan 2004 19:49:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjBBU-00025g-KS
	for sigtran@optimus.ietf.org; Wed, 21 Jan 2004 00:45:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11403
	for <sigtran@ietf.org>; Wed, 21 Jan 2004 00:45:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjBBR-0007je-00
	for sigtran@ietf.org; Wed, 21 Jan 2004 00:45:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjBAT-0007fm-00
	for sigtran@ietf.org; Wed, 21 Jan 2004 00:44:45 -0500
Received: from [213.232.102.50] (helo=rms01.rgtitech.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjB9X-0007cn-00
	for sigtran@ietf.org; Wed, 21 Jan 2004 00:43:47 -0500
Date: Wed, 21 Jan 2004 05:44:36 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Message-ID: <0FA1C4DD07A30E45895C265863CEA8730154AE@rms01.rgtitech.com>
content-class: urn:content-classes:message
Thread-Topic: REGARDING DOUBT IN SIGTRAN
Thread-Index: AcPf4ad7BRqmo2iaSUyrwoCbSIB46Q==
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
From: "Mahendaran v" <mahendaran.v@rgtitech.com>
To: <sigtran@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=LINES_OF_YELLING,
	LINES_OF_YELLING_2,SUBJ_ALL_CAPS autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Subject: [Sigtran] REGARDING DOUBT IN SIGTRAN
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi

Pls give your your suggestions regarding the following doubts

 1. There is any specific tool to test the sigtran protocol layer =
functionality individually.
 2. There is any specific rule that, M3UA must be used between MGC and =
SG,
    M2UA between MG and SG,MGC or it is based upon our requirement ?
 3. We are in implementation of sigtran protocol stack using opensource =
code available on the www.openss7.org
 4. Specifically as M2PA is not fully matured the implementation of M2PA =
will be stable and eficient ?
 5. Just refering M3UA implementation guide is enough to develop all the =
functionality of it or any other document to refer ?


Awaiting for your reply with anticipation


 warm regards
 mahendaran pv




-------------------------------------------------------------------------=
---
MAHENDARAN PV
S/W ENGINEER
RGTI TECHNOLOGY SOLUTIONS P LTD
CHENNAI
T.N
INDIA

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



From exim@www1.ietf.org  Fri Jan 23 21:54:31 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08809
	for <sigtran-archive@odin.ietf.org>; Fri, 23 Jan 2004 21:54:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkDvv-0000Ue-WC
	for sigtran-archive@odin.ietf.org; Fri, 23 Jan 2004 21:54:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0O2s3F7001890
	for sigtran-archive@odin.ietf.org; Fri, 23 Jan 2004 21:54:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkDvt-0000UN-CD; Fri, 23 Jan 2004 21:54:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkDuy-0000Ts-Jl
	for sigtran@optimus.ietf.org; Fri, 23 Jan 2004 21:53:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08780
	for <sigtran@ietf.org>; Fri, 23 Jan 2004 21:53:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkDuv-0004iw-00
	for sigtran@ietf.org; Fri, 23 Jan 2004 21:53:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AkDty-0004i0-00
	for sigtran@ietf.org; Fri, 23 Jan 2004 21:52:03 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[4Ad93+EbAd75/6Zia0AnJpbt5141T6uF])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkDtd-0004hE-00
	for sigtran@ietf.org; Fri, 23 Jan 2004 21:51:41 -0500
Received: from ns.pigworks.openss7.net (IDENT:+B6Y2/4+rYOg4Kn+fWhXMdjNpHtsbG4q@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0O2peI06670;
	Fri, 23 Jan 2004 19:51:40 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0O2pd632136;
	Fri, 23 Jan 2004 19:51:39 -0700
Date: Fri, 23 Jan 2004 19:51:39 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Mahendaran v <mahendaran.v@rgtitech.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] REGARDING DOUBT IN SIGTRAN
Message-ID: <20040123195139.A31322@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Mahendaran v <mahendaran.v@rgtitech.com>,
	sigtran@ietf.org
References: <0FA1C4DD07A30E45895C265863CEA8730154AE@rms01.rgtitech.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: <0FA1C4DD07A30E45895C265863CEA8730154AE@rms01.rgtitech.com>; from mahendaran.v@rgtitech.com on Wed, Jan 21, 2004 at 05:44:36AM -0000
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Mahendaran,

Mahendaran v wrote:                                                             (Wed, 21 Jan 2004 05:44:36)
> Hi
> 
> Pls give your your suggestions regarding the following doubts
> 
>  1. There is any specific tool to test the sigtran protocol layer
>  functionality individually.

Wrong place for this question.  Google is your friend.

>  2. There is any specific rule that, M3UA must be used between MGC and SG,
>     M2UA between MG and SG,MGC or it is based upon our requirement ?

No.

>  3. We are in implementation of sigtran protocol stack using opensource code
>  available on the www.openss7.org

Good.  You should, however, post questions specific to this implementation
to mailto:openss7-develop@openss7.org  This SIGTRAN list is for questions and
comments concerning the protocol and related to the Working Group.

>  4. Specifically as M2PA is not fully matured the implementation of M2PA
>  will be stable and eficient ?

M2PA is rather matured.  It has undergone interoperability testing and is
moving to RFC.

I will soon submit an updated draft-bidulock-sigtran-m2pa-test document and
post an opensource implmentation of M2PA that meets the test specification in
accordance with draft-ietf-sigtran-m2pa-10.txt which is the last draft text
before RFC.

>  5. Just refering M3UA implementation guide is enough to develop all the
>  functionality of it or any other document to refer ?

The implementor's guide is a implementor's guide to the protocol and acts as
an errata and corregendum to the main RFC document.  It is not intended to
instruct anyone on how to implement the M3UA protocol.

--brian

> 
> 
> Awaiting for your reply with anticipation
> 
> 
>  warm regards
>  mahendaran pv
> 
> 
> 
> 
> ----------------------------------------------------------------------------
> MAHENDARAN PV
> S/W ENGINEER
> RGTI TECHNOLOGY SOLUTIONS P LTD
> CHENNAI
> T.N
> INDIA
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Wed Jan 28 13:30:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18683
	for <sigtran-archive@odin.ietf.org>; Wed, 28 Jan 2004 13:30:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AluRw-0005fp-2V
	for sigtran-archive@odin.ietf.org; Wed, 28 Jan 2004 13:30:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0SIU455021792
	for sigtran-archive@odin.ietf.org; Wed, 28 Jan 2004 13:30:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AluRu-0005fH-OT; Wed, 28 Jan 2004 13:30:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AluRi-0005eK-TI
	for sigtran@optimus.ietf.org; Wed, 28 Jan 2004 13:29:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18674
	for <sigtran@ietf.org>; Wed, 28 Jan 2004 13:29:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AluRg-0001mg-00
	for sigtran@ietf.org; Wed, 28 Jan 2004 13:29:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AluQk-0001hP-00
	for sigtran@ietf.org; Wed, 28 Jan 2004 13:28:50 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AluQ9-0001bh-00
	for sigtran@ietf.org; Wed, 28 Jan 2004 13:28:13 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i0SIS97T008320;
	Wed, 28 Jan 2004 13:28:09 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Cc: "Seamus Gilchrist" <sgilchrist@connetcom.com>,
        "Michael Perler" <mikep@adax.com>
Date: Wed, 28 Jan 2004 13:29:39 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOKEBACEAA.barryn@adax.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
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] SUA v16: Global Titles
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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

We have some questions about global titles in SUA.

First, in section 3.10.2.3 of SUA draft 16, the definition for GTI=0001 does
not appear to match with ITU-T Q.713 (1996) 3.4.2.3.1. According to Q.713,
GTI=0001 means that the global title information only contains a nature of
address and the global title address. According to the SUA draft, GTI=0001
means that the nature of address is ignored, that the translation type must
be 0 (unknown), and that the numbering plan must be 1 (E.164). What is the
reason for this difference?

Also, section 3.10.2.3 does not include an encoding scheme field. The draft
says "Address signals to be coded as defined in ITU-T Q.713 Section
3.4.2.3.1." That section of the ITU specification includes an example of how
the digits would be encoded if BCD encoding was used. Does this mean that
SUA only supports BCD encoding? If other types of encoding can be used, how
is the encoding scheme specified in the global title?

Barry Nagelberg


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



From exim@www1.ietf.org  Wed Jan 28 14:27:32 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21912
	for <sigtran-archive@odin.ietf.org>; Wed, 28 Jan 2004 14:27:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlvL7-0008Cc-DI
	for sigtran-archive@odin.ietf.org; Wed, 28 Jan 2004 14:27:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0SJR5CU031517
	for sigtran-archive@odin.ietf.org; Wed, 28 Jan 2004 14:27:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlvL3-0008Ar-QA; Wed, 28 Jan 2004 14:27:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlvK9-0005nQ-KZ
	for sigtran@optimus.ietf.org; Wed, 28 Jan 2004 14:26:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21838
	for <sigtran@ietf.org>; Wed, 28 Jan 2004 14:26:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlvK7-000040-00
	for sigtran@ietf.org; Wed, 28 Jan 2004 14:26:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlvJN-0007jt-00
	for sigtran@ietf.org; Wed, 28 Jan 2004 14:25:17 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[W9p0z6bZqWu7uwFssyAk/HnLCvmFzsg8])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlvIc-0007aV-00
	for sigtran@ietf.org; Wed, 28 Jan 2004 14:24:30 -0500
Received: from ns.pigworks.openss7.net (IDENT:HrMhrIGF3Q4E3YO2zoJNfAEFBhjZBIhR@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0SJOBI16521;
	Wed, 28 Jan 2004 12:24:11 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0SJOBf17747;
	Wed, 28 Jan 2004 12:24:11 -0700
Date: Wed, 28 Jan 2004 12:24:11 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry Nagelberg <barryn@adax.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>,
        Seamus Gilchrist <sgilchrist@connetcom.com>,
        Michael Perler <mikep@adax.com>
Subject: Re: [Sigtran] SUA v16: Global Titles
Message-ID: <20040128122410.A16922@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry Nagelberg <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>,
	Seamus Gilchrist <sgilchrist@connetcom.com>,
	Michael Perler <mikep@adax.com>
References: <JBECLENKLBCKAAKFGAJOKEBACEAA.barryn@adax.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: <JBECLENKLBCKAAKFGAJOKEBACEAA.barryn@adax.com>; from barryn@adax.com on Wed, Jan 28, 2004 at 01:29:39PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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,

I think you'll find that it more closely resembles ANSI T1.112, which does
not have a nature of address indicator.  Also, encoding scheme is only ever
BCD (odd or even).  GTI in SUA and (for that matter) GTI in ITU and ANSI do
not match.  The GTI in SUA, like ITU and ANSI indicates the fields present
in the messsage.  If you need to specify any value, use SUA GTI=0100.  The
SUA GTI does not dictate what is passed to the SS7 network by a gateway.
The AMF or GTT result will determine that.

Did you have a specific application that cannot be met with the current
codings?

--brian

Barry Nagelberg wrote:                                                               (Wed, 28 Jan 2004 13:29:39)
> We have some questions about global titles in SUA.
> 
> First, in section 3.10.2.3 of SUA draft 16, the definition for GTI=0001 does
> not appear to match with ITU-T Q.713 (1996) 3.4.2.3.1. According to Q.713,
> GTI=0001 means that the global title information only contains a nature of
> address and the global title address. According to the SUA draft, GTI=0001
> means that the nature of address is ignored, that the translation type must
> be 0 (unknown), and that the numbering plan must be 1 (E.164). What is the
> reason for this difference?
> 
> Also, section 3.10.2.3 does not include an encoding scheme field. The draft
> says "Address signals to be coded as defined in ITU-T Q.713 Section
> 3.4.2.3.1." That section of the ITU specification includes an example of how
> the digits would be encoded if BCD encoding was used. Does this mean that
> SUA only supports BCD encoding? If other types of encoding can be used, how
> is the encoding scheme specified in the global title?
> 
> Barry Nagelberg
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jan 29 23:48:32 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11700
	for <sigtran-archive@odin.ietf.org>; Thu, 29 Jan 2004 23:48:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmQZX-0007OY-4i
	for sigtran-archive@odin.ietf.org; Thu, 29 Jan 2004 23:48:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0U4m3dS028406
	for sigtran-archive@odin.ietf.org; Thu, 29 Jan 2004 23:48:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmQZV-0007Nh-67; Thu, 29 Jan 2004 23:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmQYY-0007MB-Oi
	for sigtran@optimus.ietf.org; Thu, 29 Jan 2004 23:47:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11614
	for <sigtran@ietf.org>; Thu, 29 Jan 2004 23:46:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmQYW-0000eD-00
	for sigtran@ietf.org; Thu, 29 Jan 2004 23:47:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmQXR-0000Y2-00
	for sigtran@ietf.org; Thu, 29 Jan 2004 23:45:54 -0500
Received: from fw.cdotb.ernet.in ([202.41.72.207] helo=ws9.cdotb.ernet.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmQWg-0000Km-00
	for sigtran@ietf.org; Thu, 29 Jan 2004 23:45:07 -0500
Received: from cdotb.ernet.in ([192.168.51.210])
	by ws9.cdotb.ernet.in (8.9.3/8.9.3) with ESMTP id JAA17655
	for <sigtran@ietf.org>; Fri, 30 Jan 2004 09:46:40 +0500 (GMT+0500)
Message-ID: <4019DFEF.7090000@cdotb.ernet.in>
Date: Fri, 30 Jan 2004 10:09:11 +0530
From: Prakash R <rprakash@cdotb.ernet.in>
Reply-To: rprakash@cdotb.ernet.in
Organization: C-DOT (Center for Development of Telematics)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sigtran@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] Information on the ASP Model
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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

Hello,

I was wondering whether the ASP model that is used in M2UA, M3UA, and
SUA was based on any already known fault-tolerance model. There are a 
few aspects that I find difficult to understand. Is there some 
background reading that is expected for understaning the ASP model in 
the XUA RFCs?

Regards,
-- 
Prakash R
Business Unit Head, Softswitch and Media Gateway,(Cell & Packet Tech.)
======================================================================
C-DOT (Centre for Development of Telematics)
71/1, Sneha Complex, Miller Road, Bangalore - 560052, India
email: rprakash@cdotb.ernet.in, prakash_r@hotmail.com
Phone: +91-80-22263399 Ext. 268, +91-80-22383951, Fax: +91-80-22263256
======================================================================

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



From exim@www1.ietf.org  Fri Jan 30 02:58:33 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01380
	for <sigtran-archive@odin.ietf.org>; Fri, 30 Jan 2004 02:58:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmTXR-0002rC-NB
	for sigtran-archive@odin.ietf.org; Fri, 30 Jan 2004 02:58:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0U7w5lJ010982
	for sigtran-archive@odin.ietf.org; Fri, 30 Jan 2004 02:58:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmTXO-0002qi-EH; Fri, 30 Jan 2004 02:58:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmTWU-0002pY-Tj
	for sigtran@optimus.ietf.org; Fri, 30 Jan 2004 02:57:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01356
	for <sigtran@ietf.org>; Fri, 30 Jan 2004 02:57:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmTWR-0007de-00
	for sigtran@ietf.org; Fri, 30 Jan 2004 02:57:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmTVT-0007XO-00
	for sigtran@ietf.org; Fri, 30 Jan 2004 02:56:03 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[jQjeIuwtrseXluTcPYglBfGzEkTuY6N9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmTV4-0007Qr-00
	for sigtran@ietf.org; Fri, 30 Jan 2004 02:55:38 -0500
Received: from ns.pigworks.openss7.net (IDENT:zSfo+5OY+7zqK9M7g9igjTp+qW+K9qXz@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i0U7tcI18004;
	Fri, 30 Jan 2004 00:55:38 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i0U7tcm15820;
	Fri, 30 Jan 2004 00:55:38 -0700
Date: Fri, 30 Jan 2004 00:55:38 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Prakash R <rprakash@cdotb.ernet.in>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Information on the ASP Model
Message-ID: <20040130005538.A15310@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Prakash R <rprakash@cdotb.ernet.in>, sigtran@ietf.org
References: <4019DFEF.7090000@cdotb.ernet.in>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <4019DFEF.7090000@cdotb.ernet.in>; from rprakash@cdotb.ernet.in on Fri, Jan 30, 2004 at 10:09:11AM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Prakash,

Yes.  Active-standby (Master-slave, Leader-follower), Load sharing
(distributed) and Broadcast (reliable broadcast, 2 out of 3 vote, or 3
out of 4 vote, and others), just as found in carrier grade switching
systems.

Any good book on telecommunications switching and redundant stored
program control switches would be a good starting point.  A book on
distributed processing theory might be good also.

I have a couple of good references that I use but I don't want to plug
anyone's book on an IETF mailing list.  Send me an e-mail offline if you
are interested.

--brian


Prakash R wrote:                                                                   (Fri, 30 Jan 2004 10:09:11)
> Hello,
> 
> I was wondering whether the ASP model that is used in M2UA, M3UA, and
> SUA was based on any already known fault-tolerance model. There are a 
> few aspects that I find difficult to understand. Is there some 
> background reading that is expected for understaning the ASP model in 
> the XUA RFCs?
> 
> Regards,
> -- 
> Prakash R
> Business Unit Head, Softswitch and Media Gateway,(Cell & Packet Tech.)
> ======================================================================
> C-DOT (Centre for Development of Telematics)
> 71/1, Sneha Complex, Miller Road, Bangalore - 560052, India
> email: rprakash@cdotb.ernet.in, prakash_r@hotmail.com
> Phone: +91-80-22263399 Ext. 268, +91-80-22383951, Fax: +91-80-22263256
> ======================================================================
> 
> _______________________________________________
> 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



