From exim@www1.ietf.org  Thu Apr  1 21:09:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23025
	for <sigtran-archive@odin.ietf.org>; Thu, 1 Apr 2004 21:09: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 1B9BVd-0005GN-Vd
	for sigtran-archive@odin.ietf.org; Thu, 01 Apr 2004 18:22:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i31NM5iM020195
	for sigtran-archive@odin.ietf.org; Thu, 1 Apr 2004 18:22:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B99DM-0000vD-Sg
	for sigtran-web-archive@optimus.ietf.org; Thu, 01 Apr 2004 15:55:04 -0500
Date: Thu, 01 Apr 2004 11:17:49 -0500
Message-ID: <20040401161749.11029.60940.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 Apr  2 16:53:04 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04328
	for <sigtran-archive@odin.ietf.org>; Fri, 2 Apr 2004 16:53:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9VpG-0001jV-Ud
	for sigtran-archive@odin.ietf.org; Fri, 02 Apr 2004 16:03:43 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i32L3gRI006662
	for sigtran-archive@odin.ietf.org; Fri, 2 Apr 2004 16:03:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9SJs-0007h5-4I; Fri, 02 Apr 2004 12:19:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9QTa-0004Ox-E9
	for sigtran@optimus.ietf.org; Fri, 02 Apr 2004 10:20:58 -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 KAA13391
	for <sigtran@ietf.org>; Fri, 2 Apr 2004 10:20:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9QTY-0005tE-00
	for sigtran@ietf.org; Fri, 02 Apr 2004 10:20:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9QSa-0005mC-00
	for sigtran@ietf.org; Fri, 02 Apr 2004 10:19:56 -0500
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9QS2-0005bi-00; Fri, 02 Apr 2004 10:19:22 -0500
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i32FIo8d010916;
	Fri, 2 Apr 2004 09:18:50 -0600 (CST)
Message-ID: <406D845A.8050009@alcatel.com>
Date: Fri, 02 Apr 2004 09:18:50 -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: iesg@ietf.org
CC: SIGTRAN e-mail list <SIGTRAN@ietf.org>
Subject: Re: [Sigtran] Last Call: 'SS7 MTP2-User Peer-to-Peer Adaptation Layer'
 to Proposed Standard
References: <E1B8ojL-0000fd-Ph@optimus.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
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Here is one change that had been discussed on the SIGTRAN email list 
since the publication of draft 11.

On 03/01/04 Tom George wrote (Subject: Re: [SIGTRAN] M2PA - Local 
Processor Outage):
> The next time I get to edit the document, I will add the last
> sentence to this paragraph in 4.1.4 (version 11):
> 
> =====
> When the local processor outage condition ends, M2PA SHALL send a Link
> Status Processor Recovered message to its peer on the User Data
> stream. This message is used to signal the end of the processor outage
> condition, instead of an MSU or FISU as in MTP2. The BSN in the Link
> Status Processor Recovered message is set to the FSN of the last User
> Data message received (and not discarded) from the peer M2PA. *** M2PA
> SHALL cease transmitting User Data messages after sending the Link
> Status Processor Recovered message, until it has received the Link
> Status Ready message (see below). ***
> =====
   [...]


The IESG wrote:
> The IESG has received a request from the Signaling Transport WG to consider 
> the following document:
> 
> - 'SS7 MTP2-User Peer-to-Peer Adaptation Layer '
>    <draft-ietf-sigtran-m2pa-11.txt> as a Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by 2004-04-14.
> 
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m2pa-11.txt
> 
> 
> _______________________________________________
> 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  Tue Apr  6 05:22:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25735
	for <sigtran-archive@odin.ietf.org>; Tue, 6 Apr 2004 05:22:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAmmT-0004hw-9o
	for sigtran-archive@odin.ietf.org; Tue, 06 Apr 2004 05:22:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i369M5AM018094
	for sigtran-archive@odin.ietf.org; Tue, 6 Apr 2004 05:22:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAmmQ-0004gN-6u; Tue, 06 Apr 2004 05:22:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAmlm-0004X1-N5
	for sigtran@optimus.ietf.org; Tue, 06 Apr 2004 05:21:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25586
	for <sigtran@ietf.org>; Tue, 6 Apr 2004 05:21:18 -0400 (EDT)
From: bulent.yilmaz@turkcell.com.tr
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAmlj-0003zP-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 05:21:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAmYn-0001V1-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 05:08:00 -0400
Received: from [212.252.168.230] (helo=tplmalsmtp.turkcell.com.tr)
	by ietf-mx with smtp (Exim 4.12)
	id 1BAlzR-00065m-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 04:31:26 -0400
Received: from exh3415.turkcell.entp.tgc ([10.200.250.156]) by tcexi3401.turkcell.entp.tgc with Microsoft SMTPSVC(6.0.3790.0); Tue, 6 Apr 2004 11:30:38 +0300
Received: from exh3410.turkcell.entp.tgc ([10.200.251.99]) by exh3415.turkcell.entp.tgc with Microsoft SMTPSVC(6.0.3790.0); Tue, 6 Apr 2004 11:30:28 +0300
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-Class: urn:content-classes:message
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C41BB1.6C548295"
Importance: normal
Priority: normal
Date: Tue, 6 Apr 2004 11:30:29 +0300
Message-ID: <ACE5644D97D0124AAB3D466F33B159BE06CFDCDC@exh3410.turkcell.entp.tgc>
Thread-Topic: Header lengths of the protocols ...
thread-index: AcQbsWt07aWH/bdsT5KF76meZbPf2w==
To: <sigtran@ietf.org>
X-OriginalArrivalTime: 06 Apr 2004 08:30:28.0018 (UTC) FILETIME=[6A52A920:01C41BB1]
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=AWL,HTML_40_50,HTML_MESSAGE,
	NO_REAL_NAME autolearn=no version=2.60
Subject: [Sigtran] Header lengths of the protocols ...
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C41BB1.6C548295
Content-Type: text/plain;
	charset="iso-8859-9"
Content-Transfer-Encoding: quoted-printable

Dear Experts,

=20

Would you please provide me header lengths of each SIGTRAN (SUA, M3UA, =
M2PA and SCTP) protocol?

=20

I also would be glad if any of you could direct me to a resource where I =
can get that information.

=20

Regards,

=20

B=FClent YILMAZ=20
TURKCELL=20
TO / Coordination Office

New Technologies
Mobile  : +90 532 210 1883=20
Office   : +90 216 458 2427=20
Fax      : +90 216 427 5141=20
e-mail   : bulent.yilmaz@turkcell.com.tr=20

=20



***********************************************************************
Bu elektronik posta ve onunla iletilen b=FCt=FCn dosyalar sadece =
g=F6ndericisi taraf=FDndan almas=FD ama=E7lanan yetkili ger=E7ek ya da =
t=FCzel ki=FEinin kullan=FDm=FD i=E7indir.E=F0er s=F6z konusu yetkili =
al=FDc=FD de=F0ilseniz bu elektronik postan=FDn i=E7eri=F0ini =
a=E7=FDklaman=FDz,kopyalaman=FDz, y=F6nlendirmeniz ve kullanman=FDz =
kesinlikle yasakt=FDr ve bu elektronik postay=FD derhal silmeniz =
gerekmektedir
TURKCELL bu mesaj=FDn i=E7erdi=F0i bilgilerin do=F0rulu=F0u veya =
eksiksiz oldu=F0u konusunda herhangi bir garanti vermemektedir. Bu =
nedenle bu bilgilerin ne =FEekilde olursa olsun i=E7eri=F0inden, =
iletilmesinden, al=FDnmas=FDndan ve saklanmas=FDndan sorumlu de=F0ildir. =
Bu mesajdaki g=F6r=FC=FEler yaln=FDzca g=F6nderen ki=FEiye aittir ve =
TURKCELL'in g=F6r=FC=FElerini yans=FDtmayabilir
Bu e-posta bilinen b=FCt=FCn bilgisayar vir=FCslerine kar=FE=FD =
taranm=FD=FEt=FDr.
***********************************************************************
This e-mail and any files transmitted with it are confidential and =
intended solely for the use of the individual or entity to whom they are =
addressed. If you are not the intended recipient you are hereby notified =
that any dissemination, forwarding, copying or use of any of the =
information is strictly prohibited, and the e-mail should immediately be =
deleted.
TURKCELL makes no warranty as to the accuracy or completeness of any =
information contained in this message and hereby excludes any liability =
of any kind for the information contained therein or for the information =
transmission, reception, storage or use of such in any way =
whatsoever.The opinions expressed in this message belong to sender alone =
and may not necessarily reflect the opinions of TURKCELL.
This e-mail has been scanned for all known computer viruses.
***********************************************************************

------_=_NextPart_001_01C41BB1.6C548295
Content-Type: text/html;
	charset="iso-8859-9"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-9">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"\@Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:#606420;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DTR link=3Dblue vlink=3D"#606420">

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Dear Experts,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Would you please provide me header lengths of =
each
SIGTRAN (SUA, M3UA, M2PA and SCTP) =
protocol?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>I also would be glad if any of you could =
direct me to
a resource where I can get that =
information.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Arial Unicode MS"><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:"Arial Unicode MS"'>B=FClent =
YILMAZ <br>
</span></font><strong><b><font face=3D"Arial Unicode MS"><span =
lang=3DEN-US
style=3D'font-family:"Arial Unicode =
MS"'>TURKCELL</span></font></b></strong><font
face=3D"Arial Unicode MS"><span lang=3DEN-US style=3D'font-family:"Arial =
Unicode MS"'>
</span></font><font size=3D2 face=3D"Arial Unicode MS"><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:"Arial Unicode MS"'><br>
<strong><b><font face=3D"Arial Unicode MS"><span =
style=3D'font-family:"Arial Unicode MS"'>TO&nbsp;/
Coordination Office</span></font></b></strong></span></font><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal><strong><b><font size=3D2 face=3D"Arial Unicode =
MS"><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Arial Unicode =
MS"'>New Technologies</span></font></b></strong><font
size=3D2 face=3D"Arial Unicode MS"><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:"Arial Unicode MS"'><br>
<st1:City w:st=3D"on"><st1:place =
w:st=3D"on">Mobile</st1:place></st1:City>&nbsp; :
+90 532 210 1883 <br>
Office&nbsp;&nbsp; : +90 216 458 2427 <br>
Fax &nbsp;&nbsp; &nbsp; : +90 216 427 5141 <br>
e-mail&nbsp;&nbsp; : bulent.yilmaz@turkcell.com.tr </span></font><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<p></p><p><br><A =
HREF=3D"http://www.turkcell.com.tr/index/0,1027,3119,00.html" ><IMG =
border=3D"0" =
SRC=3D"http://www.turkcell.com.tr/mailbanner/gprsoutgoingbanner.gif"></A>=
</br></p><font face=3D"Times New Roman" size=3D"2"> <p> =
*********************************************************************** =
</p>  <p> Bu elektronik posta ve onunla iletilen b=FCt=FCn dosyalar =
sadece g=F6ndericisi taraf=FDndan almas=FD ama=E7lanan yetkili ger=E7ek =
ya da t=FCzel ki=FEinin kullan=FDm=FD i=E7indir.E=F0er s=F6z konusu =
yetkili al=FDc=FD de=F0ilseniz bu elektronik postan=FDn i=E7eri=F0ini =
a=E7=FDklaman=FDz,kopyalaman=FDz, y=F6nlendirmeniz ve kullanman=FDz =
kesinlikle yasakt=FDr ve bu elektronik postay=FD derhal silmeniz =
gerekmektedir.</p> <p>TURKCELL bu mesaj=FDn i=E7erdi=F0i bilgilerin =
do=F0rulu=F0u veya eksiksiz oldu=F0u konusunda herhangi bir garanti =
vermemektedir. Bu nedenle bu bilgilerin ne =FEekilde olursa olsun =
i=E7eri=F0inden, iletilmesinden, al=FDnmas=FDndan ve saklanmas=FDndan =
sorumlu de=F0ildir. Bu mesajdaki g=F6r=FC=FEler yaln=FDzca g=F6nderen =
ki=FEiye aittir ve TURKCELL'in g=F6r=FC=FElerini yans=FDtmayabilir.</p> =
<p>Bu e-posta bilinen b=FCt=FCn bilgisayar vir=FCslerine kar=FE=FD =
taranm=FD=FEt=FDr.</p> =
<p>**********************************************************************=
**</p> <p>This e-mail and any files transmitted with it are confidential =
and	intended solely for the use of the individual or entity to whom they =
are addressed. If you are not the intended recipient you are hereby =
notified that any dissemination, forwarding, copying or use of any of =
the information is strictly prohibited, and the e-mail should =
immediately be deleted.</p> <p>TURKCELL makes no warranty as to the =
accuracy or completeness of any information contained in this message =
and hereby excludes any liability of any kind for the information =
contained therein or for the information transmission, reception, =
storage or use of such in any way whatsoever.The opinions expressed in =
this message belong to sender alone and may not necessarily reflect the =
opinions of TURKCELL.</p> <p>This e-mail has been scanned for all known =
computer viruses.</p> =
<p>**********************************************************************=
**</p> </font></body>

</html>

------_=_NextPart_001_01C41BB1.6C548295--

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



From exim@www1.ietf.org  Tue Apr  6 08:24:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10198
	for <sigtran-archive@odin.ietf.org>; Tue, 6 Apr 2004 08:24:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BApca-0007ZI-Il
	for sigtran-archive@odin.ietf.org; Tue, 06 Apr 2004 08:24:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i36CO4so029070
	for sigtran-archive@odin.ietf.org; Tue, 6 Apr 2004 08:24:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BApcY-0007Yb-Dn; Tue, 06 Apr 2004 08:24:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BApcB-0007LP-66
	for sigtran@optimus.ietf.org; Tue, 06 Apr 2004 08:23:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10110
	for <sigtran@ietf.org>; Tue, 6 Apr 2004 08:23:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BApcA-00027D-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 08:23:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BApFa-0006p4-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 08:00:19 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[08I8N2f8fs84SJbTD/FmktB2hiYHvMcS])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAonx-0003gG-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 07:31:45 -0400
Received: from ns.pigworks.openss7.net (IDENT:z3NLvsV43dr8Wkrx7L8XzfFcTVOfKii9@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i36BVhI31990;
	Tue, 6 Apr 2004 05:31:43 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i36BVhY17623;
	Tue, 6 Apr 2004 05:31:43 -0600
Date: Tue, 6 Apr 2004 05:31:42 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: bulent.yilmaz@turkcell.com.tr
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Header lengths of the protocols ...
Message-ID: <20040406053142.A17374@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: bulent.yilmaz@turkcell.com.tr, sigtran@ietf.org
References: <ACE5644D97D0124AAB3D466F33B159BE06CFDCDC@exh3410.turkcell.entp.tgc>
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: <ACE5644D97D0124AAB3D466F33B159BE06CFDCDC@exh3410.turkcell.entp.tgc>; from bulent.yilmaz@turkcell.com.tr on Tue, Apr 06, 2004 at 11:30:29AM +0300
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 i36BVhI31990
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

bulent.yilmaz,

bulent.yilmaz@turkcell.com.tr wrote:                                     =
    (Tue, 06 Apr 2004 11:30:29)
>=20
>    Dear Experts,
>=20
>=20
>    Would you please provide me header lengths of each SIGTRAN (SUA, M3U=
A,
>    M2PA and SCTP) protocol?
>=20
>=20
>    I also would be glad if any of you could direct me to a resource whe=
re
>    I can get that information.

SUA:	ftp://ftp.ietf.org/internet-drafts/draft-ietf-sigtran-sua-16.txt
M3UA:	ftp://ftp.ietf.org/rfc/rfc3332.txt
M2PA:	ftp://ftp.ietf.org/internet-drafts/draft-ietf-sigtran-m2pa-11.txt
SCTP:	ftp://ftp.ietf.org/rfc/rfc2960.txt

--brian

>=20
>=20
>    Regards,
>=20
>=20
>    B=FClent YILMAZ

--=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 Apr  6 14:33:54 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15526
	for <sigtran-archive@odin.ietf.org>; Tue, 6 Apr 2004 14:33:54 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAvO3-0003Jz-3U
	for sigtran-archive@odin.ietf.org; Tue, 06 Apr 2004 14:33:27 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i36IXRQI012754
	for sigtran-archive@odin.ietf.org; Tue, 6 Apr 2004 14:33:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAvNh-0002oq-Tm; Tue, 06 Apr 2004 14:33:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAtIV-00061B-A6
	for sigtran@optimus.ietf.org; Tue, 06 Apr 2004 12:19:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27289
	for <sigtran@ietf.org>; Tue, 6 Apr 2004 11:18:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAsLe-00008W-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 11:18:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAs1u-0004ib-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 10:58:23 -0400
Received: from us-wkf-fwmain.comverse.com ([63.64.185.250] helo=us-wkf-interscan1.comverse.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BArZk-0001Fi-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 10:29:16 -0400
Received: from mail-in.comverse.com (localhost.localdomain [127.0.0.1])
	by us-wkf-interscan1.comverse.com (8.11.6/8.11.6) with ESMTP id i36ETF423839
	for <sigtran@ietf.org>; Tue, 6 Apr 2004 10:29:15 -0400
Received: by mail-in.comverse.com with Internet Mail Service (5.5.2657.72)
	id <2DC5TZDW>; Tue, 6 Apr 2004 10:21:59 -0400
Message-ID: <6B1DF6EEBA51D31182F20090274043680B6E77B6@mail-in.comverse.com>
From: Hecht Martin <Martin.Hecht@comverse.com>
To: "SIGTRAN Mailing List (E-mail)" <sigtran@ietf.org>
Subject: [SIGTRAN] M2PA - Local Processor Outage/Processor Recovered Proce
	ssing
Date: Tue, 6 Apr 2004 10:21:58 -0400 
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=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>

To interested M2PA parties,

I have a couple of questions concerning LPO/RPO, LPR/RPR in accordance with
draft-ietf-sigtran-m2pa-11.

I can see the basic relationship between the MTP-2 and M2PA processing of
the Processor Outage conditions.  In MTP-2 there is a short and a long RPO
condition; while in M2PA there is only RPO.

In MTP-2 RPO ends when a FISU or MSU is received; all messages in the TB and
RTB are deleted and the FSN is "reset" at that point, i.e.,
resynchronization occurs.  I can see how this is "mapped" to M2PA.

What I don't see is, referring to pg. 40:

While in LPO, A must buffer messages 14-16 without acknowledging them.

While in RPO, B may continue acknowledging messages.

LPO ends at A.  A flushes 14-16 (the messages that were buffered without
acknowledgement).

Why are 14-16 flushed?  Why were they buffered in the first place?

This means that 14-16 are lost.

On pg. 41:

B flushes 6 from its Receive Buffer.

Why is this buffer flushed?

This means that buffer 6 is lost.

Thanks,
Martin Hecht
Signaling Core Group, Embedded Division
Comverse, Inc


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



From exim@www1.ietf.org  Tue Apr  6 18:46:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07052
	for <sigtran-archive@odin.ietf.org>; Tue, 6 Apr 2004 18:46:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAzKV-0007Jw-Jz
	for sigtran-archive@odin.ietf.org; Tue, 06 Apr 2004 18:46:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i36Mk3ej028141
	for sigtran-archive@odin.ietf.org; Tue, 6 Apr 2004 18:46:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAzKT-0007JV-5X; Tue, 06 Apr 2004 18:46:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAzJs-0007IO-DN
	for sigtran@optimus.ietf.org; Tue, 06 Apr 2004 18:45:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06997
	for <sigtran@ietf.org>; Tue, 6 Apr 2004 18:45:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAzJp-0005wT-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 18:45:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAyNc-0006ok-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 17:45:13 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[P0WGZMecmwmvlyq58qtYwEZfg6A8M8A6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAxa9-0000EV-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 16:54:05 -0400
Received: from ns.pigworks.openss7.net (IDENT:dmdDd7hrsNEnceT7g2VzKibLgCqxobxh@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i36Ks5I09604;
	Tue, 6 Apr 2004 14:54:05 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i36Ks4G24093;
	Tue, 6 Apr 2004 14:54:04 -0600
Date: Tue, 6 Apr 2004 14:54:04 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Hecht Martin <Martin.Hecht@comverse.com>
Cc: "SIGTRAN Mailing List (E-mail)" <sigtran@ietf.org>
Subject: Re: [SIGTRAN] M2PA - Local Processor Outage/Processor Recovered Proce ssing
Message-ID: <20040406145404.A23407@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Hecht Martin <Martin.Hecht@comverse.com>,
	"SIGTRAN Mailing List (E-mail)" <sigtran@ietf.org>
References: <6B1DF6EEBA51D31182F20090274043680B6E77B6@mail-in.comverse.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: <6B1DF6EEBA51D31182F20090274043680B6E77B6@mail-in.comverse.com>; from Martin.Hecht@comverse.com on Tue, Apr 06, 2004 at 10:21:58AM -0400
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>

Hecht,

Hecht Martin wrote:                                                                  (Tue, 06 Apr 2004 10:21:58)
> To interested M2PA parties,
> 
> I have a couple of questions concerning LPO/RPO, LPR/RPR in accordance with
> draft-ietf-sigtran-m2pa-11.
> 
> I can see the basic relationship between the MTP-2 and M2PA processing of
> the Processor Outage conditions.  In MTP-2 there is a short and a long RPO
> condition; while in M2PA there is only RPO.

Q.703 (MTP2) does not have a short and long RPO concept.  Q.704 (MTP3) has a
short and long RPO concept.

> 
> In MTP-2 RPO ends when a FISU or MSU is received; all messages in the TB and
> RTB are deleted and the FSN is "reset" at that point, i.e.,
> resynchronization occurs.  I can see how this is "mapped" to M2PA.
> 
> What I don't see is, referring to pg. 40:
> 
> While in LPO, A must buffer messages 14-16 without acknowledging them.
> 
> While in RPO, B may continue acknowledging messages.
> 
> LPO ends at A.  A flushes 14-16 (the messages that were buffered without
> acknowledgement).
> 
> Why are 14-16 flushed?  Why were they buffered in the first place?

In the example, processor outage is of long term at A, and MTP3 flushes the
messages.  If processor outage were of short term, they would not be flushed.

> 
> This means that 14-16 are lost.

Not necessarily.  Because these messages are not acknowledged to B from A, B
will retransmit these messages on another link as part of the normal
changeover procedure, providing that B does not consider the outage to be of
long term.  If B also considers the outage to be of long term, it will flush
these messages from its RTB.

> 
> On pg. 41:
> 
> B flushes 6 from its Receive Buffer.
> 
> Why is this buffer flushed?

For the same reason as above.  When MTP3 at A flushes buffers it flushes RB,
TB and RTB.

> 
> This means that buffer 6 is lost.

Not necessarily, because it was not acknowledged, it could be retransmitted
on another link (processor outage short term) or intentionally flushed
(processor outage long term).

Consider that whether processor outage is of long term or short term is
determined by MTP3 using timer T1 at Level 3, not Level 2.  The example is
one where Q.704/T1 expires at A.

--brian

> 
> Thanks,
> Martin Hecht
> Signaling Core Group, Embedded Division
> Comverse, Inc
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Tue Apr  6 19:20:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08897
	for <sigtran-archive@odin.ietf.org>; Tue, 6 Apr 2004 19:20:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAzrQ-0005XZ-3d
	for sigtran-archive@odin.ietf.org; Tue, 06 Apr 2004 19:20:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i36NK41b021298
	for sigtran-archive@odin.ietf.org; Tue, 6 Apr 2004 19:20:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAzrN-0005X9-Ut; Tue, 06 Apr 2004 19:20:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAzqz-0005W3-P6
	for sigtran@optimus.ietf.org; Tue, 06 Apr 2004 19:19:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08886
	for <sigtran@ietf.org>; Tue, 6 Apr 2004 19:19:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAzqy-0001Nc-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 19:19:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAygp-00026M-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 18:05:04 -0400
Received: from us-wkf-fwmain.comverse.com ([63.64.185.250] helo=us-wkf-interscan1.comverse.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAy3T-0003DP-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 17:24:23 -0400
Received: from mail-in.comverse.com (localhost.localdomain [127.0.0.1])
	by us-wkf-interscan1.comverse.com (8.11.6/8.11.6) with ESMTP id i36LOKr04414;
	Tue, 6 Apr 2004 17:24:21 -0400
Received: by mail-in.comverse.com with Internet Mail Service (5.5.2657.72)
	id <2DC5TZLX>; Tue, 6 Apr 2004 17:17:04 -0400
Message-ID: <6B1DF6EEBA51D31182F20090274043680B6E77B8@mail-in.comverse.com>
From: Hecht Martin <Martin.Hecht@comverse.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: "SIGTRAN Mailing List (E-mail)" <sigtran@ietf.org>
Subject: RE: [SIGTRAN] M2PA - Local Processor Outage/Processor Recovered P
	rocessing
Date: Tue, 6 Apr 2004 17:17:03 -0400 
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=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>

Brian,

You are, of course, correct that the concept of Long and Short RPO is MTP-3,
it is just that in our implementation MTP-2 is somewhat aware of whether the
RPO is short or long. As my questions involved LPO and RPO I thought that
this was pertinent.

As I understand your response, when the diagrams in the draft (pgs 40 and
41) refer to a flush taking place, they are referring to a flush initiated
by L3, not by M2PA.

Is this correct?

Thus, if the inbound messages are buffered during LPO, and there is no flush
request from L3, then those buffers will be processed.  The same thing
basically on the RPO side.

Correct?

Thank you for your response,

Martin Hecht
Signaling Core Group, Embedded Division
Comverse, Inc

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: Tuesday, April 06, 2004 4:54 PM
To: Hecht Martin
Cc: SIGTRAN Mailing List (E-mail)
Subject: Re: [SIGTRAN] M2PA - Local Processor Outage/Processor Recovered
Proce ssing


Hecht,

Hecht Martin wrote:
(Tue, 06 Apr 2004 10:21:58)
> To interested M2PA parties,
> 
> I have a couple of questions concerning LPO/RPO, LPR/RPR in accordance
with
> draft-ietf-sigtran-m2pa-11.
> 
> I can see the basic relationship between the MTP-2 and M2PA processing of
> the Processor Outage conditions.  In MTP-2 there is a short and a long RPO
> condition; while in M2PA there is only RPO.

Q.703 (MTP2) does not have a short and long RPO concept.  Q.704 (MTP3) has a
short and long RPO concept.

> 
> In MTP-2 RPO ends when a FISU or MSU is received; all messages in the TB
and
> RTB are deleted and the FSN is "reset" at that point, i.e.,
> resynchronization occurs.  I can see how this is "mapped" to M2PA.
> 
> What I don't see is, referring to pg. 40:
> 
> While in LPO, A must buffer messages 14-16 without acknowledging them.
> 
> While in RPO, B may continue acknowledging messages.
> 
> LPO ends at A.  A flushes 14-16 (the messages that were buffered without
> acknowledgement).
> 
> Why are 14-16 flushed?  Why were they buffered in the first place?

In the example, processor outage is of long term at A, and MTP3 flushes the
messages.  If processor outage were of short term, they would not be
flushed.

> 
> This means that 14-16 are lost.

Not necessarily.  Because these messages are not acknowledged to B from A, B
will retransmit these messages on another link as part of the normal
changeover procedure, providing that B does not consider the outage to be of
long term.  If B also considers the outage to be of long term, it will flush
these messages from its RTB.

> 
> On pg. 41:
> 
> B flushes 6 from its Receive Buffer.
> 
> Why is this buffer flushed?

For the same reason as above.  When MTP3 at A flushes buffers it flushes RB,
TB and RTB.

> 
> This means that buffer 6 is lost.

Not necessarily, because it was not acknowledged, it could be retransmitted
on another link (processor outage short term) or intentionally flushed
(processor outage long term).

Consider that whether processor outage is of long term or short term is
determined by MTP3 using timer T1 at Level 3, not Level 2.  The example is
one where Q.704/T1 expires at A.

--brian

> 
> Thanks,
> Martin Hecht
> Signaling Core Group, Embedded Division
> Comverse, Inc
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
______________________________________________________________________
  This email message has been scanned by PineApp Mail-Secure and has been
found clean.

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



From exim@www1.ietf.org  Tue Apr  6 20:53:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17637
	for <sigtran-archive@odin.ietf.org>; Tue, 6 Apr 2004 20:53:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BB1JQ-00038r-R8
	for sigtran-archive@odin.ietf.org; Tue, 06 Apr 2004 20:53:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i370r4mn012078
	for sigtran-archive@odin.ietf.org; Tue, 6 Apr 2004 20:53:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BB1JM-00038U-So; Tue, 06 Apr 2004 20:53:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BB1JB-00038A-1f
	for sigtran@optimus.ietf.org; Tue, 06 Apr 2004 20:52:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17614
	for <sigtran@ietf.org>; Tue, 6 Apr 2004 20:52:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BB1J8-0004Xt-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 20:52:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BB0Fm-0005FM-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 19:45:17 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[ySgVbLjeNk4eOKSbR2yMnoBs65bnN1Ac])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAzQG-0006WJ-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 18:52:00 -0400
Received: from ns.pigworks.openss7.net (IDENT:lEODamPZ3J912Ohhbl8qQlk2bX4QDOew@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i36MpsI11582;
	Tue, 6 Apr 2004 16:51:54 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i36MpsH25797;
	Tue, 6 Apr 2004 16:51:54 -0600
Date: Tue, 6 Apr 2004 16:51:53 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Hecht Martin <Martin.Hecht@comverse.com>
Cc: "SIGTRAN Mailing List (E-mail)" <sigtran@ietf.org>
Subject: Re: [SIGTRAN] M2PA - Local Processor Outage/Processor Recovered P rocessing
Message-ID: <20040406165153.A25345@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Hecht Martin <Martin.Hecht@comverse.com>,
	"SIGTRAN Mailing List (E-mail)" <sigtran@ietf.org>
References: <6B1DF6EEBA51D31182F20090274043680B6E77B8@mail-in.comverse.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: <6B1DF6EEBA51D31182F20090274043680B6E77B8@mail-in.comverse.com>; from Martin.Hecht@comverse.com on Tue, Apr 06, 2004 at 05:17:03PM -0400
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>

Hecht,

Hecht Martin wrote:                                                                  (Tue, 06 Apr 2004 17:17:03)
> Brian,
> 
> You are, of course, correct that the concept of Long and Short RPO is MTP-3,
> it is just that in our implementation MTP-2 is somewhat aware of whether the
> RPO is short or long. As my questions involved LPO and RPO I thought that
> this was pertinent.

M2PA is specifies with the traditional L2/L3 split.  If your implementation of
MTP2 includes partial MTP3 functionality (as is often done with dedicated
link equipment) your M2PA implementation could either incorporate this partial
L3  or the partial L3 could be layerd on top of M2PA.

> 
> As I understand your response, when the diagrams in the draft (pgs 40 and
> 41) refer to a flush taking place, they are referring to a flush initiated
> by L3, not by M2PA.
> 
> Is this correct?

Yes.  Even though the signal to flush might be coming from a partial L3
implemented in the link entity, it is still coming from L3 and not M2PA.

> 
> Thus, if the inbound messages are buffered during LPO, and there is no flush
> request from L3, then those buffers will be processed.  The same thing
> basically on the RPO side.
> 
> Correct?

Yes.  Same as the LPO side.

--brian

> 
> Thank you for your response,
> 
> Martin Hecht
> Signaling Core Group, Embedded Division
> Comverse, Inc
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Tuesday, April 06, 2004 4:54 PM
> To: Hecht Martin
> Cc: SIGTRAN Mailing List (E-mail)
> Subject: Re: [SIGTRAN] M2PA - Local Processor Outage/Processor Recovered
> Proce ssing
> 
> 
> Hecht,
> 
> Hecht Martin wrote:
> (Tue, 06 Apr 2004 10:21:58)
> > To interested M2PA parties,
> > 
> > I have a couple of questions concerning LPO/RPO, LPR/RPR in accordance
> with
> > draft-ietf-sigtran-m2pa-11.
> > 
> > I can see the basic relationship between the MTP-2 and M2PA processing of
> > the Processor Outage conditions.  In MTP-2 there is a short and a long RPO
> > condition; while in M2PA there is only RPO.
> 
> Q.703 (MTP2) does not have a short and long RPO concept.  Q.704 (MTP3) has a
> short and long RPO concept.
> 
> > 
> > In MTP-2 RPO ends when a FISU or MSU is received; all messages in the TB
> and
> > RTB are deleted and the FSN is "reset" at that point, i.e.,
> > resynchronization occurs.  I can see how this is "mapped" to M2PA.
> > 
> > What I don't see is, referring to pg. 40:
> > 
> > While in LPO, A must buffer messages 14-16 without acknowledging them.
> > 
> > While in RPO, B may continue acknowledging messages.
> > 
> > LPO ends at A.  A flushes 14-16 (the messages that were buffered without
> > acknowledgement).
> > 
> > Why are 14-16 flushed?  Why were they buffered in the first place?
> 
> In the example, processor outage is of long term at A, and MTP3 flushes the
> messages.  If processor outage were of short term, they would not be
> flushed.
> 
> > 
> > This means that 14-16 are lost.
> 
> Not necessarily.  Because these messages are not acknowledged to B from A, B
> will retransmit these messages on another link as part of the normal
> changeover procedure, providing that B does not consider the outage to be of
> long term.  If B also considers the outage to be of long term, it will flush
> these messages from its RTB.
> 
> > 
> > On pg. 41:
> > 
> > B flushes 6 from its Receive Buffer.
> > 
> > Why is this buffer flushed?
> 
> For the same reason as above.  When MTP3 at A flushes buffers it flushes RB,
> TB and RTB.
> 
> > 
> > This means that buffer 6 is lost.
> 
> Not necessarily, because it was not acknowledged, it could be retransmitted
> on another link (processor outage short term) or intentionally flushed
> (processor outage long term).
> 
> Consider that whether processor outage is of long term or short term is
> determined by MTP3 using timer T1 at Level 3, not Level 2.  The example is
> one where Q.704/T1 expires at A.
> 
> --brian
> 
> > 
> > Thanks,
> > Martin Hecht
> > Signaling Core Group, Embedded Division
> > Comverse, Inc
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> ______________________________________________________________________
>   This email message has been scanned by PineApp Mail-Secure and has been
> found clean.

-- 
Brian 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 Apr  6 21:14:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18719
	for <sigtran-archive@odin.ietf.org>; Tue, 6 Apr 2004 21:14:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BB1di-0006lL-FT
	for sigtran-archive@odin.ietf.org; Tue, 06 Apr 2004 21:14:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i371E222025993
	for sigtran-archive@odin.ietf.org; Tue, 6 Apr 2004 21:14:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BB1dh-0006l0-Hk; Tue, 06 Apr 2004 21:14:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BB1df-0006kb-1B
	for sigtran@optimus.ietf.org; Tue, 06 Apr 2004 21:13:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18671
	for <sigtran@ietf.org>; Tue, 6 Apr 2004 21:13:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BB1dc-0006fw-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 21:13:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BB0S2-0007HO-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 19:57:55 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[VKbaP3HGBmxvsvO8g3eYoOosN6INpXXM])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAzir-0000bn-00
	for sigtran@ietf.org; Tue, 06 Apr 2004 19:11:13 -0400
Received: from ns.pigworks.openss7.net (IDENT:xaIwwFEH5hcw5YRfWS9itP/ik3+AZsJI@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i36NBDI11998;
	Tue, 6 Apr 2004 17:11:13 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i36NBDU26428;
	Tue, 6 Apr 2004 17:11:13 -0600
Date: Tue, 6 Apr 2004 17:11:12 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Hecht Martin <Martin.Hecht@comverse.com>
Cc: "SIGTRAN Mailing List (E-mail)" <sigtran@ietf.org>
Subject: Re: [SIGTRAN] M2PA - Local Processor Outage/Processor Recovered P rocessing
Message-ID: <20040406171112.B25345@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Hecht Martin <Martin.Hecht@comverse.com>,
	"SIGTRAN Mailing List (E-mail)" <sigtran@ietf.org>
References: <6B1DF6EEBA51D31182F20090274043680B6E77B8@mail-in.comverse.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: <6B1DF6EEBA51D31182F20090274043680B6E77B8@mail-in.comverse.com>; from Martin.Hecht@comverse.com on Tue, Apr 06, 2004 at 05:17:03PM -0400
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>

Hecht,

You might also take a look at test case 3.4.1 in

  http://www.ietf.org/internet-drafts/draft-bidulock-sigtran-m2pa-test-05.txt

as it describes the L3->L2 primitives in more detail.

Actaully, I had to resubmit m2pa-test-05 because it was sumbitted during
the last cut-off.  Until it appears, you can get it here:

  http://www.openss7.org/docs/draft-bidulock-sigtran-m2pa-test-05.txt

Which brings up another note, perhaps it would be a good idea to advance this
test specification to on INFORMATIONAL RFC on the tail of M2PA.

Comments?

--brian

Hecht Martin wrote:                                 (Tue, 06 Apr 2004 17:17:03)
> Brian,
> 
> You are, of course, correct that the concept of Long and Short RPO is MTP-3,
> it is just that in our implementation MTP-2 is somewhat aware of whether the
> RPO is short or long. As my questions involved LPO and RPO I thought that
> this was pertinent.
> 
> As I understand your response, when the diagrams in the draft (pgs 40 and
> 41) refer to a flush taking place, they are referring to a flush initiated
> by L3, not by M2PA.
> 
> Is this correct?
> 
> Thus, if the inbound messages are buffered during LPO, and there is no flush
> request from L3, then those buffers will be processed.  The same thing
> basically on the RPO side.
> 
> Correct?
> 
> Thank you for your response,
> 
> Martin Hecht
> Signaling Core Group, Embedded Division
> Comverse, Inc
> 

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

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



From exim@www1.ietf.org  Wed Apr  7 08:45:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17199
	for <sigtran-archive@odin.ietf.org>; Wed, 7 Apr 2004 08:45:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BBCQW-00009R-IQ
	for sigtran-archive@odin.ietf.org; Wed, 07 Apr 2004 08:45:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i37Cj874000560
	for sigtran-archive@odin.ietf.org; Wed, 7 Apr 2004 08:45:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BBCQO-00006e-VX; Wed, 07 Apr 2004 08:45:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BBCQ4-00005x-JZ
	for sigtran@optimus.ietf.org; Wed, 07 Apr 2004 08:44:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17170
	for <sigtran@ietf.org>; Wed, 7 Apr 2004 08:44:38 -0400 (EDT)
From: joyce_archibald@agilent.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BBCQ3-0007PA-00
	for sigtran@ietf.org; Wed, 07 Apr 2004 08:44:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BBBJy-0007TR-00
	for sigtran@ietf.org; Wed, 07 Apr 2004 07:34:19 -0400
Received: from msgbas1x.net.europe.agilent.com ([192.25.19.109])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BBAAs-00078X-00
	for sigtran@ietf.org; Wed, 07 Apr 2004 06:20:50 -0400
Received: from msgrel1.germany.agilent.com (msgrel1.germany.agilent.com [134.40.2.57])
	by msgbas1x.net.europe.agilent.com (Postfix) with ESMTP id A7C0F2FC3
	for <sigtran@ietf.org>; Wed,  7 Apr 2004 12:20:45 +0200 (METDST)
Received: from wbbnbh01.germany.agilent.com (wbbnbh01.germany.agilent.com [134.40.35.19])
	by msgrel1.germany.agilent.com (Postfix) with ESMTP id 96CF125
	for <sigtran@ietf.org>; Wed,  7 Apr 2004 12:20:45 +0200 (METDST)
Received: from wbbnmb01.germany.agilent.com ([134.40.35.18]) by wbbnbh01.germany.agilent.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 7 Apr 2004 12:20:45 +0200
Received: from wsqfmb21.britain.agilent.com ([156.141.51.130]) by wbbnmb01.germany.agilent.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 7 Apr 2004 12:20:45 +0200
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 7 Apr 2004 11:20:44 +0100
Message-ID: <C0E791D3157A0749BB9950FADC61171C279CF2@wsqfmb21b.britain.agilent.com>
Thread-Topic: SUAv16: Query on syntax of Hostname
Thread-Index: AcQcifxzt0fFiKWmQHyu3XGAu8a15g==
To: <sigtran@ietf.org>
X-OriginalArrivalTime: 07 Apr 2004 10:20:45.0459 (UTC) FILETIME=[FD09C630:01C41C89]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Subject: [Sigtran] SUAv16: Query on syntax of Hostname
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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

In Section 3.10.2.7 Hostname it states:

This field contains a host name in "host name syntax" per RFC 1123 =
Section 2.1.

RFC 1123 Section 2.1 refers to RFC 952 which states:

   A "name" (Net, Host, Gateway, or Domain name) is a text string up
   to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus
   sign (-), and period (.).  Note that periods are only allowed when
   they serve to delimit components of "domain style names".=20

RFC 1123 later refers to RFC 1035 which states:

Domain names in messages are expressed in terms of a sequence of labels.
Each label is represented as a one octet length field followed by that
number of octets.=20

So, which syntax is used in SUA messages?

Thanks,
Joyce

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



From exim@www1.ietf.org  Tue Apr 13 07:42:45 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06687
	for <sigtran-archive@odin.ietf.org>; Tue, 13 Apr 2004 07:42:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDMIx-0001Xh-0m
	for sigtran-archive@odin.ietf.org; Tue, 13 Apr 2004 07:42:16 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3DBgEBL005921
	for sigtran-archive@odin.ietf.org; Tue, 13 Apr 2004 07:42:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDMIk-0001X6-Of; Tue, 13 Apr 2004 07:42:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDMIc-0001WR-NV
	for sigtran@optimus.ietf.org; Tue, 13 Apr 2004 07:41:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06618
	for <sigtran@ietf.org>; Tue, 13 Apr 2004 07:41:52 -0400 (EDT)
From: bulent.yilmaz@turkcell.com.tr
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDMIa-0001wq-00
	for sigtran@ietf.org; Tue, 13 Apr 2004 07:41:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDMFh-0001kW-00
	for sigtran@ietf.org; Tue, 13 Apr 2004 07:38:54 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDMEJ-0001Uz-00
	for sigtran@ietf.org; Tue, 13 Apr 2004 07:37:28 -0400
Received: from [212.252.168.230] (helo=tplmalsmtp.turkcell.com.tr)
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1BDM0x-0005u1-2C
	for sigtran@ietf.org; Tue, 13 Apr 2004 07:23:39 -0400
Received: from exh3415.turkcell.entp.tgc ([10.200.250.156]) by tcexi3401.turkcell.entp.tgc with Microsoft SMTPSVC(6.0.3790.0); Tue, 13 Apr 2004 14:22:57 +0300
Received: from exh3410.turkcell.entp.tgc ([10.200.251.99]) by exh3415.turkcell.entp.tgc with Microsoft SMTPSVC(6.0.3790.0); Tue, 13 Apr 2004 14:22:41 +0300
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-Transfer-Encoding: 7bit
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Importance: normal
Priority: normal
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C42149.A37670C9"
Date: Tue, 13 Apr 2004 14:22:40 +0300
Message-ID: <ACE5644D97D0124AAB3D466F33B159BE06EFD009@exh3410.turkcell.entp.tgc>
Thread-Topic: M3UA for peer-to-peer ?
thread-index: AcQhSaIF2QHxOAbnRwiXvZexx2jp7Q==
To: <sigtran@ietf.org>
X-OriginalArrivalTime: 13 Apr 2004 11:22:41.0502 (UTC) FILETIME=[A2736FE0:01C42149]
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=AWL,HTML_40_50,HTML_MESSAGE,
	NO_REAL_NAME autolearn=no version=2.60
Subject: [Sigtran] M3UA for peer-to-peer ?
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C42149.A37670C9
Content-Type: text/plain;
	charset="iso-8859-9"
Content-Transfer-Encoding: quoted-printable

Dear Experts,

=20

Is there anyone that could explain the situation of M3UA protocol =
definitions for peer-to-peer communication, e.g. between 2 SGs ?=20

=20

Is it going to be  standart ? and how much it provides similar M2PA-like =
functions for peer-to-peer case or is it the main reason (to compete =
against M2PA or to provide M2PA-like functions) for why M3UA =
peer-to-peer is being drafted ?

=20

Regards,

=20

B=FClent YILMAZ=20
TURKCELL=20
TO / Coordination Office

New Technologies
Mobile  : +90 532 210 1883=20
Office   : +90 216 458 2427=20
Fax      : +90 216 427 5141=20
e-mail   : bulent.yilmaz@turkcell.com.tr=20

=20



***********************************************************************
Bu elektronik posta ve onunla iletilen b=FCt=FCn dosyalar sadece =
g=F6ndericisi taraf=FDndan almas=FD ama=E7lanan yetkili ger=E7ek ya da =
t=FCzel ki=FEinin kullan=FDm=FD i=E7indir.E=F0er s=F6z konusu yetkili =
al=FDc=FD de=F0ilseniz bu elektronik postan=FDn i=E7eri=F0ini =
a=E7=FDklaman=FDz,kopyalaman=FDz, y=F6nlendirmeniz ve kullanman=FDz =
kesinlikle yasakt=FDr ve bu elektronik postay=FD derhal silmeniz =
gerekmektedir
TURKCELL bu mesaj=FDn i=E7erdi=F0i bilgilerin do=F0rulu=F0u veya =
eksiksiz oldu=F0u konusunda herhangi bir garanti vermemektedir. Bu =
nedenle bu bilgilerin ne =FEekilde olursa olsun i=E7eri=F0inden, =
iletilmesinden, al=FDnmas=FDndan ve saklanmas=FDndan sorumlu de=F0ildir. =
Bu mesajdaki g=F6r=FC=FEler yaln=FDzca g=F6nderen ki=FEiye aittir ve =
TURKCELL'in g=F6r=FC=FElerini yans=FDtmayabilir
Bu e-posta bilinen b=FCt=FCn bilgisayar vir=FCslerine kar=FE=FD =
taranm=FD=FEt=FDr.
***********************************************************************
This e-mail and any files transmitted with it are confidential and =
intended solely for the use of the individual or entity to whom they are =
addressed. If you are not the intended recipient you are hereby notified =
that any dissemination, forwarding, copying or use of any of the =
information is strictly prohibited, and the e-mail should immediately be =
deleted.
TURKCELL makes no warranty as to the accuracy or completeness of any =
information contained in this message and hereby excludes any liability =
of any kind for the information contained therein or for the information =
transmission, reception, storage or use of such in any way =
whatsoever.The opinions expressed in this message belong to sender alone =
and may not necessarily reflect the opinions of TURKCELL.
This e-mail has been scanned for all known computer viruses.
***********************************************************************

------_=_NextPart_001_01C42149.A37670C9
Content-Type: text/html;
	charset="iso-8859-9"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-9">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"\@Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:#606420;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DTR link=3Dblue vlink=3D"#606420">

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Dear Experts,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Is there anyone that could explain the =
situation of
M3UA protocol definitions for peer-to-peer communication, e.g. between 2 =
SGs ? <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Is it going to be  standart ? and how much it
provides similar M2PA-like functions for peer-to-peer case or is it the =
main
reason (to compete against M2PA or to provide M2PA-like functions) for =
why M3UA
peer-to-peer is being drafted ?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Arial Unicode MS"><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:"Arial Unicode MS"'>B=FClent =
YILMAZ <br>
</span></font><strong><b><font face=3D"Arial Unicode MS"><span =
lang=3DEN-US
style=3D'font-family:"Arial Unicode =
MS"'>TURKCELL</span></font></b></strong><font
face=3D"Arial Unicode MS"><span lang=3DEN-US style=3D'font-family:"Arial =
Unicode MS"'>
</span></font><font size=3D2 face=3D"Arial Unicode MS"><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:"Arial Unicode MS"'><br>
<strong><b><font face=3D"Arial Unicode MS"><span =
style=3D'font-family:"Arial Unicode MS"'>TO&nbsp;/
Coordination Office</span></font></b></strong></span></font><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal><strong><b><font size=3D2 face=3D"Arial Unicode =
MS"><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Arial Unicode =
MS"'>New Technologies</span></font></b></strong><font
size=3D2 face=3D"Arial Unicode MS"><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:"Arial Unicode MS"'><br>
<st1:City w:st=3D"on"><st1:place =
w:st=3D"on">Mobile</st1:place></st1:City>&nbsp; :
+90 532 210 1883 <br>
Office&nbsp;&nbsp; : +90 216 458 2427 <br>
Fax &nbsp;&nbsp; &nbsp; : +90 216 427 5141 <br>
e-mail&nbsp;&nbsp; : bulent.yilmaz@turkcell.com.tr </span></font><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<p></p><p><br><A =
HREF=3D"http://www.turkcell.com.tr/index/0,1027,3119,00.html" ><IMG =
border=3D"0" =
SRC=3D"http://www.turkcell.com.tr/mailbanner/gprsoutgoingbanner.gif"></A>=
</br></p><font face=3D"Times New Roman" size=3D"2"> <p> =
*********************************************************************** =
</p>  <p> Bu elektronik posta ve onunla iletilen b=FCt=FCn dosyalar =
sadece g=F6ndericisi taraf=FDndan almas=FD ama=E7lanan yetkili ger=E7ek =
ya da t=FCzel ki=FEinin kullan=FDm=FD i=E7indir.E=F0er s=F6z konusu =
yetkili al=FDc=FD de=F0ilseniz bu elektronik postan=FDn i=E7eri=F0ini =
a=E7=FDklaman=FDz,kopyalaman=FDz, y=F6nlendirmeniz ve kullanman=FDz =
kesinlikle yasakt=FDr ve bu elektronik postay=FD derhal silmeniz =
gerekmektedir.</p> <p>TURKCELL bu mesaj=FDn i=E7erdi=F0i bilgilerin =
do=F0rulu=F0u veya eksiksiz oldu=F0u konusunda herhangi bir garanti =
vermemektedir. Bu nedenle bu bilgilerin ne =FEekilde olursa olsun =
i=E7eri=F0inden, iletilmesinden, al=FDnmas=FDndan ve saklanmas=FDndan =
sorumlu de=F0ildir. Bu mesajdaki g=F6r=FC=FEler yaln=FDzca g=F6nderen =
ki=FEiye aittir ve TURKCELL'in g=F6r=FC=FElerini yans=FDtmayabilir.</p> =
<p>Bu e-posta bilinen b=FCt=FCn bilgisayar vir=FCslerine kar=FE=FD =
taranm=FD=FEt=FDr.</p> =
<p>**********************************************************************=
**</p> <p>This e-mail and any files transmitted with it are confidential =
and	intended solely for the use of the individual or entity to whom they =
are addressed. If you are not the intended recipient you are hereby =
notified that any dissemination, forwarding, copying or use of any of =
the information is strictly prohibited, and the e-mail should =
immediately be deleted.</p> <p>TURKCELL makes no warranty as to the =
accuracy or completeness of any information contained in this message =
and hereby excludes any liability of any kind for the information =
contained therein or for the information transmission, reception, =
storage or use of such in any way whatsoever.The opinions expressed in =
this message belong to sender alone and may not necessarily reflect the =
opinions of TURKCELL.</p> <p>This e-mail has been scanned for all known =
computer viruses.</p> =
<p>**********************************************************************=
**</p> </font></body>

</html>

------_=_NextPart_001_01C42149.A37670C9--

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



From exim@www1.ietf.org  Tue Apr 13 08:44:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09049
	for <sigtran-archive@odin.ietf.org>; Tue, 13 Apr 2004 08:44:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDNGl-000107-OL
	for sigtran-archive@odin.ietf.org; Tue, 13 Apr 2004 08:44:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3DCi3xH003842
	for sigtran-archive@odin.ietf.org; Tue, 13 Apr 2004 08:44:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDNGj-0000zn-Mm; Tue, 13 Apr 2004 08:44:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDNGa-0000zN-Jp
	for sigtran@optimus.ietf.org; Tue, 13 Apr 2004 08:43:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09042
	for <sigtran@ietf.org>; Tue, 13 Apr 2004 08:43:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDNGY-0006EN-00
	for sigtran@ietf.org; Tue, 13 Apr 2004 08:43:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDNFi-0006BF-00
	for sigtran@ietf.org; Tue, 13 Apr 2004 08:43:00 -0400
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDNEd-000687-00
	for sigtran@ietf.org; Tue, 13 Apr 2004 08:41:51 -0400
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i3DCfkAh011385
	for <sigtran@ietf.org>; Tue, 13 Apr 2004 14:41:46 +0200
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 13 Apr 2004 14:41:46 +0200
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 25KSC5VF; Tue, 13 Apr 2004 14:41:47 +0200
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <HJ8Q5VHZ>; Tue, 13 Apr 2004 14:41:13 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C04331B7C@eestqnt105.es.eu.ericsson.se>
X-Sybari-Trust: 88363554 2c4885b5 934d30ee 00000138
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "'bulent.yilmaz@turkcell.com.tr'" <bulent.yilmaz@turkcell.com.tr>,
        sigtran@ietf.org
Cc: "Tolga Asveren (E-mail)" <asveren@ulticom.com>
Subject: RE: [Sigtran] M3UA for peer-to-peer ?
Date: Tue, 13 Apr 2004 14:40:35 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C42153.DF8A4450"
X-OriginalArrivalTime: 13 Apr 2004 12:41:46.0374 (UTC) FILETIME=[AE9D7260:01C42154]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_40_50,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE 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>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C42153.DF8A4450
Content-Type: text/plain;
	charset="iso-8859-9"
Content-Transfer-Encoding: quoted-printable

Hi Bulent,=20
=20
We're currently working in an M3UA SG2SG draft. We'll submit it pretty =
soon.  We'll ask for feedback from the WG about how to proceed with the =
work. I think it would be a good idea to include it as a WG item and =
get it finished during this year.
=20
Cheers // Javier.

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf =
Of bulent.yilmaz@turkcell.com.tr
Sent: martes, 13 de abril de 2004 13:23
To: sigtran@ietf.org
Subject: [Sigtran] M3UA for peer-to-peer ?



Dear Experts,

=20

Is there anyone that could explain the situation of M3UA protocol =
definitions for peer-to-peer communication, e.g. between 2 SGs ?=20

=20

Is it going to be standart ? and how much it provides similar M2PA-like =
functions for peer-to-peer case or is it the main reason (to compete =
against M2PA or to provide M2PA-like functions) for why M3UA =
peer-to-peer is being drafted ?

=20

Regards,

=20

B=FClent YILMAZ=20
TURKCELL=20
TO / Coordination Office

New Technologies
Mobile  : +90 532 210 1883=20
Office   : +90 216 458 2427=20
Fax      : +90 216 427 5141=20
e-mail   : bulent.yilmaz@turkcell.com.tr=20

=20




 <http://www.turkcell.com.tr/index/0,1027,3119,00.html>=20


*********************************************************************** =


Bu elektronik posta ve onunla iletilen b=FCt=FCn dosyalar sadece =
g=F6ndericisi taraf=FDndan almas=FD ama=E7lanan yetkili ger=E7ek ya da =
t=FCzel ki=FEinin kullan=FDm=FD i=E7indir.E=F0er s=F6z konusu yetkili =
al=FDc=FD de=F0ilseniz bu elektronik postan=FDn i=E7eri=F0ini =
a=E7=FDklaman=FDz,kopyalaman=FDz, y=F6nlendirmeniz ve kullanman=FDz =
kesinlikle yasakt=FDr ve bu elektronik postay=FD derhal silmeniz =
gerekmektedir.

TURKCELL bu mesaj=FDn i=E7erdi=F0i bilgilerin do=F0rulu=F0u veya =
eksiksiz oldu=F0u konusunda herhangi bir garanti vermemektedir. Bu =
nedenle bu bilgilerin ne =FEekilde olursa olsun i=E7eri=F0inden, =
iletilmesinden, al=FDnmas=FDndan ve saklanmas=FDndan sorumlu =
de=F0ildir. Bu mesajdaki g=F6r=FC=FEler yaln=FDzca g=F6nderen ki=FEiye =
aittir ve TURKCELL'in g=F6r=FC=FElerini yans=FDtmayabilir.

Bu e-posta bilinen b=FCt=FCn bilgisayar vir=FCslerine kar=FE=FD =
taranm=FD=FEt=FDr.

************************************************************************=


This e-mail and any files transmitted with it are confidential and =
intended solely for the use of the individual or entity to whom they =
are addressed. If you are not the intended recipient you are hereby =
notified that any dissemination, forwarding, copying or use of any of =
the information is strictly prohibited, and the e-mail should =
immediately be deleted.

TURKCELL makes no warranty as to the accuracy or completeness of any =
information contained in this message and hereby excludes any liability =
of any kind for the information contained therein or for the =
information transmission, reception, storage or use of such in any way =
whatsoever.The opinions expressed in this message belong to sender =
alone and may not necessarily reflect the opinions of TURKCELL.

This e-mail has been scanned for all known computer viruses.

************************************************************************=



------_=_NextPart_001_01C42153.DF8A4450
Content-Type: text/html;
	charset="iso-8859-9"
X-MIME-Autoconverted: from 8bit to quoted-printable by eagle.ericsson.se id i3DCfkAh011385
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-9">


<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR><o:SmartTagType =
name=3D"City"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><o:SmartTagType=20
name=3D"place"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Arial Unicode MS;
}
@font-face {
	font-family: @Arial Unicode MS;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 70.85pt 70.85pt 70.85pt 70=
.85pt; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: #606420; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: #606420; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DTR vLink=3D#606420 link=3Dblue>
<DIV><SPAN class=3D042093712-13042004><FONT face=3D"Comic Sans MS" color=3D=
#0000ff=20
size=3D2>Hi Bulent, </FONT></SPAN></DIV>
<DIV><SPAN class=3D042093712-13042004><FONT face=3D"Comic Sans MS" color=3D=
#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D042093712-13042004><FONT face=3D"Comic Sans MS" color=3D=
#0000ff=20
size=3D2>We're currently working in an M3UA SG2SG draft. We'll submit it =
pretty=20
soon.&nbsp;&nbsp;We'll ask for feedback from the WG about how to proceed =
with=20
the work. I think it would be a good idea to include it as a WG item and =
get it=20
finished during this year.</FONT></SPAN></DIV>
<DIV><SPAN class=3D042093712-13042004><FONT face=3D"Comic Sans MS" color=3D=
#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D042093712-13042004><FONT face=3D"Comic Sans MS" color=3D=
#0000ff=20
size=3D2>Cheers // Javier.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px so=
lid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT face=3DT=
ahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> sigtran-admin@ietf.=
org=20
  [mailto:sigtran-admin@ietf.org]<B>On Behalf Of=20
  </B>bulent.yilmaz@turkcell.com.tr<BR><B>Sent:</B> martes, 13 de abril d=
e 2004=20
  13:23<BR><B>To:</B> sigtran@ietf.org<BR><B>Subject:</B> [Sigtran] M3UA =
for=20
  peer-to-peer ?<BR><BR></FONT></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Dear=20
  Experts,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN><=
/FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is there anyone that coul=
d explain=20
  the situation of M3UA protocol definitions for peer-to-peer communicati=
on,=20
  e.g. between 2 SGs ? <o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN><=
/FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is it going to be standar=
t ? and=20
  how much it provides similar M2PA-like functions for peer-to-peer case =
or is=20
  it the main reason (to compete against M2PA or to provide M2PA-like fun=
ctions)=20
  for why M3UA peer-to-peer is being drafted ?<o:p></o:p></SPAN></FONT></=
P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN><=
/FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Regards,<o:p></o:p></SPAN=
></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN><=
/FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Arial Unicode MS" size=3D2><SPAN lan=
g=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial Unicode MS'">B=FClent YIL=
MAZ=20
  <BR></SPAN></FONT><STRONG><B><FONT face=3D"Arial Unicode MS"><SPAN lang=
=3DEN-US=20
  style=3D"FONT-FAMILY: 'Arial Unicode MS'">TURKCELL</SPAN></FONT></B></S=
TRONG><FONT=20
  face=3D"Arial Unicode MS"><SPAN lang=3DEN-US=20
  style=3D"FONT-FAMILY: 'Arial Unicode MS'"> </SPAN></FONT><FONT=20
  face=3D"Arial Unicode MS" size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial Unicode MS'"><BR><STRONG>=
<B><FONT=20
  face=3D"Arial Unicode MS"><SPAN=20
  style=3D"FONT-FAMILY: 'Arial Unicode MS'">TO&nbsp;/ Coordination=20
  Office</SPAN></FONT></B></STRONG></SPAN></FONT><SPAN=20
  lang=3DEN-US><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><STRONG><B><FONT face=3D"Arial Unicode MS" size=3D=
2><SPAN=20
  lang=3DEN-US style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial Unicode MS'"=
>New=20
  Technologies</SPAN></FONT></B></STRONG><FONT face=3D"Arial Unicode MS"=20
  size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial Unicode MS'"><BR><st1:Cit=
y=20
  w:st=3D"on"><st1:place w:st=3D"on">Mobile</st1:place></st1:City>&nbsp; =
: +90 532=20
  210 1883 <BR>Office&nbsp;&nbsp; : +90 216 458 2427 <BR>Fax &nbsp;&nbsp;=
 &nbsp;=20
  : +90 216 427 5141 <BR>e-mail&nbsp;&nbsp; : bulent.yilmaz@turkcell.com.=
tr=20
  </SPAN></FONT><SPAN lang=3DEN-US><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN lang=
=3DEN-US=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>
  <P></P>
  <P><BR><A href=3D"http://www.turkcell.com.tr/index/0,1027,3119,00.html"=
><IMG=20
  src=3D"http://www.turkcell.com.tr/mailbanner/gprsoutgoingbanner.gif" bo=
rder=3D0=20
  NOSEND=3D"1"></A><BR></P><FONT face=3D"Times New Roman" size=3D2>
  <P>********************************************************************=
***=20
</P>
  <P>Bu elektronik posta ve onunla iletilen b=FCt=FCn dosyalar sadece g=F6=
ndericisi=20
  taraf=FDndan almas=FD ama=E7lanan yetkili ger=E7ek ya da t=FCzel ki=FEi=
nin kullan=FDm=FD=20
  i=E7indir.E=F0er s=F6z konusu yetkili al=FDc=FD de=F0ilseniz bu elektro=
nik postan=FDn=20
  i=E7eri=F0ini a=E7=FDklaman=FDz,kopyalaman=FDz, y=F6nlendirmeniz ve kul=
lanman=FDz kesinlikle=20
  yasakt=FDr ve bu elektronik postay=FD derhal silmeniz gerekmektedir.</P=
>
  <P>TURKCELL bu mesaj=FDn i=E7erdi=F0i bilgilerin do=F0rulu=F0u veya eks=
iksiz oldu=F0u=20
  konusunda herhangi bir garanti vermemektedir. Bu nedenle bu bilgilerin =
ne=20
  =FEekilde olursa olsun i=E7eri=F0inden, iletilmesinden, al=FDnmas=FDnda=
n ve=20
  saklanmas=FDndan sorumlu de=F0ildir. Bu mesajdaki g=F6r=FC=FEler yaln=FD=
zca g=F6nderen=20
  ki=FEiye aittir ve TURKCELL'in g=F6r=FC=FElerini yans=FDtmayabilir.</P>
  <P>Bu e-posta bilinen b=FCt=FCn bilgisayar vir=FCslerine kar=FE=FD tara=
nm=FD=FEt=FDr.</P>
  <P>********************************************************************=
****</P>
  <P>This e-mail and any files transmitted with it are confidential and i=
ntended=20
  solely for the use of the individual or entity to whom they are address=
ed. If=20
  you are not the intended recipient you are hereby notified that any=20
  dissemination, forwarding, copying or use of any of the information is=20
  strictly prohibited, and the e-mail should immediately be deleted.</P>
  <P>TURKCELL makes no warranty as to the accuracy or completeness of any=
=20
  information contained in this message and hereby excludes any liability=
 of any=20
  kind for the information contained therein or for the information=20
  transmission, reception, storage or use of such in any way whatsoever.T=
he=20
  opinions expressed in this message belong to sender alone and may not=20
  necessarily reflect the opinions of TURKCELL.</P>
  <P>This e-mail has been scanned for all known computer viruses.</P>
  <P>********************************************************************=
****</P></BLOCKQUOTE></FONT></BODY></HTML>

------_=_NextPart_001_01C42153.DF8A4450--

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



From exim@www1.ietf.org  Fri Apr 16 07:23:06 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01038
	for <sigtran-archive@odin.ietf.org>; Fri, 16 Apr 2004 07:23:06 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BERPA-0002pE-BJ
	for sigtran-archive@odin.ietf.org; Fri, 16 Apr 2004 07:21:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3GBL8NH010853
	for sigtran-archive@odin.ietf.org; Fri, 16 Apr 2004 07:21:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BERII-0001ew-7o; Fri, 16 Apr 2004 07:14:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BERDV-0000qm-Ko
	for sigtran@optimus.ietf.org; Fri, 16 Apr 2004 07:09:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00500
	for <sigtran@ietf.org>; Fri, 16 Apr 2004 07:09:03 -0400 (EDT)
From: john.loughney@nokia.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BERDR-0004en-AH
	for sigtran@ietf.org; Fri, 16 Apr 2004 07:09:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BERCY-0004YV-00
	for sigtran@ietf.org; Fri, 16 Apr 2004 07:08:07 -0400
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BERBg-0004S6-00
	for sigtran@ietf.org; Fri, 16 Apr 2004 07:07:12 -0400
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i3GB7BO23961;
	Fri, 16 Apr 2004 14:07:11 +0300 (EET DST)
X-Scanned: Fri, 16 Apr 2004 14:06:53 +0300 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i3GB6rfx017578;
	Fri, 16 Apr 2004 14:06:53 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 009kIDrH; Fri, 16 Apr 2004 14:06:51 EEST
Received: from esebh004.NOE.Nokia.com (esebh004.ntc.nokia.com [172.21.138.84])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i3GB6gs00898;
	Fri, 16 Apr 2004 14:06:42 +0300 (EET DST)
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Fri, 16 Apr 2004 14:06:32 +0300
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Fri, 16 Apr 2004 14:06:32 +0300
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sigtran] SUAv16: Query on syntax of Hostname
Date: Fri, 16 Apr 2004 14:06:32 +0300
Message-ID: <DADF50F5EC506B41A0F375ABEB3206360143BBEF@esebe023.ntc.nokia.com>
Thread-Topic: SUAv16: Query on syntax of Hostname
Thread-Index: AcQcifxzt0fFiKWmQHyu3XGAu8a15gHGNKvA
To: <joyce_archibald@agilent.com>, <sigtran@ietf.org>
X-OriginalArrivalTime: 16 Apr 2004 11:06:32.0336 (UTC) FILETIME=[E005B100:01C423A2]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME 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

Joyce,

> This field contains a host name in "host name syntax" per RFC=20
> 1123 Section 2.1.
>=20
> RFC 1123 Section 2.1 refers to RFC 952 which states:
>=20
>    A "name" (Net, Host, Gateway, or Domain name) is a text string up
>    to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus
>    sign (-), and period (.).  Note that periods are only allowed when
>    they serve to delimit components of "domain style names".=20

The entent was to have it follow the above definition.

John
=20
> RFC 1123 later refers to RFC 1035 which states:
>=20
> Domain names in messages are expressed in terms of a sequence=20
> of labels.
> Each label is represented as a one octet length field followed by that
> number of octets.=20
>=20
> So, which syntax is used in SUA messages?
>=20
> Thanks,
> Joyce
>=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 Apr 20 10:32:06 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21738
	for <sigtran-archive@odin.ietf.org>; Tue, 20 Apr 2004 10:32:06 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFw9C-0005eV-Uq
	for sigtran-archive@odin.ietf.org; Tue, 20 Apr 2004 10:22:51 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KEMo7r021722
	for sigtran-archive@odin.ietf.org; Tue, 20 Apr 2004 10:22:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFw2d-0003II-N3; Tue, 20 Apr 2004 10:16:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFvsH-0002xm-Rt
	for sigtran@optimus.ietf.org; Tue, 20 Apr 2004 10:05:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19268
	for <sigtran@ietf.org>; Tue, 20 Apr 2004 10:05:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BFvsF-0002MO-J2
	for sigtran@ietf.org; Tue, 20 Apr 2004 10:05:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFvrM-000243-00
	for sigtran@ietf.org; Tue, 20 Apr 2004 10:04:25 -0400
Received: from viap100.atea.be ([194.78.143.100] helo=hrtades9.atea.be)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFvqf-0001ja-00
	for sigtran@ietf.org; Tue, 20 Apr 2004 10:03:41 -0400
Received: from hrtades10.atea.be (siemens.atea.be [139.10.143.141]) by hrtades9.atea.be with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id GZCF558M; Tue, 20 Apr 2004 16:03:10 +0200
Received: by siemens.atea.be with Internet Mail Service (5.5.2653.19)
	id <29HF8DPP>; Tue, 20 Apr 2004 16:03:11 +0200
Message-ID: <57FD2C3A246F76438CA6FDAD8FE9F195A7F4FC@hrtades7.atea.be>
From: Coene Lode <Lode.Coene@siemens.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        joyce_archibald@agilent.com, sigtran@ietf.org
Subject: RE: [Sigtran] SUAv16: Query on syntax of Hostname
Date: Tue, 20 Apr 2004 16:03:01 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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=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>

John & Joyce,

I had a llok at the definitions and the reference to RFC1123 section 2.1 is
confusing, to say the least(My fault...)
RFC1123 section 2.1 referes indeed to RFC952 which specify the DNS name as a
text string. That is the textual convention for putting the DNS name into a
program. It is the same as the textual convention for IPv4 and IPv6
address(textual ipv4 = 192.10.7.125 -> 12 ASCI characters <=> look at the
source and destination address field in a IP packet and you get 4 bytes..
That is the defined syntax of the ipvx address in the IP protocol...
It however does NOT specify how the DNS name is specified in the DNS
protocol. That is more or less specified in RFC1035: there the domain name
is specified as an sequence of labels and it is this syntax that is put in
the DNS query message.

So the specification of the Domain name as I intended that it should be the
one found in RFC1035 section 3.1.
I have in my SUA implementation used this specific encoding....
So the present specification can be interpreted in more than one way... And
that is wrong.. And my fault..

So for the implementaor guide for SUA that I am producing, I am going to
correct this so that it points to the correct interpretation....(RFC1035
section 3.1)

Yours sincerely,
Lode

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org] 
> On Behalf Of john.loughney@nokia.com
> Sent: vrijdag 16 april 2004 13:07
> To: joyce_archibald@agilent.com; sigtran@ietf.org
> Subject: RE: [Sigtran] SUAv16: Query on syntax of Hostname
> 
> 
> Joyce,
> 
> > This field contains a host name in "host name syntax" per RFC 
> > 1123 Section 2.1.
> > 
> > RFC 1123 Section 2.1 refers to RFC 952 which states:
> > 
> >    A "name" (Net, Host, Gateway, or Domain name) is a text string up
> >    to 24 characters drawn from the alphabet (A-Z), digits 
> (0-9), minus
> >    sign (-), and period (.).  Note that periods are only 
> allowed when
> >    they serve to delimit components of "domain style names". 
> 
> The entent was to have it follow the above definition.
> 
> John
>  
> > RFC 1123 later refers to RFC 1035 which states:
> > 
> > Domain names in messages are expressed in terms of a sequence 
> > of labels.
> > Each label is represented as a one octet length field 
> followed by that
> > number of octets. 
> > 
> > So, which syntax is used in SUA messages?
> > 
> > Thanks,
> > Joyce
> > 
> > _______________________________________________
> > Sigtran mailing 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  Tue Apr 20 11:02:02 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23724
	for <sigtran-archive@odin.ietf.org>; Tue, 20 Apr 2004 11:02:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFwes-0008H8-T7
	for sigtran-archive@odin.ietf.org; Tue, 20 Apr 2004 10:55:34 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KEtYuY031808
	for sigtran-archive@odin.ietf.org; Tue, 20 Apr 2004 10:55:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFwPx-0003sY-US; Tue, 20 Apr 2004 10:40:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFwL2-0001bR-0P
	for sigtran@optimus.ietf.org; Tue, 20 Apr 2004 10:35:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22007
	for <sigtran@ietf.org>; Tue, 20 Apr 2004 10:35:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BFwKz-00032B-FS
	for sigtran@ietf.org; Tue, 20 Apr 2004 10:35:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFwK0-0002m6-00
	for sigtran@ietf.org; Tue, 20 Apr 2004 10:34:01 -0400
Received: from zrc2s0jx.nortelnetworks.com ([47.103.122.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFwIw-0002Cp-00
	for sigtran@ietf.org; Tue, 20 Apr 2004 10:32:54 -0400
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i3KEWMH17790
	for <sigtran@ietf.org>; Tue, 20 Apr 2004 09:32:22 -0500 (CDT)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCQACTL6>; Tue, 20 Apr 2004 09:32:23 -0500
Message-ID: <F72ED4AED0592B469BF057F380DEECEA069CB4E4@zrc2c014.us.nortel.com>
From: "Brett Wallis" <wallis@nortelnetworks.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Date: Tue, 20 Apr 2004 09:32:08 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C426E4.42950D40"
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=AWL,HTML_20_30,
	HTML_FONTCOLOR_BLUE,HTML_FONTCOLOR_GREEN,HTML_FONTCOLOR_RED,
	HTML_MESSAGE autolearn=no version=2.60
Subject: [Sigtran] MTP3b over M2UA?
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C426E4.42950D40
Content-Type: text/plain

I'm new to this list, so perhaps this is a closed issue, but I was hoping to
get some feedback...

There are some current arguments amongst UMTS vendors as to whether M2UA was
meant to support MTP3b.  In our scenario, we have the UMTS Iu interface
which supports MTP3b/SSCF-NNI/SSCOP/AAL5/ATM and we want to terminate this
L2 (Q.2140) at the SG component of a MGW and backhaul this to the MGC via
MTP3b/M2UA/SCTP (more on this below).  So the argument is also whether
termination of Q.2140 by the SG component of a MGW is also valid in the M2UA
scenario.

I-D
http://www.ietf.org/internet-drafts/draft-ietf-sigtran-signalling-over-sctp-
applic-09.txt
<http://www.ietf.org/internet-drafts/draft-ietf-sigtran-signalling-over-sctp
-applic-09.txt>  supports M2UA transport for MTP3b (section 4.2.1.1), but
wording in RFC 3331 is being used against us.  This is mainly b/c RFC 3331
mentions MTP3b only in a section on SCTP management.  There is a reference
to Q.2140, but that's all.  Also, this I-D above has expired and I don't
know what its current validity or future status is.  

An argument used against us is that the primitives b/w MTP3b and Q.2140 are
different from the primitives between MTP3 and MTP2.  I'm not even aware
that MTP3-MTP2 interface primitives have been defined.  From what I can
gather, the only real difference between these two data link layers is that
some of the optional procedures of MTP2 are not supported by Q.2140.

Can anybody please provide opinions here?  It seems this role is exactly
what M2UA was created for, and I fail to see how Q.2140 on one side of the
MGW would prevent M2UA from being used here. 

Below is the specific argument that I had previously made for our case:


	RFC3331 clearly references MTP3b, which is for broadband transport.
RFC3331 as well as the other IETF document I referenced
(http://www.ietf.org/internet-drafts/draft-ietf-sigtran-signalling-over-sctp
-applic-09.txt
<http://www.ietf.org/internet-drafts/draft-ietf-sigtran-signalling-over-sctp
-applic-09.txt> ) clearly indicate that M2UA is applicable for MTP3b
transport.  RFC3331 even adds an informative reference to Q.2140 (B-ISDN ATM
Adaptation Layer), which is exactly what is used on the Iu interface.

	If so, then it should be agreed that the following is a supported
configuration for M2UA:

	<MTP3b user>/MTP3b/L2/L1 <---> SG component of MGW <---> <MTP3b
user>/MTP3b/M2UA/SCTP/IP/L2/L1

	The only remaining question is what are the allowed protocols for L2
on the left.  RFC3331 makes frequent reference to "MTP layer 2" which I
believe is a generic reference to the data link layer, and not specifically
to narrowband MTP2 as defined by Q.70x.  Even if they disagree with this
position, they must be able to identify the allowed protocols for L2 since
they have recognized that M2UA can carry MTP3b.

	MTP3b (Q.2210) is defined specifically to use the services of
Q.2140, which is the exact L2 supported on Iu.  So given that MTP3b/M2UA is
perfectly allowed by the IETF, and MTP3b is defined to run on
SSCF-NNI/SSCOP/AAL5/ATM, how can HW argue that this is not a supported
configuration?  L2 beneath MTP3b above must be Q.2140.  What other L2
protocols does HW believe MTP3b can use on non-SIGTRAN interface?  As Dan
pointed out, SAAL-NNI could just have easily been named MTP2b since it is
the MTP layer 2 protocol that is used with MTP3b.


I would greatly appreciate your feedback.

Thanks,

Brett Wallis
GSM/UMTS BICN Architecture
phone: 972-684-7087 (ESN 444)
email: wallis@nortelnetworks.com




------_=_NextPart_001_01C426E4.42950D40
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>MTP3b over M2UA?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Times New Roman">I'm new to this list, so =
perhaps this is a closed issue, but I was hoping to get some =
feedback...</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Times New Roman">There are some current =
arguments amongst UMTS vendors as to whether M2UA was meant to support =
MTP3b.&nbsp; In our scenario, we have the UMTS Iu interface which =
supports MTP3b/SSCF-NNI/SSCOP/AAL5/ATM and we want to terminate this L2 =
(Q.2140) at the SG component of a MGW and backhaul this to the MGC via =
MTP3b/M2UA/SCTP (more on this below).&nbsp; So the argument is also =
whether termination of Q.2140 by the SG component of a MGW is also =
valid in the M2UA scenario.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Times New Roman">I-D </FONT><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-sigtran-signallin=
g-over-sctp-applic-09.txt"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Times New =
Roman">http://www.ietf.org/internet-drafts/draft-ietf-sigtran-signalling=
-over-sctp-applic-09.txt</FONT></U></A><FONT SIZE=3D2 FACE=3D"Times New =
Roman"> supports M2UA transport for MTP3b (section 4.2.1.1), but =
wording in RFC 3331 is being used against us.&nbsp; This is mainly b/c =
RFC 3331 mentions MTP3b only in a section on SCTP management.&nbsp; =
There is a reference to Q.2140, but that's all.&nbsp; Also, this I-D =
above has expired and I don't know what its current validity or future =
status is.&nbsp; </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Times New Roman">An argument used against us =
is that the primitives b/w MTP3b and Q.2140 are different from the =
primitives between MTP3 and MTP2.&nbsp; I'm not even aware that =
MTP3-MTP2 interface primitives have been defined.&nbsp; From what I can =
gather, the only real difference between these two data link layers is =
that some of the optional procedures of MTP2 are not supported by =
Q.2140.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Times New Roman">Can anybody please provide =
opinions here?&nbsp; It seems this role is exactly what M2UA was =
created for, and I fail to see how Q.2140 on one side of the MGW would =
prevent M2UA from being used here. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Times New Roman">Below is the specific =
argument that I had previously made for our case:</FONT>
</P>
<BR>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Times New Roman">RFC3331 clearly references =
MTP3b, which is for broadband transport.&nbsp; RFC3331 as well as the =
other IETF document I referenced (</FONT><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-sigtran-signallin=
g-over-sctp-applic-09.txt"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Times New =
Roman">http://www.ietf.org/internet-drafts/draft-ietf-sigtran-signalling=
-over-sctp-applic-09.txt</FONT></U></A><FONT SIZE=3D2 FACE=3D"Times New =
Roman">) clearly indicate that M2UA is applicable for MTP3b =
transport.&nbsp; RFC3331 even adds an informative reference to Q.2140 =
(B-ISDN ATM Adaptation Layer), which is exactly what is used on the Iu =
interface.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Times New Roman">If so, then it should be =
agreed that the following is a supported configuration for M2UA:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Times New Roman">&lt;MTP3b =
user&gt;/MTP3b/L2/L1 &lt;---&gt; SG component of MGW &lt;---&gt; =
&lt;MTP3b user&gt;/MTP3b/M2UA/SCTP/IP/L2/L1</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Times New Roman">The only remaining question =
is what are the allowed protocols for L2 on the left.&nbsp; RFC3331 =
makes frequent reference to &quot;MTP layer 2&quot; which I believe is =
a generic reference to the data link layer, and not specifically to =
narrowband MTP2 as defined by Q.70x.&nbsp; Even if they disagree with =
this position, they must be able to identify the allowed protocols for =
L2 since they have recognized that M2UA can carry MTP3b.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Times New Roman">MTP3b (Q.2210) is defined =
specifically to use the services of Q.2140, which is the exact L2 =
supported on Iu.&nbsp; So given that MTP3b/M2UA is perfectly allowed by =
the IETF, and MTP3b is defined to run on SSCF-NNI/SSCOP/AAL5/ATM, how =
can HW argue that this is not a supported configuration?&nbsp; L2 =
beneath MTP3b above<U><B><I> must</I></B></U><B><I></I></B><I></I> be =
Q.2140.&nbsp; What other L2 protocols does HW believe MTP3b can use on =
non-SIGTRAN interface?&nbsp; As Dan pointed out, SAAL-NNI could just =
have easily been named MTP2b since it is<U></U><U><B></B></U><U><B><I> =
the</I></B></U><B><I></I></B><I></I> MTP layer 2 protocol that is used =
with MTP3b.</FONT></P>
<BR>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Times New Roman">I would greatly appreciate =
your feedback.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Times New Roman">Thanks,</FONT>
</P>

<P><B><FONT COLOR=3D"#008000" SIZE=3D2 FACE=3D"Arial">Brett =
Wallis</FONT></B>
<BR><B><FONT COLOR=3D"#800000" SIZE=3D2 FACE=3D"Arial">GSM/UMTS BICN =
Architecture</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial Narrow">phone</FONT></B><FONT =
SIZE=3D2 FACE=3D"Arial Narrow">: 972-684-7087 (ESN 444)</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial Narrow">email</FONT></B><FONT =
SIZE=3D2 FACE=3D"Arial Narrow">: wallis@nortelnetworks.com</FONT>
</P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C426E4.42950D40--

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



From exim@www1.ietf.org  Tue Apr 20 13:04:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04373
	for <sigtran-archive@odin.ietf.org>; Tue, 20 Apr 2004 13:04:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFyKt-0002m9-LR
	for sigtran-archive@odin.ietf.org; Tue, 20 Apr 2004 12:43:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KGh3t8010647
	for sigtran-archive@odin.ietf.org; Tue, 20 Apr 2004 12:43:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFxnc-0003JB-E8; Tue, 20 Apr 2004 12:08:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFxFO-00075J-Sw
	for sigtran@optimus.ietf.org; Tue, 20 Apr 2004 11:33:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26218
	for <sigtran@ietf.org>; Tue, 20 Apr 2004 11:33:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BFxFN-0004Jp-He
	for sigtran@ietf.org; Tue, 20 Apr 2004 11:33:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFxEe-00041a-00
	for sigtran@ietf.org; Tue, 20 Apr 2004 11:32:33 -0400
Received: from out2.smtp.messagingengine.com ([66.111.4.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFxDr-0003hi-00
	for sigtran@ietf.org; Tue, 20 Apr 2004 11:31:44 -0400
Received: from server2.messagingengine.com (server2.internal [10.202.2.133])
	by mail.messagingengine.com (Postfix) with ESMTP id EFC74A6DC31;
	Tue, 20 Apr 2004 11:31:37 -0400 (EDT)
Received: by server2.messagingengine.com (Postfix, from userid 99)
	id 1BAE48537E; Tue, 20 Apr 2004 11:31:36 -0400 (EDT)
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="ISO-8859-1"
MIME-Version: 1.0
X-Mailer: MIME::Lite 1.3  (F2.71; T1.001; A1.51; B2.12; Q2.03)
From: "Chirayu Patel" <chirayu@chirayu.org>
To: " 'sigtran@ietf.org'" <sigtran@ietf.org>
Date: Tue, 20 Apr 2004 21:01:31 +0530
X-Sasl-Enc: eyx9GGbFNCNNc8gHF4ctLg 1082475091
Message-Id: <1082475091.25656.184777780@webmail.messagingengine.com>
Cc: "Brett Wallis" <wallis@nortelnetworks.com>
Subject: Re: [Sigtran] MTP3b over M2UA?
References: ARRAY(0xa2b9c78)
In-Reply-To: ARRAY(0xa4894d4)
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

Hi,

The main argument for M2UA to not support MTP3B can arise only if it
(M2UA) does not support some of the functionality of Q.2140. In my
opinion this is not the case. It would be helpful if you could
articulate the actual technical arguments that lead to "M2UA cannot
support MTP3b" argument.

regards, 
CP

On Tue, 20 Apr 2004 09:32:08 -0500, "Brett Wallis"
<wallis@nortelnetworks.com> said:

[Snip]

> There are some current arguments amongst UMTS vendors as to whether M2UA
> was meant to support MTP3b.  

[Snip]

> An argument used against us is that the primitives b/w MTP3b and Q.2140
> are different from the primitives between MTP3 and MTP2.  I'm not even
> aware that MTP3-MTP2 interface primitives have been defined.  From what
> I can gather, the only real difference between these two data link
> layers is that some of the optional procedures of MTP2 are not
> supported by Q.2140.
>
> Can anybody please provide opinions here?  It seems this role is
> exactly what M2UA was created for, and I fail to see how Q.2140 on one
> side of the MGW would prevent M2UA from being used here.
>

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



From exim@www1.ietf.org  Tue Apr 20 13:06:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04523
	for <sigtran-archive@odin.ietf.org>; Tue, 20 Apr 2004 13:06:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFyPv-0005U9-0K
	for sigtran-archive@odin.ietf.org; Tue, 20 Apr 2004 12:48:15 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KGmEnb021073
	for sigtran-archive@odin.ietf.org; Tue, 20 Apr 2004 12:48:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFxow-00049I-BA; Tue, 20 Apr 2004 12:10:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFxPm-0003e2-O4
	for sigtran@optimus.ietf.org; Tue, 20 Apr 2004 11:44:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27228
	for <sigtran@ietf.org>; Tue, 20 Apr 2004 11:44:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BFxPl-00007T-Jv
	for sigtran@ietf.org; Tue, 20 Apr 2004 11:44:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFxOe-0007VZ-00
	for sigtran@ietf.org; Tue, 20 Apr 2004 11:42:53 -0400
Received: from zrc2s0jx.nortelnetworks.com ([47.103.122.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFxNk-000761-00
	for sigtran@ietf.org; Tue, 20 Apr 2004 11:41:56 -0400
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i3KFfPH26710
	for <sigtran@ietf.org>; Tue, 20 Apr 2004 10:41:25 -0500 (CDT)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCQACV32>; Tue, 20 Apr 2004 10:41:26 -0500
Message-ID: <F72ED4AED0592B469BF057F380DEECEA06A445FF@zrc2c014.us.nortel.com>
From: "Brett Wallis" <wallis@nortelnetworks.com>
To: "' 'sigtran@ietf.org''" <sigtran@ietf.org>
Subject: RE: [Sigtran] MTP3b over M2UA?
Date: Tue, 20 Apr 2004 10:41:23 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C426ED.EEF0E6AA"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE 
	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>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C426ED.EEF0E6AA
Content-Type: text/plain

Thank you.  As for the "technical arguments that lead to "M2UA cannot
support MTP3b"", I'm waiting for them. I have challenged them to be brought
forth, but have received none.  There is a meeting in China next week where
they might be brought forth, but I won't be there and I'm trying to provide
as much info as I can to my representative who will attend.

So I came here to hopefully get clarifications on a few key points:

1) That M2UA was clearly meant to apply to both MTP3 and MTP3b (as stated in
the expired internet-draft I quoted initially).

2) That despite the use of Q.2140 here (coming into the MG), this is the
exact role that M2UA was meant to play.  The alternate proposal is to use
M3UA here, which means the MG must terminate MTP3/MTP3b, own a point code,
play an STP role, etc.

Thanks...

Brett 



-----Original Message-----
From: Chirayu Patel [mailto:chirayu@chirayu.org] 
Sent: Tuesday, April 20, 2004 10:32 AM
To: 'sigtran@ietf.org'
Cc: Wallis, Brett [RICH2:UM59:EXCH]
Subject: Re: [Sigtran] MTP3b over M2UA?


Hi,

The main argument for M2UA to not support MTP3B can arise only if it
(M2UA) does not support some of the functionality of Q.2140. In my opinion
this is not the case. It would be helpful if you could articulate the actual
technical arguments that lead to "M2UA cannot support MTP3b" argument.

regards, 
CP

On Tue, 20 Apr 2004 09:32:08 -0500, "Brett Wallis"
<wallis@nortelnetworks.com> said:

[Snip]

> There are some current arguments amongst UMTS vendors as to whether 
> M2UA was meant to support MTP3b.

[Snip]

> An argument used against us is that the primitives b/w MTP3b and 
> Q.2140 are different from the primitives between MTP3 and MTP2.  I'm 
> not even aware that MTP3-MTP2 interface primitives have been defined.  
> From what I can gather, the only real difference between these two 
> data link layers is that some of the optional procedures of MTP2 are 
> not supported by Q.2140.
>
> Can anybody please provide opinions here?  It seems this role is 
> exactly what M2UA was created for, and I fail to see how Q.2140 on one 
> side of the MGW would prevent M2UA from being used here.
>

------_=_NextPart_001_01C426ED.EEF0E6AA
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>RE: [Sigtran] MTP3b over M2UA?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Thank you.&nbsp; As for the &quot;technical arguments =
that lead to &quot;M2UA cannot support MTP3b&quot;&quot;, I'm waiting =
for them. I have challenged them to be brought forth, but have received =
none.&nbsp; There is a meeting in China next week where they might be =
brought forth, but I won't be there and I'm trying to provide as much =
info as I can to my representative who will attend.</FONT></P>

<P><FONT SIZE=3D2>So I came here to hopefully get clarifications on a =
few key points:</FONT>
</P>

<P><FONT SIZE=3D2>1) That M2UA was clearly meant to apply to both MTP3 =
and MTP3b (as stated in the expired internet-draft I quoted =
initially).</FONT></P>

<P><FONT SIZE=3D2>2) That despite the use of Q.2140 here (coming into =
the MG), this is the exact role that M2UA was meant to play.&nbsp; The =
alternate proposal is to use M3UA here, which means the MG must =
terminate MTP3/MTP3b, own a point code, play an STP role, =
etc.</FONT></P>

<P><FONT SIZE=3D2>Thanks...</FONT>
</P>

<P><FONT SIZE=3D2>Brett </FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Chirayu Patel [<A =
HREF=3D"mailto:chirayu@chirayu.org">mailto:chirayu@chirayu.org</A>] =
</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, April 20, 2004 10:32 AM</FONT>
<BR><FONT SIZE=3D2>To: 'sigtran@ietf.org'</FONT>
<BR><FONT SIZE=3D2>Cc: Wallis, Brett [RICH2:UM59:EXCH]</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Sigtran] MTP3b over M2UA?</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi,</FONT>
</P>

<P><FONT SIZE=3D2>The main argument for M2UA to not support MTP3B can =
arise only if it</FONT>
<BR><FONT SIZE=3D2>(M2UA) does not support some of the functionality of =
Q.2140. In my opinion this is not the case. It would be helpful if you =
could articulate the actual technical arguments that lead to &quot;M2UA =
cannot support MTP3b&quot; argument.</FONT></P>

<P><FONT SIZE=3D2>regards, </FONT>
<BR><FONT SIZE=3D2>CP</FONT>
</P>

<P><FONT SIZE=3D2>On Tue, 20 Apr 2004 09:32:08 -0500, &quot;Brett =
Wallis&quot; &lt;wallis@nortelnetworks.com&gt; said:</FONT>
</P>

<P><FONT SIZE=3D2>[Snip]</FONT>
</P>

<P><FONT SIZE=3D2>&gt; There are some current arguments amongst UMTS =
vendors as to whether </FONT>
<BR><FONT SIZE=3D2>&gt; M2UA was meant to support MTP3b.</FONT>
</P>

<P><FONT SIZE=3D2>[Snip]</FONT>
</P>

<P><FONT SIZE=3D2>&gt; An argument used against us is that the =
primitives b/w MTP3b and </FONT>
<BR><FONT SIZE=3D2>&gt; Q.2140 are different from the primitives =
between MTP3 and MTP2.&nbsp; I'm </FONT>
<BR><FONT SIZE=3D2>&gt; not even aware that MTP3-MTP2 interface =
primitives have been defined.&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; From what I can gather, the only real =
difference between these two </FONT>
<BR><FONT SIZE=3D2>&gt; data link layers is that some of the optional =
procedures of MTP2 are </FONT>
<BR><FONT SIZE=3D2>&gt; not supported by Q.2140.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Can anybody please provide opinions here?&nbsp; =
It seems this role is </FONT>
<BR><FONT SIZE=3D2>&gt; exactly what M2UA was created for, and I fail =
to see how Q.2140 on one </FONT>
<BR><FONT SIZE=3D2>&gt; side of the MGW would prevent M2UA from being =
used here.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C426ED.EEF0E6AA--

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



From exim@www1.ietf.org  Tue Apr 20 13:49:02 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07943
	for <sigtran-archive@odin.ietf.org>; Tue, 20 Apr 2004 13:49:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFzBi-0001h1-LW
	for sigtran-archive@odin.ietf.org; Tue, 20 Apr 2004 13:37:39 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KHbcLD006505
	for sigtran-archive@odin.ietf.org; Tue, 20 Apr 2004 13:37:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFz0o-00056P-MG; Tue, 20 Apr 2004 13:26:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFyjA-0005pJ-0q
	for sigtran@optimus.ietf.org; Tue, 20 Apr 2004 13:08:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04630
	for <sigtran@ietf.org>; Tue, 20 Apr 2004 13:08:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BFyj8-0000vF-3E
	for sigtran@ietf.org; Tue, 20 Apr 2004 13:08:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFyiN-0000sD-00
	for sigtran@ietf.org; Tue, 20 Apr 2004 13:07:20 -0400
Received: from 192-73-206-10.ulticom.com ([192.73.206.10] helo=colby.ulticom.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFyhg-0000ln-00
	for sigtran@ietf.org; Tue, 20 Apr 2004 13:06:37 -0400
Received: from chuckie.dgms.com (chuckie-192.ulticom.com [192.73.206.4])
	by colby.ulticom.com (8.12.10/8.12.10) with ESMTP id i3KH651E009523
	for <sigtran@ietf.org>; Tue, 20 Apr 2004 13:06:05 -0400 (EDT)
Received: from pcasveren (pc-asveren.dgms.com [172.25.33.55])
	by chuckie.dgms.com (8.12.10/8.12.10) with SMTP id i3KH62oq029725
	for <sigtran@ietf.org>; Tue, 20 Apr 2004 13:06:03 -0400 (EDT)
From: "Tolga Asveren" <asveren@ulticom.com>
To: <sigtran@ietf.org>
Subject: RE: [Sigtran] MTP3b over M2UA?
Date: Tue, 20 Apr 2004 13:02:37 -0400
Message-ID: <GBEBKGPKHGPAOFCLBNAMAEEHCFAA.asveren@ulticom.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_004D_01C426D7.C1400940"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1409
In-Reply-To: <F72ED4AED0592B469BF057F380DEECEA06A445FF@zrc2c014.us.nortel.com>
Importance: Normal
X-Scanned-By: MIMEDefang 2.40
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_20_30,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE 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>

This is a multi-part message in MIME format.

------=_NextPart_000_004D_01C426D7.C1400940
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

RE: [Sigtran] MTP3b over M2UA?A feew comments below inline....

 Tolga
  -----Original Message-----
  From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
Brett Wallis
  Sent: Tuesday, April 20, 2004 11:41 AM
  To: ' 'sigtran@ietf.org''
  Subject: RE: [Sigtran] MTP3b over M2UA?


  Thank you.  As for the "technical arguments that lead to "M2UA cannot
support MTP3b"", I'm waiting for them. I have challenged them to be brought
forth, but have received none.  There is a meeting in China next week where
they might be brought forth, but I won't be there and I'm trying to provide
as much info as I can to my representative who will attend.

  So I came here to hopefully get clarifications on a few key points:

  1) That M2UA was clearly meant to apply to both MTP3 and MTP3b (as stated
in the expired internet-draft I quoted initially).

  [TOLGA] Key point is that there is a layer2 protocol and layer3 protocol
and there are certain primitives defined between them (names of the
primitives is not important but the functionality they provide/the
information they carry). If you can map all o those primitives to M2UA, then
you should be all set -so at least theoretically, you are even not limited
to MTP3/MTP3-B, the only constraint AFAICS is the above-. For that reason, I
don't see any problem on configuration you mentioned.

  2) That despite the use of Q.2140 here (coming into the MG), this is the
exact role that M2UA was meant to play.  The alternate proposal is to use
M3UA here, which means the MG must terminate MTP3/MTP3b, own a point code,
play an STP role, etc.

  [TOLGA]With M3UA, SG needs to terminate MTP3/MTP3b, but then you don't
need to have it in MGC. It will own a point code, but in your configuration,
MTP3/MTP3-b in MGC also owns a point code. For M3UA solution, MG does not
need to be a STP. I don't see any problem with M3UA solution.

  Thanks...

  Brett




  -----Original Message-----
  From: Chirayu Patel [mailto:chirayu@chirayu.org]
  Sent: Tuesday, April 20, 2004 10:32 AM
  To: 'sigtran@ietf.org'
  Cc: Wallis, Brett [RICH2:UM59:EXCH]
  Subject: Re: [Sigtran] MTP3b over M2UA?



  Hi,

  The main argument for M2UA to not support MTP3B can arise only if it
  (M2UA) does not support some of the functionality of Q.2140. In my opinion
this is not the case. It would be helpful if you could articulate the actual
technical arguments that lead to "M2UA cannot support MTP3b" argument.

  regards,
  CP

  On Tue, 20 Apr 2004 09:32:08 -0500, "Brett Wallis"
<wallis@nortelnetworks.com> said:

  [Snip]

  > There are some current arguments amongst UMTS vendors as to whether
  > M2UA was meant to support MTP3b.

  [Snip]

  > An argument used against us is that the primitives b/w MTP3b and
  > Q.2140 are different from the primitives between MTP3 and MTP2.  I'm
  > not even aware that MTP3-MTP2 interface primitives have been defined.
  > From what I can gather, the only real difference between these two
  > data link layers is that some of the optional procedures of MTP2 are
  > not supported by Q.2140.
  >
  > Can anybody please provide opinions here?  It seems this role is
  > exactly what M2UA was created for, and I fail to see how Q.2140 on one
  > side of the MGW would prevent M2UA from being used here.
  >

------=_NextPart_000_004D_01C426D7.C1400940
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: [Sigtran] MTP3b over M2UA?</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D568575016-20042004>A feew=20
comments below inline....</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D568575016-20042004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D568575016-20042004>&nbsp;Tolga</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
sigtran-admin@ietf.org=20
  [mailto:sigtran-admin@ietf.org]<B>On Behalf Of </B>Brett=20
  Wallis<BR><B>Sent:</B> Tuesday, April 20, 2004 11:41 AM<BR><B>To:</B> =
'=20
  'sigtran@ietf.org''<BR><B>Subject:</B> RE: [Sigtran] MTP3b over=20
  M2UA?<BR><BR></FONT></DIV>
  <P><FONT size=3D2>Thank you.&nbsp; As for the "technical arguments =
that lead to=20
  "M2UA cannot support MTP3b"", I'm waiting for them. I have challenged =
them to=20
  be brought forth, but have received none.&nbsp; There is a meeting in =
China=20
  next week where they might be brought forth, but I won't be there and =
I'm=20
  trying to provide as much info as I can to my representative who will=20
  attend.</FONT></P>
  <P><FONT size=3D2>So I came here to hopefully get clarifications on a =
few key=20
  points:</FONT> </P>
  <P><FONT size=3D2>1) That M2UA was clearly meant to apply to both MTP3 =
and MTP3b=20
  (as stated in the expired internet-draft I quoted initially).<SPAN=20
  class=3D568575016-20042004><FONT face=3DArial=20
  color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></P>
  <P><FONT size=3D2><SPAN class=3D568575016-20042004><FONT face=3DArial=20
  color=3D#0000ff>[TOLGA] Key&nbsp;point is that there is a layer2 =
protocol and=20
  layer3 protocol and there are certain primitives defined between them =
(names=20
  of the primitives is not important but the functionality they =
provide/the=20
  information they carry). If you can map all o those primitives to =
M2UA, then=20
  you should be all set -so at least theoretically, you are even not =
limited to=20
  MTP3/MTP3-B, the only constraint AFAICS is the above-. For that =
reason, I=20
  don't see any problem on configuration you=20
  mentioned.</FONT>&nbsp;</SPAN></FONT></P>
  <P><FONT size=3D2>2) That despite the use of Q.2140 here (coming into =
the MG),=20
  this is the exact role that M2UA was meant to play.&nbsp; The =
alternate=20
  proposal is to use M3UA here, which means the MG must terminate =
MTP3/MTP3b,=20
  own a point code, play an STP role, etc.<SPAN =
class=3D568575016-20042004><FONT=20
  face=3DArial color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></P>
  <P><FONT size=3D2><SPAN class=3D568575016-20042004><FONT face=3DArial=20
  color=3D#0000ff>[TOLGA]With M3UA, SG needs to terminate MTP3/MTP3b,=20
  but&nbsp;then you don't need to have it in MGC. It will own a point =
code, but=20
  in your configuration, MTP3/MTP3-b in MGC also owns a point code. For =
M3UA=20
  solution, MG does not need to be a STP.</FONT>&nbsp;<FONT face=3DArial =

  color=3D#0000ff>I don't see any problem with M3UA=20
  solution.</FONT></SPAN></FONT></P>
  <P><FONT size=3D2>Thanks...</FONT> </P>
  <P><FONT size=3D2>Brett </FONT></P><BR><BR>
  <P><FONT size=3D2>-----Original Message-----</FONT> <BR><FONT =
size=3D2>From:=20
  Chirayu Patel [<A=20
  href=3D"mailto:chirayu@chirayu.org">mailto:chirayu@chirayu.org</A>]=20
  </FONT><BR><FONT size=3D2>Sent: Tuesday, April 20, 2004 10:32 =
AM</FONT>=20
  <BR><FONT size=3D2>To: 'sigtran@ietf.org'</FONT> <BR><FONT =
size=3D2>Cc: Wallis,=20
  Brett [RICH2:UM59:EXCH]</FONT> <BR><FONT size=3D2>Subject: Re: =
[Sigtran] MTP3b=20
  over M2UA?</FONT> </P><BR>
  <P><FONT size=3D2>Hi,</FONT> </P>
  <P><FONT size=3D2>The main argument for M2UA to not support MTP3B can =
arise only=20
  if it</FONT> <BR><FONT size=3D2>(M2UA) does not support some of the=20
  functionality of Q.2140. In my opinion this is not the case. It would =
be=20
  helpful if you could articulate the actual technical arguments that =
lead to=20
  "M2UA cannot support MTP3b" argument.</FONT></P>
  <P><FONT size=3D2>regards, </FONT><BR><FONT size=3D2>CP</FONT> </P>
  <P><FONT size=3D2>On Tue, 20 Apr 2004 09:32:08 -0500, "Brett Wallis"=20
  &lt;wallis@nortelnetworks.com&gt; said:</FONT> </P>
  <P><FONT size=3D2>[Snip]</FONT> </P>
  <P><FONT size=3D2>&gt; There are some current arguments amongst UMTS =
vendors as=20
  to whether </FONT><BR><FONT size=3D2>&gt; M2UA was meant to support=20
  MTP3b.</FONT> </P>
  <P><FONT size=3D2>[Snip]</FONT> </P>
  <P><FONT size=3D2>&gt; An argument used against us is that the =
primitives b/w=20
  MTP3b and </FONT><BR><FONT size=3D2>&gt; Q.2140 are different from the =

  primitives between MTP3 and MTP2.&nbsp; I'm </FONT><BR><FONT =
size=3D2>&gt; not=20
  even aware that MTP3-MTP2 interface primitives have been =
defined.&nbsp;=20
  </FONT><BR><FONT size=3D2>&gt; From what I can gather, the only real =
difference=20
  between these two </FONT><BR><FONT size=3D2>&gt; data link layers is =
that some=20
  of the optional procedures of MTP2 are </FONT><BR><FONT size=3D2>&gt; =
not=20
  supported by Q.2140.</FONT> <BR><FONT size=3D2>&gt;</FONT> <BR><FONT =
size=3D2>&gt;=20
  Can anybody please provide opinions here?&nbsp; It seems this role is=20
  </FONT><BR><FONT size=3D2>&gt; exactly what M2UA was created for, and =
I fail to=20
  see how Q.2140 on one </FONT><BR><FONT size=3D2>&gt; side of the MGW =
would=20
  prevent M2UA from being used here.</FONT> <BR><FONT =
size=3D2>&gt;</FONT>=20
</P></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_004D_01C426D7.C1400940--


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



From exim@www1.ietf.org  Tue Apr 20 14:09:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09101
	for <sigtran-archive@odin.ietf.org>; Tue, 20 Apr 2004 14:09:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFzWu-0001Mi-TA
	for sigtran-archive@odin.ietf.org; Tue, 20 Apr 2004 13:59:33 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KHxWX5005236
	for sigtran-archive@odin.ietf.org; Tue, 20 Apr 2004 13:59:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFzPe-00072M-ND; Tue, 20 Apr 2004 13:52:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFzEJ-0002sC-Is
	for sigtran@optimus.ietf.org; Tue, 20 Apr 2004 13:40:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07364
	for <sigtran@ietf.org>; Tue, 20 Apr 2004 13:40:17 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BFzEH-0003AT-CD
	for sigtran@ietf.org; Tue, 20 Apr 2004 13:40:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFzDd-00036T-00
	for sigtran@ietf.org; Tue, 20 Apr 2004 13:39:37 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[WswaKjDnpGf30HDSeEht5QOSoPUc708B])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFzCf-00030a-00
	for sigtran@ietf.org; Tue, 20 Apr 2004 13:38:37 -0400
Received: from ns.pigworks.openss7.net (IDENT:KLJBKNZnQ8kEr2TBeaC37xSeMpzaOVji@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i3KHcag25498;
	Tue, 20 Apr 2004 11:38:36 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i3KHcZ711064;
	Tue, 20 Apr 2004 11:38:35 -0600
Date: Tue, 20 Apr 2004 11:38:35 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Brett Wallis <wallis@nortelnetworks.com>
Cc: "' 'sigtran@ietf.org''" <sigtran@ietf.org>
Subject: Re: [Sigtran] MTP3b over M2UA?
Message-ID: <20040420113835.A10857@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Brett Wallis <wallis@nortelnetworks.com>,
	"' 'sigtran@ietf.org''" <sigtran@ietf.org>
References: <F72ED4AED0592B469BF057F380DEECEA06A445FF@zrc2c014.us.nortel.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: <F72ED4AED0592B469BF057F380DEECEA06A445FF@zrc2c014.us.nortel.com>; from wallis@nortelnetworks.com on Tue, Apr 20, 2004 at 10:41:23AM -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>

Brett,

M2UA was intended to not only support Q.703/Q.2140 based SS7 links but was
intended to support M2PA SS7 links as well.

In IETF RFCs, it is best to consider that which is not explicitly counter-
recommended as permitted.

A reference to MTP3b exists in Section 1.5.4.1 of the RFC, with regard to
stream selection an 24-bit SLS values in MTP3b.  If M2UA were not intended to
support MTP3b, in would hardly have been worth mentioning.

M2PA is not mentioned as it was not at RFC status at the time that M2UA was
advanced.

It was alway my intention as an author of the RFC (and I think that the other
authors and editor were of like intention) that M2UA support not only current
SS7 signalling link types, but as many future signalling link types as could
be forseen.

--brian

Brett Wallis wrote:                                                                  (Tue, 20 Apr 2004 10:41:23)
> 
>    Thank  you.  As for the "technical arguments that lead to "M2UA cannot
>    support  MTP3b"",  I'm  waiting for them. I have challenged them to be
>    brought  forth,  but  have received none.  There is a meeting in China
>    next  week where they might be brought forth, but I won't be there and
>    I'm  trying  to provide as much info as I can to my representative who
>    will attend.
> 
>    So I came here to hopefully get clarifications on a few key points:
> 
>    1)  That  M2UA  was  clearly meant to apply to both MTP3 and MTP3b (as
>    stated in the expired internet-draft I quoted initially).
> 
>    2)  That  despite the use of Q.2140 here (coming into the MG), this is
>    the exact role that M2UA was meant to play.  The alternate proposal is
>    to  use M3UA here, which means the MG must terminate MTP3/MTP3b, own a
>    point code, play an STP role, etc.
> 
>    Thanks...
> 
>    Brett
> 
>    -----Original Message-----
>    From: Chirayu Patel [[1]mailto:chirayu@chirayu.org]
>    Sent: Tuesday, April 20, 2004 10:32 AM
>    To: 'sigtran@ietf.org'
>    Cc: Wallis, Brett [RICH2:UM59:EXCH]
>    Subject: Re: [Sigtran] MTP3b over M2UA?
> 
>    Hi,
> 
>    The main argument for M2UA to not support MTP3B can arise only if it
>    (M2UA)  does  not  support  some of the functionality of Q.2140. In my
>    opinion  this  is  not  the  case.  It  would  be helpful if you could
>    articulate  the  actual  technical arguments that lead to "M2UA cannot
>    support MTP3b" argument.
> 
>    regards,
>    CP
> 
>    On    Tue,    20    Apr    2004   09:32:08   -0500,   "Brett   Wallis"
>    <wallis@nortelnetworks.com> said:
> 
>    [Snip]
> 
>    > There are some current arguments amongst UMTS vendors as to whether
>    > M2UA was meant to support MTP3b.
> 
>    [Snip]
> 
>    > An argument used against us is that the primitives b/w MTP3b and
>    > Q.2140 are different from the primitives between MTP3 and MTP2.  I'm
>    >  not  even  aware  that  MTP3-MTP2  interface  primitives  have been
>    defined.
>    > From what I can gather, the only real difference between these two
>    > data link layers is that some of the optional procedures of MTP2 are
>    > not supported by Q.2140.
>    >
>    > Can anybody please provide opinions here?  It seems this role is
>    >  exactly  what M2UA was created for, and I fail to see how Q.2140 on
>    one
>    > side of the MGW would prevent M2UA from being used here.
>    >
> 
> References
> 
>    1. mailto:chirayu@chirayu.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  Thu Apr 22 17:42:03 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02994
	for <sigtran-archive@odin.ietf.org>; Thu, 22 Apr 2004 17:42:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGlLj-0004dE-43
	for sigtran-archive@odin.ietf.org; Thu, 22 Apr 2004 17:03:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3ML3BkP017798
	for sigtran-archive@odin.ietf.org; Thu, 22 Apr 2004 17:03:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGkKT-000712-Sh; Thu, 22 Apr 2004 15:57:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGk54-0001MF-03
	for sigtran@optimus.ietf.org; Thu, 22 Apr 2004 15:41:54 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22598;
	Thu, 22 Apr 2004 15:41:51 -0400 (EDT)
Message-Id: <200404221941.PAA22598@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 22 Apr 2004 15:41:51 -0400
Subject: [Sigtran] I-D ACTION:draft-ietf-sigtran-m3ua-v02-00.txt
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: Signaling System 7 (SS7) Message Transfer Part 3 (MTP3)
			  - User Adaptation Layer (M3UA)
	Author(s)	: G. Sidebottom, et al.
	Filename	: draft-ietf-sigtran-m3ua-v02-00.txt
	Pages		: 108
	Date		: 2004-4-22
	
This memo defines a protocol for supporting the transport of any SS7
   MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the
   services of the Stream Control Transmission Protocol.  Also,
   provision is made for protocol elements that enable a seamless
   operation of the MTP3-User peers in the SS7 and IP domains. This
   protocol would be used between a Signalling Gateway (SG) and a Media
   Gateway Controller (MGC) or  IP-resident Database, or between two
   IP-based applications.  It is assumed that the SG receives SS7
   signalling over a standard SS7 interface using the SS7 Message
   Transfer Part (MTP) to provide transport.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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

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


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

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

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

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

Content-Type: text/plain
Content-ID:	<2004-4-22154213.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sigtran-m3ua-v02-00.txt

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

Content-Type: text/plain
Content-ID:	<2004-4-22154213.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Fri Apr 23 08:36:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01501
	for <sigtran-archive@odin.ietf.org>; Fri, 23 Apr 2004 08:36:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGzsY-0005wp-2m
	for sigtran-archive@odin.ietf.org; Fri, 23 Apr 2004 08:34:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3NCY2eB022841
	for sigtran-archive@odin.ietf.org; Fri, 23 Apr 2004 08:34:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGznj-0004uy-35; Fri, 23 Apr 2004 08:29:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGzio-0003U8-1P
	for sigtran@optimus.ietf.org; Fri, 23 Apr 2004 08:23:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00340
	for <sigtran@ietf.org>; Fri, 23 Apr 2004 08:23:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGzim-0003TD-SM
	for sigtran@ietf.org; Fri, 23 Apr 2004 08:23:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGzgm-00033p-00
	for sigtran@ietf.org; Fri, 23 Apr 2004 08:21:53 -0400
Received: from sjmail.ciena.com ([12.7.169.25] helo=w2ksjexg01.ciena.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGzfm-0002jK-00
	for sigtran@ietf.org; Fri, 23 Apr 2004 08:20:50 -0400
Received: by w2ksjexg01.ciena.com with Internet Mail Service (5.5.2657.72)
	id <FNNCPAJJ>; Fri, 23 Apr 2004 05:20:24 -0700
Message-ID: <829F074A10F98943A218DC363D09C92A01476CD3@w2ksjexg06.ciena.com>
From: "Ong, Lyndon" <LyOng@Ciena.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Date: Fri, 23 Apr 2004 05:20:44 -0700
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=AWL autolearn=no version=2.60
Subject: [Sigtran] WG Last Call on M3UA-v02
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Folks,

At long last, let's start WG Last Call on M3UA-v02, or draft-ietf-sigtran-m3ua-v02-00.txt.
This is the next version of the M3UA spec, updated with the approved changes in the
Implementor's Guide.

To keep some order in the comments, please use "M3UA-v02 Last Call Comment" in
the subject line, and if possible please indicate if your comment is specifically on
the changes between the new document and RFC 3332 (M3UA) or is on something
not addressed by the changes.

Last Call will commence starting today and going to Friday, May 7th.

Cheers,

L. Ong

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



From exim@www1.ietf.org  Mon Apr 26 04:14:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01782
	for <sigtran-archive@odin.ietf.org>; Mon, 26 Apr 2004 04:14:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI1Dw-000065-LI
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 04:12:20 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3Q8CKEf000369
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 04:12:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI17s-0006dt-BQ; Mon, 26 Apr 2004 04:06:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI12v-0005GJ-Oo
	for sigtran@optimus.ietf.org; Mon, 26 Apr 2004 04:00:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01157
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 04:00:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BI12t-0006C6-7b
	for sigtran@ietf.org; Mon, 26 Apr 2004 04:00:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BI11s-0005xm-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 03:59:52 -0400
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BI10n-0005k7-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 03:58:45 -0400
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i3Q7wkAh005359
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 09:58:46 +0200
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 26 Apr 2004 09:58:46 +0200
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 JSDVF8TL; Mon, 26 Apr 2004 09:58:51 +0200
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <J4K8HHBV>; Mon, 26 Apr 2004 09:58:45 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C04331C0B@eestqnt105.es.eu.ericsson.se>
X-Sybari-Trust: 3d0782fb 2c4885b5 9757c2f6 00000138
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: RE: [Sigtran] I-D ACTION:draft-ietf-sigtran-m3ua-v02-00.txt
Date: Mon, 26 Apr 2004 09:58:44 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 26 Apr 2004 07:58:46.0253 (UTC) FILETIME=[4D0B59D0:01C42B64]
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>

Hi guys, 

Pls, note that the name "v02" does not mean that we need to change the version number in the M3UA packet. Consider it as RFC3332bis in the same way as IUA...

Cheers // Javier.

> -----Original Message-----
> From: sigtran-admin@ietf.org 
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Internet-Drafts@ietf.org
> Sent: jueves, 22 de abril de 2004 21:42
> To: i-d-announce@ietf.org
> Cc: sigtran@ietf.org
> Subject: [Sigtran] I-D ACTION:draft-ietf-sigtran-m3ua-v02-00.txt
> 
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the Signaling Transport Working 
> Group of the IETF.
> 
> 	Title		: Signaling System 7 (SS7) Message 
> Transfer Part 3 (MTP3)
> 			  - User Adaptation Layer (M3UA)
> 	Author(s)	: G. Sidebottom, et al.
> 	Filename	: draft-ietf-sigtran-m3ua-v02-00.txt
> 	Pages		: 108
> 	Date		: 2004-4-22
> 	
> This memo defines a protocol for supporting the transport of any SS7
>    MTP3-User signalling (e.g., ISUP and SCCP messages) over 
> IP using the
>    services of the Stream Control Transmission Protocol.  Also,
>    provision is made for protocol elements that enable a seamless
>    operation of the MTP3-User peers in the SS7 and IP domains. This
>    protocol would be used between a Signalling Gateway (SG) 
> and a Media
>    Gateway Controller (MGC) or  IP-resident Database, or between two
>    IP-based applications.  It is assumed that the SG receives SS7
>    signalling over a standard SS7 interface using the SS7 Message
>    Transfer Part (MTP) to provide transport.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-v02-00.txt
> 
> To remove yourself from the I-D Announcement list, send a message to 
> i-d-announce-request@ietf.org with the word unsubscribe in 
> the body of the message.  
> You can also visit 
https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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

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


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

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

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



From exim@www1.ietf.org  Mon Apr 26 09:50:05 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20368
	for <sigtran-archive@odin.ietf.org>; Mon, 26 Apr 2004 09:50:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI6Ql-0005tK-Mn
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 09:45:55 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3QDjtMd022627
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 09:45:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI6IK-0003EA-25; Mon, 26 Apr 2004 09:37:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI6EI-00029x-2N
	for sigtran@optimus.ietf.org; Mon, 26 Apr 2004 09:33:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19546
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 09:32:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BI6EF-0006xM-Tt
	for sigtran@ietf.org; Mon, 26 Apr 2004 09:33:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BI6DI-0006uw-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 09:32:00 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BI6D1-0006sM-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 09:31:43 -0400
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 i3QDV8TN002461
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 08:31:08 -0500 (CDT)
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 i3QDUdbK028381
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 08:30:39 -0500 (CDT)
Date: Mon, 26 Apr 2004 08:30:39 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: sigtran@ietf.org
Message-ID: <Pine.SOL.4.10.10404260818250.10328-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=AWL autolearn=no version=2.60
Subject: [Sigtran] M3UA-v02 Last Call Comment
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Hi all,

An SCCP message(cdpa->ri=rt_on_gta,cgpa->ri=rt_on_pcSsn) from
networkAppearance 1 is sent to SG. Since message is destined to SG, it
performs a GTT which results in PC/SSN of networkAppearance 2, here
my question is What will happen to cgpa parameters ? because SG
can not give cgpa->pc/ssn of networkAppearance 1 to networkAppearance 2.

I searched in RFC but could not find any answer other than section 1.5.3
in old_rfc which is not sufficient , i feel.

--Samuel

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


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



From exim@www1.ietf.org  Mon Apr 26 10:14:05 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22482
	for <sigtran-archive@odin.ietf.org>; Mon, 26 Apr 2004 10:14:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI6pp-0002JM-HH
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 10:11:49 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3QEBngd008870
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 10:11:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI6lB-0007AU-Bo; Mon, 26 Apr 2004 10:07:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI6eK-0001h0-GQ
	for sigtran@optimus.ietf.org; Mon, 26 Apr 2004 09:59:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20996
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 09:59:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BI6eH-0000lu-Oa
	for sigtran@ietf.org; Mon, 26 Apr 2004 09:59:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BI6dJ-0000jO-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 09:58:54 -0400
Received: from 192-73-206-10.ulticom.com ([192.73.206.10] helo=colby.ulticom.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BI6cP-0000fC-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 09:57:57 -0400
Received: from chuckie.dgms.com (chuckie-192.ulticom.com [192.73.206.4])
	by colby.ulticom.com (8.12.10/8.12.10) with ESMTP id i3QDvK1E021408
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 09:57:20 -0400 (EDT)
Received: from pcasveren (pc-asveren.dgms.com [172.25.33.55])
	by chuckie.dgms.com (8.12.10/8.12.10) with SMTP id i3QDvGoq008168
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 09:57:17 -0400 (EDT)
From: "Tolga Asveren" <asveren@ulticom.com>
To: <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
Date: Mon, 26 Apr 2004 09:53:11 -0400
Message-ID: <GBEBKGPKHGPAOFCLBNAMKEGACFAA.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)
x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1409
In-Reply-To: <Pine.SOL.4.10.10404260818250.10328-100000@sun2685.ssd.usa.alcatel.com>
Importance: Normal
X-Scanned-By: MIMEDefang 2.40
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 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 Samuel,

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> Samuel Dur D. Jeyaseelan
> Sent: Monday, April 26, 2004 9:31 AM
> To: sigtran@ietf.org
> Subject: [Sigtran] M3UA-v02 Last Call Comment
>
>
>
> Hi all,
>
> An SCCP message(cdpa->ri=rt_on_gta,cgpa->ri=rt_on_pcSsn) from
> networkAppearance 1 is sent to SG. Since message is destined to SG, it
> performs a GTT which results in PC/SSN of networkAppearance 2, here
> my question is What will happen to cgpa parameters ? because SG
> can not give cgpa->pc/ssn of networkAppearance 1 to networkAppearance 2.
[TOLGA]I think GTT result always should end up in the same network, i.e. the
same NA. IMO, to do otherwise, you would need a IWF on top of SCCP
(interworking two SCCP instances). I furthermore believe, this way of
operation is SS7 specific, not only applicable for M3UA case, so I would
think not to mention about it should be fine.
>
> I searched in RFC but could not find any answer other than section 1.5.3
> in old_rfc which is not sufficient , i feel.
>
> --Samuel
>
>   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA,
> Inc. *******
>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


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



From exim@www1.ietf.org  Mon Apr 26 10:39:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24725
	for <sigtran-archive@odin.ietf.org>; Mon, 26 Apr 2004 10:39:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI7Cy-0002Lu-N3
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 10:35:44 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3QEZibf009042
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 10:35:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI74X-0000D8-ND; Mon, 26 Apr 2004 10:27:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI6ws-0005rR-1M
	for sigtran@optimus.ietf.org; Mon, 26 Apr 2004 10:19:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23220
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 10:19:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BI6wp-0002GY-N1
	for sigtran@ietf.org; Mon, 26 Apr 2004 10:19:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BI6wA-0002Dk-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 10:18:22 -0400
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BI6vU-00027L-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 10:17:41 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i3QEH9Fq018962;
	Mon, 26 Apr 2004 09:17:09 -0500 (CDT)
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 i3QEGkbK007771;
	Mon, 26 Apr 2004 09:16:46 -0500 (CDT)
Date: Mon, 26 Apr 2004 09:16:46 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: Tolga Asveren <asveren@ulticom.com>
cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
In-Reply-To: <GBEBKGPKHGPAOFCLBNAMKEGACFAA.asveren@ulticom.com>
Message-ID: <Pine.SOL.4.10.10404260914420.10328-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=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>


Hi Tolga,

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

On Mon, 26 Apr 2004, Tolga Asveren wrote:

> Hi Samuel,
> 
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Samuel Dur D. Jeyaseelan
> > Sent: Monday, April 26, 2004 9:31 AM
> > To: sigtran@ietf.org
> > Subject: [Sigtran] M3UA-v02 Last Call Comment
> >
> >
> >
> > Hi all,
> >
> > An SCCP message(cdpa->ri=rt_on_gta,cgpa->ri=rt_on_pcSsn) from
> > networkAppearance 1 is sent to SG. Since message is destined to SG, it
> > performs a GTT which results in PC/SSN of networkAppearance 2, here
> > my question is What will happen to cgpa parameters ? because SG
> > can not give cgpa->pc/ssn of networkAppearance 1 to networkAppearance 2.
> [TOLGA]I think GTT result always should end up in the same network, i.e. the
> same NA. IMO, to do otherwise, you would need a IWF on top of SCCP
> (interworking two SCCP instances). I furthermore believe, this way of
> operation is SS7 specific, not only applicable for M3UA case, so I would
> think not to mention about it should be fine.

Fine, but When will SG route the message across networkAppearances?

> >
> > I searched in RFC but could not find any answer other than section 1.5.3
> > in old_rfc which is not sufficient , i feel.
> >
> > --Samuel
> >
> >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA,
> > Inc. *******
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 


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



From exim@www1.ietf.org  Mon Apr 26 10:53:02 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25342
	for <sigtran-archive@odin.ietf.org>; Mon, 26 Apr 2004 10:53:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI7P0-00068p-U3
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 10:48:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3QEmAIr023602
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 10:48:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI7GA-0003lH-C3; Mon, 26 Apr 2004 10:39:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI76j-0000bS-MC
	for sigtran@optimus.ietf.org; Mon, 26 Apr 2004 10:29:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24003
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 10:29:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BI76h-0002rK-Di
	for sigtran@ietf.org; Mon, 26 Apr 2004 10:29:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BI75n-0002mm-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 10:28:20 -0400
Received: from 192-73-206-10.ulticom.com ([192.73.206.10] helo=colby.ulticom.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BI75E-0002g1-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 10:27:45 -0400
Received: from chuckie.dgms.com (chuckie-192.ulticom.com [192.73.206.4])
	by colby.ulticom.com (8.12.10/8.12.10) with ESMTP id i3QERD1E024308
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 10:27:13 -0400 (EDT)
Received: from pcasveren (pc-asveren.dgms.com [172.25.33.55])
	by chuckie.dgms.com (8.12.10/8.12.10) with SMTP id i3QERAoq010445
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 10:27:10 -0400 (EDT)
From: "Tolga Asveren" <asveren@ulticom.com>
To: <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
Date: Mon, 26 Apr 2004 10:23:04 -0400
Message-ID: <GBEBKGPKHGPAOFCLBNAMKEGBCFAA.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)
x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1409
In-Reply-To: <Pine.SOL.4.10.10404260914420.10328-100000@sun2685.ssd.usa.alcatel.com>
Importance: Normal
X-Scanned-By: MIMEDefang 2.40
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 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 Samuel,

> -----Original Message-----
> From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> Sent: Monday, April 26, 2004 10:17 AM
> To: Tolga Asveren
> Cc: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
>
>
>
> Hi Tolga,
>
>   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA,
> Inc. *******
>
> On Mon, 26 Apr 2004, Tolga Asveren wrote:
>
> > Hi Samuel,
> >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > Samuel Dur D. Jeyaseelan
> > > Sent: Monday, April 26, 2004 9:31 AM
> > > To: sigtran@ietf.org
> > > Subject: [Sigtran] M3UA-v02 Last Call Comment
> > >
> > >
> > >
> > > Hi all,
> > >
> > > An SCCP message(cdpa->ri=rt_on_gta,cgpa->ri=rt_on_pcSsn) from
> > > networkAppearance 1 is sent to SG. Since message is destined to SG, it
> > > performs a GTT which results in PC/SSN of networkAppearance 2, here
> > > my question is What will happen to cgpa parameters ? because SG
> > > can not give cgpa->pc/ssn of networkAppearance 1 to
> networkAppearance 2.
> > [TOLGA]I think GTT result always should end up in the same
> network, i.e. the
> > same NA. IMO, to do otherwise, you would need a IWF on top of SCCP
> > (interworking two SCCP instances). I furthermore believe, this way of
> > operation is SS7 specific, not only applicable for M3UA case, so I would
> > think not to mention about it should be fine.
>
> Fine, but When will SG route the message across networkAppearances?
[TOLGA]I believe this should be done on application level. For example :
                                 SG
     +-------+              +---------------+
     |  SEP  +--------------| SS7 Ntwk |M3UA|              ----
     +-------+   SS7 links  |   "A"    |    |            /      \
                            |__________|    +-----------+  ASPs  |
                            |          |    |            \      /
     +-------+              | SS7 Ntwk |    |              ----
     |  SEP  +--------------+   "B"    |    |
     +-------+              +---------------+

Figure2 from RFC3332

SG receives messages from NtwkA, routes it to ASP. Then it is up to the
application on ASP to process this message and possibly to initiate a
message to NtwkB.
>
> > >
> > > I searched in RFC but could not find any answer other than
> section 1.5.3
> > > in old_rfc which is not sufficient , i feel.
> > >
> > > --Samuel
> > >
> > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA,
> > > Inc. *******
> > >
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >


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



From exim@www1.ietf.org  Mon Apr 26 11:43:59 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28184
	for <sigtran-archive@odin.ietf.org>; Mon, 26 Apr 2004 11:43:59 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI8CJ-0004od-9u
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 11:39:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3QFd709018494
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 11:39:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI83W-0001wH-Nw; Mon, 26 Apr 2004 11:30:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI7uE-0006hB-SJ
	for sigtran@optimus.ietf.org; Mon, 26 Apr 2004 11:20:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26502
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 11:20:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BI7uD-0005i6-Sy
	for sigtran@ietf.org; Mon, 26 Apr 2004 11:20:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BI7sw-0005cH-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 11:19:06 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BI7sX-0005Yr-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 11:18:42 -0400
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 i3QFI9TN026940;
	Mon, 26 Apr 2004 10:18:10 -0500 (CDT)
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 i3QFI2bK020196;
	Mon, 26 Apr 2004 10:18:02 -0500 (CDT)
Date: Mon, 26 Apr 2004 10:18:02 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: Tolga Asveren <asveren@ulticom.com>
cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
In-Reply-To: <GBEBKGPKHGPAOFCLBNAMKEGBCFAA.asveren@ulticom.com>
Message-ID: <Pine.SOL.4.10.10404260956060.11145-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=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>


Hi Tolga,

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

On Mon, 26 Apr 2004, Tolga Asveren wrote:

> Hi Samuel,
> 
> > -----Original Message-----
> > From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> > Sent: Monday, April 26, 2004 10:17 AM
> > To: Tolga Asveren
> > Cc: sigtran@ietf.org
> > Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
> >
> >
> >
> > Hi Tolga,
> >
> >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA,
> > Inc. *******
> >
> > On Mon, 26 Apr 2004, Tolga Asveren wrote:
> >
> > > Hi Samuel,
> > >
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > Samuel Dur D. Jeyaseelan
> > > > Sent: Monday, April 26, 2004 9:31 AM
> > > > To: sigtran@ietf.org
> > > > Subject: [Sigtran] M3UA-v02 Last Call Comment
> > > >
> > > >
> > > >
> > > > Hi all,
> > > >
> > > > An SCCP message(cdpa->ri=rt_on_gta,cgpa->ri=rt_on_pcSsn) from
> > > > networkAppearance 1 is sent to SG. Since message is destined to SG, it
> > > > performs a GTT which results in PC/SSN of networkAppearance 2, here
> > > > my question is What will happen to cgpa parameters ? because SG
> > > > can not give cgpa->pc/ssn of networkAppearance 1 to
> > networkAppearance 2.
> > > [TOLGA]I think GTT result always should end up in the same
> > network, i.e. the
> > > same NA. IMO, to do otherwise, you would need a IWF on top of SCCP
> > > (interworking two SCCP instances). I furthermore believe, this way of
> > > operation is SS7 specific, not only applicable for M3UA case, so I would
> > > think not to mention about it should be fine.
> >
> > Fine, but When will SG route the message across networkAppearances?
> [TOLGA]I believe this should be done on application level. For example :
>                                  SG
>      +-------+              +---------------+
>      |  SEP  +--------------| SS7 Ntwk |M3UA|              ----
>      +-------+   SS7 links  |   "A"    |    |            /      \
>                             |__________|    +-----------+  ASPs  |
>                             |          |    |            \      /
>      +-------+              | SS7 Ntwk |    |              ----
>      |  SEP  +--------------+   "B"    |    |
>      +-------+              +---------------+
> 
> Figure2 from RFC3332
> 
> SG receives messages from NtwkA, routes it to ASP. Then it is up to the
> application on ASP to process this message and possibly to initiate a
> message to NtwkB.

I think at SG GTT is mandatory to move messages from one networkAppearance
to another networkAppearance. This is one of the reasons why an instance
of SCCP layer is kept over M3UA. One more think is only after the GTT, SG 
routes the message to ASP with the help of new PC/SSN(this is true only
for this thread).

From 'Figure2 RFC3332' , SG even can route the messages to another
networkAppearance without he help of ASP. This is done just by doing GTT.

Since RFC3332 mentions about GTT , it should also mention about few
important questions such as my first_emial_question, i feel .


> >
> > > >
> > > > I searched in RFC but could not find any answer other than
> > section 1.5.3
> > > > in old_rfc which is not sufficient , i feel.
> > > >
> > > > --Samuel
> > > >
> > > >   Alcatel USA, Inc.                  Internet:
> > > > <userid>@ssd.usa.alcatel.com
> > > >   1000 Coit Road, Plano, Texas 75075
> > > >   ******* The opinions expressed are not those of Alcatel USA,
> > > > Inc. *******
> > > >
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 


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



From exim@www1.ietf.org  Mon Apr 26 11:52:50 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28550
	for <sigtran-archive@odin.ietf.org>; Mon, 26 Apr 2004 11:52:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI8GD-0006Wb-Em
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 11:43:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3QFh9hZ025077
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 11:43:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI8CE-0004n8-3t; Mon, 26 Apr 2004 11:39:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI83K-0001ea-DM
	for sigtran@optimus.ietf.org; Mon, 26 Apr 2004 11:29:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27235
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 11:29:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BI83J-0006Tp-Bj
	for sigtran@ietf.org; Mon, 26 Apr 2004 11:29:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BI824-0006MH-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 11:28:33 -0400
Received: from 192-73-206-10.ulticom.com ([192.73.206.10] helo=colby.ulticom.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BI81L-0006D8-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 11:27:47 -0400
Received: from chuckie.dgms.com (chuckie-192.ulticom.com [192.73.206.4])
	by colby.ulticom.com (8.12.10/8.12.10) with ESMTP id i3QFRC1E029950
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 11:27:13 -0400 (EDT)
Received: from pcasveren (pc-asveren.dgms.com [172.25.33.55])
	by chuckie.dgms.com (8.12.10/8.12.10) with SMTP id i3QFR9oq015211
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 11:27:10 -0400 (EDT)
From: "Tolga Asveren" <asveren@ulticom.com>
To: <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
Date: Mon, 26 Apr 2004 11:23:03 -0400
Message-ID: <GBEBKGPKHGPAOFCLBNAMCEGDCFAA.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)
x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1409
In-Reply-To: <Pine.SOL.4.10.10404260956060.11145-100000@sun2685.ssd.usa.alcatel.com>
Importance: Normal
X-Scanned-By: MIMEDefang 2.40
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 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 Samuel,

> -----Original Message-----
> From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> Sent: Monday, April 26, 2004 11:18 AM
> To: Tolga Asveren
> Cc: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
>
>
>
> Hi Tolga,
>
>   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA,
> Inc. *******
>
> On Mon, 26 Apr 2004, Tolga Asveren wrote:
>
> > Hi Samuel,
> >
> > > -----Original Message-----
> > > From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> > > Sent: Monday, April 26, 2004 10:17 AM
> > > To: Tolga Asveren
> > > Cc: sigtran@ietf.org
> > > Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
> > >
> > >
> > >
> > > Hi Tolga,
> > >
> > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA,
> > > Inc. *******
> > >
> > > On Mon, 26 Apr 2004, Tolga Asveren wrote:
> > >
> > > > Hi Samuel,
> > > >
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > Samuel Dur D. Jeyaseelan
> > > > > Sent: Monday, April 26, 2004 9:31 AM
> > > > > To: sigtran@ietf.org
> > > > > Subject: [Sigtran] M3UA-v02 Last Call Comment
> > > > >
> > > > >
> > > > >
> > > > > Hi all,
> > > > >
> > > > > An SCCP message(cdpa->ri=rt_on_gta,cgpa->ri=rt_on_pcSsn) from
> > > > > networkAppearance 1 is sent to SG. Since message is
> destined to SG, it
> > > > > performs a GTT which results in PC/SSN of
> networkAppearance 2, here
> > > > > my question is What will happen to cgpa parameters ? because SG
> > > > > can not give cgpa->pc/ssn of networkAppearance 1 to
> > > networkAppearance 2.
> > > > [TOLGA]I think GTT result always should end up in the same
> > > network, i.e. the
> > > > same NA. IMO, to do otherwise, you would need a IWF on top of SCCP
> > > > (interworking two SCCP instances). I furthermore believe,
> this way of
> > > > operation is SS7 specific, not only applicable for M3UA
> case, so I would
> > > > think not to mention about it should be fine.
> > >
> > > Fine, but When will SG route the message across networkAppearances?
> > [TOLGA]I believe this should be done on application level. For example :
> >                                  SG
> >      +-------+              +---------------+
> >      |  SEP  +--------------| SS7 Ntwk |M3UA|              ----
> >      +-------+   SS7 links  |   "A"    |    |            /      \
> >                             |__________|    +-----------+  ASPs  |
> >                             |          |    |            \      /
> >      +-------+              | SS7 Ntwk |    |              ----
> >      |  SEP  +--------------+   "B"    |    |
> >      +-------+              +---------------+
> >
> > Figure2 from RFC3332
> >
> > SG receives messages from NtwkA, routes it to ASP. Then it is up to the
> > application on ASP to process this message and possibly to initiate a
> > message to NtwkB.
>
> I think at SG GTT is mandatory to move messages from one networkAppearance
> to another networkAppearance. This is one of the reasons why an instance
> of SCCP layer is kept over M3UA. One more think is only after the GTT, SG
> routes the message to ASP with the help of new PC/SSN(this is true only
> for this thread).
[TOLGA]I don't see how one can move messages between NA, without IWF. If you
have one SCCP instance, this means that it is SCCP for a specific PC, which
resides in one network. To relay between two networks, you need something on
top of SCCP -something which interworks two SCCP instances on different
PCs/networks-.
>
> >From 'Figure2 RFC3332' , SG even can route the messages to another
> networkAppearance without he help of ASP. This is done just by doing GTT.
[TOLGA]IMO, this is not the intention.
>
> Since RFC3332 mentions about GTT , it should also mention about few
> important questions such as my first_emial_question, i feel .
[TOLGA]IMO, your questions are relate with SS7, not specifically with M3UA.
Also in SS7, to achieve what you want to do, you need something on top of
SCCP.
>
>
> > >
> > > > >
> > > > > I searched in RFC but could not find any answer other than
> > > section 1.5.3
> > > > > in old_rfc which is not sufficient , i feel.
> > > > >
> > > > > --Samuel
> > > > >
> > > > >   Alcatel USA, Inc.                  Internet:
> > > > > <userid>@ssd.usa.alcatel.com
> > > > >   1000 Coit Road, Plano, Texas 75075
> > > > >   ******* The opinions expressed are not those of Alcatel USA,
> > > > > Inc. *******
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >


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



From exim@www1.ietf.org  Mon Apr 26 12:56:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02323
	for <sigtran-archive@odin.ietf.org>; Mon, 26 Apr 2004 12:56:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI9BD-0000t0-4k
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 12:42:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3QGg3Ij003397
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 12:42:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI95N-00073k-T8; Mon, 26 Apr 2004 12:36:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI8v0-0003FO-4t
	for sigtran@optimus.ietf.org; Mon, 26 Apr 2004 12:25:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00529
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 12:25:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BI8uy-0002wo-JZ
	for sigtran@ietf.org; Mon, 26 Apr 2004 12:25:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BI8to-0002s9-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 12:24:05 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BI8tX-0002pC-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 12:23:47 -0400
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 i3QGNATN011984;
	Mon, 26 Apr 2004 11:23:11 -0500 (CDT)
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 i3QGMWbK003207;
	Mon, 26 Apr 2004 11:22:33 -0500 (CDT)
Date: Mon, 26 Apr 2004 11:22:32 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: Tolga Asveren <asveren@ulticom.com>
cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
In-Reply-To: <GBEBKGPKHGPAOFCLBNAMCEGDCFAA.asveren@ulticom.com>
Message-ID: <Pine.SOL.4.10.10404261048390.11145-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=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>


Hi Tolga,

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

On Mon, 26 Apr 2004, Tolga Asveren wrote:

> Hi Samuel,
> 
> > -----Original Message-----
> > From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> > Sent: Monday, April 26, 2004 11:18 AM
> > To: Tolga Asveren
> > Cc: sigtran@ietf.org
> > Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
> >
> >
> >
> > Hi Tolga,
> >
> >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA,
> > Inc. *******
> >
> > On Mon, 26 Apr 2004, Tolga Asveren wrote:
> >
> > > Hi Samuel,
> > >
> > > > -----Original Message-----
> > > > From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> > > > Sent: Monday, April 26, 2004 10:17 AM
> > > > To: Tolga Asveren
> > > > Cc: sigtran@ietf.org
> > > > Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
> > > >
> > > >
> > > >
> > > > Hi Tolga,
> > > >
> > > >   Alcatel USA, Inc.                  Internet:
> > > > <userid>@ssd.usa.alcatel.com
> > > >   1000 Coit Road, Plano, Texas 75075
> > > >   ******* The opinions expressed are not those of Alcatel USA,
> > > > Inc. *******
> > > >
> > > > On Mon, 26 Apr 2004, Tolga Asveren wrote:
> > > >
> > > > > Hi Samuel,
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: sigtran-admin@ietf.org
> > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > Samuel Dur D. Jeyaseelan
> > > > > > Sent: Monday, April 26, 2004 9:31 AM
> > > > > > To: sigtran@ietf.org
> > > > > > Subject: [Sigtran] M3UA-v02 Last Call Comment
> > > > > >
> > > > > >
> > > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > An SCCP message(cdpa->ri=rt_on_gta,cgpa->ri=rt_on_pcSsn) from
> > > > > > networkAppearance 1 is sent to SG. Since message is
> > destined to SG, it
> > > > > > performs a GTT which results in PC/SSN of
> > networkAppearance 2, here
> > > > > > my question is What will happen to cgpa parameters ? because SG
> > > > > > can not give cgpa->pc/ssn of networkAppearance 1 to
> > > > networkAppearance 2.
> > > > > [TOLGA]I think GTT result always should end up in the same
> > > > network, i.e. the
> > > > > same NA. IMO, to do otherwise, you would need a IWF on top of SCCP
> > > > > (interworking two SCCP instances). I furthermore believe,
> > this way of
> > > > > operation is SS7 specific, not only applicable for M3UA
> > case, so I would
> > > > > think not to mention about it should be fine.
> > > >
> > > > Fine, but When will SG route the message across networkAppearances?
> > > [TOLGA]I believe this should be done on application level. For example :
> > >                                  SG
> > >      +-------+              +---------------+
> > >      |  SEP  +--------------| SS7 Ntwk |M3UA|              ----
> > >      +-------+   SS7 links  |   "A"    |    |            /      \
> > >                             |__________|    +-----------+  ASPs  |
> > >                             |          |    |            \      /
> > >      +-------+              | SS7 Ntwk |    |              ----
> > >      |  SEP  +--------------+   "B"    |    |
> > >      +-------+              +---------------+
> > >
> > > Figure2 from RFC3332
> > >
> > > SG receives messages from NtwkA, routes it to ASP. Then it is up to the
> > > application on ASP to process this message and possibly to initiate a
> > > message to NtwkB.
> >
> > I think at SG GTT is mandatory to move messages from one networkAppearance
> > to another networkAppearance. This is one of the reasons why an instance
> > of SCCP layer is kept over M3UA. One more think is only after the GTT, SG
> > routes the message to ASP with the help of new PC/SSN(this is true only
> > for this thread).
> [TOLGA]I don't see how one can move messages between NA, without IWF. If you
> have one SCCP instance, this means that it is SCCP for a specific PC, which
> resides in one network. To relay between two networks, you need something on
> top of SCCP -something which interworks two SCCP instances on different
> PCs/networks-.

I dont say IWF is not required, what i am saying is without SCCP layer
SG will simply become a relay node and it can not route messages 
across networkAppearances. GTT function at SCCP layer adds an
intellligence to SG to route the SCCP messages across networkAppearances.
Just imagine an SG without SCCP layer that means it has only MTP3 layer.
This MTP3 layer shall never know the point codes of another
networkAppearance, it knows only about its local point codes means point
codes within the origination networkAppearance. Finally IWF comes into
picture while delivering messages from one protocol to another protocol.

> >
> > >From 'Figure2 RFC3332' , SG even can route the messages to another
> > networkAppearance without he help of ASP. This is done just by doing GTT.
> [TOLGA]IMO, this is not the intention.
> >
Yes, but this is one of the intentions.

> > Since RFC3332 mentions about GTT , it should also mention about few
> > important questions such as my first_emial_question, i feel .
> [TOLGA]IMO, your questions are relate with SS7, not specifically with M3UA.
> Also in SS7, to achieve what you want to do, you need something on top of
> SCCP.
To do this(to differentiate point codes between NAs) nothing is required
on top of SCCP. Just SCCP is enough.

If my question is not related with M3UA, then rfc3332 should not talk
about GTT and SCCP layer and once again i am saying it will become simply
a relay node.

 > >
> >
> > > >
> > > > > >
> > > > > > I searched in RFC but could not find any answer other than
> > > > section 1.5.3
> > > > > > in old_rfc which is not sufficient , i feel.
> > > > > >
> > > > > > --Samuel
> > > > > >
> > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > <userid>@ssd.usa.alcatel.com
> > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > >   ******* The opinions expressed are not those of Alcatel USA,
> > > > > > Inc. *******
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Sigtran mailing list
> > > > > > Sigtran@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >
> > >
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 


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



From exim@www1.ietf.org  Mon Apr 26 13:42:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04969
	for <sigtran-archive@odin.ietf.org>; Mon, 26 Apr 2004 13:42:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI9sI-0006h7-4Z
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 13:26:34 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3QHQYR3025717
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 13:26:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI9k1-00046H-QF; Mon, 26 Apr 2004 13:18:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI9eL-00020u-FI
	for sigtran@optimus.ietf.org; Mon, 26 Apr 2004 13:12:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03497
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 13:12:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BI9eJ-0006qB-HF
	for sigtran@ietf.org; Mon, 26 Apr 2004 13:12:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BI9dM-0006li-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 13:11:08 -0400
Received: from 192-73-206-10.ulticom.com ([192.73.206.10] helo=colby.ulticom.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BI9cU-0006eP-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 13:10:14 -0400
Received: from chuckie.dgms.com (chuckie-192.ulticom.com [192.73.206.4])
	by colby.ulticom.com (8.12.10/8.12.10) with ESMTP id i3QH9e1E008419
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 13:09:40 -0400 (EDT)
Received: from pcasveren (pc-asveren.dgms.com [172.25.33.55])
	by chuckie.dgms.com (8.12.10/8.12.10) with SMTP id i3QH9aoq022788
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 13:09:37 -0400 (EDT)
From: "Tolga Asveren" <asveren@ulticom.com>
To: <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
Date: Mon, 26 Apr 2004 13:05:30 -0400
Message-ID: <GBEBKGPKHGPAOFCLBNAMOEGECFAA.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)
x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1409
In-Reply-To: <Pine.SOL.4.10.10404261048390.11145-100000@sun2685.ssd.usa.alcatel.com>
Importance: Normal
X-Scanned-By: MIMEDefang 2.40
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 Samuel,


[..snip..]
> > > I think at SG GTT is mandatory to move messages from one
> networkAppearance
> > > to another networkAppearance. This is one of the reasons why
> an instance
> > > of SCCP layer is kept over M3UA. One more think is only after
> the GTT, SG
> > > routes the message to ASP with the help of new PC/SSN(this is
> true only
> > > for this thread).
> > [TOLGA]I don't see how one can move messages between NA,
> without IWF. If you
> > have one SCCP instance, this means that it is SCCP for a
> specific PC, which
> > resides in one network. To relay between two networks, you need
> something on
> > top of SCCP -something which interworks two SCCP instances on different
> > PCs/networks-.
>
> I dont say IWF is not required, what i am saying is without SCCP layer
> SG will simply become a relay node and it can not route messages
> across networkAppearances. GTT function at SCCP layer adds an
> intellligence to SG to route the SCCP messages across networkAppearances.
> Just imagine an SG without SCCP layer that means it has only MTP3 layer.
> This MTP3 layer shall never know the point codes of another
> networkAppearance, it knows only about its local point codes means point
> codes within the origination networkAppearance. Finally IWF comes into
> picture while delivering messages from one protocol to another protocol.
[TOLGA]I don't know, whether a GTT resulting in a PC in another network is
reasonable or not. BTW, if you consider the issue from M3UA point of view,
it doesn't matter whether it is SCCP or an IWF application, which runs on
top of it. Transferring of messages from one network to the other one is not
done in M3UA/MTP3 itself. If you want to use GTT (probabaly with multiple
SCCPs), then where does M3UA come into play, while transferring the message
from one network to the other one? Somebody else decides for the network, to
which the message is going to be sent, M3UA just delivers it.
>
> > >
> > > >From 'Figure2 RFC3332' , SG even can route the messages to another
> > > networkAppearance without he help of ASP. This is done just
> by doing GTT.
> > [TOLGA]IMO, this is not the intention.
> > >
> Yes, but this is one of the intentions.
>
> > > Since RFC3332 mentions about GTT , it should also mention about few
> > > important questions such as my first_emial_question, i feel .
> > [TOLGA]IMO, your questions are relate with SS7, not
> specifically with M3UA.
> > Also in SS7, to achieve what you want to do, you need something
> on top of
> > SCCP.
> To do this(to differentiate point codes between NAs) nothing is required
> on top of SCCP. Just SCCP is enough.
[TOLGA]When you cross protocol boundaries, probably you will need some kind
of IWF and two instances of SCCP, one in each network. And as I mentioned
above, even this is besides the point, the issue is that it is not M3UA that
does the transfer between networks. The transfer logic is somewhere on the
upper layers, either on a local IWF or on an application in ASP.
>
> If my question is not related with M3UA, then rfc3332 should not talk
> about GTT and SCCP layer and once again i am saying it will become simply
> a relay node.
[TOLGA]It talks about it to show a possible configuration. But please note
that configuration does not change the way M3UA works. What do you mean
exactly with "it will become simply a realy node" ?


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



From exim@www1.ietf.org  Mon Apr 26 13:43:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05168
	for <sigtran-archive@odin.ietf.org>; Mon, 26 Apr 2004 13:43:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI9t0-00076g-S8
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 13:27:19 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3QHRIod027301
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 13:27:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI9k2-00046X-NY; Mon, 26 Apr 2004 13:18:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI9fK-0002Mv-29
	for sigtran@optimus.ietf.org; Mon, 26 Apr 2004 13:13:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03589
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 13:13:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BI9fI-0006vs-4Q
	for sigtran@ietf.org; Mon, 26 Apr 2004 13:13:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BI9ec-0006sB-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 13:12:26 -0400
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 1BI9dg-0006my-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 13:11:28 -0400
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i3QHBR7T026236;
	Mon, 26 Apr 2004 13:11:27 -0400
From: "Barry Nagelberg" <barryn@adax.com>
To: "Lode Coene" <Lode.Coene@siemens.com>
Cc: "SIGTRAN Mailing List" <sigtran@ietf.org>
Date: Mon, 26 Apr 2004 13:13:03 -0400
Message-ID: <JBECLENKLBCKAAKFGAJOCEIHCGAA.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)
x-mimeole: Produced By Microsoft MimeOLE V5.50.4910.0300
Importance: Normal
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 IG
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Lode,

I suggest that we add the same paragraph that was added to M3UA v02, in
section 3.2:

<snip>
   Unless explicitly stated or shown in a message format diagram, only
   one parameter of the same type is allowed in a message.
<snip>

Barry Nagelberg


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



From exim@www1.ietf.org  Mon Apr 26 14:35:01 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08727
	for <sigtran-archive@odin.ietf.org>; Mon, 26 Apr 2004 14:35:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIArc-0005MK-C9
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 14:29:57 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3QITuBw020580
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 14:29:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIAi4-0002C1-Kl; Mon, 26 Apr 2004 14:20:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIAWU-0006xr-O6
	for sigtran@optimus.ietf.org; Mon, 26 Apr 2004 14:08:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06318
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 14:08:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BIAWS-0002bY-8I
	for sigtran@ietf.org; Mon, 26 Apr 2004 14:08:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIAVc-0002Yt-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 14:07:12 -0400
Received: from mail-n.franken.de
	([193.175.24.27] helo=ilsa.franken.de ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIAV6-0002Vd-00; Mon, 26 Apr 2004 14:06:40 -0400
Received: from [192.168.1.15] (pD9FF1FEA.dip.t-dialin.net [217.255.31.234])
	by ilsa.franken.de (Postfix) with ESMTP
	id 333CC24631; Mon, 26 Apr 2004 20:06:22 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v613)
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C19FB58-97AC-11D8-AAF0-000A95DC192A@lurchi.franken.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
To: "'lksctp-developers@lists.sourceforge.net'" <lksctp-developers@lists.sourceforge.net>,
        sigtran@ietf.org, tsvwg@ietf.org
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Date: Mon, 26 Apr 2004 20:06:21 +0200
X-Mailer: Apple Mail (2.613)
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] (no subject)
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Dear all,

the 7th SCTP interop will be held at University of Applied Sciences,=20
M=FCnster, from
July 25th to July 30th 2004.

You can now register and find more information at
http://sctp.fh-muenster.de

If you have any further questions please do not hesitate to contact me=20=

via
tuexen@fh-muenster.de

Happy SCTPing
Michael


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



From exim@www1.ietf.org  Mon Apr 26 15:31:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13607
	for <sigtran-archive@odin.ietf.org>; Mon, 26 Apr 2004 15:31:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIBfz-0007gj-30
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 15:21:59 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3QJLxkK029531
	for sigtran-archive@odin.ietf.org; Mon, 26 Apr 2004 15:21:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIBaH-0005ur-45; Mon, 26 Apr 2004 15:16:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIBNg-0007QM-Nu
	for sigtran@optimus.ietf.org; Mon, 26 Apr 2004 15:03:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10731
	for <sigtran@ietf.org>; Mon, 26 Apr 2004 15:03:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BIBNd-0007cg-NP
	for sigtran@ietf.org; Mon, 26 Apr 2004 15:03:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIBMh-0007Zw-00
	for sigtran@ietf.org; Mon, 26 Apr 2004 15:02:04 -0400
Received: from mail-n.franken.de
	([193.175.24.27] helo=ilsa.franken.de ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIBLp-0007Vz-00; Mon, 26 Apr 2004 15:01:09 -0400
Received: from [192.168.1.15] (pD9FF1FEA.dip.t-dialin.net [217.255.31.234])
	by ilsa.franken.de (Postfix) with ESMTP
	id E097E245CE; Mon, 26 Apr 2004 21:00:51 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v613)
Content-Transfer-Encoding: quoted-printable
Message-Id: <0F5E2801-97B4-11D8-AAF0-000A95DC192A@lurchi.franken.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
To: sigtran@ietf.org, tsvwg@ietf.org
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Date: Mon, 26 Apr 2004 21:01:01 +0200
X-Mailer: Apple Mail (2.613)
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] Registration for 7th SCTP interop is now open
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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

Dear all,

the 7th SCTP interop will be held at University of Applied Sciences,=20
M=FCnster, from
July 25th to July 30th 2004.

You can now register and find more information at
http://sctp.fh-muenster.de

If you have any further questions please do not hesitate to contact me=20=

via
tuexen@fh-muenster.de

Happy SCTPing
Michael

PS.: Sorry for sending it twice, I forgot the subject line...


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



From exim@www1.ietf.org  Tue Apr 27 06:18:26 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19804
	for <sigtran-archive@odin.ietf.org>; Tue, 27 Apr 2004 06:18:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIPbg-0006Bc-1g
	for sigtran-archive@odin.ietf.org; Tue, 27 Apr 2004 06:14:28 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3RAES5S023774
	for sigtran-archive@odin.ietf.org; Tue, 27 Apr 2004 06:14:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIPSX-0003Lm-84; Tue, 27 Apr 2004 06:05:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIPLY-00025I-Op
	for sigtran@optimus.ietf.org; Tue, 27 Apr 2004 05:57:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17894
	for <sigtran@ietf.org>; Tue, 27 Apr 2004 05:57:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BIPLU-0005mV-SS
	for sigtran@ietf.org; Tue, 27 Apr 2004 05:57:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIPKU-0005ZR-00
	for sigtran@ietf.org; Tue, 27 Apr 2004 05:56:43 -0400
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIPJX-0005LA-00
	for sigtran@ietf.org; Tue, 27 Apr 2004 05:55:43 -0400
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i3R9tdWR020903
	for <sigtran@ietf.org>; Tue, 27 Apr 2004 11:55:43 +0200 (MEST)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 27 Apr 2004 11:56:09 +0200
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id JQ3ZTPQN; Tue, 27 Apr 2004 11:55:39 +0200
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <J4K8HRZ9>; Tue, 27 Apr 2004 11:55:37 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C04331C21@eestqnt105.es.eu.ericsson.se>
X-Sybari-Trust: 9aa9d8f5 2c4885b5 06c9302b 00000138
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>,
        Tolga Asveren <asveren@ulticom.com>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
Date: Tue, 27 Apr 2004 11:54:42 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 27 Apr 2004 09:56:09.0150 (UTC) FILETIME=[DD59E5E0:01C42C3D]
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>

Hi Samuel, 

I also think like Tolga. It is not an issue with M3UA itself, but with the SG architecture. You may want to make SG product in several ways. One of them is including an SCCP layer above MTP3 to make this GT translation. 

Cheers // Javier.

> -----Original Message-----
> From: sigtran-admin@ietf.org 
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Samuel Dur D. Jeyaseelan
> Sent: lunes, 26 de abril de 2004 18:23
> To: Tolga Asveren
> Cc: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
> 
> 
> 
> Hi Tolga,
> 
>   Alcatel USA, Inc.                  Internet: 
> <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel 
> USA, Inc. *******
> 
> On Mon, 26 Apr 2004, Tolga Asveren wrote:
> 
> > Hi Samuel,
> > 
> > > -----Original Message-----
> > > From: Samuel Dur D. Jeyaseelan 
> [mailto:sjeyasee@ssd.usa.alcatel.com]
> > > Sent: Monday, April 26, 2004 11:18 AM
> > > To: Tolga Asveren
> > > Cc: sigtran@ietf.org
> > > Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
> > >
> > >
> > >
> > > Hi Tolga,
> > >
> > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA,
> > > Inc. *******
> > >
> > > On Mon, 26 Apr 2004, Tolga Asveren wrote:
> > >
> > > > Hi Samuel,
> > > >
> > > > > -----Original Message-----
> > > > > From: Samuel Dur D. Jeyaseelan 
> [mailto:sjeyasee@ssd.usa.alcatel.com]
> > > > > Sent: Monday, April 26, 2004 10:17 AM
> > > > > To: Tolga Asveren
> > > > > Cc: sigtran@ietf.org
> > > > > Subject: RE: [Sigtran] M3UA-v02 Last Call Comment
> > > > >
> > > > >
> > > > >
> > > > > Hi Tolga,
> > > > >
> > > > >   Alcatel USA, Inc.                  Internet:
> > > > > <userid>@ssd.usa.alcatel.com
> > > > >   1000 Coit Road, Plano, Texas 75075
> > > > >   ******* The opinions expressed are not those of Alcatel USA,
> > > > > Inc. *******
> > > > >
> > > > > On Mon, 26 Apr 2004, Tolga Asveren wrote:
> > > > >
> > > > > > Hi Samuel,
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: sigtran-admin@ietf.org
> > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > > Samuel Dur D. Jeyaseelan
> > > > > > > Sent: Monday, April 26, 2004 9:31 AM
> > > > > > > To: sigtran@ietf.org
> > > > > > > Subject: [Sigtran] M3UA-v02 Last Call Comment
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > An SCCP 
> message(cdpa->ri=rt_on_gta,cgpa->ri=rt_on_pcSsn) from
> > > > > > > networkAppearance 1 is sent to SG. Since message is
> > > destined to SG, it
> > > > > > > performs a GTT which results in PC/SSN of
> > > networkAppearance 2, here
> > > > > > > my question is What will happen to cgpa 
> parameters ? because SG
> > > > > > > can not give cgpa->pc/ssn of networkAppearance 1 to
> > > > > networkAppearance 2.
> > > > > > [TOLGA]I think GTT result always should end up in the same
> > > > > network, i.e. the
> > > > > > same NA. IMO, to do otherwise, you would need a IWF 
> on top of SCCP
> > > > > > (interworking two SCCP instances). I furthermore believe,
> > > this way of
> > > > > > operation is SS7 specific, not only applicable for M3UA
> > > case, so I would
> > > > > > think not to mention about it should be fine.
> > > > >
> > > > > Fine, but When will SG route the message across 
> networkAppearances?
> > > > [TOLGA]I believe this should be done on application 
> level. For example :
> > > >                                  SG
> > > >      +-------+              +---------------+
> > > >      |  SEP  +--------------| SS7 Ntwk |M3UA|              ----
> > > >      +-------+   SS7 links  |   "A"    |    |           
>  /      \
> > > >                             |__________|    
> +-----------+  ASPs  |
> > > >                             |          |    |           
>  \      /
> > > >      +-------+              | SS7 Ntwk |    |              ----
> > > >      |  SEP  +--------------+   "B"    |    |
> > > >      +-------+              +---------------+
> > > >
> > > > Figure2 from RFC3332
> > > >
> > > > SG receives messages from NtwkA, routes it to ASP. Then 
> it is up to the
> > > > application on ASP to process this message and possibly 
> to initiate a
> > > > message to NtwkB.
> > >
> > > I think at SG GTT is mandatory to move messages from one 
> networkAppearance
> > > to another networkAppearance. This is one of the reasons 
> why an instance
> > > of SCCP layer is kept over M3UA. One more think is only 
> after the GTT, SG
> > > routes the message to ASP with the help of new 
> PC/SSN(this is true only
> > > for this thread).
> > [TOLGA]I don't see how one can move messages between NA, 
> without IWF. If you
> > have one SCCP instance, this means that it is SCCP for a 
> specific PC, which
> > resides in one network. To relay between two networks, you 
> need something on
> > top of SCCP -something which interworks two SCCP instances 
> on different
> > PCs/networks-.
> 
> I dont say IWF is not required, what i am saying is without SCCP layer
> SG will simply become a relay node and it can not route messages 
> across networkAppearances. GTT function at SCCP layer adds an
> intellligence to SG to route the SCCP messages across 
> networkAppearances.
> Just imagine an SG without SCCP layer that means it has only 
> MTP3 layer.
> This MTP3 layer shall never know the point codes of another
> networkAppearance, it knows only about its local point codes 
> means point
> codes within the origination networkAppearance. Finally IWF comes into
> picture while delivering messages from one protocol to 
> another protocol.
> 
> > >
> > > >From 'Figure2 RFC3332' , SG even can route the messages 
> to another
> > > networkAppearance without he help of ASP. This is done 
> just by doing GTT.
> > [TOLGA]IMO, this is not the intention.
> > >
> Yes, but this is one of the intentions.
> 
> > > Since RFC3332 mentions about GTT , it should also mention 
> about few
> > > important questions such as my first_emial_question, i feel .
> > [TOLGA]IMO, your questions are relate with SS7, not 
> specifically with M3UA.
> > Also in SS7, to achieve what you want to do, you need 
> something on top of
> > SCCP.
> To do this(to differentiate point codes between NAs) nothing 
> is required
> on top of SCCP. Just SCCP is enough.
> 
> If my question is not related with M3UA, then rfc3332 should not talk
> about GTT and SCCP layer and once again i am saying it will 
> become simply
> a relay node.
> 
>  > >
> > >
> > > > >
> > > > > > >
> > > > > > > I searched in RFC but could not find any answer other than
> > > > > section 1.5.3
> > > > > > > in old_rfc which is not sufficient , i feel.
> > > > > > >
> > > > > > > --Samuel
> > > > > > >
> > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > >   ******* The opinions expressed are not those of 
> Alcatel USA,
> > > > > > > Inc. *******
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > Sigtran mailing list
> > > > > > > Sigtran@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Sigtran mailing list
> > > > > > Sigtran@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 

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



From exim@www1.ietf.org  Tue Apr 27 08:19:20 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25935
	for <sigtran-archive@odin.ietf.org>; Tue, 27 Apr 2004 08:19:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIRQJ-0008PI-4z
	for sigtran-archive@odin.ietf.org; Tue, 27 Apr 2004 08:10:51 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3RCApql032286
	for sigtran-archive@odin.ietf.org; Tue, 27 Apr 2004 08:10:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIRJl-00070D-SY; Tue, 27 Apr 2004 08:04:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIR98-0005A9-5t
	for sigtran@optimus.ietf.org; Tue, 27 Apr 2004 07:53:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24330
	for <sigtran@ietf.org>; Tue, 27 Apr 2004 07:53:02 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BIR93-0007ZU-Fo
	for sigtran@ietf.org; Tue, 27 Apr 2004 07:53:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIR8A-0007Lj-00
	for sigtran@ietf.org; Tue, 27 Apr 2004 07:52:06 -0400
Received: from spark.hss.co.in ([203.200.71.140])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIR7W-00075L-00
	for sigtran@ietf.org; Tue, 27 Apr 2004 07:51:27 -0400
Received: from sandesh.hss.hns.com (sandesh.hss.hns.com [139.85.242.35])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id i3RBndX4014526
	for <sigtran@ietf.org>; Tue, 27 Apr 2004 17:19:40 +0530 (IST)
To: sigtran@ietf.org
Date: Tue, 27 Apr 2004 17:13:31 +0530
Message-ID: <OFFB79E9EE.3947350E-ON65256E83.003FFE43@hss.hns.com>
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 27/04/2004
 05:10:13 PM
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.5 required=5.0 tests=EXCUSE_16,NO_REAL_NAME 
	autolearn=no version=2.60
Subject: [Sigtran] M3UA-v02 Last Call Comment
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>





Hi,
  As routing keys of type CIC and SSN were deleted from M3UA rfc3332 so IMO we should not give examples of CIC or SSN based routing keys as given in
section 1.2 while defining AS.

Snip <
  1.2 Terminology
   Application Server (AS) - A logical entity serving a specific
  Routing Key.  An example of an Application Server is a
  virtual switch element handling all call processing for a
   unique range of PSTN trunks, identified by an SS7
   SIO/DPC/OPC/CIC_range.  Another example is a  virtual
   database element, handling all HLR transactions for a
    particular SS7 DPC/OPC/SCCP_SSN combination.  The
    AS contains a set of one or more unique Application
   Server Processes, of which one or more is normally
   actively processing traffic.  Note that there is a   1:1
   relationship between an AS and a Routing Key.
    > Snip

Regards
Kamesh

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


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



From exim@www1.ietf.org  Tue Apr 27 08:38:10 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27510
	for <sigtran-archive@odin.ietf.org>; Tue, 27 Apr 2004 08:38:10 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIRjy-0007Ke-9h
	for sigtran-archive@odin.ietf.org; Tue, 27 Apr 2004 08:31:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3RCVAcL028181
	for sigtran-archive@odin.ietf.org; Tue, 27 Apr 2004 08:31:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIRbC-0003T7-Ov; Tue, 27 Apr 2004 08:22:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIRVH-00012K-9u
	for sigtran@optimus.ietf.org; Tue, 27 Apr 2004 08:15:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25827
	for <sigtran@ietf.org>; Tue, 27 Apr 2004 08:15:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BIRVC-0005N8-Cs
	for sigtran@ietf.org; Tue, 27 Apr 2004 08:15:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIRUR-00059I-00
	for sigtran@ietf.org; Tue, 27 Apr 2004 08:15:07 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[VYFPWyIWyHqtiVSGPuEszAP+xIiVHq2e])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIRTe-0004tT-00
	for sigtran@ietf.org; Tue, 27 Apr 2004 08:14:18 -0400
Received: from ns.pigworks.openss7.net (IDENT:S2AjixtCy3nONAXxOifU/nfI0fnsIkIO@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i3RCEJg11772;
	Tue, 27 Apr 2004 06:14:19 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i3RCEJw22310;
	Tue, 27 Apr 2004 06:14:19 -0600
Date: Tue, 27 Apr 2004 06:14:19 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: kakaul@hss.hns.com
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA-v02 Last Call Comment
Message-ID: <20040427061418.B21939@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: kakaul@hss.hns.com, sigtran@ietf.org
References: <OFFB79E9EE.3947350E-ON65256E83.003FFE43@hss.hns.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OFFB79E9EE.3947350E-ON65256E83.003FFE43@hss.hns.com>; from kakaul@hss.hns.com on Tue, Apr 27, 2004 at 05:13:31PM +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.1 required=5.0 tests=AWL,EXCUSE_16 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>

Kamesh,

Yes, I agree: strike the two sentences.

--brian

kakaul@hss.hns.com wrote:                                                           (Tue, 27 Apr 2004 17:13:31)
> 
> 
> 
> 
> Hi,
>   As routing keys of type CIC and SSN were deleted from M3UA rfc3332 so IMO
>   we should not give examples of CIC or SSN based routing keys as given in
>   section 1.2 while defining AS.
> 
> Snip <
>   1.2 Terminology
>    Application Server (AS) - A logical entity serving a specific
>   Routing Key.  An example of an Application Server is a
>   virtual switch element handling all call processing for a
>    unique range of PSTN trunks, identified by an SS7
>    SIO/DPC/OPC/CIC_range.  Another example is a  virtual
>    database element, handling all HLR transactions for a
>     particular SS7 DPC/OPC/SCCP_SSN combination.  The
>     AS contains a set of one or more unique Application
>    Server Processes, of which one or more is normally
>    actively processing traffic.  Note that there is a   1:1
>    relationship between an AS and a Routing Key.
>     > Snip
> 
> Regards
> Kamesh
> 
> "DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
> (HSS) and is intended solely for the use of the individual to whom it is
> addressed. It may contain  privileged or confidential information and
> should not be circulated or used for any purpose other than for what it is
> intended. If you have received this message in error, please notify the
> originator immediately. If you are not the intended recipient, you are
> notified that you are strictly prohibited from using, copying, altering, or
> disclosing the contents of this message. HSS accepts no responsibility for
> loss or damage arising from the use of the information transmitted by this
> email including damage from virus."
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Tue Apr 27 13:10:54 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14054
	for <sigtran-archive@odin.ietf.org>; Tue, 27 Apr 2004 13:10:54 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIVt6-0001rd-D8
	for sigtran-archive@odin.ietf.org; Tue, 27 Apr 2004 12:56:52 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3RGuqoH007165
	for sigtran-archive@odin.ietf.org; Tue, 27 Apr 2004 12:56:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIVmU-0008Og-8R; Tue, 27 Apr 2004 12:50:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIVV0-0003CJ-PC
	for sigtran@optimus.ietf.org; Tue, 27 Apr 2004 12:31:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10552
	for <sigtran@ietf.org>; Tue, 27 Apr 2004 12:31:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BIVUx-0002AB-6b
	for sigtran@ietf.org; Tue, 27 Apr 2004 12:31:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIVU2-00027x-00
	for sigtran@ietf.org; Tue, 27 Apr 2004 12:30:58 -0400
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 1BIVTg-00025Y-00
	for sigtran@ietf.org; Tue, 27 Apr 2004 12:30:37 -0400
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i3RGUc7T030208;
	Tue, 27 Apr 2004 12:30:38 -0400
From: "Barry Nagelberg" <barryn@adax.com>
To: "Lode Coene" <Lode.Coene@siemens.com>
Cc: "SIGTRAN Mailing List" <sigtran@ietf.org>
Date: Tue, 27 Apr 2004 12:32:14 -0400
Message-ID: <JBECLENKLBCKAAKFGAJOKEINCGAA.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)
x-mimeole: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <JBECLENKLBCKAAKFGAJOKEGOCGAA.barryn@adax.com>
Importance: Normal
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 IG: Usage of TID labels
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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

Lode,

Here is some updated suggested text for the SUA IG, regarding the usage of
TID labels.

I suggest that we have some mailing list discussion, or poll, or something
on this issue, even prior to publication of the SUA IG. In spite of the fact
that SUA v16 is very unclear on the use of these labels, we're apparently
moving towards the RFC stage, and companies are moving ahead on SUA
implementation. If we're not careful, we run the risk of ending up with
incompatible implementations.

In section 4.7.2.1 (Association Setup, ASP going active):

<snip>
In the ASPAC message, the ASP optionally includes a TID and/or DRN Label
Parameter for each AS. If more than one ASP in a given AS includes a TID
and/or DRN Label Parameter, then these ASPs must specify a unique label at a
fixed position in the TID or DRN parameter. The same ASPAC message is sent
to each SG used for interworking with the SS7 network.

If an ASP does not include a TID and/or DRN Label Parameter in the ASPAC
message, then the SG MAY send a TCAP message with any TID or DRN to this
ASP.
<snip>

In section 4.7.3.1 (Routing and message distribution at the SG - TCAP
traffic):

<snip>
   a. The SG examines the bits between the 'Start' bit and the 'End' bit
   of the received TCAP transaction ID (TID). The 'Start' and 'End' bits
   are defined in the 'TID Label' parameter that was sent in the ASPAC
   message for this AS.

   b. If these bits exactly match the 'Label' field of the 'TID Label'
   parameter that was sent in the ASPAC message, then the message is sent
   to the ASP that registered for this label via the ASPAC msg.

   c. If these bits do not match the label field of any ASP in this AS,
   then the SG may discard the message.
<snip>

Barry Nagelberg


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



From exim@www1.ietf.org  Tue Apr 27 19:18:18 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09581
	for <sigtran-archive@odin.ietf.org>; Tue, 27 Apr 2004 19:18:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIbol-0005wj-0I
	for sigtran-archive@odin.ietf.org; Tue, 27 Apr 2004 19:16:47 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3RNGkw2022852
	for sigtran-archive@odin.ietf.org; Tue, 27 Apr 2004 19:16:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIbk8-0005OP-L0; Tue, 27 Apr 2004 19:12:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIbiS-0005AU-IC
	for sigtran@optimus.ietf.org; Tue, 27 Apr 2004 19:10:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09402
	for <sigtran@ietf.org>; Tue, 27 Apr 2004 19:10:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BIbiN-0001G5-9u
	for sigtran@ietf.org; Tue, 27 Apr 2004 19:10:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIbhQ-0001B9-00
	for sigtran@ietf.org; Tue, 27 Apr 2004 19:09:13 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[Zq5ZzjOKI5qWnZ2FVaPNp9D3rfPAJ6f9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIbgo-00015x-00
	for sigtran@ietf.org; Tue, 27 Apr 2004 19:08:34 -0400
Received: from ns.pigworks.openss7.net (IDENT:urFR2yZLXLkHvruOUIqjI1pX134baUcA@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i3RN8Zg25410;
	Tue, 27 Apr 2004 17:08:35 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i3RN8Y330490;
	Tue, 27 Apr 2004 17:08:34 -0600
Date: Tue, 27 Apr 2004 17:08:34 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry Nagelberg <barryn@adax.com>
Cc: Lode Coene <Lode.Coene@siemens.com>,
        SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA IG: Usage of TID labels
Message-ID: <20040427170834.A25958@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry Nagelberg <barryn@adax.com>,
	Lode Coene <Lode.Coene@siemens.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <JBECLENKLBCKAAKFGAJOKEGOCGAA.barryn@adax.com> <JBECLENKLBCKAAKFGAJOKEINCGAA.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: <JBECLENKLBCKAAKFGAJOKEINCGAA.barryn@adax.com>; from barryn@adax.com on Tue, Apr 27, 2004 at 12:32:14PM -0400
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,

Barry Nagelberg wrote:                                                               (Tue, 27 Apr 2004 12:32:14)
> Lode,
> 
> Here is some updated suggested text for the SUA IG, regarding the usage of
> TID labels.
> 
> I suggest that we have some mailing list discussion, or poll, or something
> on this issue, even prior to publication of the SUA IG. In spite of the fact
> that SUA v16 is very unclear on the use of these labels, we're apparently
> moving towards the RFC stage, and companies are moving ahead on SUA
> implementation. If we're not careful, we run the risk of ending up with
> incompatible implementations.
> 
> In section 4.7.2.1 (Association Setup, ASP going active):
> 
> <snip>
> In the ASPAC message, the ASP optionally includes a TID and/or DRN Label
> Parameter for each AS. If more than one ASP in a given AS includes a TID
> and/or DRN Label Parameter, then these ASPs must specify a unique label at a
> fixed position in the TID or DRN parameter. The same ASPAC message is sent
> to each SG used for interworking with the SS7 network.
> 
> If an ASP does not include a TID and/or DRN Label Parameter in the ASPAC
> message, then the SG MAY send a TCAP message with any TID or DRN to this
> ASP.

I don't think that it was really the intent to have some APSs register TID or
DRN labels and some not.  I believe the intent was that all ASPs register TID
or DRN labels, or none.  Otherwise, if some register TID/DRN label and some do
not, there is an ambiguity as to where any given message will be sent.

draft-bidulock-sigtran-loadsel-02.txt describes a technique for using TID/DRN
labels across load sharing pools in a more structured way.  This draft is out
of date, so I will resubmit it shortly.  You can pull up a copy of the
outdated draft from http://www.openss7.org/sigtran01.html if you want to take
a look in the meantime.

> <snip>
> 
> In section 4.7.3.1 (Routing and message distribution at the SG - TCAP
> traffic):
> 
> <snip>
>    a. The SG examines the bits between the 'Start' bit and the 'End' bit
>    of the received TCAP transaction ID (TID). The 'Start' and 'End' bits
>    are defined in the 'TID Label' parameter that was sent in the ASPAC
>    message for this AS.
> 
>    b. If these bits exactly match the 'Label' field of the 'TID Label'
>    parameter that was sent in the ASPAC message, then the message is sent
>    to the ASP that registered for this label via the ASPAC msg.
> 
>    c. If these bits do not match the label field of any ASP in this AS,
>    then the SG may discard the message.
> <snip>

Discard would not be a good thing from an SS7 network perspective.  Which
SS7 message an SG discards or returns on error from the SS7 side of the
node is the business of SS7 and not SUA.  Please remove mention of discard.
More interesting is what needs to be done with the message if it is not
discarded.  Perhaps sent to any other active ASP for the RC so that the
SCCP application can deal with aborting the transaction or reseting the
connection as required by the particular SCCP application.

If you look at draft-bidulock-sigtran-loadsel-02.txt it is possible using
this approach to pend on a load selection while giving notification of
failure within a load selection to give other APSs an opportunity to sync
connection/transaction state and register for the load selection.

--brian

> 
> 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 Apr 29 00:03:44 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16035
	for <sigtran-archive@odin.ietf.org>; Thu, 29 Apr 2004 00:03:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJ2iL-0000nK-MI
	for sigtran-archive@odin.ietf.org; Wed, 28 Apr 2004 23:59:57 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3T3xvP1003030
	for sigtran-archive@odin.ietf.org; Wed, 28 Apr 2004 23:59:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJ2aj-0007Yy-J8; Wed, 28 Apr 2004 23:52:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJ2Rg-0005hX-E6
	for sigtran@optimus.ietf.org; Wed, 28 Apr 2004 23:42:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14667
	for <sigtran@ietf.org>; Wed, 28 Apr 2004 23:42:39 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BJ2Rb-0004vd-7A
	for sigtran@ietf.org; Wed, 28 Apr 2004 23:42:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJ2Qd-0004nh-00
	for sigtran@ietf.org; Wed, 28 Apr 2004 23:41:40 -0400
Received: from spark.hss.co.in ([203.200.71.140])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJ2Pg-0004ag-00
	for sigtran@ietf.org; Wed, 28 Apr 2004 23:40:40 -0400
Received: from sandesh.hss.hns.com (sandesh.hss.hns.com [139.85.242.35])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id i3T3d0X4004506
	for <sigtran@ietf.org>; Thu, 29 Apr 2004 09:09:00 +0530 (IST)
Subject: [Sigtran] M3UA-v02 Last Call Comment
To: sigtran@ietf.org
Date: Thu, 29 Apr 2004 09:02:47 +0530
Message-ID: <OF88C2A634.76E9516D-ON65256E85.0012CCC5@hss.hns.com>
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 29/04/2004
 08:59:28 AM
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.5 required=5.0 tests=AWL,EXCUSE_16,NO_REAL_NAME 
	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,

   The list of ASPs in an AS is assumed to be dynamic, taking into
   account the availability, traffic handling capability and congestion
   status of the individual ASPs in the list. How does one avoid
   missequence of Signalling traffic in case one of the active ASP
   transitions from ACTIVE to INACTIVE and vice-versa.

   Are there any controlled rerouting procedures specified in current
   M3UA v02 draft.

Regards
Kamesh

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


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



From exim@www1.ietf.org  Thu Apr 29 01:05:53 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18793
	for <sigtran-archive@odin.ietf.org>; Thu, 29 Apr 2004 01:05:53 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJ3hR-0005Q4-Ur
	for sigtran-archive@odin.ietf.org; Thu, 29 Apr 2004 01:03:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3T535KS020833
	for sigtran-archive@odin.ietf.org; Thu, 29 Apr 2004 01:03:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJ3Xi-0004HD-9W; Thu, 29 Apr 2004 00:53:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJ3Sk-0003EP-SZ
	for sigtran@optimus.ietf.org; Thu, 29 Apr 2004 00:47:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17865
	for <sigtran@ietf.org>; Thu, 29 Apr 2004 00:47:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BJ3Se-00051o-Sj
	for sigtran@ietf.org; Thu, 29 Apr 2004 00:47:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJ3Rm-0004vH-00
	for sigtran@ietf.org; Thu, 29 Apr 2004 00:46:55 -0400
Received: from web12822.mail.yahoo.com ([216.136.174.203])
	by ietf-mx with smtp (Exim 4.12)
	id 1BJ3RQ-0004oC-00
	for sigtran@ietf.org; Thu, 29 Apr 2004 00:46:32 -0400
Message-ID: <20040429044634.19129.qmail@web12822.mail.yahoo.com>
Received: from [68.44.141.139] by web12822.mail.yahoo.com via HTTP; Wed, 28 Apr 2004 21:46:34 PDT
Date: Wed, 28 Apr 2004 21:46:34 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA-v02 Last Call Comment
To: sigtran@ietf.org
In-Reply-To: <OF88C2A634.76E9516D-ON65256E85.0012CCC5@hss.hns.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>

As far as I recall, such procedures were defined in
one of Brian's drafts -cordId(?)-. I also think,
mentioning about this briefly might be a good idea. 

BTW, this also applies for ASP->SGP direction.
Basically whenever the SCTP association (or stream)
used for a group of messages changes, care should be
taken to decrease possibility of missequencing.

   Tolga
--- kakaul@hss.hns.com wrote:
> 
> 
> 
> 
> Hi,
> 
>    The list of ASPs in an AS is assumed to be
> dynamic, taking into
>    account the availability, traffic handling
> capability and congestion
>    status of the individual ASPs in the list. How
> does one avoid
>    missequence of Signalling traffic in case one of
> the active ASP
>    transitions from ACTIVE to INACTIVE and
> vice-versa.
> 
>    Are there any controlled rerouting procedures
> specified in current
>    M3UA v02 draft.
> 
> Regards
> Kamesh
> 
> "DISCLAIMER: This message is proprietary to Hughes
> Software Systems Limited
> (HSS) and is intended solely for the use of the
> individual to whom it is
> addressed. It may contain  privileged or
> confidential information and
> should not be circulated or used for any purpose
> other than for what it is
> intended. If you have received this message in
> error, please notify the
> originator immediately. If you are not the intended
> recipient, you are
> notified that you are strictly prohibited from
> using, copying, altering, or
> disclosing the contents of this message. HSS accepts
> no responsibility for
> loss or damage arising from the use of the
> information transmitted by this
> email including damage from virus."
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


	
		
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs  
http://hotjobs.sweepstakes.yahoo.com/careermakeover 

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



