From exim@www1.ietf.org  Sun Feb  1 09:05:25 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11616
	for <sigtran-archive@odin.ietf.org>; Sun, 1 Feb 2004 09:05:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnIDb-0005ix-4K
	for sigtran-archive@odin.ietf.org; Sun, 01 Feb 2004 09:04:59 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i11E4xfV021993
	for sigtran-archive@odin.ietf.org; Sun, 1 Feb 2004 09:04:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnIDa-0005iY-Ss
	for sigtran-web-archive@optimus.ietf.org; Sun, 01 Feb 2004 09:04:58 -0500
Date: Sun, 01 Feb 2004 09:04:58 -0500
Message-ID: <20040201140458.1364.34123.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  Mon Feb  2 05:03:33 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29982
	for <sigtran-archive@odin.ietf.org>; Mon, 2 Feb 2004 05:03:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Anav3-0003vs-U4
	for sigtran-archive@odin.ietf.org; Mon, 02 Feb 2004 05:03:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i12A35oF015098
	for sigtran-archive@odin.ietf.org; Mon, 2 Feb 2004 05:03:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Anauz-0003uo-Pt; Mon, 02 Feb 2004 05:03:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnauP-0003tF-0l
	for sigtran@optimus.ietf.org; Mon, 02 Feb 2004 05:02:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29945
	for <sigtran@ietf.org>; Mon, 2 Feb 2004 05:02:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnauL-0006TR-00
	for sigtran@ietf.org; Mon, 02 Feb 2004 05:02:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnatP-0006PV-00
	for sigtran@ietf.org; Mon, 02 Feb 2004 05:01:23 -0500
Received: from relay-5v.club-internet.fr ([194.158.96.110])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Anasa-0006LS-00
	for sigtran@ietf.org; Mon, 02 Feb 2004 05:00:32 -0500
Received: from PascalB (f14m-9-226.d1.club-internet.fr [212.195.96.226])
	by relay-5v.club-internet.fr (Postfix) with SMTP id C66C01763
	for <sigtran@ietf.org>; Mon,  2 Feb 2004 11:00:13 +0100 (CET)
Message-ID: <00fe01c3e973$6132dce0$1600a8c0@PascalB>
From: "Pascal Bouveron (Netbricks)" <pascal.bouveron@netbricks.com>
To: <sigtran@ietf.org>
Date: Mon, 2 Feb 2004 11:00:04 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] V5UA Message Class 9 (V5PTM) conflicts with M3UA RKM Class
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hello,

Looking at V5UA draft 04, it appears that the Message Class chosen for V5
Boundary Primitives Transport Messages (V5PTM) conflicts with M3UA RKM
Message Class: both are defined to be 9.

I think it would be a good idea to use a different Class value, so as to
have consistent Class definitions throughout all UAs.

Any comments ?

Best regards / Meilleures salutations
Pascal Bouveron
=============================================
www.netbricks.com
Netbricks - Provence - FRANCE
Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
=============================================


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



From exim@www1.ietf.org  Mon Feb  2 05:30:32 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01460
	for <sigtran-archive@odin.ietf.org>; Mon, 2 Feb 2004 05:30:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnbLB-0006sA-El
	for sigtran-archive@odin.ietf.org; Mon, 02 Feb 2004 05:30:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i12AU51H026401
	for sigtran-archive@odin.ietf.org; Mon, 2 Feb 2004 05:30:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnbL8-0006rY-Mq; Mon, 02 Feb 2004 05:30:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnbKc-0006r0-Sv
	for sigtran@optimus.ietf.org; Mon, 02 Feb 2004 05:29:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01434
	for <sigtran@ietf.org>; Mon, 2 Feb 2004 05:29:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnbKZ-0001s6-00
	for sigtran@ietf.org; Mon, 02 Feb 2004 05:29:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnbJf-0001nb-00
	for sigtran@ietf.org; Mon, 02 Feb 2004 05:28:32 -0500
Received: from relay-6v.club-internet.fr ([194.158.96.111])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnbJK-0001i6-00
	for sigtran@ietf.org; Mon, 02 Feb 2004 05:28:10 -0500
Received: from PascalB (f14m-9-226.d1.club-internet.fr [212.195.96.226])
	by relay-6v.club-internet.fr (Postfix) with SMTP
	id C27A325730; Mon,  2 Feb 2004 11:28:10 +0100 (CET)
Message-ID: <012301c3e977$40d00320$1600a8c0@PascalB>
From: "Pascal Bouveron (Netbricks)" <pascal.bouveron@netbricks.com>
To: "Eva Weilandt" <eva.weilandt@nortelnetworks.com>, <sigtran@ietf.org>
References: <9F8B82425D82D511B5AC0002A55CCCAF071F287F@zfdhc101-int2.europe.nortel.com>
Date: Mon, 2 Feb 2004 11:28:05 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0120_01C3E97F.A046AA90"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_30_40,HTML_MESSAGE 
	autolearn=no version=2.60
Subject: [Sigtran] V5UA Parameter Tags conflict with M3UA Tags
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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_0120_01C3E97F.A046AA90
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

AW: [Sigtran] V5UA Message Class 9 (V5PTM) conflicts with M3UA RKM =
ClassHello,

I found other conflicts between V5UA and other UAs, in the Parameter =
Tags definitions:

Tag 0x0011: "ASP Identifier" for M3UA, but "Link Status" for V5UA
Tag 0x0012: "Affected Point Code" for M3UA, but "Sa-Bit" (it actually =
has no name in draft-04) for V5UA
Tag 0x0013: "Correlation Id" for M3UA, but "Error Reason" for V5UA

Best regards / Meilleures salutations
Pascal Bouveron
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
www.netbricks.com
Netbricks - Provence - FRANCE
Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

------=_NextPart_000_0120_01C3E97F.A046AA90
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>AW: [Sigtran] V5UA Message Class 9 (V5PTM) conflicts =
with M3UA RKM Class</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I found other conflicts between V5UA =
and other UAs,=20
in the Parameter Tags definitions:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Tag 0x0011: "ASP Identifier" for M3UA, =
but "Link=20
Status" for V5UA</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tag 0x0012: "Affected Point Code" for =
M3UA, but=20
"Sa-Bit" (it actually has no name in draft-04) for V5UA</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tag 0x0013: "Correlation Id" for M3UA, =
but "Error=20
Reason"&nbsp;for V5UA</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>Best regards / Meilleures salutations<BR>Pascal=20
Bouveron<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<=
BR><A=20
href=3D"http://www.netbricks.com">www.netbricks.com</A><BR>Netbricks - =
Provence -=20
FRANCE<BR>Tel: (+33) (0)4 42 91 44 77 -- Fax:&nbsp; (+33) (0)4 42 91 44=20
71<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0120_01C3E97F.A046AA90--


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



From exim@www1.ietf.org  Mon Feb  2 16:08:32 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10043
	for <sigtran-archive@odin.ietf.org>; Mon, 2 Feb 2004 16:08:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnlIa-0007ju-5O
	for sigtran-archive@odin.ietf.org; Mon, 02 Feb 2004 16:08:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i12L84cQ029741
	for sigtran-archive@odin.ietf.org; Mon, 2 Feb 2004 16:08:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnlIY-0007il-22; Mon, 02 Feb 2004 16:08:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnlI6-0007Xf-Q4
	for sigtran@optimus.ietf.org; Mon, 02 Feb 2004 16:07:34 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09860;
	Mon, 2 Feb 2004 16:07:31 -0500 (EST)
Message-Id: <200402022107.QAA09860@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 02 Feb 2004 16:07:31 -0500
Subject: [Sigtran] I-D ACTION:draft-ietf-sigtran-m2pa-11.txt
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: SS7 MTP2-User Peer-to-Peer Adaptation Layer
	Author(s)	: T. George
	Filename	: draft-ietf-sigtran-m2pa-11.txt
	Pages		: 56
	Date		: 2004-2-2
	
This Internet Draft defines a protocol supporting the transport of
Signaling System Number 7 (SS7) Message Transfer Part (MTP) Level 3
signaling messages over Internet Protocol (IP) using the services of
the Stream Control Transmission Protocol (SCTP).  This protocol would
be used between SS7 Signaling Points using the MTP Level 3
protocol. The SS7 Signaling Points may also use standard SS7 links
using the SS7 MTP Level 2 to provide transport of MTP Level 3
signaling messages. The protocol operates in a manner similar to MTP
Level 2 so as to provide peer-to-peer communication between SS7
endpoints.

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

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

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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sigtran-m2pa-11.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-2-2151139.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sigtran-m2pa-11.txt

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

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

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Tue Feb  3 15:30: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 PAA29320
	for <sigtran-archive@odin.ietf.org>; Tue, 3 Feb 2004 15:30:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ao7BN-0006yB-0e
	for sigtran-archive@odin.ietf.org; Tue, 03 Feb 2004 15:30:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i13KU4TB026786
	for sigtran-archive@odin.ietf.org; Tue, 3 Feb 2004 15:30:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ao7BJ-0006ws-FH; Tue, 03 Feb 2004 15:30:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ao7Ax-0006tL-Nu
	for sigtran@optimus.ietf.org; Tue, 03 Feb 2004 15:29:39 -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 PAA29300
	for <sigtran@ietf.org>; Tue, 3 Feb 2004 15:29:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ao7Aw-0007nS-00
	for sigtran@ietf.org; Tue, 03 Feb 2004 15:29:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ao79y-0007ic-00
	for sigtran@ietf.org; Tue, 03 Feb 2004 15:28:39 -0500
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ao79J-0007YT-00
	for sigtran@ietf.org; Tue, 03 Feb 2004 15:27:57 -0500
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i13KRLiX020530;
	Tue, 3 Feb 2004 14:27:22 -0600 (CST)
Message-ID: <40200417.7010904@alcatel.com>
Date: Tue, 03 Feb 2004 14:27:03 -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: "'sigtran@ietf.org'" <sigtran@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M2PA - changes in version 11
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-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

List of comments on M2PA draft version 10.
Tom George
01/29/04

Here is my list of comments on M2PA draft version 10 and how they were
incorporated into version 11. For the most part, they are arranged by
the thread from the SIGTRAN list. The date/name/subject identify the
beginning of the thread.

01. 10/21/03 New email address for Hanns.

     A: Done.

02. 10/21/03 Schwarzbauer Hanns Juergen "[Sigtran] M2PA v10 - comments
     on M2PA draft version 9".

     Dates for some of the ITU references are wrong. Need to add
     implementor's guides.

     A: Updated some references. Added Implementors Guides.

03. 10/22/03 Andrew Booth "[Sigtran] M2PA 10: PO editorial".

     Forgot to mention the LS Ready sent by the LPO end.

     A: Added paragraph stating that the end formerly in LPO sends LS
     Ready.

04. 11/05/03 Frank Bevacqua "Question on M2PA Timer Values". Private
     email.

     In section 4, add statement that the corresponding applicable
     timer value defaults and ranges specified for the applicable MTP2
     standard should be used for the M2PA timers.

     A: This is implied by the text, but I added a paragraph in section
     4 making it explicit.

05. 12/01/03 Tom George "[Sigtran] M2PA registered port number".

     In 4.1.2, is it necessary to use the registered port number?

     A: Text is OK, says Jon Peterson. Not necessary, but a good idea.

06. 12/24/03 Franck Boesch "[Sigtran] SIGTRAN - M2PA draft 10 - T7
     timer at Busy End".

     Clarify text about T7?

     A: No. This came up in the earlier T7 discussion. We do not want
     to imply an implementation.

07. 01/08/04 Franz Gaiser "[Sigtran] M2PA draft 10 - Processor
     outage". Question about Flush and Continue.

     A: No change needed to the document. Just do what MTP2 does.

08. 01/12/04 Franck Boesch "[Sigtran] M2PA - draft 10 - Link Status
     Ready received during T4 period".

     A: No change needed to the document. Just do what MTP2 does.

09. 01/06/04 Comments from Jon Peterson (AD).

     A:

        a. Section 1.1, last paragraph: "SHOULD" is changed to
	  "should", since this is a statement of the motivation for
	  M2PA rather than a list of requirements.

        b. Point code sharing? No. No change needed to the document.

        c. 1.6.2: Are FISUs sent? No. Some explanation was added about
	  the protocols used in Figure 2 in 1.5.

        d. 3.1: Associating replaces Associate.

        e. 6.1: Security requirements strengthened to MUST. Reference
	  updated for [Security].

        f. 7.2: Added paragraph to 7.2 about the registry. Added
	  section 7.2.4 to list defined values.


-- 
* 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  Wed Feb  4 07:54: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 HAA04185
	for <sigtran-archive@odin.ietf.org>; Wed, 4 Feb 2004 07:54:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoMXc-0002AC-Ar
	for sigtran-archive@odin.ietf.org; Wed, 04 Feb 2004 07:54:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i14Cs48t008295
	for sigtran-archive@odin.ietf.org; Wed, 4 Feb 2004 07:54:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoMXZ-00029a-09; Wed, 04 Feb 2004 07:54:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoMWh-00028q-5N
	for sigtran@optimus.ietf.org; Wed, 04 Feb 2004 07:53:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04149
	for <sigtran@ietf.org>; Wed, 4 Feb 2004 07:53:05 -0500 (EST)
From: jeffrey.craig@tekelec.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoMWg-0000Dk-00
	for sigtran@ietf.org; Wed, 04 Feb 2004 07:53:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AoMVj-00009W-00
	for sigtran@ietf.org; Wed, 04 Feb 2004 07:52:08 -0500
Received: from [198.89.32.2] (helo=domino2.nc.tekelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoMVQ-000050-00
	for sigtran@ietf.org; Wed, 04 Feb 2004 07:51:48 -0500
Received: from domino4.nc.tekelec.com ([198.89.40.9])
          by domino2.nc.tekelec.com (Lotus Domino Release 5.0.12)
          with ESMTP id 2004020407462368:35198 ;
          Wed, 4 Feb 2004 07:46:23 -0500 
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.7  March 21, 2001
Message-ID: <OF120E3422.6C3AD28C-ON85256E30.004656FD@nc.tekelec.com>
Date: Wed, 4 Feb 2004 07:49:44 -0500
MIME-Version: 1.0
X-MIMETrack: Serialize by Router on Domino4/Raleigh/TEKELEC(Release 5.0.12  |February 13, 2003) at
 02/04/2004 07:49:44 AM,
	Itemize by SMTP Server on Domino2/Raleigh/TEKELEC(Release 5.0.12  |February
 13, 2003) at 02/04/2004 07:46:23 AM,
	Serialize by Router on Domino2/Raleigh/TEKELEC(Release 5.0.12  |February 13, 2003) at
 02/04/2004 07:47:03 AM,
	Serialize complete at 02/04/2004 07:47:03 AM
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.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Subject: [Sigtran] M2PA review status and draft v11
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hello All,

Can anyone provide some info. on the status of M2PA in the review
process? I am curious how the recently released draft v11 factors
into that process. Thanks.

Regards,

Jeff



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



From exim@www1.ietf.org  Wed Feb  4 08:50: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 IAA05666
	for <sigtran-archive@odin.ietf.org>; Wed, 4 Feb 2004 08:50:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoNPo-0005yN-Nw
	for sigtran-archive@odin.ietf.org; Wed, 04 Feb 2004 08:50:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i14Do4tv022938
	for sigtran-archive@odin.ietf.org; Wed, 4 Feb 2004 08:50:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoNPl-0005xP-79; Wed, 04 Feb 2004 08:50:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoNOz-0005wY-IH
	for sigtran@optimus.ietf.org; Wed, 04 Feb 2004 08:49:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05629
	for <sigtran@ietf.org>; Wed, 4 Feb 2004 08:49:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoNOy-0005Wu-00
	for sigtran@ietf.org; Wed, 04 Feb 2004 08:49:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AoNO1-0005Rt-00
	for sigtran@ietf.org; Wed, 04 Feb 2004 08:48:14 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[2bhr6cegPlvpCKdZFiA1v37Ah/CcZWn5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoNNU-0005Mw-00
	for sigtran@ietf.org; Wed, 04 Feb 2004 08:47:41 -0500
Received: from ns.pigworks.openss7.net (IDENT:/H8D1R2PgPUVhOkljo46thDMcG9uortL@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i14DlaI14657;
	Wed, 4 Feb 2004 06:47:36 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i14DlZT30778;
	Wed, 4 Feb 2004 06:47:35 -0700
Date: Wed, 4 Feb 2004 06:47:35 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: jeffrey.craig@tekelec.com
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M2PA review status and draft v11
Message-ID: <20040204064735.A30749@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: jeffrey.craig@tekelec.com, sigtran@ietf.org
References: <OF120E3422.6C3AD28C-ON85256E30.004656FD@nc.tekelec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF120E3422.6C3AD28C-ON85256E30.004656FD@nc.tekelec.com>; from jeffrey.craig@tekelec.com on Wed, Feb 04, 2004 at 07:49:44AM -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>

jeffrey.craig,

I believe it was released to address AD comments.  AFAIK it has not
yet advanced to 48hours, but should soon.

--brian

jeffrey.craig@tekelec.com wrote:                                             (Wed, 04 Feb 2004 07:49:44)
> Hello All,
> 
> Can anyone provide some info. on the status of M2PA in the review
> process? I am curious how the recently released draft v11 factors
> into that process. Thanks.
> 
> Regards,
> 
> Jeff
> 
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Wed Feb  4 11:21: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 LAA12960
	for <sigtran-archive@odin.ietf.org>; Wed, 4 Feb 2004 11:21:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoPlw-00077K-Dn
	for sigtran-archive@odin.ietf.org; Wed, 04 Feb 2004 11:21:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i14GL4KI027337
	for sigtran-archive@odin.ietf.org; Wed, 4 Feb 2004 11:21:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoPls-00074K-Se; Wed, 04 Feb 2004 11:21:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoPl7-00073N-Ei
	for sigtran@optimus.ietf.org; Wed, 04 Feb 2004 11:20:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12839
	for <sigtran@ietf.org>; Wed, 4 Feb 2004 11:20:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoPl6-0005ey-00
	for sigtran@ietf.org; Wed, 04 Feb 2004 11:20:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AoPk7-0005ZX-00
	for sigtran@ietf.org; Wed, 04 Feb 2004 11:19:12 -0500
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoPj8-0005PK-00
	for sigtran@ietf.org; Wed, 04 Feb 2004 11:18:10 -0500
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i14GHd8d027744;
	Wed, 4 Feb 2004 10:17:39 -0600 (CST)
Message-ID: <40211B23.1080008@alcatel.com>
Date: Wed, 04 Feb 2004 10:17:39 -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: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M2PA review status and draft v11
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

That's right. Version 11 addresses the AD comments, plus a few other
comments I received since version 10.

tomG.

Brian F. G. Bidulock wrote:
 > jeffrey.craig,
 >
 > I believe it was released to address AD comments.  AFAIK it has not
 > yet advanced to 48hours, but should soon.
 >
 > --brian
 >
 > jeffrey.craig@tekelec.com wrote: 
         (Wed, 04 Feb 2004 07:49:44)
 >
 >>Hello All,
 >>
 >>Can anyone provide some info. on the status of M2PA in the review
 >>process? I am curious how the recently released draft v11 factors
 >>into that process. Thanks.
 >>
 >>Regards,
 >>
 >>Jeff


-- 
* 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  Wed Feb  4 16:00:42 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 QAA26628
	for <sigtran-archive@odin.ietf.org>; Wed, 4 Feb 2004 16:00:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoU85-00062B-At
	for sigtran-archive@odin.ietf.org; Wed, 04 Feb 2004 16:00:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i14L0DrF023195
	for sigtran-archive@odin.ietf.org; Wed, 4 Feb 2004 16:00:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoU7z-00061M-CV; Wed, 04 Feb 2004 16:00:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoU7L-0005xt-Hz
	for sigtran@optimus.ietf.org; Wed, 04 Feb 2004 15:59:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26543
	for <sigtran@ietf.org>; Wed, 4 Feb 2004 15:59:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoU7J-0003JD-00
	for sigtran@ietf.org; Wed, 04 Feb 2004 15:59:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AoU6N-0003Dz-00
	for sigtran@ietf.org; Wed, 04 Feb 2004 15:58:28 -0500
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoU5s-00038r-00
	for sigtran@ietf.org; Wed, 04 Feb 2004 15:57:56 -0500
Received: from [10.0.1.2] (pD9FF180B.dip.t-dialin.net [217.255.24.11])
	by mail-n.franken.de (Postfix) with ESMTP id C97A4245FC
	for <sigtran@ietf.org>; Wed,  4 Feb 2004 21:56:51 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v612)
Content-Transfer-Encoding: 7bit
Message-Id: <A3284A14-5754-11D8-86DB-000A95DC192A@lurchi.franken.de>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: sigtran@ietf.org
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Date: Wed, 4 Feb 2004 21:56:43 +0100
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M3UA version control
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Dear all,

the RFC describes that an M3UA endpoint should check the version field
for ASP Up messages and leaves it unspecified how other messages should
be handled.

In real scenarios the first message having an unsupported message is
most likely an ASP-Up message, but my experience is, that people testing
implementations always ask how these other messages should be handled.

Therefore I would like to suggest a clarification in the IG clearly
stating how these other messages with an unsupported version should
be handled.

We can specify that it is checked for all messages or only for ASP-Up
messages, ignoring the version field for non ASP-Up messages.

The easiest solution seems to be (for me) to check the field for
all messages. So you could write

if (message->version != 1)
   send(error)

instead of

if ((message->class == 3) && (message->type == 1) && 
(message->(message->version != 1))
   send(error)

Therefore I suggest to include the following text in the IG.

Best regards
Michael


<---- SNIP
3.28 Version Control

3.28.1 Description of the problem

The RFC describes how ASP Up messages with an unsupported version
are handled but leaves it unspecified how other messages should be
handled if the version number is not supported.

3.28.2 Text changes to the document
    ---------
    Old text: (Section 4.3.4.1.1)
    ---------

4.3.4.1.1 M3UA Version Control

    If an ASP Up message with an unsupported version is received, the
    receiving end responds with an Error message, indicating the version
    the receiving node supports and notifies Layer Management.

    This is useful when protocol version upgrades are being performed in
    a network.  A node upgraded to a newer version should support the
    older versions used on other nodes it is communicating with.  Because
    ASPs initiate the ASP Up procedure it is assumed that the Error
    message would normally come from the SGP.

    ---------
    New text: (Section 4.3.4.1.1)
    ---------

4.3.4.1.1 M3UA Version Control

    If a message with an unsupported version is received, the
    receiving end responds with an Error message, indicating the version
    the receiving node supports and notifies Layer Management.

    This is useful when protocol version upgrades are being performed in
    a network.  A node upgraded to a newer version should support the
    older versions used on other nodes it is communicating with.  Because
    ASPs initiate the ASP Up procedure it is likely that the message 
having
    an unsupported version is an ASP Up message and therefore that the 
Error
    message would normally come from the SGP.


3.28.3 Solution description

The new text clearly describes that the version should be checked for 
all
messages.
<---- SNIP


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



From exim@www1.ietf.org  Wed Feb  4 17:49: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 RAA05465
	for <sigtran-archive@odin.ietf.org>; Wed, 4 Feb 2004 17:49:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoVpO-0006hR-Sp
	for sigtran-archive@odin.ietf.org; Wed, 04 Feb 2004 17:49:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i14Mn25a025731
	for sigtran-archive@odin.ietf.org; Wed, 4 Feb 2004 17:49:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoVpN-0006gl-9J; Wed, 04 Feb 2004 17:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoVoo-0006fz-PF
	for sigtran@optimus.ietf.org; Wed, 04 Feb 2004 17:48:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05422
	for <sigtran@ietf.org>; Wed, 4 Feb 2004 17:48:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoVom-0003Dn-00
	for sigtran@ietf.org; Wed, 04 Feb 2004 17:48:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AoVnp-000390-00
	for sigtran@ietf.org; Wed, 04 Feb 2004 17:47:25 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[NY6wUdy3jTC9aCjIVTnxxNJoeuTNNOSD])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoVmt-00034G-00
	for sigtran@ietf.org; Wed, 04 Feb 2004 17:46:27 -0500
Received: from ns.pigworks.openss7.net (IDENT:vdFDVPJwdbwWc3nlJ2ZkMHJjOEmmSFkj@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i14MkRI24844;
	Wed, 4 Feb 2004 15:46:27 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i14MkQ804900;
	Wed, 4 Feb 2004 15:46:26 -0700
Date: Wed, 4 Feb 2004 15:46:26 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA version control
Message-ID: <20040204154626.A4702@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	sigtran@ietf.org
References: <A3284A14-5754-11D8-86DB-000A95DC192A@lurchi.franken.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <A3284A14-5754-11D8-86DB-000A95DC192A@lurchi.franken.de>; from Michael.Tuexen@lurchi.franken.de on Wed, Feb 04, 2004 at 09:56:43PM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Michael,

I think you need to read the RFC from the viewpoint of a specification
instead of the viewpoint of an implementation.  When it says "assumed"
it means "assumed [by the authors in the specification of the protocol]"
and not "assumed [by the implementation]".

There are many place in the RFC where this is the case, because of the
editors' preference for words like "assumed".  If we are to correct the lazy
English in the document, it would require an extensive rewrite.

--brian

Michael Tuexen wrote:                                                              (Wed, 04 Feb 2004 21:56:43)
> Dear all,
> 
> the RFC describes that an M3UA endpoint should check the version field
> for ASP Up messages and leaves it unspecified how other messages should
> be handled.
> 
> In real scenarios the first message having an unsupported message is
> most likely an ASP-Up message, but my experience is, that people testing
> implementations always ask how these other messages should be handled.
> 
> Therefore I would like to suggest a clarification in the IG clearly
> stating how these other messages with an unsupported version should
> be handled.
> 
> We can specify that it is checked for all messages or only for ASP-Up
> messages, ignoring the version field for non ASP-Up messages.
> 
> The easiest solution seems to be (for me) to check the field for
> all messages. So you could write
> 
> if (message->version != 1)
>    send(error)
> 
> instead of
> 
> if ((message->class == 3) && (message->type == 1) && 
> (message->(message->version != 1))
>    send(error)
> 
> Therefore I suggest to include the following text in the IG.
> 
> Best regards
> Michael
> 
> 
> <---- SNIP
> 3.28 Version Control
> 
> 3.28.1 Description of the problem
> 
> The RFC describes how ASP Up messages with an unsupported version
> are handled but leaves it unspecified how other messages should be
> handled if the version number is not supported.
> 
> 3.28.2 Text changes to the document
>     ---------
>     Old text: (Section 4.3.4.1.1)
>     ---------
> 
> 4.3.4.1.1 M3UA Version Control
> 
>     If an ASP Up message with an unsupported version is received, the
>     receiving end responds with an Error message, indicating the version
>     the receiving node supports and notifies Layer Management.
> 
>     This is useful when protocol version upgrades are being performed in
>     a network.  A node upgraded to a newer version should support the
>     older versions used on other nodes it is communicating with.  Because
>     ASPs initiate the ASP Up procedure it is assumed that the Error
>     message would normally come from the SGP.
> 
>     ---------
>     New text: (Section 4.3.4.1.1)
>     ---------
> 
> 4.3.4.1.1 M3UA Version Control
> 
>     If a message with an unsupported version is received, the
>     receiving end responds with an Error message, indicating the version
>     the receiving node supports and notifies Layer Management.
> 
>     This is useful when protocol version upgrades are being performed in
>     a network.  A node upgraded to a newer version should support the
>     older versions used on other nodes it is communicating with.  Because
>     ASPs initiate the ASP Up procedure it is likely that the message 
> having
>     an unsupported version is an ASP Up message and therefore that the 
> Error
>     message would normally come from the SGP.
> 
> 
> 3.28.3 Solution description
> 
> The new text clearly describes that the version should be checked for 
> all
> messages.
> <---- SNIP
> 
> 
> _______________________________________________
> 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 Feb  5 04:21: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 EAA08145
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 04:21: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 1Aofh4-0005B8-Cd
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 04:21:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i159L602019903
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 04:21:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aofh0-0005AX-MG; Thu, 05 Feb 2004 04:21:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aofgl-00057I-MH
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 04:20:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08142
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 04:20:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aofgi-00078v-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 04:20:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aoffm-00073U-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 04:19:47 -0500
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aofes-0006y1-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 04:18:50 -0500
Received: from [194.95.73.175] (unknown [194.95.73.175])
	by mail-n.franken.de (Postfix) with ESMTP
	id 5AFB7245FC; Thu,  5 Feb 2004 10:17:46 +0100 (CET)
In-Reply-To: <20040204154626.A4702@openss7.org>
References: <A3284A14-5754-11D8-86DB-000A95DC192A@lurchi.franken.de> <20040204154626.A4702@openss7.org>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <25E95696-57BC-11D8-861F-000A95DC192A@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
Cc: sigtran@ietf.org
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Sigtran] M3UA version control
Date: Thu, 5 Feb 2004 10:17:40 +0100
To: bidulock@openss7.org
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Brian,

I agree with you that there are a lot of places which are not
very precisely (this is the same with other RFCs) but this
question came up multiple times. Others not. That is why I'm
asking to clarify this.

I know about customers and testers who test exactly this and
always ask: what is the correct behaviour. So what is the
problem in making this clear? Think about having different
customers requesting different implementations?

Best regards
Michael

On Feb 4, 2004, at 11:46 PM, Brian F. G. Bidulock wrote:

> Michael,
>
> I think you need to read the RFC from the viewpoint of a specification
> instead of the viewpoint of an implementation.  When it says "assumed"
> it means "assumed [by the authors in the specification of the 
> protocol]"
> and not "assumed [by the implementation]".
>
> There are many place in the RFC where this is the case, because of the
> editors' preference for words like "assumed".  If we are to correct 
> the lazy
> English in the document, it would require an extensive rewrite.
>
> --brian
>
> Michael Tuexen wrote:                                                  
>             (Wed, 04 Feb 2004 21:56:43)
>> Dear all,
>>
>> the RFC describes that an M3UA endpoint should check the version field
>> for ASP Up messages and leaves it unspecified how other messages 
>> should
>> be handled.
>>
>> In real scenarios the first message having an unsupported message is
>> most likely an ASP-Up message, but my experience is, that people 
>> testing
>> implementations always ask how these other messages should be handled.
>>
>> Therefore I would like to suggest a clarification in the IG clearly
>> stating how these other messages with an unsupported version should
>> be handled.
>>
>> We can specify that it is checked for all messages or only for ASP-Up
>> messages, ignoring the version field for non ASP-Up messages.
>>
>> The easiest solution seems to be (for me) to check the field for
>> all messages. So you could write
>>
>> if (message->version != 1)
>>    send(error)
>>
>> instead of
>>
>> if ((message->class == 3) && (message->type == 1) &&
>> (message->(message->version != 1))
>>    send(error)
>>
>> Therefore I suggest to include the following text in the IG.
>>
>> Best regards
>> Michael
>>
>>
>> <---- SNIP
>> 3.28 Version Control
>>
>> 3.28.1 Description of the problem
>>
>> The RFC describes how ASP Up messages with an unsupported version
>> are handled but leaves it unspecified how other messages should be
>> handled if the version number is not supported.
>>
>> 3.28.2 Text changes to the document
>>     ---------
>>     Old text: (Section 4.3.4.1.1)
>>     ---------
>>
>> 4.3.4.1.1 M3UA Version Control
>>
>>     If an ASP Up message with an unsupported version is received, the
>>     receiving end responds with an Error message, indicating the 
>> version
>>     the receiving node supports and notifies Layer Management.
>>
>>     This is useful when protocol version upgrades are being performed 
>> in
>>     a network.  A node upgraded to a newer version should support the
>>     older versions used on other nodes it is communicating with.  
>> Because
>>     ASPs initiate the ASP Up procedure it is assumed that the Error
>>     message would normally come from the SGP.
>>
>>     ---------
>>     New text: (Section 4.3.4.1.1)
>>     ---------
>>
>> 4.3.4.1.1 M3UA Version Control
>>
>>     If a message with an unsupported version is received, the
>>     receiving end responds with an Error message, indicating the 
>> version
>>     the receiving node supports and notifies Layer Management.
>>
>>     This is useful when protocol version upgrades are being performed 
>> in
>>     a network.  A node upgraded to a newer version should support the
>>     older versions used on other nodes it is communicating with.  
>> Because
>>     ASPs initiate the ASP Up procedure it is likely that the message
>> having
>>     an unsupported version is an ASP Up message and therefore that the
>> Error
>>     message would normally come from the SGP.
>>
>>
>> 3.28.3 Solution description
>>
>> The new text clearly describes that the version should be checked for
>> all
>> messages.
>> <---- SNIP
>>
>>
>> _______________________________________________
>> 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 Feb  5 05:32:31 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 FAA10329
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 05:32:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aognk-0000vo-30
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 05:32:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15AW4Fv003580
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 05:32:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aognh-0000vY-6B; Thu, 05 Feb 2004 05:32:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AognW-0000vM-T5
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 05:31:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10306
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 05:31:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AognT-0005rW-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 05:31:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AogmX-0005n9-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 05:30:50 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[cUvujBwaHNjSS3Up5hxFxZ9X99tWsIQH])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aogm2-0005ik-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 05:30:18 -0500
Received: from ns.pigworks.openss7.net (IDENT:1jiFuz32f6QSYpEA/qmY2kDtdq51Ydcb@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i15AUJI03858;
	Thu, 5 Feb 2004 03:30:19 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i15AUIV12936;
	Thu, 5 Feb 2004 03:30:18 -0700
Date: Thu, 5 Feb 2004 03:30:18 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA version control
Message-ID: <20040205033018.A12718@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	sigtran@ietf.org
References: <A3284A14-5754-11D8-86DB-000A95DC192A@lurchi.franken.de> <20040204154626.A4702@openss7.org> <25E95696-57BC-11D8-861F-000A95DC192A@lurchi.franken.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <25E95696-57BC-11D8-861F-000A95DC192A@lurchi.franken.de>; from Michael.Tuexen@lurchi.franken.de on Thu, Feb 05, 2004 at 10:17:40AM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Michael,

I don't think that your proposed text takes us any farther towards
that goal.  You have changed "assumed that" to "likely that the
message having an unsupported version is an ASP Up message and
therefore [likely] that".

This is just description.  The requirement is (unchanged):

> If a message with an unsupported version is received, the
> receiving end responds with an Error message, indicating the version
> the receiving node supports and notifies Layer Management.

This is obviously any message.

As there is no change to the requirement, the new text is superfluous.

Regardless of likelihoods or assumptions, the Error message is
returned to any message received with an unsupported version and Layer
Management is notified.  Suggesting that it is likely that an ASP Up
is the cause, actually distracts from the requirement to return the
error to any message.

A node might actually send message Foo with Version=100 to test a
remote node's support for message Foo (only available in Version=100)
while performing the ASP Up and ASP Active procedures using Version=1.
This requirement provides that message Foo will be retured with an
"usupported version" if version 100 is not supported (and obviously
the message Foo is not supported).

It would be better to strike the line starting with "Because", because
it was superfluous to begin with.  Changing assumptions to likelihoods
does not increase its pertinence.

--brian


Michael Tuexen wrote:                                                              (Thu, 05 Feb 2004 10:17:40)
> Brian,
> 
> I agree with you that there are a lot of places which are not
> very precisely (this is the same with other RFCs) but this
> question came up multiple times. Others not. That is why I'm
> asking to clarify this.
> 
> I know about customers and testers who test exactly this and
> always ask: what is the correct behaviour. So what is the
> problem in making this clear? Think about having different
> customers requesting different implementations?
> 
> Best regards
> Michael
> 
> On Feb 4, 2004, at 11:46 PM, Brian F. G. Bidulock wrote:
> 
> > Michael,
> >
> > I think you need to read the RFC from the viewpoint of a specification
> > instead of the viewpoint of an implementation.  When it says "assumed"
> > it means "assumed [by the authors in the specification of the 
> > protocol]"
> > and not "assumed [by the implementation]".
> >
> > There are many place in the RFC where this is the case, because of the
> > editors' preference for words like "assumed".  If we are to correct 
> > the lazy
> > English in the document, it would require an extensive rewrite.
> >
> > --brian
> >
> > Michael Tuexen wrote:                                                  
> >             (Wed, 04 Feb 2004 21:56:43)
> >> Dear all,
> >>
> >> the RFC describes that an M3UA endpoint should check the version field
> >> for ASP Up messages and leaves it unspecified how other messages 
> >> should
> >> be handled.
> >>
> >> In real scenarios the first message having an unsupported message is
> >> most likely an ASP-Up message, but my experience is, that people 
> >> testing
> >> implementations always ask how these other messages should be handled.
> >>
> >> Therefore I would like to suggest a clarification in the IG clearly
> >> stating how these other messages with an unsupported version should
> >> be handled.
> >>
> >> We can specify that it is checked for all messages or only for ASP-Up
> >> messages, ignoring the version field for non ASP-Up messages.
> >>
> >> The easiest solution seems to be (for me) to check the field for
> >> all messages. So you could write
> >>
> >> if (message->version != 1)
> >>    send(error)
> >>
> >> instead of
> >>
> >> if ((message->class == 3) && (message->type == 1) &&
> >> (message->(message->version != 1))
> >>    send(error)
> >>
> >> Therefore I suggest to include the following text in the IG.
> >>
> >> Best regards
> >> Michael
> >>
> >>
> >> <---- SNIP
> >> 3.28 Version Control
> >>
> >> 3.28.1 Description of the problem
> >>
> >> The RFC describes how ASP Up messages with an unsupported version
> >> are handled but leaves it unspecified how other messages should be
> >> handled if the version number is not supported.
> >>
> >> 3.28.2 Text changes to the document
> >>     ---------
> >>     Old text: (Section 4.3.4.1.1)
> >>     ---------
> >>
> >> 4.3.4.1.1 M3UA Version Control
> >>
> >>     If an ASP Up message with an unsupported version is received, the
> >>     receiving end responds with an Error message, indicating the 
> >> version
> >>     the receiving node supports and notifies Layer Management.
> >>
> >>     This is useful when protocol version upgrades are being performed 
> >> in
> >>     a network.  A node upgraded to a newer version should support the
> >>     older versions used on other nodes it is communicating with.  
> >> Because
> >>     ASPs initiate the ASP Up procedure it is assumed that the Error
> >>     message would normally come from the SGP.
> >>
> >>     ---------
> >>     New text: (Section 4.3.4.1.1)
> >>     ---------
> >>
> >> 4.3.4.1.1 M3UA Version Control
> >>
> >>     If a message with an unsupported version is received, the
> >>     receiving end responds with an Error message, indicating the 
> >> version
> >>     the receiving node supports and notifies Layer Management.
> >>
> >>     This is useful when protocol version upgrades are being performed 
> >> in
> >>     a network.  A node upgraded to a newer version should support the
> >>     older versions used on other nodes it is communicating with.  
> >> Because
> >>     ASPs initiate the ASP Up procedure it is likely that the message
> >> having
> >>     an unsupported version is an ASP Up message and therefore that the
> >> Error
> >>     message would normally come from the SGP.
> >>
> >>
> >> 3.28.3 Solution description
> >>
> >> The new text clearly describes that the version should be checked for
> >> all
> >> messages.
> >> <---- SNIP
> >>
> >>
> >> _______________________________________________
> >> Sigtran mailing list
> >> Sigtran@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/sigtran
> >
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >

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

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



From exim@www1.ietf.org  Thu Feb  5 06:27:28 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 GAA11564
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 06:27:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aohev-0003cl-Tz
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 06:27:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15BR1XI013930
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 06:27:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aohev-0003cS-6P; Thu, 05 Feb 2004 06:27:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aohes-0003c6-Iu
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 06:26: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 GAA11554
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 06:26:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aoheo-0002xb-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 06:26:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aohdr-0002ry-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 06:25:56 -0500
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AohdK-0002mq-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 06:25:22 -0500
Received: from [194.95.73.190] (unknown [194.95.73.190])
	by mail-n.franken.de (Postfix) with ESMTP
	id 810CA24705; Thu,  5 Feb 2004 12:24:13 +0100 (CET)
In-Reply-To: <20040205033018.A12718@openss7.org>
References: <A3284A14-5754-11D8-86DB-000A95DC192A@lurchi.franken.de> <20040204154626.A4702@openss7.org> <25E95696-57BC-11D8-861F-000A95DC192A@lurchi.franken.de> <20040205033018.A12718@openss7.org>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <D024E1DC-57CD-11D8-861F-000A95DC192A@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
Cc: sigtran@ietf.org
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Sigtran] M3UA version control
Date: Thu, 5 Feb 2004 12:24:07 +0100
To: bidulock@openss7.org
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Brian,

part of my suggestion is to replace:

     If an ASP Up message with an unsupported version is received, the

with

     If a message with an unsupported version is received, the

At least for me, this does change the requested behaviour.

Best regards
Michael

On Feb 5, 2004, at 11:30 AM, Brian F. G. Bidulock wrote:

> Michael,
>
> I don't think that your proposed text takes us any farther towards
> that goal.  You have changed "assumed that" to "likely that the
> message having an unsupported version is an ASP Up message and
> therefore [likely] that".
>
> This is just description.  The requirement is (unchanged):
>
>> If a message with an unsupported version is received, the
>> receiving end responds with an Error message, indicating the version
>> the receiving node supports and notifies Layer Management.
>
> This is obviously any message.
>
> As there is no change to the requirement, the new text is superfluous.
>
> Regardless of likelihoods or assumptions, the Error message is
> returned to any message received with an unsupported version and Layer
> Management is notified.  Suggesting that it is likely that an ASP Up
> is the cause, actually distracts from the requirement to return the
> error to any message.
>
> A node might actually send message Foo with Version=100 to test a
> remote node's support for message Foo (only available in Version=100)
> while performing the ASP Up and ASP Active procedures using Version=1.
> This requirement provides that message Foo will be retured with an
> "usupported version" if version 100 is not supported (and obviously
> the message Foo is not supported).
>
> It would be better to strike the line starting with "Because", because
> it was superfluous to begin with.  Changing assumptions to likelihoods
> does not increase its pertinence.
>
> --brian
>
>
> Michael Tuexen wrote:                                                  
>             (Thu, 05 Feb 2004 10:17:40)
>> Brian,
>>
>> I agree with you that there are a lot of places which are not
>> very precisely (this is the same with other RFCs) but this
>> question came up multiple times. Others not. That is why I'm
>> asking to clarify this.
>>
>> I know about customers and testers who test exactly this and
>> always ask: what is the correct behaviour. So what is the
>> problem in making this clear? Think about having different
>> customers requesting different implementations?
>>
>> Best regards
>> Michael
>>
>> On Feb 4, 2004, at 11:46 PM, Brian F. G. Bidulock wrote:
>>
>>> Michael,
>>>
>>> I think you need to read the RFC from the viewpoint of a 
>>> specification
>>> instead of the viewpoint of an implementation.  When it says 
>>> "assumed"
>>> it means "assumed [by the authors in the specification of the
>>> protocol]"
>>> and not "assumed [by the implementation]".
>>>
>>> There are many place in the RFC where this is the case, because of 
>>> the
>>> editors' preference for words like "assumed".  If we are to correct
>>> the lazy
>>> English in the document, it would require an extensive rewrite.
>>>
>>> --brian
>>>
>>> Michael Tuexen wrote:
>>>             (Wed, 04 Feb 2004 21:56:43)
>>>> Dear all,
>>>>
>>>> the RFC describes that an M3UA endpoint should check the version 
>>>> field
>>>> for ASP Up messages and leaves it unspecified how other messages
>>>> should
>>>> be handled.
>>>>
>>>> In real scenarios the first message having an unsupported message is
>>>> most likely an ASP-Up message, but my experience is, that people
>>>> testing
>>>> implementations always ask how these other messages should be 
>>>> handled.
>>>>
>>>> Therefore I would like to suggest a clarification in the IG clearly
>>>> stating how these other messages with an unsupported version should
>>>> be handled.
>>>>
>>>> We can specify that it is checked for all messages or only for 
>>>> ASP-Up
>>>> messages, ignoring the version field for non ASP-Up messages.
>>>>
>>>> The easiest solution seems to be (for me) to check the field for
>>>> all messages. So you could write
>>>>
>>>> if (message->version != 1)
>>>>    send(error)
>>>>
>>>> instead of
>>>>
>>>> if ((message->class == 3) && (message->type == 1) &&
>>>> (message->(message->version != 1))
>>>>    send(error)
>>>>
>>>> Therefore I suggest to include the following text in the IG.
>>>>
>>>> Best regards
>>>> Michael
>>>>
>>>>
>>>> <---- SNIP
>>>> 3.28 Version Control
>>>>
>>>> 3.28.1 Description of the problem
>>>>
>>>> The RFC describes how ASP Up messages with an unsupported version
>>>> are handled but leaves it unspecified how other messages should be
>>>> handled if the version number is not supported.
>>>>
>>>> 3.28.2 Text changes to the document
>>>>     ---------
>>>>     Old text: (Section 4.3.4.1.1)
>>>>     ---------
>>>>
>>>> 4.3.4.1.1 M3UA Version Control
>>>>
>>>>     If an ASP Up message with an unsupported version is received, 
>>>> the
>>>>     receiving end responds with an Error message, indicating the
>>>> version
>>>>     the receiving node supports and notifies Layer Management.
>>>>
>>>>     This is useful when protocol version upgrades are being 
>>>> performed
>>>> in
>>>>     a network.  A node upgraded to a newer version should support 
>>>> the
>>>>     older versions used on other nodes it is communicating with.
>>>> Because
>>>>     ASPs initiate the ASP Up procedure it is assumed that the Error
>>>>     message would normally come from the SGP.
>>>>
>>>>     ---------
>>>>     New text: (Section 4.3.4.1.1)
>>>>     ---------
>>>>
>>>> 4.3.4.1.1 M3UA Version Control
>>>>
>>>>     If a message with an unsupported version is received, the
>>>>     receiving end responds with an Error message, indicating the
>>>> version
>>>>     the receiving node supports and notifies Layer Management.
>>>>
>>>>     This is useful when protocol version upgrades are being 
>>>> performed
>>>> in
>>>>     a network.  A node upgraded to a newer version should support 
>>>> the
>>>>     older versions used on other nodes it is communicating with.
>>>> Because
>>>>     ASPs initiate the ASP Up procedure it is likely that the message
>>>> having
>>>>     an unsupported version is an ASP Up message and therefore that 
>>>> the
>>>> Error
>>>>     message would normally come from the SGP.
>>>>
>>>>
>>>> 3.28.3 Solution description
>>>>
>>>> The new text clearly describes that the version should be checked 
>>>> for
>>>> all
>>>> messages.
>>>> <---- SNIP
>>>>
>>>>
>>>> _______________________________________________
>>>> Sigtran mailing list
>>>> Sigtran@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/sigtran
>>>
>>> -- 
>>> Brian F. G. Bidulock
>>> bidulock@openss7.org
>>> http://www.openss7.org/
>>>
>
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>


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



From exim@www1.ietf.org  Thu Feb  5 06:36: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 GAA11930
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 06:36:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aohnf-0004BO-Mt
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 06:36:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15Ba3Sw016061
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 06:36:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aohnd-0004AL-Or; Thu, 05 Feb 2004 06:36:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AohnV-00049j-6H
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 06:35:53 -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 GAA11885
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 06:35:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AohnR-0003q1-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 06:35:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AohmS-0003lB-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 06:34:49 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[Zu8ku6gApDqUg3rSGnKUr03VrK8TxBYi])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AohlY-0003fQ-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 06:33:52 -0500
Received: from ns.pigworks.openss7.net (IDENT:b9FihTSYEMZy/GuFqWpYQhZjzDQye5jl@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i15BXqI05231;
	Thu, 5 Feb 2004 04:33:53 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i15BXqc13978;
	Thu, 5 Feb 2004 04:33:52 -0700
Date: Thu, 5 Feb 2004 04:33:52 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA version control
Message-ID: <20040205043352.A13951@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	sigtran@ietf.org
References: <A3284A14-5754-11D8-86DB-000A95DC192A@lurchi.franken.de> <20040204154626.A4702@openss7.org> <25E95696-57BC-11D8-861F-000A95DC192A@lurchi.franken.de> <20040205033018.A12718@openss7.org> <D024E1DC-57CD-11D8-861F-000A95DC192A@lurchi.franken.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <D024E1DC-57CD-11D8-861F-000A95DC192A@lurchi.franken.de>; from Michael.Tuexen@lurchi.franken.de on Thu, Feb 05, 2004 at 12:24:07PM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Michael,

I missed that.  And, therefore, disagree with the change.  An error
must be returned for any message with an unsupported version, not
just ASP Up, as the RFC already states.  The example case was in
my last mail.

--brian

Michael Tuexen wrote:                                                              (Thu, 05 Feb 2004 12:24:07)
> Brian,
> 
> part of my suggestion is to replace:
> 
>      If an ASP Up message with an unsupported version is received, the
> 
> with
> 
>      If a message with an unsupported version is received, the
> 
> At least for me, this does change the requested behaviour.
> 
> Best regards
> Michael
> 
> On Feb 5, 2004, at 11:30 AM, Brian F. G. Bidulock wrote:
> 
> > Michael,
> >
> > I don't think that your proposed text takes us any farther towards
> > that goal.  You have changed "assumed that" to "likely that the
> > message having an unsupported version is an ASP Up message and
> > therefore [likely] that".
> >
> > This is just description.  The requirement is (unchanged):
> >
> >> If a message with an unsupported version is received, the
> >> receiving end responds with an Error message, indicating the version
> >> the receiving node supports and notifies Layer Management.
> >
> > This is obviously any message.
> >
> > As there is no change to the requirement, the new text is superfluous.
> >
> > Regardless of likelihoods or assumptions, the Error message is
> > returned to any message received with an unsupported version and Layer
> > Management is notified.  Suggesting that it is likely that an ASP Up
> > is the cause, actually distracts from the requirement to return the
> > error to any message.
> >
> > A node might actually send message Foo with Version=100 to test a
> > remote node's support for message Foo (only available in Version=100)
> > while performing the ASP Up and ASP Active procedures using Version=1.
> > This requirement provides that message Foo will be retured with an
> > "usupported version" if version 100 is not supported (and obviously
> > the message Foo is not supported).
> >
> > It would be better to strike the line starting with "Because", because
> > it was superfluous to begin with.  Changing assumptions to likelihoods
> > does not increase its pertinence.
> >
> > --brian
> >
> >
> > Michael Tuexen wrote:                                                  
> >             (Thu, 05 Feb 2004 10:17:40)
> >> Brian,
> >>
> >> I agree with you that there are a lot of places which are not
> >> very precisely (this is the same with other RFCs) but this
> >> question came up multiple times. Others not. That is why I'm
> >> asking to clarify this.
> >>
> >> I know about customers and testers who test exactly this and
> >> always ask: what is the correct behaviour. So what is the
> >> problem in making this clear? Think about having different
> >> customers requesting different implementations?
> >>
> >> Best regards
> >> Michael
> >>
> >> On Feb 4, 2004, at 11:46 PM, Brian F. G. Bidulock wrote:
> >>
> >>> Michael,
> >>>
> >>> I think you need to read the RFC from the viewpoint of a 
> >>> specification
> >>> instead of the viewpoint of an implementation.  When it says 
> >>> "assumed"
> >>> it means "assumed [by the authors in the specification of the
> >>> protocol]"
> >>> and not "assumed [by the implementation]".
> >>>
> >>> There are many place in the RFC where this is the case, because of 
> >>> the
> >>> editors' preference for words like "assumed".  If we are to correct
> >>> the lazy
> >>> English in the document, it would require an extensive rewrite.
> >>>
> >>> --brian
> >>>
> >>> Michael Tuexen wrote:
> >>>             (Wed, 04 Feb 2004 21:56:43)
> >>>> Dear all,
> >>>>
> >>>> the RFC describes that an M3UA endpoint should check the version 
> >>>> field
> >>>> for ASP Up messages and leaves it unspecified how other messages
> >>>> should
> >>>> be handled.
> >>>>
> >>>> In real scenarios the first message having an unsupported message is
> >>>> most likely an ASP-Up message, but my experience is, that people
> >>>> testing
> >>>> implementations always ask how these other messages should be 
> >>>> handled.
> >>>>
> >>>> Therefore I would like to suggest a clarification in the IG clearly
> >>>> stating how these other messages with an unsupported version should
> >>>> be handled.
> >>>>
> >>>> We can specify that it is checked for all messages or only for 
> >>>> ASP-Up
> >>>> messages, ignoring the version field for non ASP-Up messages.
> >>>>
> >>>> The easiest solution seems to be (for me) to check the field for
> >>>> all messages. So you could write
> >>>>
> >>>> if (message->version != 1)
> >>>>    send(error)
> >>>>
> >>>> instead of
> >>>>
> >>>> if ((message->class == 3) && (message->type == 1) &&
> >>>> (message->(message->version != 1))
> >>>>    send(error)
> >>>>
> >>>> Therefore I suggest to include the following text in the IG.
> >>>>
> >>>> Best regards
> >>>> Michael
> >>>>
> >>>>
> >>>> <---- SNIP
> >>>> 3.28 Version Control
> >>>>
> >>>> 3.28.1 Description of the problem
> >>>>
> >>>> The RFC describes how ASP Up messages with an unsupported version
> >>>> are handled but leaves it unspecified how other messages should be
> >>>> handled if the version number is not supported.
> >>>>
> >>>> 3.28.2 Text changes to the document
> >>>>     ---------
> >>>>     Old text: (Section 4.3.4.1.1)
> >>>>     ---------
> >>>>
> >>>> 4.3.4.1.1 M3UA Version Control
> >>>>
> >>>>     If an ASP Up message with an unsupported version is received, 
> >>>> the
> >>>>     receiving end responds with an Error message, indicating the
> >>>> version
> >>>>     the receiving node supports and notifies Layer Management.
> >>>>
> >>>>     This is useful when protocol version upgrades are being 
> >>>> performed
> >>>> in
> >>>>     a network.  A node upgraded to a newer version should support 
> >>>> the
> >>>>     older versions used on other nodes it is communicating with.
> >>>> Because
> >>>>     ASPs initiate the ASP Up procedure it is assumed that the Error
> >>>>     message would normally come from the SGP.
> >>>>
> >>>>     ---------
> >>>>     New text: (Section 4.3.4.1.1)
> >>>>     ---------
> >>>>
> >>>> 4.3.4.1.1 M3UA Version Control
> >>>>
> >>>>     If a message with an unsupported version is received, the
> >>>>     receiving end responds with an Error message, indicating the
> >>>> version
> >>>>     the receiving node supports and notifies Layer Management.
> >>>>
> >>>>     This is useful when protocol version upgrades are being 
> >>>> performed
> >>>> in
> >>>>     a network.  A node upgraded to a newer version should support 
> >>>> the
> >>>>     older versions used on other nodes it is communicating with.
> >>>> Because
> >>>>     ASPs initiate the ASP Up procedure it is likely that the message
> >>>> having
> >>>>     an unsupported version is an ASP Up message and therefore that 
> >>>> the
> >>>> Error
> >>>>     message would normally come from the SGP.
> >>>>
> >>>>
> >>>> 3.28.3 Solution description
> >>>>
> >>>> The new text clearly describes that the version should be checked 
> >>>> for
> >>>> all
> >>>> messages.
> >>>> <---- SNIP
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Sigtran mailing list
> >>>> Sigtran@ietf.org
> >>>> https://www1.ietf.org/mailman/listinfo/sigtran
> >>>
> >>> -- 
> >>> Brian F. G. Bidulock
> >>> bidulock@openss7.org
> >>> http://www.openss7.org/
> >>>
> >
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >

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

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



From exim@www1.ietf.org  Thu Feb  5 07:05: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 HAA12703
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 07:05:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoiFk-0005dS-77
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 07:05:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15C548X021662
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 07:05:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoiFi-0005ch-0Z; Thu, 05 Feb 2004 07:05:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoiEi-0005Yk-Vt
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 07:04:01 -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 HAA12677
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 07:03:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoiEe-0006dt-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 07:03:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AoiDi-0006YP-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 07:02:59 -0500
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoiDE-0006Sq-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 07:02:28 -0500
Received: from [194.95.73.190] (unknown [194.95.73.190])
	by mail-n.franken.de (Postfix) with ESMTP
	id 6DE2F2462C; Thu,  5 Feb 2004 13:01:23 +0100 (CET)
In-Reply-To: <20040205043352.A13951@openss7.org>
References: <A3284A14-5754-11D8-86DB-000A95DC192A@lurchi.franken.de> <20040204154626.A4702@openss7.org> <25E95696-57BC-11D8-861F-000A95DC192A@lurchi.franken.de> <20040205033018.A12718@openss7.org> <D024E1DC-57CD-11D8-861F-000A95DC192A@lurchi.franken.de> <20040205043352.A13951@openss7.org>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <01BFFB31-57D3-11D8-861F-000A95DC192A@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
Cc: sigtran@ietf.org
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Sigtran] M3UA version control
Date: Thu, 5 Feb 2004 13:01:18 +0100
To: bidulock@openss7.org
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Brian,

you disagree with the change? This means you want to have an
error ONLY returned for ASP-Up messages as the RFC states?

I'm suggesting a change that it is returned for all messages.

Best regards
Michael


On Feb 5, 2004, at 12:33 PM, Brian F. G. Bidulock wrote:

> Michael,
>
> I missed that.  And, therefore, disagree with the change.  An error
> must be returned for any message with an unsupported version, not
> just ASP Up, as the RFC already states.  The example case was in
> my last mail.
>
> --brian
>
> Michael Tuexen wrote:                                                  
>             (Thu, 05 Feb 2004 12:24:07)
>> Brian,
>>
>> part of my suggestion is to replace:
>>
>>      If an ASP Up message with an unsupported version is received, the
>>
>> with
>>
>>      If a message with an unsupported version is received, the
>>
>> At least for me, this does change the requested behaviour.
>>
>> Best regards
>> Michael
>>
>> On Feb 5, 2004, at 11:30 AM, Brian F. G. Bidulock wrote:
>>
>>> Michael,
>>>
>>> I don't think that your proposed text takes us any farther towards
>>> that goal.  You have changed "assumed that" to "likely that the
>>> message having an unsupported version is an ASP Up message and
>>> therefore [likely] that".
>>>
>>> This is just description.  The requirement is (unchanged):
>>>
>>>> If a message with an unsupported version is received, the
>>>> receiving end responds with an Error message, indicating the version
>>>> the receiving node supports and notifies Layer Management.
>>>
>>> This is obviously any message.
>>>
>>> As there is no change to the requirement, the new text is 
>>> superfluous.
>>>
>>> Regardless of likelihoods or assumptions, the Error message is
>>> returned to any message received with an unsupported version and 
>>> Layer
>>> Management is notified.  Suggesting that it is likely that an ASP Up
>>> is the cause, actually distracts from the requirement to return the
>>> error to any message.
>>>
>>> A node might actually send message Foo with Version=100 to test a
>>> remote node's support for message Foo (only available in Version=100)
>>> while performing the ASP Up and ASP Active procedures using 
>>> Version=1.
>>> This requirement provides that message Foo will be retured with an
>>> "usupported version" if version 100 is not supported (and obviously
>>> the message Foo is not supported).
>>>
>>> It would be better to strike the line starting with "Because", 
>>> because
>>> it was superfluous to begin with.  Changing assumptions to 
>>> likelihoods
>>> does not increase its pertinence.
>>>
>>> --brian
>>>
>>>
>>> Michael Tuexen wrote:
>>>             (Thu, 05 Feb 2004 10:17:40)
>>>> Brian,
>>>>
>>>> I agree with you that there are a lot of places which are not
>>>> very precisely (this is the same with other RFCs) but this
>>>> question came up multiple times. Others not. That is why I'm
>>>> asking to clarify this.
>>>>
>>>> I know about customers and testers who test exactly this and
>>>> always ask: what is the correct behaviour. So what is the
>>>> problem in making this clear? Think about having different
>>>> customers requesting different implementations?
>>>>
>>>> Best regards
>>>> Michael
>>>>
>>>> On Feb 4, 2004, at 11:46 PM, Brian F. G. Bidulock wrote:
>>>>
>>>>> Michael,
>>>>>
>>>>> I think you need to read the RFC from the viewpoint of a
>>>>> specification
>>>>> instead of the viewpoint of an implementation.  When it says
>>>>> "assumed"
>>>>> it means "assumed [by the authors in the specification of the
>>>>> protocol]"
>>>>> and not "assumed [by the implementation]".
>>>>>
>>>>> There are many place in the RFC where this is the case, because of
>>>>> the
>>>>> editors' preference for words like "assumed".  If we are to correct
>>>>> the lazy
>>>>> English in the document, it would require an extensive rewrite.
>>>>>
>>>>> --brian
>>>>>
>>>>> Michael Tuexen wrote:
>>>>>             (Wed, 04 Feb 2004 21:56:43)
>>>>>> Dear all,
>>>>>>
>>>>>> the RFC describes that an M3UA endpoint should check the version
>>>>>> field
>>>>>> for ASP Up messages and leaves it unspecified how other messages
>>>>>> should
>>>>>> be handled.
>>>>>>
>>>>>> In real scenarios the first message having an unsupported message 
>>>>>> is
>>>>>> most likely an ASP-Up message, but my experience is, that people
>>>>>> testing
>>>>>> implementations always ask how these other messages should be
>>>>>> handled.
>>>>>>
>>>>>> Therefore I would like to suggest a clarification in the IG 
>>>>>> clearly
>>>>>> stating how these other messages with an unsupported version 
>>>>>> should
>>>>>> be handled.
>>>>>>
>>>>>> We can specify that it is checked for all messages or only for
>>>>>> ASP-Up
>>>>>> messages, ignoring the version field for non ASP-Up messages.
>>>>>>
>>>>>> The easiest solution seems to be (for me) to check the field for
>>>>>> all messages. So you could write
>>>>>>
>>>>>> if (message->version != 1)
>>>>>>    send(error)
>>>>>>
>>>>>> instead of
>>>>>>
>>>>>> if ((message->class == 3) && (message->type == 1) &&
>>>>>> (message->(message->version != 1))
>>>>>>    send(error)
>>>>>>
>>>>>> Therefore I suggest to include the following text in the IG.
>>>>>>
>>>>>> Best regards
>>>>>> Michael
>>>>>>
>>>>>>
>>>>>> <---- SNIP
>>>>>> 3.28 Version Control
>>>>>>
>>>>>> 3.28.1 Description of the problem
>>>>>>
>>>>>> The RFC describes how ASP Up messages with an unsupported version
>>>>>> are handled but leaves it unspecified how other messages should be
>>>>>> handled if the version number is not supported.
>>>>>>
>>>>>> 3.28.2 Text changes to the document
>>>>>>     ---------
>>>>>>     Old text: (Section 4.3.4.1.1)
>>>>>>     ---------
>>>>>>
>>>>>> 4.3.4.1.1 M3UA Version Control
>>>>>>
>>>>>>     If an ASP Up message with an unsupported version is received,
>>>>>> the
>>>>>>     receiving end responds with an Error message, indicating the
>>>>>> version
>>>>>>     the receiving node supports and notifies Layer Management.
>>>>>>
>>>>>>     This is useful when protocol version upgrades are being
>>>>>> performed
>>>>>> in
>>>>>>     a network.  A node upgraded to a newer version should support
>>>>>> the
>>>>>>     older versions used on other nodes it is communicating with.
>>>>>> Because
>>>>>>     ASPs initiate the ASP Up procedure it is assumed that the 
>>>>>> Error
>>>>>>     message would normally come from the SGP.
>>>>>>
>>>>>>     ---------
>>>>>>     New text: (Section 4.3.4.1.1)
>>>>>>     ---------
>>>>>>
>>>>>> 4.3.4.1.1 M3UA Version Control
>>>>>>
>>>>>>     If a message with an unsupported version is received, the
>>>>>>     receiving end responds with an Error message, indicating the
>>>>>> version
>>>>>>     the receiving node supports and notifies Layer Management.
>>>>>>
>>>>>>     This is useful when protocol version upgrades are being
>>>>>> performed
>>>>>> in
>>>>>>     a network.  A node upgraded to a newer version should support
>>>>>> the
>>>>>>     older versions used on other nodes it is communicating with.
>>>>>> Because
>>>>>>     ASPs initiate the ASP Up procedure it is likely that the 
>>>>>> message
>>>>>> having
>>>>>>     an unsupported version is an ASP Up message and therefore that
>>>>>> the
>>>>>> Error
>>>>>>     message would normally come from the SGP.
>>>>>>
>>>>>>
>>>>>> 3.28.3 Solution description
>>>>>>
>>>>>> The new text clearly describes that the version should be checked
>>>>>> for
>>>>>> all
>>>>>> messages.
>>>>>> <---- SNIP
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Sigtran mailing list
>>>>>> Sigtran@ietf.org
>>>>>> https://www1.ietf.org/mailman/listinfo/sigtran
>>>>>
>>>>> -- 
>>>>> Brian F. G. Bidulock
>>>>> bidulock@openss7.org
>>>>> http://www.openss7.org/
>>>>>
>>>
>>> -- 
>>> Brian F. G. Bidulock
>>> bidulock@openss7.org
>>> http://www.openss7.org/
>>>
>
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>


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



From exim@www1.ietf.org  Thu Feb  5 07:17:31 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 HAA13005
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 07:17:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoiRJ-0006MH-Ix
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 07:17:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15CH1RZ024420
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 07:17:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoiRJ-0006Lg-7W; Thu, 05 Feb 2004 07:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoiQL-0006Kp-Km
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 07:16:01 -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 HAA12978
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 07:16:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoiQL-00000A-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 07:16:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AoiPM-0007io-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 07:15:01 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[HD5GxmZKHXTTw2UN1bUJaJ4j+2xhRye0])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoiOR-0007di-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 07:14:03 -0500
Received: from ns.pigworks.openss7.net (IDENT:351XeCderkulrd/x4XLRB19hlMiFXZfw@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i15CE2I06110;
	Thu, 5 Feb 2004 05:14:02 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i15CE1m14480;
	Thu, 5 Feb 2004 05:14:01 -0700
Date: Thu, 5 Feb 2004 05:14:01 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA version control
Message-ID: <20040205051401.A14432@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	sigtran@ietf.org
References: <A3284A14-5754-11D8-86DB-000A95DC192A@lurchi.franken.de> <20040204154626.A4702@openss7.org> <25E95696-57BC-11D8-861F-000A95DC192A@lurchi.franken.de> <20040205033018.A12718@openss7.org> <D024E1DC-57CD-11D8-861F-000A95DC192A@lurchi.franken.de> <20040205043352.A13951@openss7.org> <01BFFB31-57D3-11D8-861F-000A95DC192A@lurchi.franken.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <01BFFB31-57D3-11D8-861F-000A95DC192A@lurchi.franken.de>; from Michael.Tuexen@lurchi.franken.de on Thu, Feb 05, 2004 at 01:01:18PM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Michael,

Pardon me.  I'm really twisted around this morning.

Sorry.  Yes, I agree wholeheartedly.

Anything else would reduce the message version to the
effect of a parameter of the ASP Up message and would
not necessitate including it in each message header in
the first place.

I second your correction.

--brian

Michael Tuexen wrote:                                                              (Thu, 05 Feb 2004 13:01:18)
> Brian,
> 
> you disagree with the change? This means you want to have an
> error ONLY returned for ASP-Up messages as the RFC states?
> 
> I'm suggesting a change that it is returned for all messages.
> 
> Best regards
> Michael
> 
> 
> On Feb 5, 2004, at 12:33 PM, Brian F. G. Bidulock wrote:
> 
> > Michael,
> >
> > I missed that.  And, therefore, disagree with the change.  An error
> > must be returned for any message with an unsupported version, not
> > just ASP Up, as the RFC already states.  The example case was in
> > my last mail.
> >
> > --brian
> >
> > Michael Tuexen wrote:                                                  
> >             (Thu, 05 Feb 2004 12:24:07)
> >> Brian,
> >>
> >> part of my suggestion is to replace:
> >>
> >>      If an ASP Up message with an unsupported version is received, the
> >>
> >> with
> >>
> >>      If a message with an unsupported version is received, the
> >>
> >> At least for me, this does change the requested behaviour.
> >>
> >> Best regards
> >> Michael
> >>
> >> On Feb 5, 2004, at 11:30 AM, Brian F. G. Bidulock wrote:
> >>
> >>> Michael,
> >>>
> >>> I don't think that your proposed text takes us any farther towards
> >>> that goal.  You have changed "assumed that" to "likely that the
> >>> message having an unsupported version is an ASP Up message and
> >>> therefore [likely] that".
> >>>
> >>> This is just description.  The requirement is (unchanged):
> >>>
> >>>> If a message with an unsupported version is received, the
> >>>> receiving end responds with an Error message, indicating the version
> >>>> the receiving node supports and notifies Layer Management.
> >>>
> >>> This is obviously any message.
> >>>
> >>> As there is no change to the requirement, the new text is 
> >>> superfluous.
> >>>
> >>> Regardless of likelihoods or assumptions, the Error message is
> >>> returned to any message received with an unsupported version and 
> >>> Layer
> >>> Management is notified.  Suggesting that it is likely that an ASP Up
> >>> is the cause, actually distracts from the requirement to return the
> >>> error to any message.
> >>>
> >>> A node might actually send message Foo with Version=100 to test a
> >>> remote node's support for message Foo (only available in Version=100)
> >>> while performing the ASP Up and ASP Active procedures using 
> >>> Version=1.
> >>> This requirement provides that message Foo will be retured with an
> >>> "usupported version" if version 100 is not supported (and obviously
> >>> the message Foo is not supported).
> >>>
> >>> It would be better to strike the line starting with "Because", 
> >>> because
> >>> it was superfluous to begin with.  Changing assumptions to 
> >>> likelihoods
> >>> does not increase its pertinence.
> >>>
> >>> --brian
> >>>
> >>>
> >>> Michael Tuexen wrote:
> >>>             (Thu, 05 Feb 2004 10:17:40)
> >>>> Brian,
> >>>>
> >>>> I agree with you that there are a lot of places which are not
> >>>> very precisely (this is the same with other RFCs) but this
> >>>> question came up multiple times. Others not. That is why I'm
> >>>> asking to clarify this.
> >>>>
> >>>> I know about customers and testers who test exactly this and
> >>>> always ask: what is the correct behaviour. So what is the
> >>>> problem in making this clear? Think about having different
> >>>> customers requesting different implementations?
> >>>>
> >>>> Best regards
> >>>> Michael
> >>>>
> >>>> On Feb 4, 2004, at 11:46 PM, Brian F. G. Bidulock wrote:
> >>>>
> >>>>> Michael,
> >>>>>
> >>>>> I think you need to read the RFC from the viewpoint of a
> >>>>> specification
> >>>>> instead of the viewpoint of an implementation.  When it says
> >>>>> "assumed"
> >>>>> it means "assumed [by the authors in the specification of the
> >>>>> protocol]"
> >>>>> and not "assumed [by the implementation]".
> >>>>>
> >>>>> There are many place in the RFC where this is the case, because of
> >>>>> the
> >>>>> editors' preference for words like "assumed".  If we are to correct
> >>>>> the lazy
> >>>>> English in the document, it would require an extensive rewrite.
> >>>>>
> >>>>> --brian
> >>>>>
> >>>>> Michael Tuexen wrote:
> >>>>>             (Wed, 04 Feb 2004 21:56:43)
> >>>>>> Dear all,
> >>>>>>
> >>>>>> the RFC describes that an M3UA endpoint should check the version
> >>>>>> field
> >>>>>> for ASP Up messages and leaves it unspecified how other messages
> >>>>>> should
> >>>>>> be handled.
> >>>>>>
> >>>>>> In real scenarios the first message having an unsupported message 
> >>>>>> is
> >>>>>> most likely an ASP-Up message, but my experience is, that people
> >>>>>> testing
> >>>>>> implementations always ask how these other messages should be
> >>>>>> handled.
> >>>>>>
> >>>>>> Therefore I would like to suggest a clarification in the IG 
> >>>>>> clearly
> >>>>>> stating how these other messages with an unsupported version 
> >>>>>> should
> >>>>>> be handled.
> >>>>>>
> >>>>>> We can specify that it is checked for all messages or only for
> >>>>>> ASP-Up
> >>>>>> messages, ignoring the version field for non ASP-Up messages.
> >>>>>>
> >>>>>> The easiest solution seems to be (for me) to check the field for
> >>>>>> all messages. So you could write
> >>>>>>
> >>>>>> if (message->version != 1)
> >>>>>>    send(error)
> >>>>>>
> >>>>>> instead of
> >>>>>>
> >>>>>> if ((message->class == 3) && (message->type == 1) &&
> >>>>>> (message->(message->version != 1))
> >>>>>>    send(error)
> >>>>>>
> >>>>>> Therefore I suggest to include the following text in the IG.
> >>>>>>
> >>>>>> Best regards
> >>>>>> Michael
> >>>>>>
> >>>>>>
> >>>>>> <---- SNIP
> >>>>>> 3.28 Version Control
> >>>>>>
> >>>>>> 3.28.1 Description of the problem
> >>>>>>
> >>>>>> The RFC describes how ASP Up messages with an unsupported version
> >>>>>> are handled but leaves it unspecified how other messages should be
> >>>>>> handled if the version number is not supported.
> >>>>>>
> >>>>>> 3.28.2 Text changes to the document
> >>>>>>     ---------
> >>>>>>     Old text: (Section 4.3.4.1.1)
> >>>>>>     ---------
> >>>>>>
> >>>>>> 4.3.4.1.1 M3UA Version Control
> >>>>>>
> >>>>>>     If an ASP Up message with an unsupported version is received,
> >>>>>> the
> >>>>>>     receiving end responds with an Error message, indicating the
> >>>>>> version
> >>>>>>     the receiving node supports and notifies Layer Management.
> >>>>>>
> >>>>>>     This is useful when protocol version upgrades are being
> >>>>>> performed
> >>>>>> in
> >>>>>>     a network.  A node upgraded to a newer version should support
> >>>>>> the
> >>>>>>     older versions used on other nodes it is communicating with.
> >>>>>> Because
> >>>>>>     ASPs initiate the ASP Up procedure it is assumed that the 
> >>>>>> Error
> >>>>>>     message would normally come from the SGP.
> >>>>>>
> >>>>>>     ---------
> >>>>>>     New text: (Section 4.3.4.1.1)
> >>>>>>     ---------
> >>>>>>
> >>>>>> 4.3.4.1.1 M3UA Version Control
> >>>>>>
> >>>>>>     If a message with an unsupported version is received, the
> >>>>>>     receiving end responds with an Error message, indicating the
> >>>>>> version
> >>>>>>     the receiving node supports and notifies Layer Management.
> >>>>>>
> >>>>>>     This is useful when protocol version upgrades are being
> >>>>>> performed
> >>>>>> in
> >>>>>>     a network.  A node upgraded to a newer version should support
> >>>>>> the
> >>>>>>     older versions used on other nodes it is communicating with.
> >>>>>> Because
> >>>>>>     ASPs initiate the ASP Up procedure it is likely that the 
> >>>>>> message
> >>>>>> having
> >>>>>>     an unsupported version is an ASP Up message and therefore that
> >>>>>> the
> >>>>>> Error
> >>>>>>     message would normally come from the SGP.
> >>>>>>
> >>>>>>
> >>>>>> 3.28.3 Solution description
> >>>>>>
> >>>>>> The new text clearly describes that the version should be checked
> >>>>>> for
> >>>>>> all
> >>>>>> messages.
> >>>>>> <---- SNIP
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> Sigtran mailing list
> >>>>>> Sigtran@ietf.org
> >>>>>> https://www1.ietf.org/mailman/listinfo/sigtran
> >>>>>
> >>>>> -- 
> >>>>> Brian F. G. Bidulock
> >>>>> bidulock@openss7.org
> >>>>> http://www.openss7.org/
> >>>>>
> >>>
> >>> -- 
> >>> Brian F. G. Bidulock
> >>> bidulock@openss7.org
> >>> http://www.openss7.org/
> >>>
> >
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >

-- 
Brian 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 Feb  5 07:19: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 HAA13068
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 07:19:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoiTE-0006Vx-M6
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 07:19:00 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15CJ0iq025010
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 07:19:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoiTE-0006VI-C4; Thu, 05 Feb 2004 07:19:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoiT8-0006Uy-4p
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 07:18:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13057
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 07:18:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoiT7-0000Gc-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 07:18:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AoiSB-0000Bb-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 07:17:57 -0500
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoiRM-00001O-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 07:17:04 -0500
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i15CGXTN012958;
	Thu, 5 Feb 2004 06:16:33 -0600 (CST)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id i15CFk1C022449;
	Thu, 5 Feb 2004 06:15:46 -0600 (CST)
Date: Thu, 5 Feb 2004 06:15:46 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
cc: bidulock@openss7.org, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA version control
In-Reply-To: <01BFFB31-57D3-11D8-861F-000A95DC192A@lurchi.franken.de>
Message-ID: <Pine.SOL.4.10.10402050612280.14937-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>


Brian,
 Is there any reason why you disagree with the change?

 Is it is because ASP Up is the first message comes from ASP and
 version control is checked at very first time with the assumption
 all remaining messges will have the same version?

--Samuel

On Thu, 5 Feb 2004, Michael Tuexen wrote:

> Brian,
> 
> you disagree with the change? This means you want to have an
> error ONLY returned for ASP-Up messages as the RFC states?
> 
> I'm suggesting a change that it is returned for all messages.
> 
> Best regards
> Michael
> 
> 
> On Feb 5, 2004, at 12:33 PM, Brian F. G. Bidulock wrote:
> 
> > Michael,
> >
> > I missed that.  And, therefore, disagree with the change.  An error
> > must be returned for any message with an unsupported version, not
> > just ASP Up, as the RFC already states.  The example case was in
> > my last mail.
> >
> > --brian
> >
> > Michael Tuexen wrote:                                                  
> >             (Thu, 05 Feb 2004 12:24:07)
> >> Brian,
> >>
> >> part of my suggestion is to replace:
> >>
> >>      If an ASP Up message with an unsupported version is received, the
> >>
> >> with
> >>
> >>      If a message with an unsupported version is received, the
> >>
> >> At least for me, this does change the requested behaviour.
> >>
> >> Best regards
> >> Michael
> >>
> >> On Feb 5, 2004, at 11:30 AM, Brian F. G. Bidulock wrote:
> >>
> >>> Michael,
> >>>
> >>> I don't think that your proposed text takes us any farther towards
> >>> that goal.  You have changed "assumed that" to "likely that the
> >>> message having an unsupported version is an ASP Up message and
> >>> therefore [likely] that".
> >>>
> >>> This is just description.  The requirement is (unchanged):
> >>>
> >>>> If a message with an unsupported version is received, the
> >>>> receiving end responds with an Error message, indicating the version
> >>>> the receiving node supports and notifies Layer Management.
> >>>
> >>> This is obviously any message.
> >>>
> >>> As there is no change to the requirement, the new text is 
> >>> superfluous.
> >>>
> >>> Regardless of likelihoods or assumptions, the Error message is
> >>> returned to any message received with an unsupported version and 
> >>> Layer
> >>> Management is notified.  Suggesting that it is likely that an ASP Up
> >>> is the cause, actually distracts from the requirement to return the
> >>> error to any message.
> >>>
> >>> A node might actually send message Foo with Version=100 to test a
> >>> remote node's support for message Foo (only available in Version=100)
> >>> while performing the ASP Up and ASP Active procedures using 
> >>> Version=1.
> >>> This requirement provides that message Foo will be retured with an
> >>> "usupported version" if version 100 is not supported (and obviously
> >>> the message Foo is not supported).
> >>>
> >>> It would be better to strike the line starting with "Because", 
> >>> because
> >>> it was superfluous to begin with.  Changing assumptions to 
> >>> likelihoods
> >>> does not increase its pertinence.
> >>>
> >>> --brian
> >>>
> >>>
> >>> Michael Tuexen wrote:
> >>>             (Thu, 05 Feb 2004 10:17:40)
> >>>> Brian,
> >>>>
> >>>> I agree with you that there are a lot of places which are not
> >>>> very precisely (this is the same with other RFCs) but this
> >>>> question came up multiple times. Others not. That is why I'm
> >>>> asking to clarify this.
> >>>>
> >>>> I know about customers and testers who test exactly this and
> >>>> always ask: what is the correct behaviour. So what is the
> >>>> problem in making this clear? Think about having different
> >>>> customers requesting different implementations?
> >>>>
> >>>> Best regards
> >>>> Michael
> >>>>
> >>>> On Feb 4, 2004, at 11:46 PM, Brian F. G. Bidulock wrote:
> >>>>
> >>>>> Michael,
> >>>>>
> >>>>> I think you need to read the RFC from the viewpoint of a
> >>>>> specification
> >>>>> instead of the viewpoint of an implementation.  When it says
> >>>>> "assumed"
> >>>>> it means "assumed [by the authors in the specification of the
> >>>>> protocol]"
> >>>>> and not "assumed [by the implementation]".
> >>>>>
> >>>>> There are many place in the RFC where this is the case, because of
> >>>>> the
> >>>>> editors' preference for words like "assumed".  If we are to correct
> >>>>> the lazy
> >>>>> English in the document, it would require an extensive rewrite.
> >>>>>
> >>>>> --brian
> >>>>>
> >>>>> Michael Tuexen wrote:
> >>>>>             (Wed, 04 Feb 2004 21:56:43)
> >>>>>> Dear all,
> >>>>>>
> >>>>>> the RFC describes that an M3UA endpoint should check the version
> >>>>>> field
> >>>>>> for ASP Up messages and leaves it unspecified how other messages
> >>>>>> should
> >>>>>> be handled.
> >>>>>>
> >>>>>> In real scenarios the first message having an unsupported message 
> >>>>>> is
> >>>>>> most likely an ASP-Up message, but my experience is, that people
> >>>>>> testing
> >>>>>> implementations always ask how these other messages should be
> >>>>>> handled.
> >>>>>>
> >>>>>> Therefore I would like to suggest a clarification in the IG 
> >>>>>> clearly
> >>>>>> stating how these other messages with an unsupported version 
> >>>>>> should
> >>>>>> be handled.
> >>>>>>
> >>>>>> We can specify that it is checked for all messages or only for
> >>>>>> ASP-Up
> >>>>>> messages, ignoring the version field for non ASP-Up messages.
> >>>>>>
> >>>>>> The easiest solution seems to be (for me) to check the field for
> >>>>>> all messages. So you could write
> >>>>>>
> >>>>>> if (message->version != 1)
> >>>>>>    send(error)
> >>>>>>
> >>>>>> instead of
> >>>>>>
> >>>>>> if ((message->class == 3) && (message->type == 1) &&
> >>>>>> (message->(message->version != 1))
> >>>>>>    send(error)
> >>>>>>
> >>>>>> Therefore I suggest to include the following text in the IG.
> >>>>>>
> >>>>>> Best regards
> >>>>>> Michael
> >>>>>>
> >>>>>>
> >>>>>> <---- SNIP
> >>>>>> 3.28 Version Control
> >>>>>>
> >>>>>> 3.28.1 Description of the problem
> >>>>>>
> >>>>>> The RFC describes how ASP Up messages with an unsupported version
> >>>>>> are handled but leaves it unspecified how other messages should be
> >>>>>> handled if the version number is not supported.
> >>>>>>
> >>>>>> 3.28.2 Text changes to the document
> >>>>>>     ---------
> >>>>>>     Old text: (Section 4.3.4.1.1)
> >>>>>>     ---------
> >>>>>>
> >>>>>> 4.3.4.1.1 M3UA Version Control
> >>>>>>
> >>>>>>     If an ASP Up message with an unsupported version is received,
> >>>>>> the
> >>>>>>     receiving end responds with an Error message, indicating the
> >>>>>> version
> >>>>>>     the receiving node supports and notifies Layer Management.
> >>>>>>
> >>>>>>     This is useful when protocol version upgrades are being
> >>>>>> performed
> >>>>>> in
> >>>>>>     a network.  A node upgraded to a newer version should support
> >>>>>> the
> >>>>>>     older versions used on other nodes it is communicating with.
> >>>>>> Because
> >>>>>>     ASPs initiate the ASP Up procedure it is assumed that the 
> >>>>>> Error
> >>>>>>     message would normally come from the SGP.
> >>>>>>
> >>>>>>     ---------
> >>>>>>     New text: (Section 4.3.4.1.1)
> >>>>>>     ---------
> >>>>>>
> >>>>>> 4.3.4.1.1 M3UA Version Control
> >>>>>>
> >>>>>>     If a message with an unsupported version is received, the
> >>>>>>     receiving end responds with an Error message, indicating the
> >>>>>> version
> >>>>>>     the receiving node supports and notifies Layer Management.
> >>>>>>
> >>>>>>     This is useful when protocol version upgrades are being
> >>>>>> performed
> >>>>>> in
> >>>>>>     a network.  A node upgraded to a newer version should support
> >>>>>> the
> >>>>>>     older versions used on other nodes it is communicating with.
> >>>>>> Because
> >>>>>>     ASPs initiate the ASP Up procedure it is likely that the 
> >>>>>> message
> >>>>>> having
> >>>>>>     an unsupported version is an ASP Up message and therefore that
> >>>>>> the
> >>>>>> Error
> >>>>>>     message would normally come from the SGP.
> >>>>>>
> >>>>>>
> >>>>>> 3.28.3 Solution description
> >>>>>>
> >>>>>> The new text clearly describes that the version should be checked
> >>>>>> for
> >>>>>> all
> >>>>>> messages.
> >>>>>> <---- SNIP
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> Sigtran mailing list
> >>>>>> Sigtran@ietf.org
> >>>>>> https://www1.ietf.org/mailman/listinfo/sigtran
> >>>>>
> >>>>> -- 
> >>>>> Brian F. G. Bidulock
> >>>>> bidulock@openss7.org
> >>>>> http://www.openss7.org/
> >>>>>
> >>>
> >>> -- 
> >>> Brian F. G. Bidulock
> >>> bidulock@openss7.org
> >>> http://www.openss7.org/
> >>>
> >
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 


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



From exim@www1.ietf.org  Thu Feb  5 07:48: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 HAA13709
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 07:48:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoivL-00083h-RP
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 07:48:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15Cm3vj030952
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 07:48:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoivJ-00082z-3K; Thu, 05 Feb 2004 07:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AoivC-00082h-V4
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 07:47:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13702
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 07:47:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoivC-0002py-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 07:47:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AoiuE-0002lU-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 07:46:55 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[4zPXQsp857+0rmh/Iw82mFjAENy1vMm9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoitY-0002hC-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 07:46:12 -0500
Received: from ns.pigworks.openss7.net (IDENT:drfW98agnxJTeFbadh+ggQhE7fQ8ZRlX@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i15CkBI06456;
	Thu, 5 Feb 2004 05:46:11 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i15CkAH14990;
	Thu, 5 Feb 2004 05:46:10 -0700
Date: Thu, 5 Feb 2004 05:46:10 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA version control
Message-ID: <20040205054610.A14760@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, sigtran@ietf.org
References: <01BFFB31-57D3-11D8-861F-000A95DC192A@lurchi.franken.de> <Pine.SOL.4.10.10402050612280.14937-100000@sun2685.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10402050612280.14937-100000@sun2685.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Thu, Feb 05, 2004 at 06:15:46AM -0600
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Samuel,

No, I'm sorry, I was completely twisted around in my earlier
comments.  I must have been running "patch -r": I agree with
Michael's proposal, I just originally thought that he was
proposing the reverse.

I agree with Michael's changes.  I take it you do too?

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 05 Feb 2004 06:15:46)
> 
> Brian,
>  Is there any reason why you disagree with the change?
> 
>  Is it is because ASP Up is the first message comes from ASP and
>  version control is checked at very first time with the assumption
>  all remaining messges will have the same version?
> 
> --Samuel
> 
> On Thu, 5 Feb 2004, Michael Tuexen wrote:
> 
> > Brian,
> > 
> > you disagree with the change? This means you want to have an
> > error ONLY returned for ASP-Up messages as the RFC states?
> > 
> > I'm suggesting a change that it is returned for all messages.
> > 
> > Best regards
> > Michael
> > 
> > 
> > On Feb 5, 2004, at 12:33 PM, Brian F. G. Bidulock wrote:
> > 
> > > Michael,
> > >
> > > I missed that.  And, therefore, disagree with the change.  An error
> > > must be returned for any message with an unsupported version, not
> > > just ASP Up, as the RFC already states.  The example case was in
> > > my last mail.
> > >
> > > --brian
> > >
> > > Michael Tuexen wrote:                                                  
> > >             (Thu, 05 Feb 2004 12:24:07)
> > >> Brian,
> > >>
> > >> part of my suggestion is to replace:
> > >>
> > >>      If an ASP Up message with an unsupported version is received, the
> > >>
> > >> with
> > >>
> > >>      If a message with an unsupported version is received, the
> > >>
> > >> At least for me, this does change the requested behaviour.
> > >>
> > >> Best regards
> > >> Michael
> > >>
> > >> On Feb 5, 2004, at 11:30 AM, Brian F. G. Bidulock wrote:
> > >>
> > >>> Michael,
> > >>>
> > >>> I don't think that your proposed text takes us any farther towards
> > >>> that goal.  You have changed "assumed that" to "likely that the
> > >>> message having an unsupported version is an ASP Up message and
> > >>> therefore [likely] that".
> > >>>
> > >>> This is just description.  The requirement is (unchanged):
> > >>>
> > >>>> If a message with an unsupported version is received, the
> > >>>> receiving end responds with an Error message, indicating the version
> > >>>> the receiving node supports and notifies Layer Management.
> > >>>
> > >>> This is obviously any message.
> > >>>
> > >>> As there is no change to the requirement, the new text is 
> > >>> superfluous.
> > >>>
> > >>> Regardless of likelihoods or assumptions, the Error message is
> > >>> returned to any message received with an unsupported version and 
> > >>> Layer
> > >>> Management is notified.  Suggesting that it is likely that an ASP Up
> > >>> is the cause, actually distracts from the requirement to return the
> > >>> error to any message.
> > >>>
> > >>> A node might actually send message Foo with Version=100 to test a
> > >>> remote node's support for message Foo (only available in Version=100)
> > >>> while performing the ASP Up and ASP Active procedures using 
> > >>> Version=1.
> > >>> This requirement provides that message Foo will be retured with an
> > >>> "usupported version" if version 100 is not supported (and obviously
> > >>> the message Foo is not supported).
> > >>>
> > >>> It would be better to strike the line starting with "Because", 
> > >>> because
> > >>> it was superfluous to begin with.  Changing assumptions to 
> > >>> likelihoods
> > >>> does not increase its pertinence.
> > >>>
> > >>> --brian
> > >>>
> > >>>
> > >>> Michael Tuexen wrote:
> > >>>             (Thu, 05 Feb 2004 10:17:40)
> > >>>> Brian,
> > >>>>
> > >>>> I agree with you that there are a lot of places which are not
> > >>>> very precisely (this is the same with other RFCs) but this
> > >>>> question came up multiple times. Others not. That is why I'm
> > >>>> asking to clarify this.
> > >>>>
> > >>>> I know about customers and testers who test exactly this and
> > >>>> always ask: what is the correct behaviour. So what is the
> > >>>> problem in making this clear? Think about having different
> > >>>> customers requesting different implementations?
> > >>>>
> > >>>> Best regards
> > >>>> Michael
> > >>>>
> > >>>> On Feb 4, 2004, at 11:46 PM, Brian F. G. Bidulock wrote:
> > >>>>
> > >>>>> Michael,
> > >>>>>
> > >>>>> I think you need to read the RFC from the viewpoint of a
> > >>>>> specification
> > >>>>> instead of the viewpoint of an implementation.  When it says
> > >>>>> "assumed"
> > >>>>> it means "assumed [by the authors in the specification of the
> > >>>>> protocol]"
> > >>>>> and not "assumed [by the implementation]".
> > >>>>>
> > >>>>> There are many place in the RFC where this is the case, because of
> > >>>>> the
> > >>>>> editors' preference for words like "assumed".  If we are to correct
> > >>>>> the lazy
> > >>>>> English in the document, it would require an extensive rewrite.
> > >>>>>
> > >>>>> --brian
> > >>>>>
> > >>>>> Michael Tuexen wrote:
> > >>>>>             (Wed, 04 Feb 2004 21:56:43)
> > >>>>>> Dear all,
> > >>>>>>
> > >>>>>> the RFC describes that an M3UA endpoint should check the version
> > >>>>>> field
> > >>>>>> for ASP Up messages and leaves it unspecified how other messages
> > >>>>>> should
> > >>>>>> be handled.
> > >>>>>>
> > >>>>>> In real scenarios the first message having an unsupported message 
> > >>>>>> is
> > >>>>>> most likely an ASP-Up message, but my experience is, that people
> > >>>>>> testing
> > >>>>>> implementations always ask how these other messages should be
> > >>>>>> handled.
> > >>>>>>
> > >>>>>> Therefore I would like to suggest a clarification in the IG 
> > >>>>>> clearly
> > >>>>>> stating how these other messages with an unsupported version 
> > >>>>>> should
> > >>>>>> be handled.
> > >>>>>>
> > >>>>>> We can specify that it is checked for all messages or only for
> > >>>>>> ASP-Up
> > >>>>>> messages, ignoring the version field for non ASP-Up messages.
> > >>>>>>
> > >>>>>> The easiest solution seems to be (for me) to check the field for
> > >>>>>> all messages. So you could write
> > >>>>>>
> > >>>>>> if (message->version != 1)
> > >>>>>>    send(error)
> > >>>>>>
> > >>>>>> instead of
> > >>>>>>
> > >>>>>> if ((message->class == 3) && (message->type == 1) &&
> > >>>>>> (message->(message->version != 1))
> > >>>>>>    send(error)
> > >>>>>>
> > >>>>>> Therefore I suggest to include the following text in the IG.
> > >>>>>>
> > >>>>>> Best regards
> > >>>>>> Michael
> > >>>>>>
> > >>>>>>
> > >>>>>> <---- SNIP
> > >>>>>> 3.28 Version Control
> > >>>>>>
> > >>>>>> 3.28.1 Description of the problem
> > >>>>>>
> > >>>>>> The RFC describes how ASP Up messages with an unsupported version
> > >>>>>> are handled but leaves it unspecified how other messages should be
> > >>>>>> handled if the version number is not supported.
> > >>>>>>
> > >>>>>> 3.28.2 Text changes to the document
> > >>>>>>     ---------
> > >>>>>>     Old text: (Section 4.3.4.1.1)
> > >>>>>>     ---------
> > >>>>>>
> > >>>>>> 4.3.4.1.1 M3UA Version Control
> > >>>>>>
> > >>>>>>     If an ASP Up message with an unsupported version is received,
> > >>>>>> the
> > >>>>>>     receiving end responds with an Error message, indicating the
> > >>>>>> version
> > >>>>>>     the receiving node supports and notifies Layer Management.
> > >>>>>>
> > >>>>>>     This is useful when protocol version upgrades are being
> > >>>>>> performed
> > >>>>>> in
> > >>>>>>     a network.  A node upgraded to a newer version should support
> > >>>>>> the
> > >>>>>>     older versions used on other nodes it is communicating with.
> > >>>>>> Because
> > >>>>>>     ASPs initiate the ASP Up procedure it is assumed that the 
> > >>>>>> Error
> > >>>>>>     message would normally come from the SGP.
> > >>>>>>
> > >>>>>>     ---------
> > >>>>>>     New text: (Section 4.3.4.1.1)
> > >>>>>>     ---------
> > >>>>>>
> > >>>>>> 4.3.4.1.1 M3UA Version Control
> > >>>>>>
> > >>>>>>     If a message with an unsupported version is received, the
> > >>>>>>     receiving end responds with an Error message, indicating the
> > >>>>>> version
> > >>>>>>     the receiving node supports and notifies Layer Management.
> > >>>>>>
> > >>>>>>     This is useful when protocol version upgrades are being
> > >>>>>> performed
> > >>>>>> in
> > >>>>>>     a network.  A node upgraded to a newer version should support
> > >>>>>> the
> > >>>>>>     older versions used on other nodes it is communicating with.
> > >>>>>> Because
> > >>>>>>     ASPs initiate the ASP Up procedure it is likely that the 
> > >>>>>> message
> > >>>>>> having
> > >>>>>>     an unsupported version is an ASP Up message and therefore that
> > >>>>>> the
> > >>>>>> Error
> > >>>>>>     message would normally come from the SGP.
> > >>>>>>
> > >>>>>>
> > >>>>>> 3.28.3 Solution description
> > >>>>>>
> > >>>>>> The new text clearly describes that the version should be checked
> > >>>>>> for
> > >>>>>> all
> > >>>>>> messages.
> > >>>>>> <---- SNIP
> > >>>>>>
> > >>>>>>
> > >>>>>> _______________________________________________
> > >>>>>> Sigtran mailing list
> > >>>>>> Sigtran@ietf.org
> > >>>>>> https://www1.ietf.org/mailman/listinfo/sigtran
> > >>>>>
> > >>>>> -- 
> > >>>>> Brian F. G. Bidulock
> > >>>>> bidulock@openss7.org
> > >>>>> http://www.openss7.org/
> > >>>>>
> > >>>
> > >>> -- 
> > >>> Brian F. G. Bidulock
> > >>> bidulock@openss7.org
> > >>> http://www.openss7.org/
> > >>>
> > >
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 

-- 
Brian 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 Feb  5 08:53: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 IAA15202
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 08:53:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AojwG-0003pR-7D
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 08:53:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15Dr4c0014708
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 08:53:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AojwD-0003ov-4I; Thu, 05 Feb 2004 08:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AojvE-0003n2-CH
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 08:52:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15177
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 08:51:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AojvC-0000bo-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 08:51:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AojuJ-0000XC-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 08:51:05 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aojtd-0000Rn-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 08:50:21 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i15DoKAh007793
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 14:50:21 +0100
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 5 Feb 2004 14:50:20 +0100
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id 1A6J6PHB; Thu, 5 Feb 2004 14:50:34 +0100
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <VRLLDP31>; Thu, 5 Feb 2004 14:47:04 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C04331A2B@eestqnt105.es.eu.ericsson.se>
X-Sybari-Trust: fdb990df 6b512624 6c3547e6 00000138
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>,
        Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Cc: bidulock@openss7.org, sigtran@ietf.org
Subject: RE: [Sigtran] M3UA version control
Date: Thu, 5 Feb 2004 14:49:30 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 05 Feb 2004 13:50:20.0813 (UTC) FILETIME=[FEEC03D0:01C3EBEE]
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 Michael et al., 


Take into account that you are referring to a section that talks about the ASPUP procedures. ASPUP message is what is really discussed and we should not include there the behavior as a response to any other messages. 

What should be included in the IG is paragraph within the section 3.8.1 explaining the "Invalid Version" code. I've just seen that we have a typo there and include the "Invalid Stream Identifier" twice while there is no mention of the "Invalid Version". We'll update the IG with some text explaining the general behavior.

Anyway, a good implementation that is following the state machines and so on from the M3UA document will not have this problems...

Cheers // Javier.

> -----Original Message-----
> From: sigtran-admin@ietf.org 
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Samuel Dur D. Jeyaseelan
> Sent: jueves, 05 de febrero de 2004 13:16
> To: Michael Tuexen
> Cc: bidulock@openss7.org; sigtran@ietf.org
> Subject: Re: [Sigtran] M3UA version control
> 
> 
> 
> Brian,
>  Is there any reason why you disagree with the change?
> 
>  Is it is because ASP Up is the first message comes from ASP and
>  version control is checked at very first time with the assumption
>  all remaining messges will have the same version?
> 
> --Samuel
> 
> On Thu, 5 Feb 2004, Michael Tuexen wrote:
> 
> > Brian,
> > 
> > you disagree with the change? This means you want to have an
> > error ONLY returned for ASP-Up messages as the RFC states?
> > 
> > I'm suggesting a change that it is returned for all messages.
> > 
> > Best regards
> > Michael
> > 
> > 
> > On Feb 5, 2004, at 12:33 PM, Brian F. G. Bidulock wrote:
> > 
> > > Michael,
> > >
> > > I missed that.  And, therefore, disagree with the change. 
>  An error
> > > must be returned for any message with an unsupported version, not
> > > just ASP Up, as the RFC already states.  The example case was in
> > > my last mail.
> > >
> > > --brian
> > >
> > > Michael Tuexen wrote:                                     
>              
> > >             (Thu, 05 Feb 2004 12:24:07)
> > >> Brian,
> > >>
> > >> part of my suggestion is to replace:
> > >>
> > >>      If an ASP Up message with an unsupported version is 
> received, the
> > >>
> > >> with
> > >>
> > >>      If a message with an unsupported version is received, the
> > >>
> > >> At least for me, this does change the requested behaviour.
> > >>
> > >> Best regards
> > >> Michael
> > >>
> > >> On Feb 5, 2004, at 11:30 AM, Brian F. G. Bidulock wrote:
> > >>
> > >>> Michael,
> > >>>
> > >>> I don't think that your proposed text takes us any 
> farther towards
> > >>> that goal.  You have changed "assumed that" to "likely that the
> > >>> message having an unsupported version is an ASP Up message and
> > >>> therefore [likely] that".
> > >>>
> > >>> This is just description.  The requirement is (unchanged):
> > >>>
> > >>>> If a message with an unsupported version is received, the
> > >>>> receiving end responds with an Error message, 
> indicating the version
> > >>>> the receiving node supports and notifies Layer Management.
> > >>>
> > >>> This is obviously any message.
> > >>>
> > >>> As there is no change to the requirement, the new text is 
> > >>> superfluous.
> > >>>
> > >>> Regardless of likelihoods or assumptions, the Error message is
> > >>> returned to any message received with an unsupported 
> version and 
> > >>> Layer
> > >>> Management is notified.  Suggesting that it is likely 
> that an ASP Up
> > >>> is the cause, actually distracts from the requirement 
> to return the
> > >>> error to any message.
> > >>>
> > >>> A node might actually send message Foo with Version=100 
> to test a
> > >>> remote node's support for message Foo (only available 
> in Version=100)
> > >>> while performing the ASP Up and ASP Active procedures using 
> > >>> Version=1.
> > >>> This requirement provides that message Foo will be 
> retured with an
> > >>> "usupported version" if version 100 is not supported 
> (and obviously
> > >>> the message Foo is not supported).
> > >>>
> > >>> It would be better to strike the line starting with "Because", 
> > >>> because
> > >>> it was superfluous to begin with.  Changing assumptions to 
> > >>> likelihoods
> > >>> does not increase its pertinence.
> > >>>
> > >>> --brian
> > >>>
> > >>>
> > >>> Michael Tuexen wrote:
> > >>>             (Thu, 05 Feb 2004 10:17:40)
> > >>>> Brian,
> > >>>>
> > >>>> I agree with you that there are a lot of places which are not
> > >>>> very precisely (this is the same with other RFCs) but this
> > >>>> question came up multiple times. Others not. That is why I'm
> > >>>> asking to clarify this.
> > >>>>
> > >>>> I know about customers and testers who test exactly this and
> > >>>> always ask: what is the correct behaviour. So what is the
> > >>>> problem in making this clear? Think about having different
> > >>>> customers requesting different implementations?
> > >>>>
> > >>>> Best regards
> > >>>> Michael
> > >>>>
> > >>>> On Feb 4, 2004, at 11:46 PM, Brian F. G. Bidulock wrote:
> > >>>>
> > >>>>> Michael,
> > >>>>>
> > >>>>> I think you need to read the RFC from the viewpoint of a
> > >>>>> specification
> > >>>>> instead of the viewpoint of an implementation.  When it says
> > >>>>> "assumed"
> > >>>>> it means "assumed [by the authors in the specification of the
> > >>>>> protocol]"
> > >>>>> and not "assumed [by the implementation]".
> > >>>>>
> > >>>>> There are many place in the RFC where this is the 
> case, because of
> > >>>>> the
> > >>>>> editors' preference for words like "assumed".  If we 
> are to correct
> > >>>>> the lazy
> > >>>>> English in the document, it would require an 
> extensive rewrite.
> > >>>>>
> > >>>>> --brian
> > >>>>>
> > >>>>> Michael Tuexen wrote:
> > >>>>>             (Wed, 04 Feb 2004 21:56:43)
> > >>>>>> Dear all,
> > >>>>>>
> > >>>>>> the RFC describes that an M3UA endpoint should check 
> the version
> > >>>>>> field
> > >>>>>> for ASP Up messages and leaves it unspecified how 
> other messages
> > >>>>>> should
> > >>>>>> be handled.
> > >>>>>>
> > >>>>>> In real scenarios the first message having an 
> unsupported message 
> > >>>>>> is
> > >>>>>> most likely an ASP-Up message, but my experience is, 
> that people
> > >>>>>> testing
> > >>>>>> implementations always ask how these other messages should be
> > >>>>>> handled.
> > >>>>>>
> > >>>>>> Therefore I would like to suggest a clarification in the IG 
> > >>>>>> clearly
> > >>>>>> stating how these other messages with an unsupported version 
> > >>>>>> should
> > >>>>>> be handled.
> > >>>>>>
> > >>>>>> We can specify that it is checked for all messages 
> or only for
> > >>>>>> ASP-Up
> > >>>>>> messages, ignoring the version field for non ASP-Up messages.
> > >>>>>>
> > >>>>>> The easiest solution seems to be (for me) to check 
> the field for
> > >>>>>> all messages. So you could write
> > >>>>>>
> > >>>>>> if (message->version != 1)
> > >>>>>>    send(error)
> > >>>>>>
> > >>>>>> instead of
> > >>>>>>
> > >>>>>> if ((message->class == 3) && (message->type == 1) &&
> > >>>>>> (message->(message->version != 1))
> > >>>>>>    send(error)
> > >>>>>>
> > >>>>>> Therefore I suggest to include the following text in the IG.
> > >>>>>>
> > >>>>>> Best regards
> > >>>>>> Michael
> > >>>>>>
> > >>>>>>
> > >>>>>> <---- SNIP
> > >>>>>> 3.28 Version Control
> > >>>>>>
> > >>>>>> 3.28.1 Description of the problem
> > >>>>>>
> > >>>>>> The RFC describes how ASP Up messages with an 
> unsupported version
> > >>>>>> are handled but leaves it unspecified how other 
> messages should be
> > >>>>>> handled if the version number is not supported.
> > >>>>>>
> > >>>>>> 3.28.2 Text changes to the document
> > >>>>>>     ---------
> > >>>>>>     Old text: (Section 4.3.4.1.1)
> > >>>>>>     ---------
> > >>>>>>
> > >>>>>> 4.3.4.1.1 M3UA Version Control
> > >>>>>>
> > >>>>>>     If an ASP Up message with an unsupported version 
> is received,
> > >>>>>> the
> > >>>>>>     receiving end responds with an Error message, 
> indicating the
> > >>>>>> version
> > >>>>>>     the receiving node supports and notifies Layer 
> Management.
> > >>>>>>
> > >>>>>>     This is useful when protocol version upgrades are being
> > >>>>>> performed
> > >>>>>> in
> > >>>>>>     a network.  A node upgraded to a newer version 
> should support
> > >>>>>> the
> > >>>>>>     older versions used on other nodes it is 
> communicating with.
> > >>>>>> Because
> > >>>>>>     ASPs initiate the ASP Up procedure it is assumed 
> that the 
> > >>>>>> Error
> > >>>>>>     message would normally come from the SGP.
> > >>>>>>
> > >>>>>>     ---------
> > >>>>>>     New text: (Section 4.3.4.1.1)
> > >>>>>>     ---------
> > >>>>>>
> > >>>>>> 4.3.4.1.1 M3UA Version Control
> > >>>>>>
> > >>>>>>     If a message with an unsupported version is received, the
> > >>>>>>     receiving end responds with an Error message, 
> indicating the
> > >>>>>> version
> > >>>>>>     the receiving node supports and notifies Layer 
> Management.
> > >>>>>>
> > >>>>>>     This is useful when protocol version upgrades are being
> > >>>>>> performed
> > >>>>>> in
> > >>>>>>     a network.  A node upgraded to a newer version 
> should support
> > >>>>>> the
> > >>>>>>     older versions used on other nodes it is 
> communicating with.
> > >>>>>> Because
> > >>>>>>     ASPs initiate the ASP Up procedure it is likely that the 
> > >>>>>> message
> > >>>>>> having
> > >>>>>>     an unsupported version is an ASP Up message and 
> therefore that
> > >>>>>> the
> > >>>>>> Error
> > >>>>>>     message would normally come from the SGP.
> > >>>>>>
> > >>>>>>
> > >>>>>> 3.28.3 Solution description
> > >>>>>>
> > >>>>>> The new text clearly describes that the version 
> should be checked
> > >>>>>> for
> > >>>>>> all
> > >>>>>> messages.
> > >>>>>> <---- SNIP
> > >>>>>>
> > >>>>>>
> > >>>>>> _______________________________________________
> > >>>>>> Sigtran mailing list
> > >>>>>> Sigtran@ietf.org
> > >>>>>> https://www1.ietf.org/mailman/listinfo/sigtran
> > >>>>>
> > >>>>> -- 
> > >>>>> Brian F. G. Bidulock
> > >>>>> bidulock@openss7.org
> > >>>>> http://www.openss7.org/
> > >>>>>
> > >>>
> > >>> -- 
> > >>> Brian F. G. Bidulock
> > >>> bidulock@openss7.org
> > >>> http://www.openss7.org/
> > >>>
> > >
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Thu Feb  5 09:14: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 JAA15935
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 09:14:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AokGa-0007nx-KT
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 09:14:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15EE4oO029979
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 09:14:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AokGX-0007nI-Ly; Thu, 05 Feb 2004 09:14:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AokFa-0007lo-7j
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 09:13:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15893
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 09:12:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AokFY-00035q-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 09:13:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AokEd-000314-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 09:12:04 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AokEE-0002vj-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 09:11:38 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i15EBZ7T010634
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 09:11:35 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Date: Thu, 5 Feb 2004 09:13:04 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOGEEICEAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] SUA v16: sequence control parameter in CLDT msg
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Table 10/Q.711 notes that the sequence control parameter is optional in the
SCCP UNITDATA msg.
However the sequence control parameter is listed as mandatory in the SUA
CLDT msg.
So I have 2 questions:

1. Why do we have this mandatory/optional mismatch?

2. If sequence control is not present in a SCCP UNITDATA msg, what should be
the value of the mandatory sequence control param in the CLDT msg.

Barry Nagelberg


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



From exim@www1.ietf.org  Thu Feb  5 09:23: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 JAA16178
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 09:23:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AokPF-00087Z-Ac
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 09:23:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15EN1he031195
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 09:23:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AokPF-000872-2E; Thu, 05 Feb 2004 09:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AokPD-00086r-5z
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 09:22:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16166
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 09:22:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AokPB-0003z5-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 09:22:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AokOE-0003tq-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 09:21:59 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AokNN-0003om-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 09:21:06 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i15EL5qY020670
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 15:21:05 +0100 (MET)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 5 Feb 2004 15:21:04 +0100
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id 1AZBDMP9; Thu, 5 Feb 2004 15:21:04 +0100
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <VRLLDP79>; Thu, 5 Feb 2004 15:17:48 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C04331A2E@eestqnt105.es.eu.ericsson.se>
X-Sybari-Trust: dbd758f0 6b512624 6c3547e6 00000138
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>,
        "'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>,
        Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Cc: bidulock@openss7.org, sigtran@ietf.org
Subject: RE: [Sigtran] M3UA version control
Date: Thu, 5 Feb 2004 15:20:12 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 05 Feb 2004 14:21:04.0838 (UTC) FILETIME=[4A0BE660:01C3EBF3]
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>

Here is the proposed text:


3.28 Invalid Version parameter explanation

3.28.1 Description of the problem

There is a typo in the current RFC within the ERROR message sub-section. "Invalid Stream identifier" parameter is explained twice while the "Invalid Version" is not even mentioned.

3.28.2 Text changes to the document

--------- 
Old text: (Section 3.8.1) 
---------

The Error message is used to notify a peer of an error event associated with an incoming message.  For example, the message type might be unexpected given the current state, or a parameter value might be invalid.

--------- 
New text: (Section 3.8.1) 
---------

The Error message is used to notify a peer of an error event associated with an incoming message.  For example, the message type might be unexpected given the current state, or a parameter value might be invalid. Error messages MUST NOT be generated in response to other Error messages.


--------- 
Old text: (Section 3.8.1) 
---------

The "Invalid Stream Identifier" error is sent if a message is received on an unexpected SCTP stream (e.g., a MGMT message was received on a stream other than "0").  Error messages MUST NOT be generated in response to other Error messages.

--------- 
New text: (Section 3.8.1) 
---------

The "Invalid Version" error is sent if a message with an unsupported version is received, the receiving end responds with an Error message, indicating the version the receiving node supports and notifies layer management.


3.28.3 Solution Description

The duplicated text has been substituted by an explanation of the missing parameter "Invalid Version". Also, the last sentence next to the duplicated text has been moved to the beginning  of the section 3.8.1. 



Cheers // Javier.

> -----Original Message-----
> From: sigtran-admin@ietf.org 
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> J.Javier Pastor (ML/EEM)
> Sent: jueves, 05 de febrero de 2004 14:50
> To: 'Samuel Dur D. Jeyaseelan'; Michael Tuexen
> Cc: bidulock@openss7.org; sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA version control
> 
> 
> Hi Michael et al., 
> 
> 
> Take into account that you are referring to a section that 
> talks about the ASPUP procedures. ASPUP message is what is 
> really discussed and we should not include there the behavior 
> as a response to any other messages. 
> 
> What should be included in the IG is paragraph within the 
> section 3.8.1 explaining the "Invalid Version" code. I've 
> just seen that we have a typo there and include the "Invalid 
> Stream Identifier" twice while there is no mention of the 
> "Invalid Version". We'll update the IG with some text 
> explaining the general behavior.
> 
> Anyway, a good implementation that is following the state 
> machines and so on from the M3UA document will not have this 
> problems...
> 
> Cheers // Javier.
> 
> > -----Original Message-----
> > From: sigtran-admin@ietf.org 
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Samuel Dur D. Jeyaseelan
> > Sent: jueves, 05 de febrero de 2004 13:16
> > To: Michael Tuexen
> > Cc: bidulock@openss7.org; sigtran@ietf.org
> > Subject: Re: [Sigtran] M3UA version control
> > 
> > 
> > 
> > Brian,
> >  Is there any reason why you disagree with the change?
> > 
> >  Is it is because ASP Up is the first message comes from ASP and
> >  version control is checked at very first time with the assumption
> >  all remaining messges will have the same version?
> > 
> > --Samuel
> > 
> > On Thu, 5 Feb 2004, Michael Tuexen wrote:
> > 
> > > Brian,
> > > 
> > > you disagree with the change? This means you want to have an
> > > error ONLY returned for ASP-Up messages as the RFC states?
> > > 
> > > I'm suggesting a change that it is returned for all messages.
> > > 
> > > Best regards
> > > Michael
> > > 
> > > 
> > > On Feb 5, 2004, at 12:33 PM, Brian F. G. Bidulock wrote:
> > > 
> > > > Michael,
> > > >
> > > > I missed that.  And, therefore, disagree with the change. 
> >  An error
> > > > must be returned for any message with an unsupported 
> version, not
> > > > just ASP Up, as the RFC already states.  The example case was in
> > > > my last mail.
> > > >
> > > > --brian
> > > >
> > > > Michael Tuexen wrote:                                     
> >              
> > > >             (Thu, 05 Feb 2004 12:24:07)
> > > >> Brian,
> > > >>
> > > >> part of my suggestion is to replace:
> > > >>
> > > >>      If an ASP Up message with an unsupported version is 
> > received, the
> > > >>
> > > >> with
> > > >>
> > > >>      If a message with an unsupported version is received, the
> > > >>
> > > >> At least for me, this does change the requested behaviour.
> > > >>
> > > >> Best regards
> > > >> Michael
> > > >>
> > > >> On Feb 5, 2004, at 11:30 AM, Brian F. G. Bidulock wrote:
> > > >>
> > > >>> Michael,
> > > >>>
> > > >>> I don't think that your proposed text takes us any 
> > farther towards
> > > >>> that goal.  You have changed "assumed that" to 
> "likely that the
> > > >>> message having an unsupported version is an ASP Up message and
> > > >>> therefore [likely] that".
> > > >>>
> > > >>> This is just description.  The requirement is (unchanged):
> > > >>>
> > > >>>> If a message with an unsupported version is received, the
> > > >>>> receiving end responds with an Error message, 
> > indicating the version
> > > >>>> the receiving node supports and notifies Layer Management.
> > > >>>
> > > >>> This is obviously any message.
> > > >>>
> > > >>> As there is no change to the requirement, the new text is 
> > > >>> superfluous.
> > > >>>
> > > >>> Regardless of likelihoods or assumptions, the Error message is
> > > >>> returned to any message received with an unsupported 
> > version and 
> > > >>> Layer
> > > >>> Management is notified.  Suggesting that it is likely 
> > that an ASP Up
> > > >>> is the cause, actually distracts from the requirement 
> > to return the
> > > >>> error to any message.
> > > >>>
> > > >>> A node might actually send message Foo with Version=100 
> > to test a
> > > >>> remote node's support for message Foo (only available 
> > in Version=100)
> > > >>> while performing the ASP Up and ASP Active procedures using 
> > > >>> Version=1.
> > > >>> This requirement provides that message Foo will be 
> > retured with an
> > > >>> "usupported version" if version 100 is not supported 
> > (and obviously
> > > >>> the message Foo is not supported).
> > > >>>
> > > >>> It would be better to strike the line starting with 
> "Because", 
> > > >>> because
> > > >>> it was superfluous to begin with.  Changing assumptions to 
> > > >>> likelihoods
> > > >>> does not increase its pertinence.
> > > >>>
> > > >>> --brian
> > > >>>
> > > >>>
> > > >>> Michael Tuexen wrote:
> > > >>>             (Thu, 05 Feb 2004 10:17:40)
> > > >>>> Brian,
> > > >>>>
> > > >>>> I agree with you that there are a lot of places which are not
> > > >>>> very precisely (this is the same with other RFCs) but this
> > > >>>> question came up multiple times. Others not. That is why I'm
> > > >>>> asking to clarify this.
> > > >>>>
> > > >>>> I know about customers and testers who test exactly this and
> > > >>>> always ask: what is the correct behaviour. So what is the
> > > >>>> problem in making this clear? Think about having different
> > > >>>> customers requesting different implementations?
> > > >>>>
> > > >>>> Best regards
> > > >>>> Michael
> > > >>>>
> > > >>>> On Feb 4, 2004, at 11:46 PM, Brian F. G. Bidulock wrote:
> > > >>>>
> > > >>>>> Michael,
> > > >>>>>
> > > >>>>> I think you need to read the RFC from the viewpoint of a
> > > >>>>> specification
> > > >>>>> instead of the viewpoint of an implementation.  When it says
> > > >>>>> "assumed"
> > > >>>>> it means "assumed [by the authors in the 
> specification of the
> > > >>>>> protocol]"
> > > >>>>> and not "assumed [by the implementation]".
> > > >>>>>
> > > >>>>> There are many place in the RFC where this is the 
> > case, because of
> > > >>>>> the
> > > >>>>> editors' preference for words like "assumed".  If we 
> > are to correct
> > > >>>>> the lazy
> > > >>>>> English in the document, it would require an 
> > extensive rewrite.
> > > >>>>>
> > > >>>>> --brian
> > > >>>>>
> > > >>>>> Michael Tuexen wrote:
> > > >>>>>             (Wed, 04 Feb 2004 21:56:43)
> > > >>>>>> Dear all,
> > > >>>>>>
> > > >>>>>> the RFC describes that an M3UA endpoint should check 
> > the version
> > > >>>>>> field
> > > >>>>>> for ASP Up messages and leaves it unspecified how 
> > other messages
> > > >>>>>> should
> > > >>>>>> be handled.
> > > >>>>>>
> > > >>>>>> In real scenarios the first message having an 
> > unsupported message 
> > > >>>>>> is
> > > >>>>>> most likely an ASP-Up message, but my experience is, 
> > that people
> > > >>>>>> testing
> > > >>>>>> implementations always ask how these other 
> messages should be
> > > >>>>>> handled.
> > > >>>>>>
> > > >>>>>> Therefore I would like to suggest a clarification 
> in the IG 
> > > >>>>>> clearly
> > > >>>>>> stating how these other messages with an 
> unsupported version 
> > > >>>>>> should
> > > >>>>>> be handled.
> > > >>>>>>
> > > >>>>>> We can specify that it is checked for all messages 
> > or only for
> > > >>>>>> ASP-Up
> > > >>>>>> messages, ignoring the version field for non 
> ASP-Up messages.
> > > >>>>>>
> > > >>>>>> The easiest solution seems to be (for me) to check 
> > the field for
> > > >>>>>> all messages. So you could write
> > > >>>>>>
> > > >>>>>> if (message->version != 1)
> > > >>>>>>    send(error)
> > > >>>>>>
> > > >>>>>> instead of
> > > >>>>>>
> > > >>>>>> if ((message->class == 3) && (message->type == 1) &&
> > > >>>>>> (message->(message->version != 1))
> > > >>>>>>    send(error)
> > > >>>>>>
> > > >>>>>> Therefore I suggest to include the following text 
> in the IG.
> > > >>>>>>
> > > >>>>>> Best regards
> > > >>>>>> Michael
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> <---- SNIP
> > > >>>>>> 3.28 Version Control
> > > >>>>>>
> > > >>>>>> 3.28.1 Description of the problem
> > > >>>>>>
> > > >>>>>> The RFC describes how ASP Up messages with an 
> > unsupported version
> > > >>>>>> are handled but leaves it unspecified how other 
> > messages should be
> > > >>>>>> handled if the version number is not supported.
> > > >>>>>>
> > > >>>>>> 3.28.2 Text changes to the document
> > > >>>>>>     ---------
> > > >>>>>>     Old text: (Section 4.3.4.1.1)
> > > >>>>>>     ---------
> > > >>>>>>
> > > >>>>>> 4.3.4.1.1 M3UA Version Control
> > > >>>>>>
> > > >>>>>>     If an ASP Up message with an unsupported version 
> > is received,
> > > >>>>>> the
> > > >>>>>>     receiving end responds with an Error message, 
> > indicating the
> > > >>>>>> version
> > > >>>>>>     the receiving node supports and notifies Layer 
> > Management.
> > > >>>>>>
> > > >>>>>>     This is useful when protocol version upgrades are being
> > > >>>>>> performed
> > > >>>>>> in
> > > >>>>>>     a network.  A node upgraded to a newer version 
> > should support
> > > >>>>>> the
> > > >>>>>>     older versions used on other nodes it is 
> > communicating with.
> > > >>>>>> Because
> > > >>>>>>     ASPs initiate the ASP Up procedure it is assumed 
> > that the 
> > > >>>>>> Error
> > > >>>>>>     message would normally come from the SGP.
> > > >>>>>>
> > > >>>>>>     ---------
> > > >>>>>>     New text: (Section 4.3.4.1.1)
> > > >>>>>>     ---------
> > > >>>>>>
> > > >>>>>> 4.3.4.1.1 M3UA Version Control
> > > >>>>>>
> > > >>>>>>     If a message with an unsupported version is 
> received, the
> > > >>>>>>     receiving end responds with an Error message, 
> > indicating the
> > > >>>>>> version
> > > >>>>>>     the receiving node supports and notifies Layer 
> > Management.
> > > >>>>>>
> > > >>>>>>     This is useful when protocol version upgrades are being
> > > >>>>>> performed
> > > >>>>>> in
> > > >>>>>>     a network.  A node upgraded to a newer version 
> > should support
> > > >>>>>> the
> > > >>>>>>     older versions used on other nodes it is 
> > communicating with.
> > > >>>>>> Because
> > > >>>>>>     ASPs initiate the ASP Up procedure it is 
> likely that the 
> > > >>>>>> message
> > > >>>>>> having
> > > >>>>>>     an unsupported version is an ASP Up message and 
> > therefore that
> > > >>>>>> the
> > > >>>>>> Error
> > > >>>>>>     message would normally come from the SGP.
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> 3.28.3 Solution description
> > > >>>>>>
> > > >>>>>> The new text clearly describes that the version 
> > should be checked
> > > >>>>>> for
> > > >>>>>> all
> > > >>>>>> messages.
> > > >>>>>> <---- SNIP
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> _______________________________________________
> > > >>>>>> Sigtran mailing list
> > > >>>>>> Sigtran@ietf.org
> > > >>>>>> https://www1.ietf.org/mailman/listinfo/sigtran
> > > >>>>>
> > > >>>>> -- 
> > > >>>>> Brian F. G. Bidulock
> > > >>>>> bidulock@openss7.org
> > > >>>>> http://www.openss7.org/
> > > >>>>>
> > > >>>
> > > >>> -- 
> > > >>> Brian F. G. Bidulock
> > > >>> bidulock@openss7.org
> > > >>> http://www.openss7.org/
> > > >>>
> > > >
> > > > -- 
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > >
> > > 
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> 
> This communication is confidential and intended solely for 
> the addressee(s). Any unauthorized review, use, disclosure or 
> distribution is prohibited. If you believe this message has 
> been sent to you in error, please notify the sender by 
> replying to this transmission and delete the message without 
> disclosing it. Thank you.
> 
> E-mail including attachments is susceptible to data 
> corruption, interruption, unauthorized amendment, tampering 
> and viruses, and we only send and receive e-mails on the 
> basis that we are not liable for any such corruption, 
> interception, amendment, tampering or viruses or any 
> consequences thereof.
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Thu Feb  5 10:18: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 KAA19260
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 10:18:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AolGV-0001S4-9P
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 10:18:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15FI3Pe005579
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 10:18:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AolGT-0001RF-2N; Thu, 05 Feb 2004 10:18:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AolFd-0001Ec-9A
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 10:17:09 -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 KAA19063
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 10:17:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AolFb-0001cN-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 10:17:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AolEg-0001S9-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 10:16:12 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[kRcg3fRc5AfqRc6MRYCUP/tKEB4RDFyr])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AolDl-0001Jf-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 10:15:13 -0500
Received: from ns.pigworks.openss7.net (IDENT:kh9i/KOY7JdbNGDlw9uuckbq6U4+17mN@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i15FFCI09225;
	Thu, 5 Feb 2004 08:15:12 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i15FFBm17060;
	Thu, 5 Feb 2004 08:15:11 -0700
Date: Thu, 5 Feb 2004 08:15:11 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
Cc: "'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>,
        Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA version control
Message-ID: <20040205081511.A17025@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>,
	"'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>,
	Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, sigtran@ietf.org
References: <1AB3D30B989BF141BBD5C70057B2EF7C04331A2E@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C04331A2E@eestqnt105.es.eu.ericsson.se>; from j.javier.pastor@ericsson.com on Thu, Feb 05, 2004 at 03:20:12PM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

J.Javier,

Works for me.

--brian

J.Javier Pastor (ML/EEM) wrote:                                                   (Thu, 05 Feb 2004 15:20:12)
> Here is the proposed text:
> 
> 
> 3.28 Invalid Version parameter explanation
> 
> 3.28.1 Description of the problem
> 
> There is a typo in the current RFC within the ERROR message sub-section. "Invalid Stream identifier" parameter is explained twice while the "Invalid Version" is not even mentioned.
> 
> 3.28.2 Text changes to the document
> 
> --------- 
> Old text: (Section 3.8.1) 
> ---------
> 
> The Error message is used to notify a peer of an error event associated with an incoming message.  For example, the message type might be unexpected given the current state, or a parameter value might be invalid.
> 
> --------- 
> New text: (Section 3.8.1) 
> ---------
> 
> The Error message is used to notify a peer of an error event associated with an incoming message.  For example, the message type might be unexpected given the current state, or a parameter value might be invalid. Error messages MUST NOT be generated in response to other Error messages.
> 
> 
> --------- 
> Old text: (Section 3.8.1) 
> ---------
> 
> The "Invalid Stream Identifier" error is sent if a message is received on an unexpected SCTP stream (e.g., a MGMT message was received on a stream other than "0").  Error messages MUST NOT be generated in response to other Error messages.
> 
> --------- 
> New text: (Section 3.8.1) 
> ---------
> 
> The "Invalid Version" error is sent if a message with an unsupported version is received, the receiving end responds with an Error message, indicating the version the receiving node supports and notifies layer management.
> 
> 
> 3.28.3 Solution Description
> 
> The duplicated text has been substituted by an explanation of the missing parameter "Invalid Version". Also, the last sentence next to the duplicated text has been moved to the beginning  of the section 3.8.1. 
> 
> 
> 
> Cheers // Javier.
> 
> > -----Original Message-----
> > From: sigtran-admin@ietf.org 
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > J.Javier Pastor (ML/EEM)
> > Sent: jueves, 05 de febrero de 2004 14:50
> > To: 'Samuel Dur D. Jeyaseelan'; Michael Tuexen
> > Cc: bidulock@openss7.org; sigtran@ietf.org
> > Subject: RE: [Sigtran] M3UA version control
> > 
> > 
> > Hi Michael et al., 
> > 
> > 
> > Take into account that you are referring to a section that 
> > talks about the ASPUP procedures. ASPUP message is what is 
> > really discussed and we should not include there the behavior 
> > as a response to any other messages. 
> > 
> > What should be included in the IG is paragraph within the 
> > section 3.8.1 explaining the "Invalid Version" code. I've 
> > just seen that we have a typo there and include the "Invalid 
> > Stream Identifier" twice while there is no mention of the 
> > "Invalid Version". We'll update the IG with some text 
> > explaining the general behavior.
> > 
> > Anyway, a good implementation that is following the state 
> > machines and so on from the M3UA document will not have this 
> > problems...
> > 
> > Cheers // Javier.
> > 
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org 
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > Samuel Dur D. Jeyaseelan
> > > Sent: jueves, 05 de febrero de 2004 13:16
> > > To: Michael Tuexen
> > > Cc: bidulock@openss7.org; sigtran@ietf.org
> > > Subject: Re: [Sigtran] M3UA version control
> > > 
> > > 
> > > 
> > > Brian,
> > >  Is there any reason why you disagree with the change?
> > > 
> > >  Is it is because ASP Up is the first message comes from ASP and
> > >  version control is checked at very first time with the assumption
> > >  all remaining messges will have the same version?
> > > 
> > > --Samuel
> > > 
> > > On Thu, 5 Feb 2004, Michael Tuexen wrote:
> > > 
> > > > Brian,
> > > > 
> > > > you disagree with the change? This means you want to have an
> > > > error ONLY returned for ASP-Up messages as the RFC states?
> > > > 
> > > > I'm suggesting a change that it is returned for all messages.
> > > > 
> > > > Best regards
> > > > Michael
> > > > 
> > > > 
> > > > On Feb 5, 2004, at 12:33 PM, Brian F. G. Bidulock wrote:
> > > > 
> > > > > Michael,
> > > > >
> > > > > I missed that.  And, therefore, disagree with the change. 
> > >  An error
> > > > > must be returned for any message with an unsupported 
> > version, not
> > > > > just ASP Up, as the RFC already states.  The example case was in
> > > > > my last mail.
> > > > >
> > > > > --brian
> > > > >
> > > > > Michael Tuexen wrote:                                     
> > >              
> > > > >             (Thu, 05 Feb 2004 12:24:07)
> > > > >> Brian,
> > > > >>
> > > > >> part of my suggestion is to replace:
> > > > >>
> > > > >>      If an ASP Up message with an unsupported version is 
> > > received, the
> > > > >>
> > > > >> with
> > > > >>
> > > > >>      If a message with an unsupported version is received, the
> > > > >>
> > > > >> At least for me, this does change the requested behaviour.
> > > > >>
> > > > >> Best regards
> > > > >> Michael
> > > > >>
> > > > >> On Feb 5, 2004, at 11:30 AM, Brian F. G. Bidulock wrote:
> > > > >>
> > > > >>> Michael,
> > > > >>>
> > > > >>> I don't think that your proposed text takes us any 
> > > farther towards
> > > > >>> that goal.  You have changed "assumed that" to 
> > "likely that the
> > > > >>> message having an unsupported version is an ASP Up message and
> > > > >>> therefore [likely] that".
> > > > >>>
> > > > >>> This is just description.  The requirement is (unchanged):
> > > > >>>
> > > > >>>> If a message with an unsupported version is received, the
> > > > >>>> receiving end responds with an Error message, 
> > > indicating the version
> > > > >>>> the receiving node supports and notifies Layer Management.
> > > > >>>
> > > > >>> This is obviously any message.
> > > > >>>
> > > > >>> As there is no change to the requirement, the new text is 
> > > > >>> superfluous.
> > > > >>>
> > > > >>> Regardless of likelihoods or assumptions, the Error message is
> > > > >>> returned to any message received with an unsupported 
> > > version and 
> > > > >>> Layer
> > > > >>> Management is notified.  Suggesting that it is likely 
> > > that an ASP Up
> > > > >>> is the cause, actually distracts from the requirement 
> > > to return the
> > > > >>> error to any message.
> > > > >>>
> > > > >>> A node might actually send message Foo with Version=100 
> > > to test a
> > > > >>> remote node's support for message Foo (only available 
> > > in Version=100)
> > > > >>> while performing the ASP Up and ASP Active procedures using 
> > > > >>> Version=1.
> > > > >>> This requirement provides that message Foo will be 
> > > retured with an
> > > > >>> "usupported version" if version 100 is not supported 
> > > (and obviously
> > > > >>> the message Foo is not supported).
> > > > >>>
> > > > >>> It would be better to strike the line starting with 
> > "Because", 
> > > > >>> because
> > > > >>> it was superfluous to begin with.  Changing assumptions to 
> > > > >>> likelihoods
> > > > >>> does not increase its pertinence.
> > > > >>>
> > > > >>> --brian
> > > > >>>
> > > > >>>
> > > > >>> Michael Tuexen wrote:
> > > > >>>             (Thu, 05 Feb 2004 10:17:40)
> > > > >>>> Brian,
> > > > >>>>
> > > > >>>> I agree with you that there are a lot of places which are not
> > > > >>>> very precisely (this is the same with other RFCs) but this
> > > > >>>> question came up multiple times. Others not. That is why I'm
> > > > >>>> asking to clarify this.
> > > > >>>>
> > > > >>>> I know about customers and testers who test exactly this and
> > > > >>>> always ask: what is the correct behaviour. So what is the
> > > > >>>> problem in making this clear? Think about having different
> > > > >>>> customers requesting different implementations?
> > > > >>>>
> > > > >>>> Best regards
> > > > >>>> Michael
> > > > >>>>
> > > > >>>> On Feb 4, 2004, at 11:46 PM, Brian F. G. Bidulock wrote:
> > > > >>>>
> > > > >>>>> Michael,
> > > > >>>>>
> > > > >>>>> I think you need to read the RFC from the viewpoint of a
> > > > >>>>> specification
> > > > >>>>> instead of the viewpoint of an implementation.  When it says
> > > > >>>>> "assumed"
> > > > >>>>> it means "assumed [by the authors in the 
> > specification of the
> > > > >>>>> protocol]"
> > > > >>>>> and not "assumed [by the implementation]".
> > > > >>>>>
> > > > >>>>> There are many place in the RFC where this is the 
> > > case, because of
> > > > >>>>> the
> > > > >>>>> editors' preference for words like "assumed".  If we 
> > > are to correct
> > > > >>>>> the lazy
> > > > >>>>> English in the document, it would require an 
> > > extensive rewrite.
> > > > >>>>>
> > > > >>>>> --brian
> > > > >>>>>
> > > > >>>>> Michael Tuexen wrote:
> > > > >>>>>             (Wed, 04 Feb 2004 21:56:43)
> > > > >>>>>> Dear all,
> > > > >>>>>>
> > > > >>>>>> the RFC describes that an M3UA endpoint should check 
> > > the version
> > > > >>>>>> field
> > > > >>>>>> for ASP Up messages and leaves it unspecified how 
> > > other messages
> > > > >>>>>> should
> > > > >>>>>> be handled.
> > > > >>>>>>
> > > > >>>>>> In real scenarios the first message having an 
> > > unsupported message 
> > > > >>>>>> is
> > > > >>>>>> most likely an ASP-Up message, but my experience is, 
> > > that people
> > > > >>>>>> testing
> > > > >>>>>> implementations always ask how these other 
> > messages should be
> > > > >>>>>> handled.
> > > > >>>>>>
> > > > >>>>>> Therefore I would like to suggest a clarification 
> > in the IG 
> > > > >>>>>> clearly
> > > > >>>>>> stating how these other messages with an 
> > unsupported version 
> > > > >>>>>> should
> > > > >>>>>> be handled.
> > > > >>>>>>
> > > > >>>>>> We can specify that it is checked for all messages 
> > > or only for
> > > > >>>>>> ASP-Up
> > > > >>>>>> messages, ignoring the version field for non 
> > ASP-Up messages.
> > > > >>>>>>
> > > > >>>>>> The easiest solution seems to be (for me) to check 
> > > the field for
> > > > >>>>>> all messages. So you could write
> > > > >>>>>>
> > > > >>>>>> if (message->version != 1)
> > > > >>>>>>    send(error)
> > > > >>>>>>
> > > > >>>>>> instead of
> > > > >>>>>>
> > > > >>>>>> if ((message->class == 3) && (message->type == 1) &&
> > > > >>>>>> (message->(message->version != 1))
> > > > >>>>>>    send(error)
> > > > >>>>>>
> > > > >>>>>> Therefore I suggest to include the following text 
> > in the IG.
> > > > >>>>>>
> > > > >>>>>> Best regards
> > > > >>>>>> Michael
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> <---- SNIP
> > > > >>>>>> 3.28 Version Control
> > > > >>>>>>
> > > > >>>>>> 3.28.1 Description of the problem
> > > > >>>>>>
> > > > >>>>>> The RFC describes how ASP Up messages with an 
> > > unsupported version
> > > > >>>>>> are handled but leaves it unspecified how other 
> > > messages should be
> > > > >>>>>> handled if the version number is not supported.
> > > > >>>>>>
> > > > >>>>>> 3.28.2 Text changes to the document
> > > > >>>>>>     ---------
> > > > >>>>>>     Old text: (Section 4.3.4.1.1)
> > > > >>>>>>     ---------
> > > > >>>>>>
> > > > >>>>>> 4.3.4.1.1 M3UA Version Control
> > > > >>>>>>
> > > > >>>>>>     If an ASP Up message with an unsupported version 
> > > is received,
> > > > >>>>>> the
> > > > >>>>>>     receiving end responds with an Error message, 
> > > indicating the
> > > > >>>>>> version
> > > > >>>>>>     the receiving node supports and notifies Layer 
> > > Management.
> > > > >>>>>>
> > > > >>>>>>     This is useful when protocol version upgrades are being
> > > > >>>>>> performed
> > > > >>>>>> in
> > > > >>>>>>     a network.  A node upgraded to a newer version 
> > > should support
> > > > >>>>>> the
> > > > >>>>>>     older versions used on other nodes it is 
> > > communicating with.
> > > > >>>>>> Because
> > > > >>>>>>     ASPs initiate the ASP Up procedure it is assumed 
> > > that the 
> > > > >>>>>> Error
> > > > >>>>>>     message would normally come from the SGP.
> > > > >>>>>>
> > > > >>>>>>     ---------
> > > > >>>>>>     New text: (Section 4.3.4.1.1)
> > > > >>>>>>     ---------
> > > > >>>>>>
> > > > >>>>>> 4.3.4.1.1 M3UA Version Control
> > > > >>>>>>
> > > > >>>>>>     If a message with an unsupported version is 
> > received, the
> > > > >>>>>>     receiving end responds with an Error message, 
> > > indicating the
> > > > >>>>>> version
> > > > >>>>>>     the receiving node supports and notifies Layer 
> > > Management.
> > > > >>>>>>
> > > > >>>>>>     This is useful when protocol version upgrades are being
> > > > >>>>>> performed
> > > > >>>>>> in
> > > > >>>>>>     a network.  A node upgraded to a newer version 
> > > should support
> > > > >>>>>> the
> > > > >>>>>>     older versions used on other nodes it is 
> > > communicating with.
> > > > >>>>>> Because
> > > > >>>>>>     ASPs initiate the ASP Up procedure it is 
> > likely that the 
> > > > >>>>>> message
> > > > >>>>>> having
> > > > >>>>>>     an unsupported version is an ASP Up message and 
> > > therefore that
> > > > >>>>>> the
> > > > >>>>>> Error
> > > > >>>>>>     message would normally come from the SGP.
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> 3.28.3 Solution description
> > > > >>>>>>
> > > > >>>>>> The new text clearly describes that the version 
> > > should be checked
> > > > >>>>>> for
> > > > >>>>>> all
> > > > >>>>>> messages.
> > > > >>>>>> <---- SNIP
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> _______________________________________________
> > > > >>>>>> Sigtran mailing list
> > > > >>>>>> Sigtran@ietf.org
> > > > >>>>>> https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >>>>>
> > > > >>>>> -- 
> > > > >>>>> Brian F. G. Bidulock
> > > > >>>>> bidulock@openss7.org
> > > > >>>>> http://www.openss7.org/
> > > > >>>>>
> > > > >>>
> > > > >>> -- 
> > > > >>> Brian F. G. Bidulock
> > > > >>> bidulock@openss7.org
> > > > >>> http://www.openss7.org/
> > > > >>>
> > > > >
> > > > > -- 
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > > > >
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > 
> > > 
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> > 
> > This communication is confidential and intended solely for 
> > the addressee(s). Any unauthorized review, use, disclosure or 
> > distribution is prohibited. If you believe this message has 
> > been sent to you in error, please notify the sender by 
> > replying to this transmission and delete the message without 
> > disclosing it. Thank you.
> > 
> > E-mail including attachments is susceptible to data 
> > corruption, interruption, unauthorized amendment, tampering 
> > and viruses, and we only send and receive e-mails on the 
> > basis that we are not liable for any such corruption, 
> > interception, amendment, tampering or viruses or any 
> > consequences thereof.
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> 
> This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.
> 
> E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.

-- 
Brian 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 Feb  5 10:31: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 KAA19805
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 10:31:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AolT7-00036X-Th
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 10:31:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15FV54i011924
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 10:31:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AolT5-00035z-Rs; Thu, 05 Feb 2004 10:31:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AolT1-00034f-NU
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 10:30:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19751
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 10:30:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AolSz-0002un-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 10:30:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AolS0-0002pe-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 10:29:57 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[9wtFiWlt6eE5awcf3VcCxktLkTPha9Ia])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AolR3-0002k5-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 10:28:57 -0500
Received: from ns.pigworks.openss7.net (IDENT:fLRBE5Mh83H8iuYAonzgnKIAXDT4JH50@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i15FSuI09350;
	Thu, 5 Feb 2004 08:28:56 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i15FSuC17203;
	Thu, 5 Feb 2004 08:28:56 -0700
Date: Thu, 5 Feb 2004 08:28:56 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry Nagelberg <barryn@adax.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
Message-ID: <20040205082856.B17025@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry Nagelberg <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <JBECLENKLBCKAAKFGAJOGEEICEAA.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: <JBECLENKLBCKAAKFGAJOGEEICEAA.barryn@adax.com>; from barryn@adax.com on Thu, Feb 05, 2004 at 09:13:04AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Barry,

In Q.711, for N-UNITDATA Request it is marked as a "User Option" and not as
"Optional".  See also Q.711/6.2.2.2.2.  (If the SCCP user does not provide
a sequence control parameter, then the SCCP assumes protocol class 0.)
Also note that there is no "Protocol Class" argument to N-UNITDATA Request.

Rather than have to handle the case where Sequence Control was missing for
protocol class 1, SUA specifies the Protocol Class in CLDT and when the
protocol class is zero (0), sequence control is set to (0) as described in the
the Implementation note in SUA/3.2.1.

CLDT __corresponds__ to N-UNITDATA Req/Ind.  It is not exact.  One of the
reasons for differences is the multiple SG as STP case.

--brian


Barry Nagelberg wrote:                                                               (Thu, 05 Feb 2004 09:13:04)
> Table 10/Q.711 notes that the sequence control parameter is optional in the
> SCCP UNITDATA msg.
> However the sequence control parameter is listed as mandatory in the SUA
> CLDT msg.
> So I have 2 questions:
> 
> 1. Why do we have this mandatory/optional mismatch?
> 
> 2. If sequence control is not present in a SCCP UNITDATA msg, what should be
> the value of the mandatory sequence control param in the CLDT msg.
> 
> 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 Feb  5 10:57:28 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 KAA20691
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 10:57:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AolsD-0005NG-Qe
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 10:57:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15Fv15Y020652
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 10:57:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AolsD-0005Mm-1t; Thu, 05 Feb 2004 10:57:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AolrH-00051l-Vk
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 10:56:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20554
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 10:56:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AolrF-0005FJ-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 10:56:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AolqG-000583-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 10:55:00 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AolpM-00051D-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 10:54:05 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i15Fs47T010991
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 10:54:04 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] SUA v16: sequence control parameter in CLDT msg
Date: Thu, 5 Feb 2004 10:55:34 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOGEEJCEAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <20040205082856.B17025@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
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Brian,

Thanks, but I can't find the "Implementation note in SUA/3.2.1" to which you
refer.

Barry

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Thursday, February 05, 2004 10:29 AM
> To: Barry Nagelberg
> Cc: SIGTRAN Mailing List
> Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
>
>
> Barry,
>
> In Q.711, for N-UNITDATA Request it is marked as a "User Option"
> and not as
> "Optional".  See also Q.711/6.2.2.2.2.  (If the SCCP user does not provide
> a sequence control parameter, then the SCCP assumes protocol class 0.)
> Also note that there is no "Protocol Class" argument to
> N-UNITDATA Request.
>
> Rather than have to handle the case where Sequence Control was missing for
> protocol class 1, SUA specifies the Protocol Class in CLDT and when the
> protocol class is zero (0), sequence control is set to (0) as
> described in the
> the Implementation note in SUA/3.2.1.
>
> CLDT __corresponds__ to N-UNITDATA Req/Ind.  It is not exact.  One of the
> reasons for differences is the multiple SG as STP case.
>
> --brian
>
>
> Barry Nagelberg wrote:
>                    (Thu, 05 Feb 2004 09:13:04)
> > Table 10/Q.711 notes that the sequence control parameter is
> optional in the
> > SCCP UNITDATA msg.
> > However the sequence control parameter is listed as mandatory in the SUA
> > CLDT msg.
> > So I have 2 questions:
> >
> > 1. Why do we have this mandatory/optional mismatch?
> >
> > 2. If sequence control is not present in a SCCP UNITDATA msg,
> what should be
> > the value of the mandatory sequence control param in the CLDT msg.
> >
> > Barry Nagelberg


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



From exim@www1.ietf.org  Thu Feb  5 12:06: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 MAA24411
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 12:06:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aomx2-0006h4-EI
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 12:06:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15H6435025725
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 12:06:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aomx1-0006gd-6C; Thu, 05 Feb 2004 12:06:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AomwI-0006fJ-6w
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 12:05:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24351
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 12:05:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AomwG-0005Cx-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 12:05:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AomvX-00052d-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 12:04:32 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[6RpA8gnFIzByKoJqwpLEwq4pjHxdYRuj])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aomu9-0004ip-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 12:03:05 -0500
Received: from ns.pigworks.openss7.net (IDENT:gNuBwMulZJtfrQ4bCWbaTiYsZxWB+aRb@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i15H34I11107;
	Thu, 5 Feb 2004 10:03:04 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i15H34E18792;
	Thu, 5 Feb 2004 10:03:04 -0700
Date: Thu, 5 Feb 2004 10:03:04 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry Nagelberg <barryn@adax.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
Message-ID: <20040205100304.A18523@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry Nagelberg <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <20040205082856.B17025@openss7.org> <JBECLENKLBCKAAKFGAJOGEEJCEAA.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: <JBECLENKLBCKAAKFGAJOGEEJCEAA.barryn@adax.com>; from barryn@adax.com on Thu, Feb 05, 2004 at 10:55:34AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Barry,

SUA-15, page 24:

"  Implementation note: This message covers the following SCCP 
"  messages: unitdata (UDT), extended unitdata (XUDT), long unitdata 
"  (LUDT). Sequence Control is set to 0 for class 0 messages. 

--brian

Barry Nagelberg wrote:                                                               (Thu, 05 Feb 2004 10:55:34)
> Brian,
> 
> Thanks, but I can't find the "Implementation note in SUA/3.2.1" to which you
> refer.
> 
> Barry
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Thursday, February 05, 2004 10:29 AM
> > To: Barry Nagelberg
> > Cc: SIGTRAN Mailing List
> > Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
> >
> >
> > Barry,
> >
> > In Q.711, for N-UNITDATA Request it is marked as a "User Option"
> > and not as
> > "Optional".  See also Q.711/6.2.2.2.2.  (If the SCCP user does not provide
> > a sequence control parameter, then the SCCP assumes protocol class 0.)
> > Also note that there is no "Protocol Class" argument to
> > N-UNITDATA Request.
> >
> > Rather than have to handle the case where Sequence Control was missing for
> > protocol class 1, SUA specifies the Protocol Class in CLDT and when the
> > protocol class is zero (0), sequence control is set to (0) as
> > described in the
> > the Implementation note in SUA/3.2.1.
> >
> > CLDT __corresponds__ to N-UNITDATA Req/Ind.  It is not exact.  One of the
> > reasons for differences is the multiple SG as STP case.
> >
> > --brian
> >
> >
> > Barry Nagelberg wrote:
> >                    (Thu, 05 Feb 2004 09:13:04)
> > > Table 10/Q.711 notes that the sequence control parameter is
> > optional in the
> > > SCCP UNITDATA msg.
> > > However the sequence control parameter is listed as mandatory in the SUA
> > > CLDT msg.
> > > So I have 2 questions:
> > >
> > > 1. Why do we have this mandatory/optional mismatch?
> > >
> > > 2. If sequence control is not present in a SCCP UNITDATA msg,
> > what should be
> > > the value of the mandatory sequence control param in the CLDT msg.
> > >
> > > 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 Feb  5 12:35: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 MAA25274
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 12:35:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AonP6-0000Lm-UL
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 12:35:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15HZ42R001345
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 12:35:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AonP5-0000LV-K1; Thu, 05 Feb 2004 12:35:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AonOA-0000Ho-Bl
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 12:34:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25227
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 12:34:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AonO8-00007i-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 12:34:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AonNH-00001q-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 12:33:11 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[lyT90gzPlFlVZ47fcwwElJgw/BAHNrrV])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AonMY-0007k0-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 12:32:26 -0500
Received: from ns.pigworks.openss7.net (IDENT:eicRsV++Tky9+d/C1fUjbezpjOvvk45W@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i15HWKI11471;
	Thu, 5 Feb 2004 10:32:20 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i15HWJq19163;
	Thu, 5 Feb 2004 10:32:19 -0700
Date: Thu, 5 Feb 2004 10:32:19 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry Nagelberg <barryn@adax.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
Message-ID: <20040205103219.A18993@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry Nagelberg <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <20040205082856.B17025@openss7.org> <JBECLENKLBCKAAKFGAJOGEEJCEAA.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: <JBECLENKLBCKAAKFGAJOGEEJCEAA.barryn@adax.com>; from barryn@adax.com on Thu, Feb 05, 2004 at 10:55:34AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Barry,

It was struct from sua-16 at my request:

>     Implementation note: This message covers the following SCCP 
>     messages: unitdata (UDT), extended unitdata (XUDT), long unitdata 
> -   (LUDT). 
> +   (LUDT). Sequence Control is set to 0 for class 0 messages. 
> 
> This change is incorrect.  Please remove this addition.  We discussed this
> long ago and Sequence Control is required in class 0 messages for some
> network configurations and for proper MTP relay accross a relay point.  It
> might not be provided by the SCCP/SUA-User for class 0, but then the SUA
> layer (at ASP, IPSP or SGP) must ultimately select a loadsharing value.
> That is why we made the parameter MANDATORY for all protocol classes.

--brian

Barry Nagelberg wrote:                                                               (Thu, 05 Feb 2004 10:55:34)
> Brian,
> 
> Thanks, but I can't find the "Implementation note in SUA/3.2.1" to which you
> refer.
> 
> Barry
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Thursday, February 05, 2004 10:29 AM
> > To: Barry Nagelberg
> > Cc: SIGTRAN Mailing List
> > Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
> >
> >
> > Barry,
> >
> > In Q.711, for N-UNITDATA Request it is marked as a "User Option"
> > and not as
> > "Optional".  See also Q.711/6.2.2.2.2.  (If the SCCP user does not provide
> > a sequence control parameter, then the SCCP assumes protocol class 0.)
> > Also note that there is no "Protocol Class" argument to
> > N-UNITDATA Request.
> >
> > Rather than have to handle the case where Sequence Control was missing for
> > protocol class 1, SUA specifies the Protocol Class in CLDT and when the
> > protocol class is zero (0), sequence control is set to (0) as
> > described in the
> > the Implementation note in SUA/3.2.1.
> >
> > CLDT __corresponds__ to N-UNITDATA Req/Ind.  It is not exact.  One of the
> > reasons for differences is the multiple SG as STP case.
> >
> > --brian
> >
> >
> > Barry Nagelberg wrote:
> >                    (Thu, 05 Feb 2004 09:13:04)
> > > Table 10/Q.711 notes that the sequence control parameter is
> > optional in the
> > > SCCP UNITDATA msg.
> > > However the sequence control parameter is listed as mandatory in the SUA
> > > CLDT msg.
> > > So I have 2 questions:
> > >
> > > 1. Why do we have this mandatory/optional mismatch?
> > >
> > > 2. If sequence control is not present in a SCCP UNITDATA msg,
> > what should be
> > > the value of the mandatory sequence control param in the CLDT msg.
> > >
> > > 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 Feb  5 12:42:28 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 MAA25478
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 12:42:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AonVp-00016A-ER
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 12:42:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15Hg1Sf004216
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 12:42:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AonVo-00015p-UN; Thu, 05 Feb 2004 12:42:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AonUt-00013j-W3
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 12:41:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25441
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 12:41:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AonUs-0000l4-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 12:41:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AonTv-0000ft-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 12:40:04 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AonT8-0000aM-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 12:39:14 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i15HdB7T011469
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 12:39:11 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] SUA v16: sequence control parameter in CLDT msg
Date: Thu, 5 Feb 2004 12:40:41 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOAEEMCEAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <20040205100304.A18523@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
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

The last sentence ("Sequence Control is set to 0 for class 0 messages"), in
the implementation note that Brian mentions below, was removed in v16. Does
anyone know why?

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Thursday, February 05, 2004 12:03 PM
> To: Barry Nagelberg
> Cc: SIGTRAN Mailing List
> Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
>
>
> Barry,
>
> SUA-15, page 24:
>
> "  Implementation note: This message covers the following SCCP
> "  messages: unitdata (UDT), extended unitdata (XUDT), long unitdata
> "  (LUDT). Sequence Control is set to 0 for class 0 messages.
>
> --brian
>
> Barry Nagelberg wrote:
>                    (Thu, 05 Feb 2004 10:55:34)
> > Brian,
> >
> > Thanks, but I can't find the "Implementation note in SUA/3.2.1"
> to which you
> > refer.
> >
> > Barry
> >
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: Thursday, February 05, 2004 10:29 AM
> > > To: Barry Nagelberg
> > > Cc: SIGTRAN Mailing List
> > > Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
> > >
> > >
> > > Barry,
> > >
> > > In Q.711, for N-UNITDATA Request it is marked as a "User Option"
> > > and not as
> > > "Optional".  See also Q.711/6.2.2.2.2.  (If the SCCP user
> does not provide
> > > a sequence control parameter, then the SCCP assumes protocol class 0.)
> > > Also note that there is no "Protocol Class" argument to
> > > N-UNITDATA Request.
> > >
> > > Rather than have to handle the case where Sequence Control
> was missing for
> > > protocol class 1, SUA specifies the Protocol Class in CLDT
> and when the
> > > protocol class is zero (0), sequence control is set to (0) as
> > > described in the
> > > the Implementation note in SUA/3.2.1.
> > >
> > > CLDT __corresponds__ to N-UNITDATA Req/Ind.  It is not exact.
>  One of the
> > > reasons for differences is the multiple SG as STP case.
> > >
> > > --brian
> > >
> > >
> > > Barry Nagelberg wrote:
> > >                    (Thu, 05 Feb 2004 09:13:04)
> > > > Table 10/Q.711 notes that the sequence control parameter is
> > > optional in the
> > > > SCCP UNITDATA msg.
> > > > However the sequence control parameter is listed as
> mandatory in the SUA
> > > > CLDT msg.
> > > > So I have 2 questions:
> > > >
> > > > 1. Why do we have this mandatory/optional mismatch?
> > > >
> > > > 2. If sequence control is not present in a SCCP UNITDATA msg,
> > > what should be
> > > > the value of the mandatory sequence control param in the CLDT msg.
> > > >
> > > > Barry Nagelberg


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



From exim@www1.ietf.org  Thu Feb  5 12:48:28 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 MAA25635
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 12:48:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aonbd-0001sU-HA
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 12:48:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15Hm1kW007193
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 12:48:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aonbd-0001rn-4V; Thu, 05 Feb 2004 12:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aonaj-0001oO-Mc
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 12:47:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25604
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 12:47:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aonah-0001G8-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 12:47:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AonZo-0001Bd-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 12:46:09 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AonZB-00016d-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 12:45:30 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i15HjT7T011497
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 12:45:30 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] SUA v16: sequence control parameter in CLDT msg
Date: Thu, 5 Feb 2004 12:46:59 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOGEEMCEAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <20040205103219.A18993@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
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Brian,

OK, at least we know how the note got removed from the draft. But I don't
understand the link between loadsharing and the sequence control value. So I
repeat my question:

If the optional sequence control param is not present in an SCCP UNITDATA
indication, what should be the value of the mandatory sequence control param
in the CLDT msg?

Barry

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Thursday, February 05, 2004 12:32 PM
> To: Barry Nagelberg
> Cc: SIGTRAN Mailing List
> Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
>
>
> Barry,
>
> It was struct from sua-16 at my request:
>
> >     Implementation note: This message covers the following SCCP
> >     messages: unitdata (UDT), extended unitdata (XUDT), long unitdata
> > -   (LUDT).
> > +   (LUDT). Sequence Control is set to 0 for class 0 messages.
> >
> > This change is incorrect.  Please remove this addition.  We
> discussed this
> > long ago and Sequence Control is required in class 0 messages for some
> > network configurations and for proper MTP relay accross a relay
> point.  It
> > might not be provided by the SCCP/SUA-User for class 0, but then the SUA
> > layer (at ASP, IPSP or SGP) must ultimately select a loadsharing value.
> > That is why we made the parameter MANDATORY for all protocol classes.
>
> --brian
>
> Barry Nagelberg wrote:
>                    (Thu, 05 Feb 2004 10:55:34)
> > Brian,
> >
> > Thanks, but I can't find the "Implementation note in SUA/3.2.1"
> to which you
> > refer.
> >
> > Barry
> >
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: Thursday, February 05, 2004 10:29 AM
> > > To: Barry Nagelberg
> > > Cc: SIGTRAN Mailing List
> > > Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
> > >
> > >
> > > Barry,
> > >
> > > In Q.711, for N-UNITDATA Request it is marked as a "User Option"
> > > and not as
> > > "Optional".  See also Q.711/6.2.2.2.2.  (If the SCCP user
> does not provide
> > > a sequence control parameter, then the SCCP assumes protocol class 0.)
> > > Also note that there is no "Protocol Class" argument to
> > > N-UNITDATA Request.
> > >
> > > Rather than have to handle the case where Sequence Control
> was missing for
> > > protocol class 1, SUA specifies the Protocol Class in CLDT
> and when the
> > > protocol class is zero (0), sequence control is set to (0) as
> > > described in the
> > > the Implementation note in SUA/3.2.1.
> > >
> > > CLDT __corresponds__ to N-UNITDATA Req/Ind.  It is not exact.
>  One of the
> > > reasons for differences is the multiple SG as STP case.
> > >
> > > --brian
> > >
> > >
> > > Barry Nagelberg wrote:
> > >                    (Thu, 05 Feb 2004 09:13:04)
> > > > Table 10/Q.711 notes that the sequence control parameter is
> > > optional in the
> > > > SCCP UNITDATA msg.
> > > > However the sequence control parameter is listed as
> mandatory in the SUA
> > > > CLDT msg.
> > > > So I have 2 questions:
> > > >
> > > > 1. Why do we have this mandatory/optional mismatch?
> > > >
> > > > 2. If sequence control is not present in a SCCP UNITDATA msg,
> > > what should be
> > > > the value of the mandatory sequence control param in the CLDT msg.
> > > >
> > > > 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 Feb  5 13:26:31 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 NAA27209
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 13:26:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AooCT-0004H8-1X
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 13:26:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15IQ4p4016413
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 13:26:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AooCQ-0004G0-IX; Thu, 05 Feb 2004 13:26:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AooBZ-0004Bz-2i
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 13:25:09 -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 NAA27163
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 13:25:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AooBX-00058V-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 13:25:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AooAa-00052n-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 13:24:09 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[3NiSMtI+2l+hxuwN5z6iTWKhUkxweicH])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aoo9o-0004xr-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 13:23:20 -0500
Received: from ns.pigworks.openss7.net (IDENT:rcTQaQqCawK4VUp/nH/ItIpC5Qsx8qoa@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i15INJI12280;
	Thu, 5 Feb 2004 11:23:19 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i15INJQ19810;
	Thu, 5 Feb 2004 11:23:19 -0700
Date: Thu, 5 Feb 2004 11:23:18 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry Nagelberg <barryn@adax.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
Message-ID: <20040205112318.B18993@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry Nagelberg <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <20040205103219.A18993@openss7.org> <JBECLENKLBCKAAKFGAJOGEEMCEAA.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: <JBECLENKLBCKAAKFGAJOGEEMCEAA.barryn@adax.com>; from barryn@adax.com on Thu, Feb 05, 2004 at 12:46:59PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Barry,

For the link between loadsharing and sequence control, see Q.711/6.2.2.2.2.

When multiple SG are acting as STP, each must choose the same SLS for
Class 1 operation.  Thus the ASP must provide the sequence control value
which the SG may use to derive the SLS.

--brian

Barry Nagelberg wrote:                                                               (Thu, 05 Feb 2004 12:46:59)
> Brian,
> 
> OK, at least we know how the note got removed from the draft. But I don't
> understand the link between loadsharing and the sequence control value. So I
> repeat my question:
> 
> If the optional sequence control param is not present in an SCCP UNITDATA
> indication, what should be the value of the mandatory sequence control param
> in the CLDT msg?
> 
> Barry
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Thursday, February 05, 2004 12:32 PM
> > To: Barry Nagelberg
> > Cc: SIGTRAN Mailing List
> > Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
> >
> >
> > Barry,
> >
> > It was struct from sua-16 at my request:
> >
> > >     Implementation note: This message covers the following SCCP
> > >     messages: unitdata (UDT), extended unitdata (XUDT), long unitdata
> > > -   (LUDT).
> > > +   (LUDT). Sequence Control is set to 0 for class 0 messages.
> > >
> > > This change is incorrect.  Please remove this addition.  We
> > discussed this
> > > long ago and Sequence Control is required in class 0 messages for some
> > > network configurations and for proper MTP relay accross a relay
> > point.  It
> > > might not be provided by the SCCP/SUA-User for class 0, but then the SUA
> > > layer (at ASP, IPSP or SGP) must ultimately select a loadsharing value.
> > > That is why we made the parameter MANDATORY for all protocol classes.
> >
> > --brian
> >
> > Barry Nagelberg wrote:
> >                    (Thu, 05 Feb 2004 10:55:34)
> > > Brian,
> > >
> > > Thanks, but I can't find the "Implementation note in SUA/3.2.1"
> > to which you
> > > refer.
> > >
> > > Barry
> > >
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: Thursday, February 05, 2004 10:29 AM
> > > > To: Barry Nagelberg
> > > > Cc: SIGTRAN Mailing List
> > > > Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
> > > >
> > > >
> > > > Barry,
> > > >
> > > > In Q.711, for N-UNITDATA Request it is marked as a "User Option"
> > > > and not as
> > > > "Optional".  See also Q.711/6.2.2.2.2.  (If the SCCP user
> > does not provide
> > > > a sequence control parameter, then the SCCP assumes protocol class 0.)
> > > > Also note that there is no "Protocol Class" argument to
> > > > N-UNITDATA Request.
> > > >
> > > > Rather than have to handle the case where Sequence Control
> > was missing for
> > > > protocol class 1, SUA specifies the Protocol Class in CLDT
> > and when the
> > > > protocol class is zero (0), sequence control is set to (0) as
> > > > described in the
> > > > the Implementation note in SUA/3.2.1.
> > > >
> > > > CLDT __corresponds__ to N-UNITDATA Req/Ind.  It is not exact.
> >  One of the
> > > > reasons for differences is the multiple SG as STP case.
> > > >
> > > > --brian
> > > >
> > > >

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

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



From exim@www1.ietf.org  Thu Feb  5 13:35:31 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 NAA27789
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 13:35:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AooL9-0004v8-66
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 13:35:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15IZ3N9018911
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 13:35:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AooL7-0004uZ-Jp; Thu, 05 Feb 2004 13:35:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AooKR-0004s1-QL
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 13:34:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27771
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 13:34:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AooKP-0006VM-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 13:34:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AooJG-0006Qs-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 13:33:07 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AooJ0-0006MD-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 13:32:50 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i15IWo7T011703
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 13:32:50 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] SUA v16: sequence control parameter in CLDT msg
Date: Thu, 5 Feb 2004 13:34:19 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOGEEOCEAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <20040205112318.B18993@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
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Brian,

I cannot follow your logic. Please just answer my question:

If the optional sequence control param is not present in an SCCP UNITDATA
indication, what should be the value of the mandatory sequence control param
in the CLDT msg?

Barry

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Thursday, February 05, 2004 1:23 PM
> To: Barry Nagelberg
> Cc: SIGTRAN Mailing List
> Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
>
>
> Barry,
>
> For the link between loadsharing and sequence control, see
> Q.711/6.2.2.2.2.
>
> When multiple SG are acting as STP, each must choose the same SLS for
> Class 1 operation.  Thus the ASP must provide the sequence control value
> which the SG may use to derive the SLS.
>
> --brian
>
> Barry Nagelberg wrote:
>                    (Thu, 05 Feb 2004 12:46:59)
> > Brian,
> >
> > OK, at least we know how the note got removed from the draft.
> But I don't
> > understand the link between loadsharing and the sequence
> control value. So I
> > repeat my question:
> >
> > If the optional sequence control param is not present in an
> SCCP UNITDATA
> > indication, what should be the value of the mandatory sequence
> control param
> > in the CLDT msg?
> >
> > Barry
> >
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: Thursday, February 05, 2004 12:32 PM
> > > To: Barry Nagelberg
> > > Cc: SIGTRAN Mailing List
> > > Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
> > >
> > >
> > > Barry,
> > >
> > > It was struct from sua-16 at my request:
> > >
> > > >     Implementation note: This message covers the following SCCP
> > > >     messages: unitdata (UDT), extended unitdata (XUDT),
> long unitdata
> > > > -   (LUDT).
> > > > +   (LUDT). Sequence Control is set to 0 for class 0 messages.
> > > >
> > > > This change is incorrect.  Please remove this addition.  We
> > > discussed this
> > > > long ago and Sequence Control is required in class 0
> messages for some
> > > > network configurations and for proper MTP relay accross a relay
> > > point.  It
> > > > might not be provided by the SCCP/SUA-User for class 0, but
> then the SUA
> > > > layer (at ASP, IPSP or SGP) must ultimately select a
> loadsharing value.
> > > > That is why we made the parameter MANDATORY for all
> protocol classes.
> > >
> > > --brian
> > >
> > > Barry Nagelberg wrote:
> > >                    (Thu, 05 Feb 2004 10:55:34)
> > > > Brian,
> > > >
> > > > Thanks, but I can't find the "Implementation note in SUA/3.2.1"
> > > to which you
> > > > refer.
> > > >
> > > > Barry
> > > >
> > > > > -----Original Message-----
> > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > Sent: Thursday, February 05, 2004 10:29 AM
> > > > > To: Barry Nagelberg
> > > > > Cc: SIGTRAN Mailing List
> > > > > Subject: Re: [Sigtran] SUA v16: sequence control
> parameter in CLDT msg
> > > > >
> > > > >
> > > > > Barry,
> > > > >
> > > > > In Q.711, for N-UNITDATA Request it is marked as a "User Option"
> > > > > and not as
> > > > > "Optional".  See also Q.711/6.2.2.2.2.  (If the SCCP user
> > > does not provide
> > > > > a sequence control parameter, then the SCCP assumes
> protocol class 0.)
> > > > > Also note that there is no "Protocol Class" argument to
> > > > > N-UNITDATA Request.
> > > > >
> > > > > Rather than have to handle the case where Sequence Control
> > > was missing for
> > > > > protocol class 1, SUA specifies the Protocol Class in CLDT
> > > and when the
> > > > > protocol class is zero (0), sequence control is set to (0) as
> > > > > described in the
> > > > > the Implementation note in SUA/3.2.1.
> > > > >
> > > > > CLDT __corresponds__ to N-UNITDATA Req/Ind.  It is not exact.
> > >  One of the
> > > > > reasons for differences is the multiple SG as STP case.
> > > > >
> > > > > --brian
> > > > >
> > > > >
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


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



From exim@www1.ietf.org  Thu Feb  5 14:23: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 OAA00231
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 14:23:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aop5Y-0008ME-Vs
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 14:23:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15JN0dC032105
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 14:23:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aop5Y-0008Le-8f; Thu, 05 Feb 2004 14:23:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aop5B-0008L8-5O
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 14:22:37 -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 OAA00154
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 14:22:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aop58-0003gO-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 14:22:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aop4K-0003ZF-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 14:21:45 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[yVHD9yHoS4vd3wkMkNTYqH5dd9FaWDc2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aop3N-0003Qo-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 14:20:45 -0500
Received: from ns.pigworks.openss7.net (IDENT:vV8UZF+WJMk7fUES9AFD9s8hzrNHh6u+@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i15JKjI13212;
	Thu, 5 Feb 2004 12:20:45 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i15JKih20545;
	Thu, 5 Feb 2004 12:20:44 -0700
Date: Thu, 5 Feb 2004 12:20:44 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry Nagelberg <barryn@adax.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
Message-ID: <20040205122044.A19999@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry Nagelberg <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <20040205112318.B18993@openss7.org> <JBECLENKLBCKAAKFGAJOGEEOCEAA.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: <JBECLENKLBCKAAKFGAJOGEEOCEAA.barryn@adax.com>; from barryn@adax.com on Thu, Feb 05, 2004 at 01:34:19PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Barry,

Barry Nagelberg wrote:                                                               (Thu, 05 Feb 2004 13:34:19)
> Brian,
> 
> I cannot follow your logic. Please just answer my question:
> 
> If the optional sequence control param is not present in an SCCP UNITDATA
> indication, what should be the value of the mandatory sequence control param
> in the CLDT msg?

A value selected to ensure proper loadsharing across SLS at MTP ala
Q.711/6.2.2.2.2.

Try:
	if (your_subsystem_cannot_provide_one) {
		static loadshare_sequence = 0;
		sequence_control = loadshare_sequence++;
	}

--brian


> 
> Barry
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Thursday, February 05, 2004 1:23 PM
> > To: Barry Nagelberg
> > Cc: SIGTRAN Mailing List
> > Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
> >
> >
> > Barry,
> >
> > For the link between loadsharing and sequence control, see
> > Q.711/6.2.2.2.2.
> >
> > When multiple SG are acting as STP, each must choose the same SLS for
> > Class 1 operation.  Thus the ASP must provide the sequence control value
> > which the SG may use to derive the SLS.
> >
> > --brian
> >
> > Barry Nagelberg wrote:
> >                    (Thu, 05 Feb 2004 12:46:59)
> > > Brian,
> > >
> > > OK, at least we know how the note got removed from the draft.
> > But I don't
> > > understand the link between loadsharing and the sequence
> > control value. So I
> > > repeat my question:
> > >
> > > If the optional sequence control param is not present in an
> > SCCP UNITDATA
> > > indication, what should be the value of the mandatory sequence
> > control param
> > > in the CLDT msg?
> > >
> > > Barry
> > >
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: Thursday, February 05, 2004 12:32 PM
> > > > To: Barry Nagelberg
> > > > Cc: SIGTRAN Mailing List
> > > > Subject: Re: [Sigtran] SUA v16: sequence control parameter in CLDT msg
> > > >
> > > >
> > > > Barry,
> > > >
> > > > It was struct from sua-16 at my request:
> > > >
> > > > >     Implementation note: This message covers the following SCCP
> > > > >     messages: unitdata (UDT), extended unitdata (XUDT),
> > long unitdata
> > > > > -   (LUDT).
> > > > > +   (LUDT). Sequence Control is set to 0 for class 0 messages.
> > > > >
> > > > > This change is incorrect.  Please remove this addition.  We
> > > > discussed this
> > > > > long ago and Sequence Control is required in class 0
> > messages for some
> > > > > network configurations and for proper MTP relay accross a relay
> > > > point.  It
> > > > > might not be provided by the SCCP/SUA-User for class 0, but
> > then the SUA
> > > > > layer (at ASP, IPSP or SGP) must ultimately select a
> > loadsharing value.
> > > > > That is why we made the parameter MANDATORY for all
> > protocol classes.
> > > >
> > > > --brian
> > > >
> > > > Barry Nagelberg wrote:
> > > >                    (Thu, 05 Feb 2004 10:55:34)
> > > > > Brian,
> > > > >
> > > > > Thanks, but I can't find the "Implementation note in SUA/3.2.1"
> > > > to which you
> > > > > refer.
> > > > >
> > > > > Barry
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > Sent: Thursday, February 05, 2004 10:29 AM
> > > > > > To: Barry Nagelberg
> > > > > > Cc: SIGTRAN Mailing List
> > > > > > Subject: Re: [Sigtran] SUA v16: sequence control
> > parameter in CLDT msg
> > > > > >
> > > > > >
> > > > > > Barry,
> > > > > >
> > > > > > In Q.711, for N-UNITDATA Request it is marked as a "User Option"
> > > > > > and not as
> > > > > > "Optional".  See also Q.711/6.2.2.2.2.  (If the SCCP user
> > > > does not provide
> > > > > > a sequence control parameter, then the SCCP assumes
> > protocol class 0.)
> > > > > > Also note that there is no "Protocol Class" argument to
> > > > > > N-UNITDATA Request.
> > > > > >
> > > > > > Rather than have to handle the case where Sequence Control
> > > > was missing for
> > > > > > protocol class 1, SUA specifies the Protocol Class in CLDT
> > > > and when the
> > > > > > protocol class is zero (0), sequence control is set to (0) as
> > > > > > described in the
> > > > > > the Implementation note in SUA/3.2.1.
> > > > > >
> > > > > > CLDT __corresponds__ to N-UNITDATA Req/Ind.  It is not exact.
> > > >  One of the
> > > > > > reasons for differences is the multiple SG as STP case.
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > >
> >
> > --
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Feb  5 14:50:34 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 OAA01433
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Feb 2004 14:50:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AopVl-0001bI-Ni
	for sigtran-archive@odin.ietf.org; Thu, 05 Feb 2004 14:50:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i15Jo5OA006151
	for sigtran-archive@odin.ietf.org; Thu, 5 Feb 2004 14:50:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AopVi-0001aN-SR; Thu, 05 Feb 2004 14:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AopUw-0001XF-PF
	for sigtran@optimus.ietf.org; Thu, 05 Feb 2004 14:49:14 -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 OAA01394
	for <sigtran@ietf.org>; Thu, 5 Feb 2004 14:49:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AopUt-0006Uf-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 14:49:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AopU7-0006Ov-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 14:48:25 -0500
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AopTE-0006Jf-00
	for sigtran@ietf.org; Thu, 05 Feb 2004 14:47:28 -0500
Received: from [10.0.1.2] (pD9FF1286.dip.t-dialin.net [217.255.18.134])
	by mail-n.franken.de (Postfix) with ESMTP
	id 7F41524620; Thu,  5 Feb 2004 20:46:20 +0100 (CET)
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C04331A2E@eestqnt105.es.eu.ericsson.se>
References: <1AB3D30B989BF141BBD5C70057B2EF7C04331A2E@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F3DB1584-5813-11D8-861F-000A95DC192A@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
Cc: bidulock@openss7.org,
        "'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>,
        sigtran@ietf.org
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Sigtran] M3UA version control
Date: Thu, 5 Feb 2004 20:46:12 +0100
To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Javier,

you are right, the text is part of subsection
4.3.4.1 ASP Up Procedures

So I suggest, to delete the paragraph 4.3.4.1.1 and
move the text to a general place. It has to be applied to all messages, 
not
only ASP-UP.

This has to be stated somewhere.

Best regards
Michael

On Feb 5, 2004, at 3:20 PM, J.Javier Pastor (ML/EEM) wrote:

> Here is the proposed text:
>
>
> 3.28 Invalid Version parameter explanation
>
> 3.28.1 Description of the problem
>
> There is a typo in the current RFC within the ERROR message 
> sub-section. "Invalid Stream identifier" parameter is explained twice 
> while the "Invalid Version" is not even mentioned.
>
> 3.28.2 Text changes to the document
>
> ---------
> Old text: (Section 3.8.1)
> ---------
>
> The Error message is used to notify a peer of an error event 
> associated with an incoming message.  For example, the message type 
> might be unexpected given the current state, or a parameter value 
> might be invalid.
>
> ---------
> New text: (Section 3.8.1)
> ---------
>
> The Error message is used to notify a peer of an error event 
> associated with an incoming message.  For example, the message type 
> might be unexpected given the current state, or a parameter value 
> might be invalid. Error messages MUST NOT be generated in response to 
> other Error messages.
>
>
> ---------
> Old text: (Section 3.8.1)
> ---------
>
> The "Invalid Stream Identifier" error is sent if a message is received 
> on an unexpected SCTP stream (e.g., a MGMT message was received on a 
> stream other than "0").  Error messages MUST NOT be generated in 
> response to other Error messages.
>
> ---------
> New text: (Section 3.8.1)
> ---------
>
> The "Invalid Version" error is sent if a message with an unsupported 
> version is received, the receiving end responds with an Error message, 
> indicating the version the receiving node supports and notifies layer 
> management.
>
>
> 3.28.3 Solution Description
>
> The duplicated text has been substituted by an explanation of the 
> missing parameter "Invalid Version". Also, the last sentence next to 
> the duplicated text has been moved to the beginning  of the section 
> 3.8.1.
>
>
>
> Cheers // Javier.
>
>> -----Original Message-----
>> From: sigtran-admin@ietf.org
>> [mailto:sigtran-admin@ietf.org]On Behalf Of
>> J.Javier Pastor (ML/EEM)
>> Sent: jueves, 05 de febrero de 2004 14:50
>> To: 'Samuel Dur D. Jeyaseelan'; Michael Tuexen
>> Cc: bidulock@openss7.org; sigtran@ietf.org
>> Subject: RE: [Sigtran] M3UA version control
>>
>>
>> Hi Michael et al.,
>>
>>
>> Take into account that you are referring to a section that
>> talks about the ASPUP procedures. ASPUP message is what is
>> really discussed and we should not include there the behavior
>> as a response to any other messages.
>>
>> What should be included in the IG is paragraph within the
>> section 3.8.1 explaining the "Invalid Version" code. I've
>> just seen that we have a typo there and include the "Invalid
>> Stream Identifier" twice while there is no mention of the
>> "Invalid Version". We'll update the IG with some text
>> explaining the general behavior.
>>
>> Anyway, a good implementation that is following the state
>> machines and so on from the M3UA document will not have this
>> problems...
>>
>> Cheers // Javier.
>>
>>> -----Original Message-----
>>> From: sigtran-admin@ietf.org
>>> [mailto:sigtran-admin@ietf.org]On Behalf Of
>>> Samuel Dur D. Jeyaseelan
>>> Sent: jueves, 05 de febrero de 2004 13:16
>>> To: Michael Tuexen
>>> Cc: bidulock@openss7.org; sigtran@ietf.org
>>> Subject: Re: [Sigtran] M3UA version control
>>>
>>>
>>>
>>> Brian,
>>>  Is there any reason why you disagree with the change?
>>>
>>>  Is it is because ASP Up is the first message comes from ASP and
>>>  version control is checked at very first time with the assumption
>>>  all remaining messges will have the same version?
>>>
>>> --Samuel
>>>
>>> On Thu, 5 Feb 2004, Michael Tuexen wrote:
>>>
>>>> Brian,
>>>>
>>>> you disagree with the change? This means you want to have an
>>>> error ONLY returned for ASP-Up messages as the RFC states?
>>>>
>>>> I'm suggesting a change that it is returned for all messages.
>>>>
>>>> Best regards
>>>> Michael
>>>>
>>>>
>>>> On Feb 5, 2004, at 12:33 PM, Brian F. G. Bidulock wrote:
>>>>
>>>>> Michael,
>>>>>
>>>>> I missed that.  And, therefore, disagree with the change.
>>>  An error
>>>>> must be returned for any message with an unsupported
>> version, not
>>>>> just ASP Up, as the RFC already states.  The example case was in
>>>>> my last mail.
>>>>>
>>>>> --brian
>>>>>
>>>>> Michael Tuexen wrote:
>>>
>>>>>             (Thu, 05 Feb 2004 12:24:07)
>>>>>> Brian,
>>>>>>
>>>>>> part of my suggestion is to replace:
>>>>>>
>>>>>>      If an ASP Up message with an unsupported version is
>>> received, the
>>>>>>
>>>>>> with
>>>>>>
>>>>>>      If a message with an unsupported version is received, the
>>>>>>
>>>>>> At least for me, this does change the requested behaviour.
>>>>>>
>>>>>> Best regards
>>>>>> Michael
>>>>>>
>>>>>> On Feb 5, 2004, at 11:30 AM, Brian F. G. Bidulock wrote:
>>>>>>
>>>>>>> Michael,
>>>>>>>
>>>>>>> I don't think that your proposed text takes us any
>>> farther towards
>>>>>>> that goal.  You have changed "assumed that" to
>> "likely that the
>>>>>>> message having an unsupported version is an ASP Up message and
>>>>>>> therefore [likely] that".
>>>>>>>
>>>>>>> This is just description.  The requirement is (unchanged):
>>>>>>>
>>>>>>>> If a message with an unsupported version is received, the
>>>>>>>> receiving end responds with an Error message,
>>> indicating the version
>>>>>>>> the receiving node supports and notifies Layer Management.
>>>>>>>
>>>>>>> This is obviously any message.
>>>>>>>
>>>>>>> As there is no change to the requirement, the new text is
>>>>>>> superfluous.
>>>>>>>
>>>>>>> Regardless of likelihoods or assumptions, the Error message is
>>>>>>> returned to any message received with an unsupported
>>> version and
>>>>>>> Layer
>>>>>>> Management is notified.  Suggesting that it is likely
>>> that an ASP Up
>>>>>>> is the cause, actually distracts from the requirement
>>> to return the
>>>>>>> error to any message.
>>>>>>>
>>>>>>> A node might actually send message Foo with Version=100
>>> to test a
>>>>>>> remote node's support for message Foo (only available
>>> in Version=100)
>>>>>>> while performing the ASP Up and ASP Active procedures using
>>>>>>> Version=1.
>>>>>>> This requirement provides that message Foo will be
>>> retured with an
>>>>>>> "usupported version" if version 100 is not supported
>>> (and obviously
>>>>>>> the message Foo is not supported).
>>>>>>>
>>>>>>> It would be better to strike the line starting with
>> "Because",
>>>>>>> because
>>>>>>> it was superfluous to begin with.  Changing assumptions to
>>>>>>> likelihoods
>>>>>>> does not increase its pertinence.
>>>>>>>
>>>>>>> --brian
>>>>>>>
>>>>>>>
>>>>>>> Michael Tuexen wrote:
>>>>>>>             (Thu, 05 Feb 2004 10:17:40)
>>>>>>>> Brian,
>>>>>>>>
>>>>>>>> I agree with you that there are a lot of places which are not
>>>>>>>> very precisely (this is the same with other RFCs) but this
>>>>>>>> question came up multiple times. Others not. That is why I'm
>>>>>>>> asking to clarify this.
>>>>>>>>
>>>>>>>> I know about customers and testers who test exactly this and
>>>>>>>> always ask: what is the correct behaviour. So what is the
>>>>>>>> problem in making this clear? Think about having different
>>>>>>>> customers requesting different implementations?
>>>>>>>>
>>>>>>>> Best regards
>>>>>>>> Michael
>>>>>>>>
>>>>>>>> On Feb 4, 2004, at 11:46 PM, Brian F. G. Bidulock wrote:
>>>>>>>>
>>>>>>>>> Michael,
>>>>>>>>>
>>>>>>>>> I think you need to read the RFC from the viewpoint of a
>>>>>>>>> specification
>>>>>>>>> instead of the viewpoint of an implementation.  When it says
>>>>>>>>> "assumed"
>>>>>>>>> it means "assumed [by the authors in the
>> specification of the
>>>>>>>>> protocol]"
>>>>>>>>> and not "assumed [by the implementation]".
>>>>>>>>>
>>>>>>>>> There are many place in the RFC where this is the
>>> case, because of
>>>>>>>>> the
>>>>>>>>> editors' preference for words like "assumed".  If we
>>> are to correct
>>>>>>>>> the lazy
>>>>>>>>> English in the document, it would require an
>>> extensive rewrite.
>>>>>>>>>
>>>>>>>>> --brian
>>>>>>>>>
>>>>>>>>> Michael Tuexen wrote:
>>>>>>>>>             (Wed, 04 Feb 2004 21:56:43)
>>>>>>>>>> Dear all,
>>>>>>>>>>
>>>>>>>>>> the RFC describes that an M3UA endpoint should check
>>> the version
>>>>>>>>>> field
>>>>>>>>>> for ASP Up messages and leaves it unspecified how
>>> other messages
>>>>>>>>>> should
>>>>>>>>>> be handled.
>>>>>>>>>>
>>>>>>>>>> In real scenarios the first message having an
>>> unsupported message
>>>>>>>>>> is
>>>>>>>>>> most likely an ASP-Up message, but my experience is,
>>> that people
>>>>>>>>>> testing
>>>>>>>>>> implementations always ask how these other
>> messages should be
>>>>>>>>>> handled.
>>>>>>>>>>
>>>>>>>>>> Therefore I would like to suggest a clarification
>> in the IG
>>>>>>>>>> clearly
>>>>>>>>>> stating how these other messages with an
>> unsupported version
>>>>>>>>>> should
>>>>>>>>>> be handled.
>>>>>>>>>>
>>>>>>>>>> We can specify that it is checked for all messages
>>> or only for
>>>>>>>>>> ASP-Up
>>>>>>>>>> messages, ignoring the version field for non
>> ASP-Up messages.
>>>>>>>>>>
>>>>>>>>>> The easiest solution seems to be (for me) to check
>>> the field for
>>>>>>>>>> all messages. So you could write
>>>>>>>>>>
>>>>>>>>>> if (message->version != 1)
>>>>>>>>>>    send(error)
>>>>>>>>>>
>>>>>>>>>> instead of
>>>>>>>>>>
>>>>>>>>>> if ((message->class == 3) && (message->type == 1) &&
>>>>>>>>>> (message->(message->version != 1))
>>>>>>>>>>    send(error)
>>>>>>>>>>
>>>>>>>>>> Therefore I suggest to include the following text
>> in the IG.
>>>>>>>>>>
>>>>>>>>>> Best regards
>>>>>>>>>> Michael
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> <---- SNIP
>>>>>>>>>> 3.28 Version Control
>>>>>>>>>>
>>>>>>>>>> 3.28.1 Description of the problem
>>>>>>>>>>
>>>>>>>>>> The RFC describes how ASP Up messages with an
>>> unsupported version
>>>>>>>>>> are handled but leaves it unspecified how other
>>> messages should be
>>>>>>>>>> handled if the version number is not supported.
>>>>>>>>>>
>>>>>>>>>> 3.28.2 Text changes to the document
>>>>>>>>>>     ---------
>>>>>>>>>>     Old text: (Section 4.3.4.1.1)
>>>>>>>>>>     ---------
>>>>>>>>>>
>>>>>>>>>> 4.3.4.1.1 M3UA Version Control
>>>>>>>>>>
>>>>>>>>>>     If an ASP Up message with an unsupported version
>>> is received,
>>>>>>>>>> the
>>>>>>>>>>     receiving end responds with an Error message,
>>> indicating the
>>>>>>>>>> version
>>>>>>>>>>     the receiving node supports and notifies Layer
>>> Management.
>>>>>>>>>>
>>>>>>>>>>     This is useful when protocol version upgrades are being
>>>>>>>>>> performed
>>>>>>>>>> in
>>>>>>>>>>     a network.  A node upgraded to a newer version
>>> should support
>>>>>>>>>> the
>>>>>>>>>>     older versions used on other nodes it is
>>> communicating with.
>>>>>>>>>> Because
>>>>>>>>>>     ASPs initiate the ASP Up procedure it is assumed
>>> that the
>>>>>>>>>> Error
>>>>>>>>>>     message would normally come from the SGP.
>>>>>>>>>>
>>>>>>>>>>     ---------
>>>>>>>>>>     New text: (Section 4.3.4.1.1)
>>>>>>>>>>     ---------
>>>>>>>>>>
>>>>>>>>>> 4.3.4.1.1 M3UA Version Control
>>>>>>>>>>
>>>>>>>>>>     If a message with an unsupported version is
>> received, the
>>>>>>>>>>     receiving end responds with an Error message,
>>> indicating the
>>>>>>>>>> version
>>>>>>>>>>     the receiving node supports and notifies Layer
>>> Management.
>>>>>>>>>>
>>>>>>>>>>     This is useful when protocol version upgrades are being
>>>>>>>>>> performed
>>>>>>>>>> in
>>>>>>>>>>     a network.  A node upgraded to a newer version
>>> should support
>>>>>>>>>> the
>>>>>>>>>>     older versions used on other nodes it is
>>> communicating with.
>>>>>>>>>> Because
>>>>>>>>>>     ASPs initiate the ASP Up procedure it is
>> likely that the
>>>>>>>>>> message
>>>>>>>>>> having
>>>>>>>>>>     an unsupported version is an ASP Up message and
>>> therefore that
>>>>>>>>>> the
>>>>>>>>>> Error
>>>>>>>>>>     message would normally come from the SGP.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 3.28.3 Solution description
>>>>>>>>>>
>>>>>>>>>> The new text clearly describes that the version
>>> should be checked
>>>>>>>>>> for
>>>>>>>>>> all
>>>>>>>>>> messages.
>>>>>>>>>> <---- SNIP
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Sigtran mailing list
>>>>>>>>>> Sigtran@ietf.org
>>>>>>>>>> https://www1.ietf.org/mailman/listinfo/sigtran
>>>>>>>>>
>>>>>>>>> -- 
>>>>>>>>> Brian F. G. Bidulock
>>>>>>>>> bidulock@openss7.org
>>>>>>>>> http://www.openss7.org/
>>>>>>>>>
>>>>>>>
>>>>>>> -- 
>>>>>>> Brian F. G. Bidulock
>>>>>>> bidulock@openss7.org
>>>>>>> http://www.openss7.org/
>>>>>>>
>>>>>
>>>>> -- 
>>>>> Brian F. G. Bidulock
>>>>> bidulock@openss7.org
>>>>> http://www.openss7.org/
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Sigtran mailing list
>>>> Sigtran@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/sigtran
>>>>
>>>
>>>
>>> _______________________________________________
>>> Sigtran mailing list
>>> Sigtran@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/sigtran
>>>
>>
>> This communication is confidential and intended solely for
>> the addressee(s). Any unauthorized review, use, disclosure or
>> distribution is prohibited. If you believe this message has
>> been sent to you in error, please notify the sender by
>> replying to this transmission and delete the message without
>> disclosing it. Thank you.
>>
>> E-mail including attachments is susceptible to data
>> corruption, interruption, unauthorized amendment, tampering
>> and viruses, and we only send and receive e-mails on the
>> basis that we are not liable for any such corruption,
>> interception, amendment, tampering or viruses or any
>> consequences thereof.
>>
>>
>> _______________________________________________
>> Sigtran mailing list
>> Sigtran@ietf.org
>> https://www1.ietf.org/mailman/listinfo/sigtran
>>
>
> This communication is confidential and intended solely for the 
> addressee(s). Any unauthorized review, use, disclosure or distribution 
> is prohibited. If you believe this message has been sent to you in 
> error, please notify the sender by replying to this transmission and 
> delete the message without disclosing it. Thank you.
>
> E-mail including attachments is susceptible to data corruption, 
> interruption, unauthorized amendment, tampering and viruses, and we 
> only send and receive e-mails on the basis that we are not liable for 
> any such corruption, interception, amendment, tampering or viruses or 
> any consequences thereof.
>
>


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



From exim@www1.ietf.org  Sat Feb  7 06:23: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 GAA29923
	for <sigtran-archive@odin.ietf.org>; Sat, 7 Feb 2004 06:23:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ApQYE-0005VD-It
	for sigtran-archive@odin.ietf.org; Sat, 07 Feb 2004 06:23:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i17BN6O8021134
	for sigtran-archive@odin.ietf.org; Sat, 7 Feb 2004 06:23:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ApQY9-0005Ue-Cr; Sat, 07 Feb 2004 06:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ApQXZ-0005MC-SQ
	for sigtran@optimus.ietf.org; Sat, 07 Feb 2004 06:22:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29908
	for <sigtran@ietf.org>; Sat, 7 Feb 2004 06:22:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ApQXV-0003Bi-00
	for sigtran@ietf.org; Sat, 07 Feb 2004 06:22:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ApQWY-00037n-00
	for sigtran@ietf.org; Sat, 07 Feb 2004 06:21:22 -0500
Received: from znsgs01r.nortelnetworks.com ([47.166.48.91])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ApQVb-000313-00
	for sigtran@ietf.org; Sat, 07 Feb 2004 06:20:23 -0500
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.160.46.124])
	by znsgs01r.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i17BJq907355;
	Sat, 7 Feb 2004 11:19:52 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1FPW0QZJ>; Sat, 7 Feb 2004 11:19:52 -0000
Message-ID: <9F8B82425D82D511B5AC0002A55CCCAF072ACC84@zfdhc101-int2.europe.nortel.com>
From: "Eva Weilandt" <eva.weilandt@nortelnetworks.com>
To: "'Pascal Bouveron (Netbricks)'" <pascal.bouveron@netbricks.com>,
        "'sigtran@ietf.org'" <sigtran@ietf.org>
Date: Sat, 7 Feb 2004 11:19:51 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3ED6C.4D97D896"
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_30_40,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60
Subject: [Sigtran] AW: V5UA Parameter Tags conflict with M3UA Tags
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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_01C3ED6C.4D97D896
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Pascal,
=20
we will change the message tags together with the message class for the =
RFC
version of V5UA. This will hopefully happen soon. If you need the new =
tags
in the meantime, let me know.
=20
Thanks for pointing this out. It is always helpful if someone =
proof-read
your documents :-)
=20
Eva

-----Urspr=FCngliche Nachricht-----
Von: Pascal Bouveron (Netbricks) [mailto:pascal.bouveron@netbricks.com] =

Gesendet: February 2, 2004 11:28 AM
An: Weilandt, Eva [FRIED:NRA11:EXCH]; sigtran@ietf.org
Betreff: V5UA Parameter Tags conflict with M3UA Tags


Hello,
=20
I found other conflicts between V5UA and other UAs, in the Parameter =
Tags
definitions:
=20
Tag 0x0011: "ASP Identifier" for M3UA, but "Link Status" for V5UA
Tag 0x0012: "Affected Point Code" for M3UA, but "Sa-Bit" (it actually =
has no
name in draft-04) for V5UA
Tag 0x0013: "Correlation Id" for M3UA, but "Error Reason" for V5UA
=20
Best regards / Meilleures salutations
Pascal Bouveron
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
www.netbricks.com <http://www.netbricks.com>=20
Netbricks - Provence - FRANCE
Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=20


------_=_NextPart_001_01C3ED6C.4D97D896
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<TITLE>Nachricht</TITLE>

<META content=3D"MSHTML 5.50.4916.2300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D635101811-07022004><FONT face=3DArial =
color=3D#0000ff size=3D2>Hi=20
Pascal,</FONT></SPAN></DIV>
<DIV><SPAN class=3D635101811-07022004><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D635101811-07022004><FONT face=3DArial =
color=3D#0000ff size=3D2>we=20
will change the message tags together with the message class for the =
RFC version=20
of V5UA. This will hopefully happen soon. If you need the new tags in =
the=20
meantime, let me know.</FONT></SPAN></DIV>
<DIV><SPAN class=3D635101811-07022004><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D635101811-07022004><FONT face=3DArial =
color=3D#0000ff size=3D2>Thanks=20
for pointing this out. It is always helpful if someone proof-read your =
documents=20
:-)</FONT></SPAN></DIV>
<DIV><SPAN class=3D635101811-07022004><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D635101811-07022004><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Eva</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Dde dir=3Dltr =
align=3Dleft><FONT face=3DTahoma=20
  size=3D2>-----Urspr=FCngliche Nachricht-----<BR><B>Von:</B> Pascal =
Bouveron=20
  (Netbricks) [mailto:pascal.bouveron@netbricks.com] =
<BR><B>Gesendet:</B>=20
  February 2, 2004 11:28 AM<BR><B>An:</B> Weilandt, Eva =
[FRIED:NRA11:EXCH];=20
  sigtran@ietf.org<BR><B>Betreff:</B> V5UA Parameter Tags conflict with =
M3UA=20
  Tags<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>I found other conflicts between V5UA =
and other=20
  UAs, in the Parameter Tags definitions:</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Tag 0x0011: "ASP Identifier" for =
M3UA, but "Link=20
  Status" for V5UA</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Tag 0x0012: "Affected Point Code" =
for M3UA, but=20
  "Sa-Bit" (it actually has no name in draft-04) for V5UA</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Tag 0x0013: "Correlation Id" for =
M3UA, but "Error=20
  Reason"&nbsp;for V5UA</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV>Best regards / Meilleures salutations<BR>Pascal=20
  =
Bouveron<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D<BR><A=20
  href=3D"http://www.netbricks.com">www.netbricks.com</A><BR>Netbricks =
- Provence=20
  - FRANCE<BR>Tel: (+33) (0)4 42 91 44 77 -- Fax:&nbsp; (+33) (0)4 42 =
91 44=20
  =
71<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</D=
IV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C3ED6C.4D97D896--

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



From exim@www1.ietf.org  Sun Feb  8 06:25:31 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 GAA16098
	for <sigtran-archive@odin.ietf.org>; Sun, 8 Feb 2004 06:25:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Apn3g-0003fu-Ss
	for sigtran-archive@odin.ietf.org; Sun, 08 Feb 2004 06:25:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i18BP4vU014104
	for sigtran-archive@odin.ietf.org; Sun, 8 Feb 2004 06:25:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Apn3f-0003fJ-1E; Sun, 08 Feb 2004 06:25:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Apn2r-0003bf-8H
	for sigtran@optimus.ietf.org; Sun, 08 Feb 2004 06:24:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16063
	for <sigtran@ietf.org>; Sun, 8 Feb 2004 06:24:09 -0500 (EST)
From: d86942004@ntu.edu.tw
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Apn2n-0005W0-00
	for sigtran@ietf.org; Sun, 08 Feb 2004 06:24:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Apn1t-0005Rq-00
	for sigtran@ietf.org; Sun, 08 Feb 2004 06:23:13 -0500
Received: from wmail1.cc.ntu.edu.tw ([140.112.2.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Apn1B-0005Nv-00
	for sigtran@ietf.org; Sun, 08 Feb 2004 06:22:30 -0500
Received: by wmail1.cc.ntu.edu.tw (Postfix, from userid 80)
	id BB160372; Sun,  8 Feb 2004 19:22:24 +0800 (CST)
Received: from 221.120.49.88 ([221.120.49.88]) by wmail1.cc.ntu.edu.tw
	(Horde) with HTTP for <d86942004@wmail1.cc.ntu.edu.tw>; Sun,  8 Feb 2004
	19:22:24 +0800
Message-ID: <20040208192224.w9w00ss080ggss48@wmail1.cc.ntu.edu.tw>
Date: Sun,  8 Feb 2004 19:22:24 +0800
To: sigtran@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="BIG5"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) 4.0-cvs
X-Originating-IP: 221.120.49.88
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.2 required=5.0 tests=FROM_ENDS_IN_NUMS,NO_REAL_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] questions about M3UA
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Dear all,

The upper layer protocol is carried in the Protocol Data of M3UA Payload Data
Message (DATA).

How to distinguish various upper layer protocol, such as SCCP, BICC?

Is any protocol identifier defined in IETF?


Thanks

Ling-Chih Kao

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



From exim@www1.ietf.org  Sun Feb  8 06:59:27 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 GAA16801
	for <sigtran-archive@odin.ietf.org>; Sun, 8 Feb 2004 06:59:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ApnaX-0005c8-Jz
	for sigtran-archive@odin.ietf.org; Sun, 08 Feb 2004 06:59:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i18Bx1nd021558
	for sigtran-archive@odin.ietf.org; Sun, 8 Feb 2004 06:59:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ApnaW-0005bX-MI; Sun, 08 Feb 2004 06:59:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ApnZn-0005ay-4c
	for sigtran@optimus.ietf.org; Sun, 08 Feb 2004 06:58:15 -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 GAA16792
	for <sigtran@ietf.org>; Sun, 8 Feb 2004 06:58:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ApnZi-0007lV-00
	for sigtran@ietf.org; Sun, 08 Feb 2004 06:58:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ApnYl-0007i9-00
	for sigtran@ietf.org; Sun, 08 Feb 2004 06:57:11 -0500
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ApnYS-0007eq-00
	for sigtran@ietf.org; Sun, 08 Feb 2004 06:56:52 -0500
Received: from [10.0.1.3] (p5089DB7D.dip.t-dialin.net [80.137.219.125])
	by mail-n.franken.de (Postfix) with ESMTP
	id 2C69024604; Sun,  8 Feb 2004 12:55:42 +0100 (CET)
In-Reply-To: <20040208192224.w9w00ss080ggss48@wmail1.cc.ntu.edu.tw>
References: <20040208192224.w9w00ss080ggss48@wmail1.cc.ntu.edu.tw>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <8F38279E-5A2D-11D8-A054-000A95C37894@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
Cc: sigtran@ietf.org
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Sigtran] questions about M3UA
Date: Sun, 8 Feb 2004 12:54:33 +0100
To: d86942004@ntu.edu.tw
X-Mailer: Apple Mail (2.612)
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,MAILTO_TO_SPAM_ADDR 
	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,

this information is part of the protocol data parameter like
it is part of an MSU. It is in the SI field.
See section 3.3.1 of the RFC.

Best regards
Michael

On 8. Feb 2004, at 12:22 Uhr, d86942004@ntu.edu.tw wrote:

> Dear all,
>
> The upper layer protocol is carried in the Protocol Data of M3UA 
> Payload Data
> Message (DATA).
>
> How to distinguish various upper layer protocol, such as SCCP, BICC?
>
> Is any protocol identifier defined in IETF?
>
>
> Thanks
>
> Ling-Chih Kao
>
> _______________________________________________
> Sigtran mailing 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 Feb  9 12:20:34 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 MAA28923
	for <sigtran-archive@odin.ietf.org>; Mon, 9 Feb 2004 12:20:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqF4o-0007eu-NQ
	for sigtran-archive@odin.ietf.org; Mon, 09 Feb 2004 12:20:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i19HK6RY029419
	for sigtran-archive@odin.ietf.org; Mon, 9 Feb 2004 12:20:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqF4m-0007eD-S6; Mon, 09 Feb 2004 12:20:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqF42-0007ch-EJ
	for sigtran@optimus.ietf.org; Mon, 09 Feb 2004 12:19:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28844
	for <sigtran@ietf.org>; Mon, 9 Feb 2004 12:19:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqF40-0003KX-00
	for sigtran@ietf.org; Mon, 09 Feb 2004 12:19:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqF3C-0003FG-00
	for sigtran@ietf.org; Mon, 09 Feb 2004 12:18:26 -0500
Received: from znsgs01r.nortelnetworks.com ([47.166.48.91])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqF2H-00034X-00
	for sigtran@ietf.org; Mon, 09 Feb 2004 12:17:29 -0500
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.160.46.124])
	by znsgs01r.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i19HGQc10459;
	Mon, 9 Feb 2004 17:16:27 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1FPXA1GF>; Mon, 9 Feb 2004 17:16:27 -0000
Message-ID: <9F8B82425D82D511B5AC0002A55CCCAF072AD038@zfdhc101-int2.europe.nortel.com>
From: "Eva Weilandt" <eva.weilandt@nortelnetworks.com>
To: "'Pascal Bouveron'" <pascal.bouveron@netbricks.com>,
        "'sigtran@ietf.org'" <sigtran@ietf.org>
Cc: "'Alain CHAMPENOIS'" <alain.champenois@netbricks.com>
Date: Mon, 9 Feb 2004 17:16:23 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3EF30.7109406A"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL,HTML_30_40,HTML_MESSAGE 
	autolearn=no version=2.60
Subject: [Sigtran] V5UA: Proposed changes to V5UA for the RFC version
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-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_01C3EF30.7109406A
Content-Type: text/plain

Hi everybody,

for the RFC version of the V5UA, there will be changes for the V5UA draft
regarding the V5PTM message class and parameter tags. These changes are
necessary due to conflicts with other SIGTRAN message classes/parameter
tags.

Changes are as follows:

- V5 Boundary Primitives Transport Messages (V5PTM): 
	Message class changed from 9 to 14

- V5UA Message Parameter tags:
	* DLCI/EFA             changed from  0x5 to 0x81
	* Link Status          changed from 0x11 to 0x82
	* Bit ID/Bit Value     changed from 0x12 to 0x83
	* Error Reason         changed from 0x13 to 0x84

Regards,

Eva

------_=_NextPart_001_01C3EF30.7109406A
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>V5UA: Proposed changes to V5UA for the RFC version</TITLE>
</HEAD>
<BODY>

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

<P><FONT SIZE=3D2>for the RFC version of the V5UA, there will be =
changes for the V5UA draft regarding the V5PTM message class and =
parameter tags. These changes are necessary due to conflicts with other =
SIGTRAN message classes/parameter tags.</FONT></P>

<P><FONT SIZE=3D2>Changes are as follows:</FONT>
</P>

<P><FONT SIZE=3D2>- V5 Boundary Primitives Transport Messages (V5PTM): =
</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>Message =
class changed from 9 to 14</FONT>
</P>

<P><FONT SIZE=3D2>- V5UA Message Parameter tags:</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>* =
DLCI/EFA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; changed from&nbsp; 0x5 to 0x81</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>* Link =
Status&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; changed =
from 0x11 to 0x82</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>* Bit =
ID/Bit Value&nbsp;&nbsp;&nbsp;&nbsp; changed from 0x12 to 0x83</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>* Error =
Reason&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; changed from =
0x13 to 0x84</FONT>
</P>

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

<P><FONT SIZE=3D2>Eva</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C3EF30.7109406A--

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



From exim@www1.ietf.org  Mon Feb  9 13:41: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 NAA03467
	for <sigtran-archive@odin.ietf.org>; Mon, 9 Feb 2004 13:41:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqGLA-0006PN-Aa
	for sigtran-archive@odin.ietf.org; Mon, 09 Feb 2004 13:41:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i19If4Dm024611
	for sigtran-archive@odin.ietf.org; Mon, 9 Feb 2004 13:41:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqGL9-0006Om-0K; Mon, 09 Feb 2004 13:41:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqGKU-0006NB-0X
	for sigtran@optimus.ietf.org; Mon, 09 Feb 2004 13:40:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03381
	for <sigtran@ietf.org>; Mon, 9 Feb 2004 13:40:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqGKR-0003qq-00
	for sigtran@ietf.org; Mon, 09 Feb 2004 13:40:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqGJq-0003jt-00
	for sigtran@ietf.org; Mon, 09 Feb 2004 13:39:43 -0500
Received: from sjmail.ciena.com ([12.7.169.25] helo=w2ksjexg01.ciena.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqGJ7-0003di-00
	for sigtran@ietf.org; Mon, 09 Feb 2004 13:38:57 -0500
Received: by w2ksjexg01.ciena.com with Internet Mail Service (5.5.2657.72)
	id <1JQBS3QC>; Mon, 9 Feb 2004 10:38:37 -0800
Message-ID: <829F074A10F98943A218DC363D09C92A0147695C@w2ksjexg06.oni.com>
From: "Ong, Lyndon" <LyOng@Ciena.com>
To: "'Eva Weilandt'" <eva.weilandt@nortelnetworks.com>,
        "'Pascal Bouveron'"
	 <pascal.bouveron@netbricks.com>,
        "'sigtran@ietf.org'" <sigtran@ietf.org>
Cc: "'Alain CHAMPENOIS'" <alain.champenois@netbricks.com>
Subject: RE: [Sigtran] V5UA: Proposed changes to V5UA for the RFC version
Date: Mon, 9 Feb 2004 10:38:55 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3EF3B.F8CF9B10"
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,HTML_30_40,
	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_01C3EF3B.F8CF9B10
Content-Type: text/plain;
	charset="iso-8859-1"

If this causes anyone a problem (hopefully not), please send in your email now.
 
Cheers,
 
L. Ong

-----Original Message-----
From: Eva Weilandt [mailto:eva.weilandt@nortelnetworks.com]
Sent: Monday, February 09, 2004 9:16 AM
To: 'Pascal Bouveron'; 'sigtran@ietf.org'
Cc: 'Alain CHAMPENOIS'
Subject: [Sigtran] V5UA: Proposed changes to V5UA for the RFC version



Hi everybody, 

for the RFC version of the V5UA, there will be changes for the V5UA draft regarding the V5PTM message class and parameter tags. These changes are necessary due to conflicts with other SIGTRAN message classes/parameter tags.

Changes are as follows: 

- V5 Boundary Primitives Transport Messages (V5PTM): 
        Message class changed from 9 to 14 

- V5UA Message Parameter tags: 
        * DLCI/EFA             changed from  0x5 to 0x81 
        * Link Status          changed from 0x11 to 0x82 
        * Bit ID/Bit Value     changed from 0x12 to 0x83 
        * Error Reason         changed from 0x13 to 0x84 

Regards, 

Eva 


------_=_NextPart_001_01C3EF3B.F8CF9B10
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>V5UA: Proposed changes to V5UA for the RFC version</TITLE>

<META content="MSHTML 5.50.4522.1800" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=209223818-09022004><FONT face=Arial color=#0000ff size=2>If 
this causes anyone a problem (hopefully not), please send in your email 
now.</FONT></SPAN></DIV>
<DIV><SPAN class=209223818-09022004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=209223818-09022004><FONT face=Arial color=#0000ff 
size=2>Cheers,</FONT></SPAN></DIV>
<DIV><SPAN class=209223818-09022004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=209223818-09022004><FONT face=Arial color=#0000ff size=2>L. 
Ong</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Eva Weilandt 
  [mailto:eva.weilandt@nortelnetworks.com]<BR><B>Sent:</B> Monday, February 09, 
  2004 9:16 AM<BR><B>To:</B> 'Pascal Bouveron'; 'sigtran@ietf.org'<BR><B>Cc:</B> 
  'Alain CHAMPENOIS'<BR><B>Subject:</B> [Sigtran] V5UA: Proposed changes to V5UA 
  for the RFC version<BR><BR></FONT></DIV>
  <P><FONT size=2>Hi everybody,</FONT> </P>
  <P><FONT size=2>for the RFC version of the V5UA, there will be changes for the 
  V5UA draft regarding the V5PTM message class and parameter tags. These changes 
  are necessary due to conflicts with other SIGTRAN message classes/parameter 
  tags.</FONT></P>
  <P><FONT size=2>Changes are as follows:</FONT> </P>
  <P><FONT size=2>- V5 Boundary Primitives Transport Messages (V5PTM): 
  </FONT><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT size=2>Message 
  class changed from 9 to 14</FONT> </P>
  <P><FONT size=2>- V5UA Message Parameter tags:</FONT> 
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT size=2>* 
  DLCI/EFA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  changed from&nbsp; 0x5 to 0x81</FONT> 
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT size=2>* Link 
  Status&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; changed from 0x11 
  to 0x82</FONT> <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT size=2>* 
  Bit ID/Bit Value&nbsp;&nbsp;&nbsp;&nbsp; changed from 0x12 to 0x83</FONT> 
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT size=2>* Error 
  Reason&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; changed from 0x13 to 
  0x84</FONT> </P>
  <P><FONT size=2>Regards,</FONT> </P>
  <P><FONT size=2>Eva</FONT> </P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C3EF3B.F8CF9B10--

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



From exim@www1.ietf.org  Tue Feb 10 04:16: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 EAA06926
	for <sigtran-archive@odin.ietf.org>; Tue, 10 Feb 2004 04:16: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 1AqTzy-0001Kc-Bq
	for sigtran-archive@odin.ietf.org; Tue, 10 Feb 2004 04:16:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1A9G6u0005088
	for sigtran-archive@odin.ietf.org; Tue, 10 Feb 2004 04:16:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqTzu-0001Jm-GW; Tue, 10 Feb 2004 04:16:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqTza-0001Iu-DM
	for sigtran@optimus.ietf.org; Tue, 10 Feb 2004 04:15:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06913
	for <sigtran@ietf.org>; Tue, 10 Feb 2004 04:15:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqTzX-0004r0-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 04:15:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqTyg-0004lD-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 04:14:47 -0500
Received: from fw.cdotb.ernet.in ([202.41.72.207] helo=ws9.cdotb.ernet.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqTxo-0004Wn-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 04:13:53 -0500
Received: from cdotb.ernet.in ([192.168.51.210])
	by ws9.cdotb.ernet.in (8.9.3/8.9.3) with ESMTP id OAA08516;
	Tue, 10 Feb 2004 14:15:05 +0500 (GMT+0500)
Message-ID: <40289F54.6060102@cdotb.ernet.in>
Date: Tue, 10 Feb 2004 14:37:32 +0530
From: Prakash R <rprakash@cdotb.ernet.in>
Reply-To: rprakash@cdotb.ernet.in
Organization: C-DOT (Center for Development of Telematics)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: cdotb.itg.devel.mgc
To: sigtran@ietf.org
CC: Prakash R <rprakash@cdotb.ernet.in>, Meghna Doshi <mdoshi@cdotb.ernet.in>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] Is M2UA less relevant?
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-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,

After checking the sigtran mail-archive, googling the web and the IETF 
site, I'm under the impression that somehow M2UA is not very relevant.

* There doesn't seem to be too much discussion about M2UA right now.
* There's no activity on the M2UA MIB.
* The test-suites didn't make it beyond the first drafts.
* Either it's very stable and done with, or it's of lower priority.

Could somebody kindly help me out with this?

Thanks in advance.

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

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



From exim@www1.ietf.org  Tue Feb 10 09:42:39 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 JAA20192
	for <sigtran-archive@odin.ietf.org>; Tue, 10 Feb 2004 09:42:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqZ5W-0007NR-T2
	for sigtran-archive@odin.ietf.org; Tue, 10 Feb 2004 09:42:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1AEgAsh028335
	for sigtran-archive@odin.ietf.org; Tue, 10 Feb 2004 09:42:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqZ5N-0007Mg-3u; Tue, 10 Feb 2004 09:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqZ5F-0007MQ-LZ
	for sigtran@optimus.ietf.org; Tue, 10 Feb 2004 09:41:53 -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 JAA20177
	for <sigtran@ietf.org>; Tue, 10 Feb 2004 09:41:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqZ5D-0006Te-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 09:41:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqZ4F-0006PU-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 09:40:52 -0500
Received: from mail4.telekom.de ([195.243.210.197])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqZ3Y-0006GF-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 09:40:08 -0500
Received: from g8pbr.blf01.telekom.de by mail2.dmz.telekom.de with ESMTP for sigtran@ietf.org; Tue, 10 Feb 2004 15:39:37 +0100
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <1SQ47FSL>; Tue, 10 Feb 2004 15:39:32 +0100
Message-Id: <53CD1252F68ED61183F5000347AE5F5505EBFC51@G8PPZ.blf01.telekom.de>
From: "Poetzl, Joachim" <Joachim.Poetzl@t-com.net>
To: sigtran@ietf.org
Date: Tue, 10 Feb 2004 15:39:28 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Subject: [Sigtran] Stream Mapping
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi,

could someone help on that:

In SUAv16 it is explicitly statet, how stream mapping has to be done - =
stream 0 is reserved for management messages.

Is this somewhere required for the other user adaption layers as well? =
I haven=B4t found it anywhere.

Thanks

snip--

   =20
1.5.4 SCTP Stream Mapping=20
   =20
   The SUA supports SCTP streams. Signalling Gateway SG and Application =

   Servers need to maintain a list of SCTP and SUA-users for mapping=20
   purposes.  SCCP-users requiring sequenced message transfer need to=20
   be sent over a stream with sequenced delivery.=20
   =20
   SUA uses stream 0 for SUA management messages.  It is OPTIONAL that=20
   sequenced delivery be used to preserve the order of management=20
   message delivery.=20
   =20
--snap


> Best Regards
>=20
> Joachim P=F6tzl
Deutsche Telekom AG
T-Com Zentrale
T332-4; Signalling, Gateways and Switching Systems
64307 DARMSTADT, GERMANY=20
Phone:  +49 6151 83-2134
Fax:      +49 6151 83-4577
PCFax:  +49 521 52244 983
> mailto:joachim.poetzl@t-com.net=20
>=20

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



From exim@www1.ietf.org  Tue Feb 10 09:50: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 JAA20390
	for <sigtran-archive@odin.ietf.org>; Tue, 10 Feb 2004 09:50:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqZDB-0007nX-Im
	for sigtran-archive@odin.ietf.org; Tue, 10 Feb 2004 09:50:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1AEo5Mh029952
	for sigtran-archive@odin.ietf.org; Tue, 10 Feb 2004 09:50:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqZDA-0007mo-R6; Tue, 10 Feb 2004 09:50:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqZCz-0007lL-0F
	for sigtran@optimus.ietf.org; Tue, 10 Feb 2004 09:49:53 -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 JAA20371
	for <sigtran@ietf.org>; Tue, 10 Feb 2004 09:49:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqZCx-000774-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 09:49:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqZC0-00071p-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 09:48:53 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqZB4-0006x2-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 09:47:54 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id JAA03303
	for <sigtran@ietf.org>; Tue, 10 Feb 2004 09:47:53 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: <sigtran@ietf.org>
Subject: RE: [Sigtran] Stream Mapping
Date: Tue, 10 Feb 2004 09:45:46 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMIEMKCDAA.asveren@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <53CD1252F68ED61183F5000347AE5F5505EBFC51@G8PPZ.blf01.telekom.de>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by chuckie.dgms.com id JAA03303
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

Joachim,

M3UA-IG 3.12 addresses this issue.

   Tolga

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf O=
f
> Poetzl, Joachim
> Sent: Tuesday, February 10, 2004 9:39 AM
> To: sigtran@ietf.org
> Subject: [Sigtran] Stream Mapping
>
>
> Hi,
>
> could someone help on that:
>
> In SUAv16 it is explicitly statet, how stream mapping has to be
> done - stream 0 is reserved for management messages.
>
> Is this somewhere required for the other user adaption layers as
> well? I haven=B4t found it anywhere.
>
> Thanks
>
> snip--
>
>
> 1.5.4 SCTP Stream Mapping
>
>    The SUA supports SCTP streams. Signalling Gateway SG and Application
>    Servers need to maintain a list of SCTP and SUA-users for mapping
>    purposes.  SCCP-users requiring sequenced message transfer need to
>    be sent over a stream with sequenced delivery.
>
>    SUA uses stream 0 for SUA management messages.  It is OPTIONAL that
>    sequenced delivery be used to preserve the order of management
>    message delivery.
>
> --snap
>
>
> > Best Regards
> >
> > Joachim P=F6tzl
> Deutsche Telekom AG
> T-Com Zentrale
> T332-4; Signalling, Gateways and Switching Systems
> 64307 DARMSTADT, GERMANY
> Phone:  +49 6151 83-2134
> Fax:      +49 6151 83-4577
> PCFax:  +49 521 52244 983
> > mailto:joachim.poetzl@t-com.net
> >
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


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



From exim@www1.ietf.org  Tue Feb 10 16:10:34 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 QAA15998
	for <sigtran-archive@odin.ietf.org>; Tue, 10 Feb 2004 16:10:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aqf8v-0006we-R3
	for sigtran-archive@odin.ietf.org; Tue, 10 Feb 2004 16:10:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1ALA5dW026674
	for sigtran-archive@odin.ietf.org; Tue, 10 Feb 2004 16:10:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aqf8s-0006vd-FN; Tue, 10 Feb 2004 16:10:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aqf87-0006dt-DG
	for sigtran@optimus.ietf.org; Tue, 10 Feb 2004 16:09:15 -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 QAA15623
	for <sigtran@ietf.org>; Tue, 10 Feb 2004 16:09:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aqf85-0001Xx-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 16:09:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aqf75-0001O2-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 16:08:12 -0500
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 1Aqf63-0001FH-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 16:07:07 -0500
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 i1AL73623014
	for <sigtran@ietf.org>; Tue, 10 Feb 2004 16:07:04 -0500
Received: by mail-in.comverse.com with Internet Mail Service (5.5.2657.72)
	id <1T0CBTLH>; Tue, 10 Feb 2004 16:00:06 -0500
Message-ID: <6B1DF6EEBA51D31182F20090274043680B6E774B@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
Date: Tue, 10 Feb 2004 16:00:05 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

To whomever is interested in answering this enquiry:

In Section 4.1.4 (draft 11) it states:

	While in a local processor outage (LPO) condition:

	   (c) M2PA SHOULD continue to transmit messages that have been sent
by its upper layer MTP3.

Further on it states:

	When the local processor outage condition ends,....

	M2PA SHALL NOT resume transmitting User Data messages until it has
received the Link Status Ready message.

So, I am trying to understand these two statements.

Does it mean:

a) That M2PA should transmit messages received from MTP3 prior to the LPO
indication. But not transmit messages from its MTP3 received after LPO,
until LPR (Processor Recovered).  Then, when the Ready is received to start
transmitting them.

or

b) That transmission continues throughout the LPO condition, but that when
M2PA sends the Processor Recovered Link Status Message it must suspend
transmission until the Ready is received from the peer.  At that time
transmission will resume.

or

c) Something else is meant.

Note:
In our implementation of SS7 MTP2 messages are not transmitted at all during
LPO.  The only reason MSUs would be pending transmission (on the Transmit
Buffer Queue) when the LPO started would be that the RTB was full and the
LPO indication came prior to being able to transmit those messages..

Thank you,
Martin Hecht
 

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



From exim@www1.ietf.org  Tue Feb 10 17:39:31 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 RAA26750
	for <sigtran-archive@odin.ietf.org>; Tue, 10 Feb 2004 17:39:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqgX2-0001wT-51
	for sigtran-archive@odin.ietf.org; Tue, 10 Feb 2004 17:39:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1AMd4vC007443
	for sigtran-archive@odin.ietf.org; Tue, 10 Feb 2004 17:39:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqgWz-0001vq-Lh; Tue, 10 Feb 2004 17:39:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqgWI-0001kv-NZ
	for sigtran@optimus.ietf.org; Tue, 10 Feb 2004 17:38:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26709
	for <sigtran@ietf.org>; Tue, 10 Feb 2004 17:38:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqgWG-0002Fl-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 17:38:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqgVH-00029I-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 17:37:16 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[kLfr4T9v8xXMhmmzoYvnSoYKFP2Df3r3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqgUk-00023a-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 17:36:42 -0500
Received: from ns.pigworks.openss7.net (IDENT:fQa0bJi4gUHmY6LYJ6xuLI+giHoCwpQD@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1AMafI02097;
	Tue, 10 Feb 2004 15:36:41 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1AMaei24712;
	Tue, 10 Feb 2004 15:36:40 -0700
Date: Tue, 10 Feb 2004 15:36:40 -0700
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
Message-ID: <20040210153640.A23493@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: <6B1DF6EEBA51D31182F20090274043680B6E774B@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: <6B1DF6EEBA51D31182F20090274043680B6E774B@mail-in.comverse.com>; from Martin.Hecht@comverse.com on Tue, Feb 10, 2004 at 04:00:05PM -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>

Hecht,

Hecht Martin wrote:                                                                  (Tue, 10 Feb 2004 16:00:05)
> To whomever is interested in answering this enquiry:
> 
> In Section 4.1.4 (draft 11) it states:
> 
> 	While in a local processor outage (LPO) condition:
> 
> 	   (c) M2PA SHOULD continue to transmit messages that have been sent
> by its upper layer MTP3.
> 
> Further on it states:
> 
> 	When the local processor outage condition ends,....
> 
> 	M2PA SHALL NOT resume transmitting User Data messages until it has
> received the Link Status Ready message.
> 
> So, I am trying to understand these two statements.
> 
> Does it mean:
> 
> a) That M2PA should transmit messages received from MTP3 prior to the LPO
> indication. But not transmit messages from its MTP3 received after LPO,
> until LPR (Processor Recovered).  Then, when the Ready is received to start
> transmitting them.
> 
> or
> 
> b) That transmission continues throughout the LPO condition, but that when
> M2PA sends the Processor Recovered Link Status Message it must suspend
> transmission until the Ready is received from the peer.  At that time
> transmission will resume.

This one.  LSPR is sent in the data stream and no messages should be sent
after the LSPR until LSR is received (also in the data stream) and sequence
numbers sychronized.

Maybe we should have said more explicity that sending of data messages is
suppressed between sending of LSPR and reception of LSR.

> 
> or
> 
> c) Something else is meant.
> 
> Note:
> In our implementation of SS7 MTP2 messages are not transmitted at all during
> LPO.  The only reason MSUs would be pending transmission (on the Transmit
> Buffer Queue) when the LPO started would be that the RTB was full and the
> LPO indication came prior to being able to transmit those messages..

The point is that you SHOULD continue to send those messages in the TB after
the LPO condition, unlike Q.703 which blocks them in the TB because it must
send continuous SIPO.  So, it is recomended to send messages during LPO.

In addition (c) in 4.1.4 was meant to handle the case (in some implementations
where the data path and control path are independent) where there is a local
processor outage (control path), but M2PA continues to receive messages from
MTP3 (data path).

--brian

> 
> Thank you,
> Martin Hecht
>  
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Wed Feb 11 10:19: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 KAA04910
	for <sigtran-archive@odin.ietf.org>; Wed, 11 Feb 2004 10:19:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aqw8n-0007RI-Bk
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 10:19:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1BFJ5uC028570
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 10:19:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aqw8j-0007MI-9I; Wed, 11 Feb 2004 10:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aqw8S-0007Dj-3F
	for sigtran@optimus.ietf.org; Wed, 11 Feb 2004 10:18:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04869
	for <sigtran@ietf.org>; Wed, 11 Feb 2004 10:18:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aqw8P-0006ZQ-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 10:18:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aqw7R-0006Se-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 10:17:42 -0500
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 1Aqw6U-0006Mp-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 10:16:42 -0500
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 i1BFGc511163;
	Wed, 11 Feb 2004 10:16:39 -0500
Received: by mail-in.comverse.com with Internet Mail Service (5.5.2657.72)
	id <1WLM8PKM>; Wed, 11 Feb 2004 10:09:41 -0500
Message-ID: <6B1DF6EEBA51D31182F20090274043680B6E774C@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
Date: Wed, 11 Feb 2004 10:09:40 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,

Thank you for your answer.  Your answer leads me to further questions:

1) M2PA is sending User Data messages during LPO and the peer is ACKing
these messages.  This implies, according to the spec, that the M2PA in LPO
is processing the ACK but still buffering the incoming User Data messages.
Is this correct?

2) How "deep" should the buffering be?  If the buffer becomes full does M2PA
start to discard incoming messages?

3) Does resynchronization imply retransmission?  What of the case where
buffers were discarded due to "item 2 above" or some other reason such as a
packet in error? What if the peer provides a BSN that is less than the last
FSN transmitted?  Does M2PA retransmit at this point?

And a general question concerning the fact that there is no retransmission.
If a packet is discarded, due to Bad BSN or other reason, this packet is
lost?

Thanks for your time,
Martin


-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: Tuesday, February 10, 2004 5:37 PM
To: Hecht Martin
Cc: SIGTRAN Mailing List (E-mail)
Subject: Re: [SIGTRAN] M2PA - Local Processor Outage


Hecht,

Hecht Martin wrote:
(Tue, 10 Feb 2004 16:00:05)
> To whomever is interested in answering this enquiry:
> 
> In Section 4.1.4 (draft 11) it states:
> 
> 	While in a local processor outage (LPO) condition:
> 
> 	   (c) M2PA SHOULD continue to transmit messages that have been sent
> by its upper layer MTP3.
> 
> Further on it states:
> 
> 	When the local processor outage condition ends,....
> 
> 	M2PA SHALL NOT resume transmitting User Data messages until it has
> received the Link Status Ready message.
> 
> So, I am trying to understand these two statements.
> 
> Does it mean:
> 
> a) That M2PA should transmit messages received from MTP3 prior to the LPO
> indication. But not transmit messages from its MTP3 received after LPO,
> until LPR (Processor Recovered).  Then, when the Ready is received to
start
> transmitting them.
> 
> or
> 
> b) That transmission continues throughout the LPO condition, but that when
> M2PA sends the Processor Recovered Link Status Message it must suspend
> transmission until the Ready is received from the peer.  At that time
> transmission will resume.

This one.  LSPR is sent in the data stream and no messages should be sent
after the LSPR until LSR is received (also in the data stream) and sequence
numbers sychronized.

Maybe we should have said more explicity that sending of data messages is
suppressed between sending of LSPR and reception of LSR.

> 
> or
> 
> c) Something else is meant.
> 
> Note:
> In our implementation of SS7 MTP2 messages are not transmitted at all
during
> LPO.  The only reason MSUs would be pending transmission (on the Transmit
> Buffer Queue) when the LPO started would be that the RTB was full and the
> LPO indication came prior to being able to transmit those messages..

The point is that you SHOULD continue to send those messages in the TB after
the LPO condition, unlike Q.703 which blocks them in the TB because it must
send continuous SIPO.  So, it is recomended to send messages during LPO.

In addition (c) in 4.1.4 was meant to handle the case (in some
implementations
where the data path and control path are independent) where there is a local
processor outage (control path), but M2PA continues to receive messages from
MTP3 (data path).

--brian

> 
> Thank you,
> Martin Hecht
>  
> 
> _______________________________________________
> 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  Wed Feb 11 16:25:39 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 QAA26805
	for <sigtran-archive@odin.ietf.org>; Wed, 11 Feb 2004 16:25:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar1r4-0008GE-Qx
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 16:25:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1BLPAja031752
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 16:25:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar1qw-0008Ff-RK; Wed, 11 Feb 2004 16:25:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar1q6-00089v-1C
	for sigtran@optimus.ietf.org; Wed, 11 Feb 2004 16:24:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26439
	for <sigtran@ietf.org>; Wed, 11 Feb 2004 16:24:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar1q3-0001Ok-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 16:24:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ar1oW-000116-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 16:22:33 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar1nV-0000m6-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 16:21:29 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[gYig8dSEmeFANWOLpBw5R646XjJ2UPag])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Ar1i4-0006IY-U3
	for sigtran@ietf.org; Wed, 11 Feb 2004 16:15:53 -0500
Received: from ns.pigworks.openss7.net (IDENT:D/yhr3RCdP8nbyAO6xjDX7oYif2TtgYz@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1BLFkI27809;
	Wed, 11 Feb 2004 14:15:46 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1BLFji13206;
	Wed, 11 Feb 2004 14:15:45 -0700
Date: Wed, 11 Feb 2004 14:15:45 -0700
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
Message-ID: <20040211141545.B12496@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: <6B1DF6EEBA51D31182F20090274043680B6E774C@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: <6B1DF6EEBA51D31182F20090274043680B6E774C@mail-in.comverse.com>; from Martin.Hecht@comverse.com on Wed, Feb 11, 2004 at 10:09:40AM -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>

Hecht,

Hecht Martin wrote:                                                                  (Wed, 11 Feb 2004 10:09:40)
> Brian,
> 
> Thank you for your answer.  Your answer leads me to further questions:
> 
> 1) M2PA is sending User Data messages during LPO and the peer is ACKing
> these messages.  This implies, according to the spec, that the M2PA in LPO
> is processing the ACK but still buffering the incoming User Data messages.
> Is this correct?

Yes.

> 
> 2) How "deep" should the buffering be?  If the buffer becomes full does M2PA
> start to discard incoming messages?

No, messages are not discarded.  If the receiving M2PA can no longer
buffer messages it should stop servicing the read side of SCTP,
resulting in a closed arwnd at the peer and the peer's SCTP send buffer
will fill.  This should not persist for long (just while the LSPO is in
transit) because the peer M2PA will inform MTP3 of remote processor
outage and MTP3 will block the link.  To avoid link failure due to a
transmit congestion situation before LSPO is indicated, SCTP buffers
should have same sizing on both ends of the link.  The size of the M2PA
RB is not really the issue.

> 
> 3) Does resynchronization imply retransmission?  What of the case where
> buffers were discarded due to "item 2 above" or some other reason such as a
> packet in error? What if the peer provides a BSN that is less than the last
> FSN transmitted?  Does M2PA retransmit at this point?

M2PA does not retransmit.  SCTP (or MTP3) performs all necessary
retransmissions.

> 
> And a general question concerning the fact that there is no retransmission.
> If a packet is discarded, due to Bad BSN or other reason, this packet is
> lost?

Packets are not discarded, in general.  A bad BSN is a strange event and
would likely be due to a broken peer or a late arriving message from a
restarted peer (where M2PA restarts but SCTP does not) and is likely a
cause for link failure.

--brian

> 
> Thanks for your time,
> Martin
> 
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Tuesday, February 10, 2004 5:37 PM
> To: Hecht Martin
> Cc: SIGTRAN Mailing List (E-mail)
> Subject: Re: [SIGTRAN] M2PA - Local Processor Outage
> 
> 
> Hecht,
> 
> Hecht Martin wrote:
> (Tue, 10 Feb 2004 16:00:05)
> > To whomever is interested in answering this enquiry:
> > 
> > In Section 4.1.4 (draft 11) it states:
> > 
> > 	While in a local processor outage (LPO) condition:
> > 
> > 	   (c) M2PA SHOULD continue to transmit messages that have been sent
> > by its upper layer MTP3.
> > 
> > Further on it states:
> > 
> > 	When the local processor outage condition ends,....
> > 
> > 	M2PA SHALL NOT resume transmitting User Data messages until it has
> > received the Link Status Ready message.
> > 
> > So, I am trying to understand these two statements.
> > 
> > Does it mean:
> > 
> > a) That M2PA should transmit messages received from MTP3 prior to the LPO
> > indication. But not transmit messages from its MTP3 received after LPO,
> > until LPR (Processor Recovered).  Then, when the Ready is received to
> start
> > transmitting them.
> > 
> > or
> > 
> > b) That transmission continues throughout the LPO condition, but that when
> > M2PA sends the Processor Recovered Link Status Message it must suspend
> > transmission until the Ready is received from the peer.  At that time
> > transmission will resume.
> 
> This one.  LSPR is sent in the data stream and no messages should be sent
> after the LSPR until LSR is received (also in the data stream) and sequence
> numbers sychronized.
> 
> Maybe we should have said more explicity that sending of data messages is
> suppressed between sending of LSPR and reception of LSR.
> 
> > 
> > or
> > 
> > c) Something else is meant.
> > 
> > Note:
> > In our implementation of SS7 MTP2 messages are not transmitted at all
> during
> > LPO.  The only reason MSUs would be pending transmission (on the Transmit
> > Buffer Queue) when the LPO started would be that the RTB was full and the
> > LPO indication came prior to being able to transmit those messages..
> 
> The point is that you SHOULD continue to send those messages in the TB after
> the LPO condition, unlike Q.703 which blocks them in the TB because it must
> send continuous SIPO.  So, it is recomended to send messages during LPO.
> 
> In addition (c) in 4.1.4 was meant to handle the case (in some
> implementations
> where the data path and control path are independent) where there is a local
> processor outage (control path), but M2PA continues to receive messages from
> MTP3 (data path).
> 
> --brian
> 
> > 
> > Thank you,
> > Martin Hecht
> >  
> > 
> > _______________________________________________
> > 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  Wed Feb 11 19:16: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 TAA13019
	for <sigtran-archive@odin.ietf.org>; Wed, 11 Feb 2004 19:16:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar4WS-0006Wz-RO
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 19:16:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1C0G4JE025053
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 19:16:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar4WQ-0006Us-NO; Wed, 11 Feb 2004 19:16:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqA72-0008GD-Kd
	for sigtran@optimus.ietf.org; Mon, 09 Feb 2004 07:02:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14239
	for <sigtran@ietf.org>; Mon, 9 Feb 2004 07:01:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqA6y-0004MM-00
	for sigtran@ietf.org; Mon, 09 Feb 2004 07:02:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqA62-0004Hn-00
	for sigtran@ietf.org; Mon, 09 Feb 2004 07:01:03 -0500
Received: from imo-r07.mx.aol.com ([152.163.225.103])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqA5n-0004DF-00
	for sigtran@ietf.org; Mon, 09 Feb 2004 07:00:47 -0500
Received: from Pascalbouveron@aol.com
	by imo-r07.mx.aol.com (mail_out_v36_r4.12.) id d.1e2.190eb90b (16097);
	Mon, 9 Feb 2004 07:00:00 -0500 (EST)
Received: from  PascalB (acb07493.ipt.aol.com [172.176.116.147]) by air-id11.mx.aol.com (v97.18) with ESMTP id MAILINID111-3ee14027763d338; Mon, 09 Feb 2004 06:59:59 -0500
Message-ID: <041501c3ef04$3cd31540$3797ceac@PascalB>
Reply-To: "Pascal Bouveron" <pascal.bouveron@netbricks.com>
From: "Pascal Bouveron" <pascalbouveron@aol.com>
To: "Eva Weilandt" <eva.weilandt@nortelnetworks.com>, <sigtran@ietf.org>
Cc: "Alain CHAMPENOIS" <alain.champenois@netbricks.com>
References: <9F8B82425D82D511B5AC0002A55CCCAF072ACC84@zfdhc101-int2.europe.nortel.com>
Date: Mon, 9 Feb 2004 12:59:45 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-AOL-IP: 172.176.116.147
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
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id HAA14240
Subject: [Sigtran] Silent changes to V5UA draft 04 before moving to RFC ?
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hello Eva,

Thanks for the confirmation about changes on the V5UA Message Class, and
Parameter Tags values.

I was wondering: i can't see any anouncement on the Sigtran mailing list
about the fact that the V5UA draft is moving to RFC soon. I saw it is now=
 a
"proposed standard".
As i understand it, the Mailing List is the mainstream for discussions on
the evolutions of the drafts/rfc's, right ?
I'm not familiar with the RFC procedures, but i would imagine that, befor=
e a
draft can move to RFC status, it has to be stable for a while.
Which does not seem to be the case here, considering that you have decide=
d
to change MAJOR elements of the so-called "proposed standard", and call t=
hat
an RFC, without notifying the Sigtran community thru the Mailing List.

These are major changes, as they lead to total INCOMPATIBILITY between th=
e
draft 04 and the future RFC.
Meaning that vendors developing their V5UA right now based on draft 04 wi=
ll
not be able to interop with systems based on the future RFC.

I am just a bit disappointed to see that important changes to the documen=
t
were not made public, and therefore not subject to discussion.
The good news here is that the RFC will include changes to the draft04 wh=
ich
makes it move to the right direction, i.e consistency with other UAs, whi=
ch
is good.

I would appreciate if you would clearly detail in the Mailing List the fu=
ll
changes that you are planning to apply to V5UA draft 04 before it is
approved as a new RFC, so that the community can review them quickly.

Many thanks for your efforts.

Best regards / Meilleures salutations
Pascal Bouveron
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
www.netbricks.com
Netbricks - Provence - FRANCE
Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

----- Original Message -----=20
From: Eva Weilandt
To: 'Pascal Bouveron (Netbricks)' ; 'sigtran@ietf.org'
Sent: Saturday, February 07, 2004 12:19 PM
Subject: AW: V5UA Parameter Tags conflict with M3UA Tags


Hi Pascal,

we will change the message tags together with the message class for the R=
FC
version of V5UA. This will hopefully happen soon. If you need the new tag=
s
in the meantime, let me know.

Thanks for pointing this out. It is always helpful if someone proof-read
your documents :-)

Eva
-----Urspr=FCngliche Nachricht-----
Von: Pascal Bouveron (Netbricks) [mailto:pascal.bouveron@netbricks.com]
Gesendet: February 2, 2004 11:28 AM
An: Weilandt, Eva [FRIED:NRA11:EXCH]; sigtran@ietf.org
Betreff: V5UA Parameter Tags conflict with M3UA Tags


Hello,

I found other conflicts between V5UA and other UAs, in the Parameter Tags
definitions:

Tag 0x0011: "ASP Identifier" for M3UA, but "Link Status" for V5UA
Tag 0x0012: "Affected Point Code" for M3UA, but "Sa-Bit" (it actually has=
 no
name in draft-04) for V5UA
Tag 0x0013: "Correlation Id" for M3UA, but "Error Reason" for V5UA

Best regards / Meilleures salutations
Pascal Bouveron
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
www.netbricks.com
Netbricks - Provence - FRANCE
Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From exim@www1.ietf.org  Wed Feb 11 19:29: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 TAA13604
	for <sigtran-archive@odin.ietf.org>; Wed, 11 Feb 2004 19:29:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar4j0-00083a-0j
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 19:29:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1C0T144030953
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 19:29:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar4iz-000835-53; Wed, 11 Feb 2004 19:29:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar4ih-00081O-D7
	for sigtran@optimus.ietf.org; Wed, 11 Feb 2004 19:28:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13592
	for <sigtran@ietf.org>; Wed, 11 Feb 2004 19:28:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar4if-0004O4-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 19:28:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ar4hi-0004IX-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 19:27:43 -0500
Received: from sjmail.ciena.com ([12.7.169.25] helo=w2ksjexg01.ciena.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar4gp-0004Cc-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 19:26:48 -0500
Received: by w2ksjexg01.ciena.com with Internet Mail Service (5.5.2657.72)
	id <1JQBTMLL>; Wed, 11 Feb 2004 16:26:26 -0800
Message-ID: <829F074A10F98943A218DC363D09C92A01476984@w2ksjexg06.oni.com>
From: "Ong, Lyndon" <LyOng@Ciena.com>
To: "'Pascal Bouveron'" <pascal.bouveron@netbricks.com>,
        Eva Weilandt
	 <eva.weilandt@nortelnetworks.com>, sigtran@ietf.org
Cc: Alain CHAMPENOIS <alain.champenois@netbricks.com>
Subject: RE: [Sigtran] Silent changes to V5UA draft 04 before moving to RF
	C ?
Date: Wed, 11 Feb 2004 16:26:45 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 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

Hi Pascal,

I think the confusion here is that V5UA progressed to WG approval
some time ago and it is only recently that these tag issues have
come up (of course they should have come up earlier, but that is
hindsight).

Eva rightly sent out a message to the WG list with the changes.
I believe that the intent of the changes is beneficial to all,
including any folks with previous implementations.  Hopefully
people will be able to make the changes without serious=20
difficulty.

It sounds like what you would like is for Eva to release another
version with the changes in it so that you can see the full=20
impact, and then have a more formal comment period.  Would that
help you?

Cheers,

L. Ong

-----Original Message-----
From: Pascal Bouveron [mailto:pascalbouveron@aol.com]
Sent: Monday, February 09, 2004 4:00 AM
To: Eva Weilandt; sigtran@ietf.org
Cc: Alain CHAMPENOIS
Subject: [Sigtran] Silent changes to V5UA draft 04 before moving to RFC
?


Hello Eva,

Thanks for the confirmation about changes on the V5UA Message Class, =
and
Parameter Tags values.

I was wondering: i can't see any anouncement on the Sigtran mailing =
list
about the fact that the V5UA draft is moving to RFC soon. I saw it is =
now a
"proposed standard".
As i understand it, the Mailing List is the mainstream for discussions =
on
the evolutions of the drafts/rfc's, right ?
I'm not familiar with the RFC procedures, but i would imagine that, =
before a
draft can move to RFC status, it has to be stable for a while.
Which does not seem to be the case here, considering that you have =
decided
to change MAJOR elements of the so-called "proposed standard", and call =
that
an RFC, without notifying the Sigtran community thru the Mailing List.

These are major changes, as they lead to total INCOMPATIBILITY between =
the
draft 04 and the future RFC.
Meaning that vendors developing their V5UA right now based on draft 04 =
will
not be able to interop with systems based on the future RFC.

I am just a bit disappointed to see that important changes to the =
document
were not made public, and therefore not subject to discussion.
The good news here is that the RFC will include changes to the draft04 =
which
makes it move to the right direction, i.e consistency with other UAs, =
which
is good.

I would appreciate if you would clearly detail in the Mailing List the =
full
changes that you are planning to apply to V5UA draft 04 before it is
approved as a new RFC, so that the community can review them quickly.

Many thanks for your efforts.

Best regards / Meilleures salutations
Pascal Bouveron
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
www.netbricks.com
Netbricks - Provence - FRANCE
Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

----- Original Message -----=20
From: Eva Weilandt
To: 'Pascal Bouveron (Netbricks)' ; 'sigtran@ietf.org'
Sent: Saturday, February 07, 2004 12:19 PM
Subject: AW: V5UA Parameter Tags conflict with M3UA Tags


Hi Pascal,

we will change the message tags together with the message class for the =
RFC
version of V5UA. This will hopefully happen soon. If you need the new =
tags
in the meantime, let me know.

Thanks for pointing this out. It is always helpful if someone =
proof-read
your documents :-)

Eva
-----Urspr=FCngliche Nachricht-----
Von: Pascal Bouveron (Netbricks) [mailto:pascal.bouveron@netbricks.com]
Gesendet: February 2, 2004 11:28 AM
An: Weilandt, Eva [FRIED:NRA11:EXCH]; sigtran@ietf.org
Betreff: V5UA Parameter Tags conflict with M3UA Tags


Hello,

I found other conflicts between V5UA and other UAs, in the Parameter =
Tags
definitions:

Tag 0x0011: "ASP Identifier" for M3UA, but "Link Status" for V5UA
Tag 0x0012: "Affected Point Code" for M3UA, but "Sa-Bit" (it actually =
has no
name in draft-04) for V5UA
Tag 0x0013: "Correlation Id" for M3UA, but "Error Reason" for V5UA

Best regards / Meilleures salutations
Pascal Bouveron
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
www.netbricks.com
Netbricks - Provence - FRANCE
Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


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

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



From exim@www1.ietf.org  Wed Feb 11 19:57: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 TAA15594
	for <sigtran-archive@odin.ietf.org>; Wed, 11 Feb 2004 19:57:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar5A6-0001VN-Uz
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 19:57:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1C0v2WS005782
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 19:57:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar5A4-0001Uu-Sk; Wed, 11 Feb 2004 19:57:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar59q-0001Tk-Gc
	for sigtran@optimus.ietf.org; Wed, 11 Feb 2004 19:56:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15546
	for <sigtran@ietf.org>; Wed, 11 Feb 2004 19:56:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar59o-0000Rx-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 19:56:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ar58q-0000LH-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 19:55:45 -0500
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar57v-0000EM-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 19:54:47 -0500
Received: from [10.0.1.3] (p5089EA4A.dip.t-dialin.net [80.137.234.74])
	by mail-n.franken.de (Postfix) with ESMTP
	id 7EE5724636; Thu, 12 Feb 2004 01:53:26 +0100 (CET)
In-Reply-To: <041501c3ef04$3cd31540$3797ceac@PascalB>
References: <9F8B82425D82D511B5AC0002A55CCCAF072ACC84@zfdhc101-int2.europe.nortel.com> <041501c3ef04$3cd31540$3797ceac@PascalB>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <B5EA0C6A-5CF5-11D8-8E04-000A95C37894@lurchi.franken.de>
Content-Transfer-Encoding: quoted-printable
Cc: "Eva Weilandt" <eva.weilandt@nortelnetworks.com>, <sigtran@ietf.org>,
        "Alain CHAMPENOIS" <alain.champenois@netbricks.com>
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Sigtran] Silent changes to V5UA draft 04 before moving to RFC ?
Date: Thu, 12 Feb 2004 01:52:19 +0100
To: "Pascal Bouveron" <pascal.bouveron@netbricks.com>
X-Mailer: Apple Mail (2.612)
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: 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

Pascal,

there was a WG last call on the document a long time ago.

What 'important changes' are you talking about?

I do understand that the change of tags (or other numbers) breaks
interoperability, but if I'm right all these numbers are handled
by IANA and IANA looks at the documents after IESG approval. So these
numbers can change right lately. The numbers chosen by the authors
of the IDs are 'just recommendations'.

But in this concrete case the question is:

Do you prefer to keep the old numbers and therefore have them not
coherent between all adaptation layers

or

Do you prefer to change the numbers and have them coherent between
all adaptation layers?

What do others think?

Best regards
Michael

PS.: We do have similar problems with other adaptation layers: I know
      that there are M3UA versions deployed based on version 5, version=20=

6,
      version 7 and the RFC. And all have their 'own' tag values.=20
Hopefully
      all will upgrade to the RFC version...


On 9. Feb 2004, at 12:59 Uhr, Pascal Bouveron wrote:

> Hello Eva,
>
> Thanks for the confirmation about changes on the V5UA Message Class,=20=

> and
> Parameter Tags values.
>
> I was wondering: i can't see any anouncement on the Sigtran mailing=20
> list
> about the fact that the V5UA draft is moving to RFC soon. I saw it is=20=

> now a
> "proposed standard".
> As i understand it, the Mailing List is the mainstream for discussions=20=

> on
> the evolutions of the drafts/rfc's, right ?
> I'm not familiar with the RFC procedures, but i would imagine that,=20
> before a
> draft can move to RFC status, it has to be stable for a while.
> Which does not seem to be the case here, considering that you have=20
> decided
> to change MAJOR elements of the so-called "proposed standard", and=20
> call that
> an RFC, without notifying the Sigtran community thru the Mailing List.
>
> These are major changes, as they lead to total INCOMPATIBILITY between=20=

> the
> draft 04 and the future RFC.
> Meaning that vendors developing their V5UA right now based on draft 04=20=

> will
> not be able to interop with systems based on the future RFC.
>
> I am just a bit disappointed to see that important changes to the=20
> document
> were not made public, and therefore not subject to discussion.
> The good news here is that the RFC will include changes to the draft04=20=

> which
> makes it move to the right direction, i.e consistency with other UAs,=20=

> which
> is good.
>
> I would appreciate if you would clearly detail in the Mailing List the=20=

> full
> changes that you are planning to apply to V5UA draft 04 before it is
> approved as a new RFC, so that the community can review them quickly.
>
> Many thanks for your efforts.
>
> Best regards / Meilleures salutations
> Pascal Bouveron
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> www.netbricks.com
> Netbricks - Provence - FRANCE
> Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> ----- Original Message -----
> From: Eva Weilandt
> To: 'Pascal Bouveron (Netbricks)' ; 'sigtran@ietf.org'
> Sent: Saturday, February 07, 2004 12:19 PM
> Subject: AW: V5UA Parameter Tags conflict with M3UA Tags
>
>
> Hi Pascal,
>
> we will change the message tags together with the message class for=20
> the RFC
> version of V5UA. This will hopefully happen soon. If you need the new=20=

> tags
> in the meantime, let me know.
>
> Thanks for pointing this out. It is always helpful if someone=20
> proof-read
> your documents :-)
>
> Eva
> -----Urspr=FCngliche Nachricht-----
> Von: Pascal Bouveron (Netbricks) =
[mailto:pascal.bouveron@netbricks.com]
> Gesendet: February 2, 2004 11:28 AM
> An: Weilandt, Eva [FRIED:NRA11:EXCH]; sigtran@ietf.org
> Betreff: V5UA Parameter Tags conflict with M3UA Tags
>
>
> Hello,
>
> I found other conflicts between V5UA and other UAs, in the Parameter=20=

> Tags
> definitions:
>
> Tag 0x0011: "ASP Identifier" for M3UA, but "Link Status" for V5UA
> Tag 0x0012: "Affected Point Code" for M3UA, but "Sa-Bit" (it actually=20=

> has no
> name in draft-04) for V5UA
> Tag 0x0013: "Correlation Id" for M3UA, but "Error Reason" for V5UA
>
> Best regards / Meilleures salutations
> Pascal Bouveron
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> www.netbricks.com
> Netbricks - Provence - FRANCE
> Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>


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



From exim@www1.ietf.org  Wed Feb 11 19:59: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 TAA15746
	for <sigtran-archive@odin.ietf.org>; Wed, 11 Feb 2004 19:59:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar5C1-0001eY-EM
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 19:59:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1C0x1Cp006327
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 19:59:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar5C1-0001dx-89; Wed, 11 Feb 2004 19:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar5Bt-0001df-0s
	for sigtran@optimus.ietf.org; Wed, 11 Feb 2004 19:58:53 -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 TAA15700
	for <sigtran@ietf.org>; Wed, 11 Feb 2004 19:58:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar5Bq-0000gr-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 19:58:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ar5B2-0000aQ-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 19:58:01 -0500
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar5AJ-0000UB-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 19:57:15 -0500
Received: from [10.0.1.3] (p5089EA4A.dip.t-dialin.net [80.137.234.74])
	by mail-n.franken.de (Postfix) with ESMTP
	id 2BED02461D; Thu, 12 Feb 2004 01:55:58 +0100 (CET)
In-Reply-To: <53CD1252F68ED61183F5000347AE5F5505EBFC4C@G8PPZ.blf01.telekom.de>
References: <53CD1252F68ED61183F5000347AE5F5505EBFC4C@G8PPZ.blf01.telekom.de>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <10630257-5CF6-11D8-8E04-000A95C37894@lurchi.franken.de>
Content-Transfer-Encoding: quoted-printable
Cc: sigtran@ietf.org
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Sigtran] Stream Mapping
Date: Thu, 12 Feb 2004 01:54:51 +0100
To: "Poetzl, Joachim" <Joachim.Poetzl@t-com.net>
X-Mailer: Apple Mail (2.612)
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: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi,

the principle (management messages on stream 0, the rest on other=20
streams) is
also used in other adaptation layers, but this does not mean that it is
specified how the stream mapping has to be done. Implementations are=20
free to
choose which stream to use for a particular non management message. Only
the SS7 restrictions apply.

Best regards
Michael


On 10. Feb 2004, at 15:21 Uhr, Poetzl, Joachim wrote:

> Hi,
>
> could someone help on that:
>
> In SUAv16 it is explicitly statet, how stream mapping has to be done -=20=

> stream 0 is reserved for management messages.
>
> Is this somewhere required for the other user adaption layers as well?=20=

> I haven=B4t found it anywhere.
>
> Thanks
>
> snip--
>
>
> 1.5.4 SCTP Stream Mapping
>
>    The SUA supports SCTP streams. Signalling Gateway SG and =
Application
>    Servers need to maintain a list of SCTP and SUA-users for mapping
>    purposes.  SCCP-users requiring sequenced message transfer need to
>    be sent over a stream with sequenced delivery.
>
>    SUA uses stream 0 for SUA management messages.  It is OPTIONAL that
>    sequenced delivery be used to preserve the order of management
>    message delivery.
>
> --snap
>
>
>> Best Regards
>>
>> Joachim P=F6tzl
> Deutsche Telekom AG
> T-Com Zentrale
> T332-4; Signalling, Gateways and Switching Systems
> 64307 DARMSTADT, GERMANY
> Phone:  +49 6151 83-2134
> Fax:      +49 6151 83-4577
> PCFax:  +49 521 52244 983
>> mailto:joachim.poetzl@t-com.net
>>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>


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



From exim@www1.ietf.org  Wed Feb 11 20:01: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 TAA13018
	for <sigtran-archive@odin.ietf.org>; Wed, 11 Feb 2004 19:16:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar4WS-0006X0-Rf
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 19:16:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1C0G44A025055
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 19:16:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar4WR-0006VL-93; Wed, 11 Feb 2004 19:16:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqYns-0006AQ-Co
	for sigtran@optimus.ietf.org; Tue, 10 Feb 2004 09:23:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19567
	for <sigtran@ietf.org>; Tue, 10 Feb 2004 09:23:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqYnq-0004tO-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 09:23:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqYmz-0004nr-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 09:23:02 -0500
Received: from mail4.telekom.de ([195.243.210.197])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqYm3-0004bm-00
	for sigtran@ietf.org; Tue, 10 Feb 2004 09:22:03 -0500
Received: from g8pbr.blf01.telekom.de by mail2.dmz.telekom.de with ESMTP for sigtran@ietf.org; Tue, 10 Feb 2004 15:21:19 +0100
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <1SQ47C6W>; Tue, 10 Feb 2004 15:21:14 +0100
Message-Id: <53CD1252F68ED61183F5000347AE5F5505EBFC4C@G8PPZ.blf01.telekom.de>
From: "Poetzl, Joachim" <Joachim.Poetzl@t-com.net>
To: sigtran@ietf.org
Date: Tue, 10 Feb 2004 15:21:14 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Subject: [Sigtran] Stream Mapping
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi,

could someone help on that:

In SUAv16 it is explicitly statet, how stream mapping has to be done - =
stream 0 is reserved for management messages.

Is this somewhere required for the other user adaption layers as well? =
I haven=B4t found it anywhere.

Thanks

snip--

   =20
1.5.4 SCTP Stream Mapping=20
   =20
   The SUA supports SCTP streams. Signalling Gateway SG and Application =

   Servers need to maintain a list of SCTP and SUA-users for mapping=20
   purposes.  SCCP-users requiring sequenced message transfer need to=20
   be sent over a stream with sequenced delivery.=20
   =20
   SUA uses stream 0 for SUA management messages.  It is OPTIONAL that=20
   sequenced delivery be used to preserve the order of management=20
   message delivery.=20
   =20
--snap


> Best Regards
>=20
> Joachim P=F6tzl
Deutsche Telekom AG
T-Com Zentrale
T332-4; Signalling, Gateways and Switching Systems
64307 DARMSTADT, GERMANY=20
Phone:  +49 6151 83-2134
Fax:      +49 6151 83-4577
PCFax:  +49 521 52244 983
> mailto:joachim.poetzl@t-com.net=20
>=20

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



From exim@www1.ietf.org  Wed Feb 11 20: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 UAA17055
	for <sigtran-archive@odin.ietf.org>; Wed, 11 Feb 2004 20:24:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar5aG-0003vp-Fo
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 20:24:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1C1O4r8015090
	for sigtran-archive@odin.ietf.org; Wed, 11 Feb 2004 20:24:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar5aD-0003vD-8X; Wed, 11 Feb 2004 20:24:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar5Zy-0003uR-Tr
	for sigtran@optimus.ietf.org; Wed, 11 Feb 2004 20:23:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17047
	for <sigtran@ietf.org>; Wed, 11 Feb 2004 20:23:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar5Zw-0003SN-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 20:23:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ar5Yz-0003N9-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 20:22:46 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[USJhxM/fiAQ375ygYTeXB8HMcMAYl6UG])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar5Y2-0003He-00
	for sigtran@ietf.org; Wed, 11 Feb 2004 20:21:47 -0500
Received: from ns.pigworks.openss7.net (IDENT:XSzqfkwA4n6SxZS3vzF2iwZp9Rsp2ovN@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1C1LiI32209;
	Wed, 11 Feb 2004 18:21:44 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1C1LhN16578;
	Wed, 11 Feb 2004 18:21:43 -0700
Date: Wed, 11 Feb 2004 18:21:43 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Pascal Bouveron <pascalbouveron@aol.com>
Cc: Eva Weilandt <eva.weilandt@nortelnetworks.com>, sigtran@ietf.org,
        Alain CHAMPENOIS <alain.champenois@netbricks.com>
Subject: Re: [Sigtran] Silent changes to V5UA draft 04 before moving to RFC ?
Message-ID: <20040211182143.A15843@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Pascal Bouveron <pascalbouveron@aol.com>,
	Eva Weilandt <eva.weilandt@nortelnetworks.com>, sigtran@ietf.org,
	Alain CHAMPENOIS <alain.champenois@netbricks.com>
References: <9F8B82425D82D511B5AC0002A55CCCAF072ACC84@zfdhc101-int2.europe.nortel.com> <041501c3ef04$3cd31540$3797ceac@PascalB>
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: <041501c3ef04$3cd31540$3797ceac@PascalB>; from pascalbouveron@aol.com on Mon, Feb 09, 2004 at 12:59:45PM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i1C1LiI32209
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

Pascal,

Pascal Bouveron wrote:                                                   =
           (Mon, 09 Feb 2004 12:59:45)
> Hello Eva,
>=20
> Thanks for the confirmation about changes on the V5UA Message Class, an=
d
> Parameter Tags values.
>=20
> I was wondering: i can't see any anouncement on the Sigtran mailing lis=
t
> about the fact that the V5UA draft is moving to RFC soon. I saw it is n=
ow a
> "proposed standard".
> As i understand it, the Mailing List is the mainstream for discussions =
on
> the evolutions of the drafts/rfc's, right ?
> I'm not familiar with the RFC procedures, but i would imagine that, bef=
ore a
> draft can move to RFC status, it has to be stable for a while.
> Which does not seem to be the case here, considering that you have deci=
ded
> to change MAJOR elements of the so-called "proposed standard", and call=
 that
> an RFC, without notifying the Sigtran community thru the Mailing List.
>=20
> These are major changes, as they lead to total INCOMPATIBILITY between =
the
> draft 04 and the future RFC.

Someone correct me if I'm wrong, but:

An internet-draft is just that: a draft.  No compatibility, whether backw=
ards
or forwards is necessary between drafts.  Implementation of a draft is fo=
r
protocol development purposes only.  A protocol is not a "Proposed Standa=
rd"
until it acheives RFC status.  Drafts are working group documents and not
intended for general implementation.

> Meaning that vendors developing their V5UA right now based on draft 04 =
will
> not be able to interop with systems based on the future RFC.

That is the risk one takes by implementing a draft.

>=20
> I am just a bit disappointed to see that important changes to the docum=
ent
> were not made public, and therefore not subject to discussion.

Tag values are not important changes: they affect neither the design nor =
the
operation of the protocol.  Assignment of numbers is a matter for IANA an=
d,
until the protocol moves to RFC, are not maintained.  Crossing the t's an=
d
dotting the i's in this manner is fairly common practice in the RFC
development process, at least within the SIGTRAN working group.

> The good news here is that the RFC will include changes to the draft04 =
which
> makes it move to the right direction, i.e consistency with other UAs, w=
hich
> is good.
>=20
> I would appreciate if you would clearly detail in the Mailing List the =
full
> changes that you are planning to apply to V5UA draft 04 before it is
> approved as a new RFC, so that the community can review them quickly.

That said, it makes sense to release a final draft.

--brian

>=20
> Many thanks for your efforts.
>=20
> Best regards / Meilleures salutations
> Pascal Bouveron
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> www.netbricks.com
> Netbricks - Provence - FRANCE
> Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> ----- Original Message -----=20
> From: Eva Weilandt
> To: 'Pascal Bouveron (Netbricks)' ; 'sigtran@ietf.org'
> Sent: Saturday, February 07, 2004 12:19 PM
> Subject: AW: V5UA Parameter Tags conflict with M3UA Tags
>=20
>=20
> Hi Pascal,
>=20
> we will change the message tags together with the message class for the=
 RFC
> version of V5UA. This will hopefully happen soon. If you need the new t=
ags
> in the meantime, let me know.
>=20
> Thanks for pointing this out. It is always helpful if someone proof-rea=
d
> your documents :-)
>=20
> Eva
> -----Urspr=FCngliche Nachricht-----
> Von: Pascal Bouveron (Netbricks) [mailto:pascal.bouveron@netbricks.com]
> Gesendet: February 2, 2004 11:28 AM
> An: Weilandt, Eva [FRIED:NRA11:EXCH]; sigtran@ietf.org
> Betreff: V5UA Parameter Tags conflict with M3UA Tags
>=20
>=20
> Hello,
>=20
> I found other conflicts between V5UA and other UAs, in the Parameter Ta=
gs
> definitions:
>=20
> Tag 0x0011: "ASP Identifier" for M3UA, but "Link Status" for V5UA
> Tag 0x0012: "Affected Point Code" for M3UA, but "Sa-Bit" (it actually h=
as no
> name in draft-04) for V5UA
> Tag 0x0013: "Correlation Id" for M3UA, but "Error Reason" for V5UA
>=20
> Best regards / Meilleures salutations
> Pascal Bouveron
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> www.netbricks.com
> Netbricks - Provence - FRANCE
> Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Feb 12 03:56: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 DAA15012
	for <sigtran-archive@odin.ietf.org>; Thu, 12 Feb 2004 03:56:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArCdi-0002o2-8q
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 03:56:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1C8u6O9010777
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 03:56:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArCde-0002nZ-PW; Thu, 12 Feb 2004 03:56:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArCcg-0002kf-Ue
	for sigtran@optimus.ietf.org; Thu, 12 Feb 2004 03:55:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14999
	for <sigtran@ietf.org>; Thu, 12 Feb 2004 03:55:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArCce-00017n-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 03:55:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArCbf-00010z-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 03:54:01 -0500
Received: from znsgs01r.nortelnetworks.com ([47.166.48.91])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArCai-0000qP-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 03:53:00 -0500
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.160.46.124])
	by znsgs01r.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i1C8qNR11532;
	Thu, 12 Feb 2004 08:52:23 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1W6WF4J4>; Thu, 12 Feb 2004 08:52:23 -0000
Message-ID: <9F8B82425D82D511B5AC0002A55CCCAF0737A982@zfdhc101-int2.europe.nortel.com>
From: "Eva Weilandt" <eva.weilandt@nortelnetworks.com>
To: "'Ong, Lyndon'" <LyOng@Ciena.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>,
        "'bidulock@openss7.org'"
	 <bidulock@openss7.org>
Subject: AW: [Sigtran] Silent changes to V5UA draft 04 before moving to RF
	C ?
Date: Thu, 12 Feb 2004 08:52:20 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3F145.8625C308"
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_01C3F145.8625C308
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Lyndon,

shall I submitt a new draft of the standard? Jon Peterson explicitely =
told
me to wait for the authors final 48 hours to do this. I got the new =
version
available, but the changes in there are simply the changed message =
class/tag
values as described in my email.=20

Eva

-----Urspr=FCngliche Nachricht-----
Von: Brian F. G. Bidulock [mailto:bidulock@openss7.org]=20
Gesendet: February 12, 2004 2:22 AM
An: Pascal Bouveron
Cc: Weilandt, Eva [FRIED:NRA11:EXCH]; sigtran@ietf.org; Alain =
CHAMPENOIS
Betreff: Re: [Sigtran] Silent changes to V5UA draft 04 before moving to =
RFC
?


Pascal,

Pascal Bouveron wrote:
(Mon, 09 Feb 2004 12:59:45)
> Hello Eva,
>=20
> Thanks for the confirmation about changes on the V5UA Message Class,=20
> and Parameter Tags values.
>=20
> I was wondering: i can't see any anouncement on the Sigtran mailing=20
> list about the fact that the V5UA draft is moving to RFC soon. I saw=20
> it is now a "proposed standard". As i understand it, the Mailing List =

> is the mainstream for discussions on the evolutions of the=20
> drafts/rfc's, right ? I'm not familiar with the RFC procedures, but i =

> would imagine that, before a draft can move to RFC status, it has to=20
> be stable for a while. Which does not seem to be the case here,=20
> considering that you have decided to change MAJOR elements of the=20
> so-called "proposed standard", and call that an RFC, without =
notifying=20
> the Sigtran community thru the Mailing List.
>=20
> These are major changes, as they lead to total INCOMPATIBILITY =
between=20
> the draft 04 and the future RFC.

Someone correct me if I'm wrong, but:

An internet-draft is just that: a draft.  No compatibility, whether
backwards or forwards is necessary between drafts.  Implementation of a
draft is for protocol development purposes only.  A protocol is not a
"Proposed Standard" until it acheives RFC status.  Drafts are working =
group
documents and not intended for general implementation.

> Meaning that vendors developing their V5UA right now based on draft =
04=20
> will not be able to interop with systems based on the future RFC.

That is the risk one takes by implementing a draft.

>=20
> I am just a bit disappointed to see that important changes to the=20
> document were not made public, and therefore not subject to=20
> discussion.

Tag values are not important changes: they affect neither the design =
nor the
operation of the protocol.  Assignment of numbers is a matter for IANA =
and,
until the protocol moves to RFC, are not maintained.  Crossing the t's =
and
dotting the i's in this manner is fairly common practice in the RFC
development process, at least within the SIGTRAN working group.

> The good news here is that the RFC will include changes to the =
draft04=20
> which makes it move to the right direction, i.e consistency with =
other=20
> UAs, which is good.
>=20
> I would appreciate if you would clearly detail in the Mailing List =
the=20
> full changes that you are planning to apply to V5UA draft 04 before =
it=20
> is approved as a new RFC, so that the community can review them=20
> quickly.

That said, it makes sense to release a final draft.

--brian

>=20
> Many thanks for your efforts.
>=20
> Best regards / Meilleures salutations
> Pascal Bouveron
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> www.netbricks.com
> Netbricks - Provence - FRANCE
> Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> ----- Original Message -----
> From: Eva Weilandt
> To: 'Pascal Bouveron (Netbricks)' ; 'sigtran@ietf.org'
> Sent: Saturday, February 07, 2004 12:19 PM
> Subject: AW: V5UA Parameter Tags conflict with M3UA Tags
>=20
>=20
> Hi Pascal,
>=20
> we will change the message tags together with the message class for=20
> the RFC version of V5UA. This will hopefully happen soon. If you need =

> the new tags in the meantime, let me know.
>=20
> Thanks for pointing this out. It is always helpful if someone=20
> proof-read your documents :-)
>=20
> Eva
> -----Urspr=FCngliche Nachricht-----
> Von: Pascal Bouveron (Netbricks)=20
> [mailto:pascal.bouveron@netbricks.com]
> Gesendet: February 2, 2004 11:28 AM
> An: Weilandt, Eva [FRIED:NRA11:EXCH]; sigtran@ietf.org
> Betreff: V5UA Parameter Tags conflict with M3UA Tags
>=20
>=20
> Hello,
>=20
> I found other conflicts between V5UA and other UAs, in the Parameter=20
> Tags
> definitions:
>=20
> Tag 0x0011: "ASP Identifier" for M3UA, but "Link Status" for V5UA Tag =

> 0x0012: "Affected Point Code" for M3UA, but "Sa-Bit" (it actually has =

> no name in draft-04) for V5UA Tag 0x0013: "Correlation Id" for M3UA,=20
> but "Error Reason" for V5UA
>=20
> Best regards / Meilleures salutations
> Pascal Bouveron
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> www.netbricks.com
> Netbricks - Provence - FRANCE
> Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org https://www1.ietf.org/mailman/listinfo/sigtran

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

------_=_NextPart_001_01C3F145.8625C308
Content-Type: text/html;
	charset="ISO-8859-1"
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=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>AW: [Sigtran] Silent changes to V5UA draft 04 before moving to =
RFC ?</TITLE>
</HEAD>
<BODY>

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

<P><FONT SIZE=3D2>shall I submitt a new draft of the standard? Jon =
Peterson explicitely told me to wait for the authors final 48 hours to =
do this. I got the new version available, but the changes in there are =
simply the changed message class/tag values as described in my email. =
</FONT></P>

<P><FONT SIZE=3D2>Eva</FONT>
</P>

<P><FONT SIZE=3D2>-----Urspr=FCngliche Nachricht-----</FONT>
<BR><FONT SIZE=3D2>Von: Brian F. G. Bidulock [<A =
HREF=3D"mailto:bidulock@openss7.org">mailto:bidulock@openss7.org</A>] =
</FONT>
<BR><FONT SIZE=3D2>Gesendet: February 12, 2004 2:22 AM</FONT>
<BR><FONT SIZE=3D2>An: Pascal Bouveron</FONT>
<BR><FONT SIZE=3D2>Cc: Weilandt, Eva [FRIED:NRA11:EXCH]; =
sigtran@ietf.org; Alain CHAMPENOIS</FONT>
<BR><FONT SIZE=3D2>Betreff: Re: [Sigtran] Silent changes to V5UA draft =
04 before moving to RFC ?</FONT>
</P>
<BR>

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

<P><FONT SIZE=3D2>Pascal Bouveron =
wrote:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; (Mon, 09 Feb 2004 12:59:45)</FONT>
<BR><FONT SIZE=3D2>&gt; Hello Eva,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Thanks for the confirmation about changes on =
the V5UA Message Class, </FONT>
<BR><FONT SIZE=3D2>&gt; and Parameter Tags values.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I was wondering: i can't see any anouncement on =
the Sigtran mailing </FONT>
<BR><FONT SIZE=3D2>&gt; list about the fact that the V5UA draft is =
moving to RFC soon. I saw </FONT>
<BR><FONT SIZE=3D2>&gt; it is now a &quot;proposed standard&quot;. As i =
understand it, the Mailing List </FONT>
<BR><FONT SIZE=3D2>&gt; is the mainstream for discussions on the =
evolutions of the </FONT>
<BR><FONT SIZE=3D2>&gt; drafts/rfc's, right ? I'm not familiar with the =
RFC procedures, but i </FONT>
<BR><FONT SIZE=3D2>&gt; would imagine that, before a draft can move to =
RFC status, it has to </FONT>
<BR><FONT SIZE=3D2>&gt; be stable for a while. Which does not seem to =
be the case here, </FONT>
<BR><FONT SIZE=3D2>&gt; considering that you have decided to change =
MAJOR elements of the </FONT>
<BR><FONT SIZE=3D2>&gt; so-called &quot;proposed standard&quot;, and =
call that an RFC, without notifying </FONT>
<BR><FONT SIZE=3D2>&gt; the Sigtran community thru the Mailing =
List.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; These are major changes, as they lead to total =
INCOMPATIBILITY between </FONT>
<BR><FONT SIZE=3D2>&gt; the draft 04 and the future RFC.</FONT>
</P>

<P><FONT SIZE=3D2>Someone correct me if I'm wrong, but:</FONT>
</P>

<P><FONT SIZE=3D2>An internet-draft is just that: a draft.&nbsp; No =
compatibility, whether backwards or forwards is necessary between =
drafts.&nbsp; Implementation of a draft is for protocol development =
purposes only.&nbsp; A protocol is not a &quot;Proposed Standard&quot; =
until it acheives RFC status.&nbsp; Drafts are working group documents =
and not intended for general implementation.</FONT></P>

<P><FONT SIZE=3D2>&gt; Meaning that vendors developing their V5UA right =
now based on draft 04 </FONT>
<BR><FONT SIZE=3D2>&gt; will not be able to interop with systems based =
on the future RFC.</FONT>
</P>

<P><FONT SIZE=3D2>That is the risk one takes by implementing a draft.</F=
ONT>
</P>

<P><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I am just a bit disappointed to see that =
important changes to the </FONT>
<BR><FONT SIZE=3D2>&gt; document were not made public, and therefore =
not subject to </FONT>
<BR><FONT SIZE=3D2>&gt; discussion.</FONT>
</P>

<P><FONT SIZE=3D2>Tag values are not important changes: they affect =
neither the design nor the operation of the protocol.&nbsp; Assignment =
of numbers is a matter for IANA and, until the protocol moves to RFC, =
are not maintained.&nbsp; Crossing the t's and dotting the i's in this =
manner is fairly common practice in the RFC development process, at =
least within the SIGTRAN working group.</FONT></P>

<P><FONT SIZE=3D2>&gt; The good news here is that the RFC will include =
changes to the draft04 </FONT>
<BR><FONT SIZE=3D2>&gt; which makes it move to the right direction, i.e =
consistency with other </FONT>
<BR><FONT SIZE=3D2>&gt; UAs, which is good.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I would appreciate if you would clearly detail =
in the Mailing List the </FONT>
<BR><FONT SIZE=3D2>&gt; full changes that you are planning to apply to =
V5UA draft 04 before it </FONT>
<BR><FONT SIZE=3D2>&gt; is approved as a new RFC, so that the community =
can review them </FONT>
<BR><FONT SIZE=3D2>&gt; quickly.</FONT>
</P>

<P><FONT SIZE=3D2>That said, it makes sense to release a final =
draft.</FONT>
</P>

<P><FONT SIZE=3D2>--brian</FONT>
</P>

<P><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Many thanks for your efforts.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Best regards / Meilleures salutations</FONT>
<BR><FONT SIZE=3D2>&gt; Pascal Bouveron</FONT>
<BR><FONT SIZE=3D2>&gt; =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>
<BR><FONT SIZE=3D2>&gt; www.netbricks.com</FONT>
<BR><FONT SIZE=3D2>&gt; Netbricks - Provence - FRANCE</FONT>
<BR><FONT SIZE=3D2>&gt; Tel: (+33) (0)4 42 91 44 77 -- Fax:&nbsp; (+33) =
(0)4 42 91 44 71 </FONT>
<BR><FONT SIZE=3D2>&gt; =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; ----- Original Message -----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Eva Weilandt</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'Pascal Bouveron (Netbricks)' ; =
'sigtran@ietf.org'</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Saturday, February 07, 2004 12:19 =
PM</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: AW: V5UA Parameter Tags conflict with =
M3UA Tags</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hi Pascal,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; we will change the message tags together with =
the message class for </FONT>
<BR><FONT SIZE=3D2>&gt; the RFC version of V5UA. This will hopefully =
happen soon. If you need </FONT>
<BR><FONT SIZE=3D2>&gt; the new tags in the meantime, let me =
know.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Thanks for pointing this out. It is always =
helpful if someone </FONT>
<BR><FONT SIZE=3D2>&gt; proof-read your documents :-)</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Eva</FONT>
<BR><FONT SIZE=3D2>&gt; -----Urspr=FCngliche Nachricht-----</FONT>
<BR><FONT SIZE=3D2>&gt; Von: Pascal Bouveron (Netbricks) </FONT>
<BR><FONT SIZE=3D2>&gt; [<A =
HREF=3D"mailto:pascal.bouveron@netbricks.com">mailto:pascal.bouveron@net=
bricks.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Gesendet: February 2, 2004 11:28 AM</FONT>
<BR><FONT SIZE=3D2>&gt; An: Weilandt, Eva [FRIED:NRA11:EXCH]; =
sigtran@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Betreff: V5UA Parameter Tags conflict with M3UA =
Tags</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hello,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I found other conflicts between V5UA and other =
UAs, in the Parameter </FONT>
<BR><FONT SIZE=3D2>&gt; Tags</FONT>
<BR><FONT SIZE=3D2>&gt; definitions:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Tag 0x0011: &quot;ASP Identifier&quot; for =
M3UA, but &quot;Link Status&quot; for V5UA Tag </FONT>
<BR><FONT SIZE=3D2>&gt; 0x0012: &quot;Affected Point Code&quot; for =
M3UA, but &quot;Sa-Bit&quot; (it actually has </FONT>
<BR><FONT SIZE=3D2>&gt; no name in draft-04) for V5UA Tag 0x0013: =
&quot;Correlation Id&quot; for M3UA, </FONT>
<BR><FONT SIZE=3D2>&gt; but &quot;Error Reason&quot; for V5UA</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Best regards / Meilleures salutations</FONT>
<BR><FONT SIZE=3D2>&gt; Pascal Bouveron</FONT>
<BR><FONT SIZE=3D2>&gt; =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>
<BR><FONT SIZE=3D2>&gt; www.netbricks.com</FONT>
<BR><FONT SIZE=3D2>&gt; Netbricks - Provence - FRANCE</FONT>
<BR><FONT SIZE=3D2>&gt; Tel: (+33) (0)4 42 91 44 77 -- Fax:&nbsp; (+33) =
(0)4 42 91 44 71 </FONT>
<BR><FONT SIZE=3D2>&gt; =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Sigtran mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; Sigtran@ietf.org <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sigtran" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sigtran</A></FO=
NT>
</P>

<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>Brian F. G. Bidulock</FONT>
<BR><FONT SIZE=3D2>bidulock@openss7.org</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://www.openss7.org/" =
TARGET=3D"_blank">http://www.openss7.org/</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C3F145.8625C308--

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



From exim@www1.ietf.org  Thu Feb 12 09:11: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 JAA24621
	for <sigtran-archive@odin.ietf.org>; Thu, 12 Feb 2004 09:11:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArHYV-000675-Ii
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 09:11:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1CEB3vE023495
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 09:11:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArHYT-00065q-BK; Thu, 12 Feb 2004 09:11:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArHXk-00060M-LY
	for sigtran@optimus.ietf.org; Thu, 12 Feb 2004 09:10:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24566
	for <sigtran@ietf.org>; Thu, 12 Feb 2004 09:10:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArHXf-0007gC-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 09:10:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArHWm-0007aU-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 09:09:17 -0500
Received: from relay-6m.club-internet.fr ([194.158.104.45])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArHWH-0007V6-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 09:08:45 -0500
Received: from PascalB (f13m-8-193.d1.club-internet.fr [212.195.83.193])
	by relay-6m.club-internet.fr (Postfix) with SMTP
	id 81BBF2572B; Thu, 12 Feb 2004 15:08:42 +0100 (CET)
Message-ID: <001601c3f171$b8da0440$1600a8c0@PascalB>
From: "Pascal Bouveron (Netbricks)" <pascal.bouveron@netbricks.com>
To: "Ong, Lyndon" <LyOng@Ciena.com>,
        "Eva Weilandt" <eva.weilandt@nortelnetworks.com>, <sigtran@ietf.org>,
        "Michael Tuexen (Sigtran)" <Michael.Tuexen@lurchi.franken.de>
Cc: "Alain CHAMPENOIS" <alain.champenois@netbricks.com>
References: <829F074A10F98943A218DC363D09C92A01476984@w2ksjexg06.oni.com>
Subject: Re: [Sigtran] Silent changes to V5UA draft 04 before moving to RFC ?
Date: Thu, 12 Feb 2004 15:08:37 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL 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

Hello,

As Brian says, drafts are working group documents.
And as such, they are meant to be criticized by the working group community,
which is a good way to rapidly improve the protocol and make it a fairly
stable and supported protocol in the end, ie when it becomes an RFC.

My point was that the draft 04, which was approved as "Proposed standard" by
the IESG back in november 2003, was about to move to RFC status, but at the
same time, the RFC document would include major changes which were not
announced to the working group.
And that is what desappointed me.
These protocols are meant to be implemented by vendors some day  (like us,
but also Nortel and others), and therefore there needs to be full
transparency on the decisions that are taken to modify the documents.

The changes i suggested for V5UA (Message Class and Parameter Tags) were
motivated by the fact that all the UAs should be seen as the same family of
protocols, and therefore there should be an overall consistency between the
different documents.
This simply makes life easier to everybody, and allowing implementations to
handle multiple UAs with the same UA "core".

M2UA and M3UA have overcome several changes to make them consistent (error
code values, etc) while they were still drafts, and once they had moved to
RFC status.
But these changes where largely discussed on the mailing list, and that's
fine to me because everybody is made aware of the propositions, and can
therefore give their point of view, and everybody wins in the end.

Calling this modified document "draft-05" rather than "RFCxxxx" would be
better in my opinion, although these proposed changes will probably make the
V5UA spec much more stable in the future.
Then we can move it to RFC with a high probability that it will remain
stable, and therefore allow companies to have a strong confidence in it.
And that is the purpose of an RFC, correct ?

Now i'm happy that Eva has clearly stated the list of changes to the draft
document.
I agree with these changes.

Best regards / Meilleures salutations
Pascal Bouveron
=============================================
www.netbricks.com
Netbricks - Provence - FRANCE
Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
=============================================


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



From exim@www1.ietf.org  Thu Feb 12 11:49: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 LAA01980
	for <sigtran-archive@odin.ietf.org>; Thu, 12 Feb 2004 11:49:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArK1P-0001jB-TV
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 11:49:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1CGn3xa006642
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 11:49:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArK1M-0001iE-N5; Thu, 12 Feb 2004 11:49:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArK0i-0001do-LE
	for sigtran@optimus.ietf.org; Thu, 12 Feb 2004 11:48:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01936
	for <sigtran@ietf.org>; Thu, 12 Feb 2004 11:48:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArK0f-0000cW-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 11:48:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArJzn-0000XU-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 11:47:24 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[ztqewAS4rdOJlTMU+xcQhq/KcNYKhUG3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArJzM-0000SI-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 11:46:56 -0500
Received: from ns.pigworks.openss7.net (IDENT:geBy7324hOjpo9TNgegP9v0IhS+RMGL3@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1CGklI16750;
	Thu, 12 Feb 2004 09:46:47 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1CGklj28485;
	Thu, 12 Feb 2004 09:46:47 -0700
Date: Thu, 12 Feb 2004 09:46:46 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Pascal Bouveron (Netbricks)" <pascal.bouveron@netbricks.com>
Cc: "Ong, Lyndon" <LyOng@Ciena.com>,
        Eva Weilandt <eva.weilandt@nortelnetworks.com>, sigtran@ietf.org,
        "Michael Tuexen (Sigtran)" <Michael.Tuexen@lurchi.franken.de>,
        Alain CHAMPENOIS <alain.champenois@netbricks.com>
Subject: Re: [Sigtran] Silent changes to V5UA draft 04 before moving to RFC ?
Message-ID: <20040212094646.A28228@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Pascal Bouveron (Netbricks)" <pascal.bouveron@netbricks.com>,
	"Ong, Lyndon" <LyOng@Ciena.com>,
	Eva Weilandt <eva.weilandt@nortelnetworks.com>, sigtran@ietf.org,
	"Michael Tuexen (Sigtran)" <Michael.Tuexen@lurchi.franken.de>,
	Alain CHAMPENOIS <alain.champenois@netbricks.com>
References: <829F074A10F98943A218DC363D09C92A01476984@w2ksjexg06.oni.com> <001601c3f171$b8da0440$1600a8c0@PascalB>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <001601c3f171$b8da0440$1600a8c0@PascalB>; from pascal.bouveron@netbricks.com on Thu, Feb 12, 2004 at 03:08:37PM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Pascal,

Pascal Bouveron (Netbricks) wrote:                                                  (Thu, 12 Feb 2004 15:08:37)
> Hello,
> 
> As Brian says, drafts are working group documents.
> And as such, they are meant to be criticized by the working group community,
> which is a good way to rapidly improve the protocol and make it a fairly
> stable and supported protocol in the end, ie when it becomes an RFC.
> 
> My point was that the draft 04, which was approved as "Proposed standard" by
> the IESG back in november 2003, was about to move to RFC status, but at the
> same time, the RFC document would include major changes which were not
> announced to the working group.
> And that is what desappointed me.
> These protocols are meant to be implemented by vendors some day  (like us,
> but also Nortel and others), and therefore there needs to be full
> transparency on the decisions that are taken to modify the documents.
> 
> The changes i suggested for V5UA (Message Class and Parameter Tags) were
> motivated by the fact that all the UAs should be seen as the same family of
> protocols, and therefore there should be an overall consistency between the
> different documents.

> This simply makes life easier to everybody, and allowing implementations to
> handle multiple UAs with the same UA "core".

You can give up on that.  I tried to push in that direction several years
ago, however, each UA is unique.  The "common" procedures are not common and
the "common" parameters do not align either.

If this is of concern to you, I suggest you get involved earlier in the
process: (several years earlier) see the thread

  "SUA09, M3UA-10, M2UA-11, RFC2057: Common parameters." December 30, 2001

for the general attitutde of the editors and chair towards the "unified UA
theory."

> 
> M2UA and M3UA have overcome several changes to make them consistent (error
> code values, etc) while they were still drafts, and once they had moved to
> RFC status.

See the above cited thread for the inconsistencies that were not addressed
at draft and were not addressed before RFC either.


> But these changes where largely discussed on the mailing list, and that's
> fine to me because everybody is made aware of the propositions, and can
> therefore give their point of view, and everybody wins in the end.

In fact they did not receive much discussion: aside from myself, the editors
and the chair, there were three or four others (rarely) in the discussions.
I don't see your name on the thread.

> 
> Calling this modified document "draft-05" rather than "RFCxxxx" would be
> better in my opinion, although these proposed changes will probably make the
> V5UA spec much more stable in the future.
> Then we can move it to RFC with a high probability that it will remain
> stable, and therefore allow companies to have a strong confidence in it.
> And that is the purpose of an RFC, correct ?

That is the purpose of a "Standard", however, the document will only be a
"Proposed Standard".  It has many changes to suffer from the experience of
implementation.

--brian

> 
> Now i'm happy that Eva has clearly stated the list of changes to the draft
> document.
> I agree with these changes.
> 
> Best regards / Meilleures salutations
> Pascal Bouveron
> =============================================
> www.netbricks.com
> Netbricks - Provence - FRANCE
> Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
> =============================================
> 
> 
> _______________________________________________
> 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 Feb 12 12:48:31 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 MAA04233
	for <sigtran-archive@odin.ietf.org>; Thu, 12 Feb 2004 12:48:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArKwV-0000Kk-0W
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 12:48:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1CHm2U5001259
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 12:48:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArKwT-0000K7-8i; Thu, 12 Feb 2004 12:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArKvv-0000Ir-6L
	for sigtran@optimus.ietf.org; Thu, 12 Feb 2004 12:47:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04200
	for <sigtran@ietf.org>; Thu, 12 Feb 2004 12:47:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArKvr-0006tJ-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 12:47:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArKv5-0006nm-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 12:46:36 -0500
Received: from relay-3m.club-internet.fr ([194.158.104.42])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArKuV-0006hg-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 12:45:59 -0500
Received: from PascalB (f09v-8-69.d1.club-internet.fr [212.194.187.69])
	by relay-3m.club-internet.fr (Postfix) with SMTP
	id DD5F9E058; Thu, 12 Feb 2004 18:45:58 +0100 (CET)
Message-ID: <007d01c3f190$10b3a860$1600a8c0@PascalB>
From: "Pascal Bouveron (Netbricks)" <pascal.bouveron@netbricks.com>
To: <bidulock@openss7.org>
Cc: "Ong, Lyndon" <LyOng@Ciena.com>,
        "Eva Weilandt" <eva.weilandt@nortelnetworks.com>, <sigtran@ietf.org>,
        "Michael Tuexen (Sigtran)" <Michael.Tuexen@lurchi.franken.de>,
        "Alain CHAMPENOIS" <alain.champenois@netbricks.com>
References: <829F074A10F98943A218DC363D09C92A01476984@w2ksjexg06.oni.com> <001601c3f171$b8da0440$1600a8c0@PascalB> <20040212094646.A28228@openss7.org>
Subject: Re: [Sigtran] Silent changes to V5UA draft 04 before moving to RFC ?
Date: Thu, 12 Feb 2004 18:45:49 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Brian,

The fact is that in the past two years significant efforts were made to push
towards consistency over UAs.
For instance, M3UA drafts from 2000/2001 (draft-02 for instance) were really
"early" drafts, with some fields not even being described as full Parameters
(no Tag/Length for instance).
But all this was changed thanks to guys like you.
I haven't had a look at M2PA yet, but i can tell that IUA, M2UA and M3UA do
not suffer inconsistency anymore, and it is pretty straightforward to
implement a "UA core" which suits well all these UAs (i wrote one!).

There is little to be done to achieve consistency with V5UA as well, and
that is exactly what I proposed to Eva, who detailed all changes that will
be part of the next draft -- or RFC.

If the future V5UA RFC needs changes, we can still move to those
"Implementor's Guides" anyway...

BTW: i posted a remark about the format of the IGs back in october 2003,
saying that full documents would be a lot easier to read and understand than
simply listing the incremental changes.
People seemed to agree with me on this point.
But it looks like nothing was done yet in that direction...
Lyndon, how do we proceed here ?

Best regards / Meilleures salutations
Pascal Bouveron
=============================================
www.netbricks.com
Netbricks - Provence - FRANCE
Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
=============================================

----- Original Message ----- 
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Pascal Bouveron (Netbricks)" <pascal.bouveron@netbricks.com>
Cc: "Ong, Lyndon" <LyOng@Ciena.com>; "Eva Weilandt"
<eva.weilandt@nortelnetworks.com>; <sigtran@ietf.org>; "Michael Tuexen
(Sigtran)" <Michael.Tuexen@lurchi.franken.de>; "Alain CHAMPENOIS"
<alain.champenois@netbricks.com>
Sent: Thursday, February 12, 2004 5:46 PM
Subject: Re: [Sigtran] Silent changes to V5UA draft 04 before moving to RFC
?


| Pascal,
|
| Pascal Bouveron (Netbricks) wrote:
(Thu, 12 Feb 2004 15:08:37)
| > Hello,
| >
| > As Brian says, drafts are working group documents.
| > And as such, they are meant to be criticized by the working group
community,
| > which is a good way to rapidly improve the protocol and make it a fairly
| > stable and supported protocol in the end, ie when it becomes an RFC.
| >
| > My point was that the draft 04, which was approved as "Proposed
standard" by
| > the IESG back in november 2003, was about to move to RFC status, but at
the
| > same time, the RFC document would include major changes which were not
| > announced to the working group.
| > And that is what desappointed me.
| > These protocols are meant to be implemented by vendors some day  (like
us,
| > but also Nortel and others), and therefore there needs to be full
| > transparency on the decisions that are taken to modify the documents.
| >
| > The changes i suggested for V5UA (Message Class and Parameter Tags) were
| > motivated by the fact that all the UAs should be seen as the same family
of
| > protocols, and therefore there should be an overall consistency between
the
| > different documents.
|
| > This simply makes life easier to everybody, and allowing implementations
to
| > handle multiple UAs with the same UA "core".
|
| You can give up on that.  I tried to push in that direction several years
| ago, however, each UA is unique.  The "common" procedures are not common
and
| the "common" parameters do not align either.
|
| If this is of concern to you, I suggest you get involved earlier in the
| process: (several years earlier) see the thread
|
|   "SUA09, M3UA-10, M2UA-11, RFC2057: Common parameters." December 30, 2001
|
| for the general attitutde of the editors and chair towards the "unified UA
| theory."
|
| >
| > M2UA and M3UA have overcome several changes to make them consistent
(error
| > code values, etc) while they were still drafts, and once they had moved
to
| > RFC status.
|
| See the above cited thread for the inconsistencies that were not addressed
| at draft and were not addressed before RFC either.
|
|
| > But these changes where largely discussed on the mailing list, and
that's
| > fine to me because everybody is made aware of the propositions, and can
| > therefore give their point of view, and everybody wins in the end.
|
| In fact they did not receive much discussion: aside from myself, the
editors
| and the chair, there were three or four others (rarely) in the
discussions.
| I don't see your name on the thread.
|
| >
| > Calling this modified document "draft-05" rather than "RFCxxxx" would be
| > better in my opinion, although these proposed changes will probably make
the
| > V5UA spec much more stable in the future.
| > Then we can move it to RFC with a high probability that it will remain
| > stable, and therefore allow companies to have a strong confidence in it.
| > And that is the purpose of an RFC, correct ?
|
| That is the purpose of a "Standard", however, the document will only be a
| "Proposed Standard".  It has many changes to suffer from the experience of
| implementation.
|
| --brian
|
| >
| > Now i'm happy that Eva has clearly stated the list of changes to the
draft
| > document.
| > I agree with these changes.
| >
| > Best regards / Meilleures salutations
| > Pascal Bouveron
| > =============================================
| > www.netbricks.com
| > Netbricks - Provence - FRANCE
| > Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
| > =============================================
| >
| >
| > _______________________________________________
| > 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 Feb 12 12:52:31 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 MAA04444
	for <sigtran-archive@odin.ietf.org>; Thu, 12 Feb 2004 12:52:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArL0N-0000zK-VC
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 12:52:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1CHq3G2003781
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 12:52:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArL0M-0000yf-1e; Thu, 12 Feb 2004 12:52:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArKzt-0000xE-00
	for sigtran@optimus.ietf.org; Thu, 12 Feb 2004 12:51:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04382
	for <sigtran@ietf.org>; Thu, 12 Feb 2004 12:51:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArKzp-0007Mr-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 12:51:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArKyw-0007FW-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 12:50:35 -0500
Received: from sjmail.ciena.com ([12.7.169.25] helo=w2ksjexg01.ciena.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArKy2-00078Z-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 12:49:38 -0500
Received: by w2ksjexg01.ciena.com with Internet Mail Service (5.5.2657.72)
	id <1JQBTTLH>; Thu, 12 Feb 2004 09:49:18 -0800
Message-ID: <829F074A10F98943A218DC363D09C92A0147698B@w2ksjexg06.oni.com>
From: "Ong, Lyndon" <LyOng@Ciena.com>
To: "'Pascal Bouveron (Netbricks)'" <pascal.bouveron@netbricks.com>,
        bidulock@openss7.org
Cc: Eva Weilandt <eva.weilandt@nortelnetworks.com>, sigtran@ietf.org,
        "Michael Tuexen (Sigtran)" <Michael.Tuexen@lurchi.franken.de>,
        Alain CHAMPENOIS <alain.champenois@netbricks.com>
Subject: RE: [Sigtran] Silent changes to V5UA draft 04 before moving to RF
	C ?
Date: Thu, 12 Feb 2004 09:49:36 -0800
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.1 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 Pascal,

Thanks for your cooperation and comments on V5UA.  As it turns out
we will need to put out another version when we get to the authors'
review part of the RFC process, so you will see a version 5 at that
point.

Regarding the IGs, we did decide to put out a new version of IUA
rather than an IG for that spec, in response to your and others'
comments.  We're very close to completing the IG for M3UA now,
and when we have agreement on this we can consider whether to
update the RFC or put out a separate document, I think.

Cheers,

Lyndon

-----Original Message-----
From: Pascal Bouveron (Netbricks) [mailto:pascal.bouveron@netbricks.com]
Sent: Thursday, February 12, 2004 9:46 AM
To: bidulock@openss7.org
Cc: Ong, Lyndon; Eva Weilandt; sigtran@ietf.org; Michael Tuexen
(Sigtran); Alain CHAMPENOIS
Subject: Re: [Sigtran] Silent changes to V5UA draft 04 before moving to
RFC ?


Brian,

The fact is that in the past two years significant efforts were made to push
towards consistency over UAs.
For instance, M3UA drafts from 2000/2001 (draft-02 for instance) were really
"early" drafts, with some fields not even being described as full Parameters
(no Tag/Length for instance).
But all this was changed thanks to guys like you.
I haven't had a look at M2PA yet, but i can tell that IUA, M2UA and M3UA do
not suffer inconsistency anymore, and it is pretty straightforward to
implement a "UA core" which suits well all these UAs (i wrote one!).

There is little to be done to achieve consistency with V5UA as well, and
that is exactly what I proposed to Eva, who detailed all changes that will
be part of the next draft -- or RFC.

If the future V5UA RFC needs changes, we can still move to those
"Implementor's Guides" anyway...

BTW: i posted a remark about the format of the IGs back in october 2003,
saying that full documents would be a lot easier to read and understand than
simply listing the incremental changes.
People seemed to agree with me on this point.
But it looks like nothing was done yet in that direction...
Lyndon, how do we proceed here ?

Best regards / Meilleures salutations
Pascal Bouveron
=============================================
www.netbricks.com
Netbricks - Provence - FRANCE
Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
=============================================

----- Original Message ----- 
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Pascal Bouveron (Netbricks)" <pascal.bouveron@netbricks.com>
Cc: "Ong, Lyndon" <LyOng@Ciena.com>; "Eva Weilandt"
<eva.weilandt@nortelnetworks.com>; <sigtran@ietf.org>; "Michael Tuexen
(Sigtran)" <Michael.Tuexen@lurchi.franken.de>; "Alain CHAMPENOIS"
<alain.champenois@netbricks.com>
Sent: Thursday, February 12, 2004 5:46 PM
Subject: Re: [Sigtran] Silent changes to V5UA draft 04 before moving to RFC
?


| Pascal,
|
| Pascal Bouveron (Netbricks) wrote:
(Thu, 12 Feb 2004 15:08:37)
| > Hello,
| >
| > As Brian says, drafts are working group documents.
| > And as such, they are meant to be criticized by the working group
community,
| > which is a good way to rapidly improve the protocol and make it a fairly
| > stable and supported protocol in the end, ie when it becomes an RFC.
| >
| > My point was that the draft 04, which was approved as "Proposed
standard" by
| > the IESG back in november 2003, was about to move to RFC status, but at
the
| > same time, the RFC document would include major changes which were not
| > announced to the working group.
| > And that is what desappointed me.
| > These protocols are meant to be implemented by vendors some day  (like
us,
| > but also Nortel and others), and therefore there needs to be full
| > transparency on the decisions that are taken to modify the documents.
| >
| > The changes i suggested for V5UA (Message Class and Parameter Tags) were
| > motivated by the fact that all the UAs should be seen as the same family
of
| > protocols, and therefore there should be an overall consistency between
the
| > different documents.
|
| > This simply makes life easier to everybody, and allowing implementations
to
| > handle multiple UAs with the same UA "core".
|
| You can give up on that.  I tried to push in that direction several years
| ago, however, each UA is unique.  The "common" procedures are not common
and
| the "common" parameters do not align either.
|
| If this is of concern to you, I suggest you get involved earlier in the
| process: (several years earlier) see the thread
|
|   "SUA09, M3UA-10, M2UA-11, RFC2057: Common parameters." December 30, 2001
|
| for the general attitutde of the editors and chair towards the "unified UA
| theory."
|
| >
| > M2UA and M3UA have overcome several changes to make them consistent
(error
| > code values, etc) while they were still drafts, and once they had moved
to
| > RFC status.
|
| See the above cited thread for the inconsistencies that were not addressed
| at draft and were not addressed before RFC either.
|
|
| > But these changes where largely discussed on the mailing list, and
that's
| > fine to me because everybody is made aware of the propositions, and can
| > therefore give their point of view, and everybody wins in the end.
|
| In fact they did not receive much discussion: aside from myself, the
editors
| and the chair, there were three or four others (rarely) in the
discussions.
| I don't see your name on the thread.
|
| >
| > Calling this modified document "draft-05" rather than "RFCxxxx" would be
| > better in my opinion, although these proposed changes will probably make
the
| > V5UA spec much more stable in the future.
| > Then we can move it to RFC with a high probability that it will remain
| > stable, and therefore allow companies to have a strong confidence in it.
| > And that is the purpose of an RFC, correct ?
|
| That is the purpose of a "Standard", however, the document will only be a
| "Proposed Standard".  It has many changes to suffer from the experience of
| implementation.
|
| --brian
|
| >
| > Now i'm happy that Eva has clearly stated the list of changes to the
draft
| > document.
| > I agree with these changes.
| >
| > Best regards / Meilleures salutations
| > Pascal Bouveron
| > =============================================
| > www.netbricks.com
| > Netbricks - Provence - FRANCE
| > Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
| > =============================================
| >
| >
| > _______________________________________________
| > 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 Feb 12 13:13:31 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 NAA05270
	for <sigtran-archive@odin.ietf.org>; Thu, 12 Feb 2004 13:13:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArLKi-00046z-52
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 13:13:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1CID4DR015787
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 13:13:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArLKf-00046S-8L; Thu, 12 Feb 2004 13:13:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArLK7-00041f-7J
	for sigtran@optimus.ietf.org; Thu, 12 Feb 2004 13:12:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05240
	for <sigtran@ietf.org>; Thu, 12 Feb 2004 13:12:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArLK3-0001nG-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 13:12:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArLJP-0001gK-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 13:11:44 -0500
Received: from relay-3m.club-internet.fr ([194.158.104.42])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArLIZ-0001Zb-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 13:10:51 -0500
Received: from PascalB (f09v-8-69.d1.club-internet.fr [212.194.187.69])
	by relay-3m.club-internet.fr (Postfix) with SMTP
	id 1AFD8E1AA; Thu, 12 Feb 2004 19:10:52 +0100 (CET)
Message-ID: <008a01c3f193$8a8cb6b0$1600a8c0@PascalB>
From: "Pascal Bouveron (Netbricks)" <pascal.bouveron@netbricks.com>
To: "Ong, Lyndon" <LyOng@Ciena.com>, <bidulock@openss7.org>
Cc: "Eva Weilandt" <eva.weilandt@nortelnetworks.com>, <sigtran@ietf.org>,
        "Michael Tuexen (Sigtran)" <Michael.Tuexen@lurchi.franken.de>,
        "Alain CHAMPENOIS" <alain.champenois@netbricks.com>
References: <829F074A10F98943A218DC363D09C92A0147698B@w2ksjexg06.oni.com>
Subject: Re: [Sigtran] Silent changes to V5UA draft 04 before moving to RFC ?
Date: Thu, 12 Feb 2004 19:10:44 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I saw the RFC3057bis-00 document.
I think the full M3UA document will be welcome!
Many thanks for the effort, Lyndon.

Best regards / Meilleures salutations
Pascal Bouveron
=============================================
www.netbricks.com
Netbricks - Provence - FRANCE
Tel: (+33) (0)4 42 91 44 77 -- Fax:  (+33) (0)4 42 91 44 71
=============================================

----- Original Message ----- 
From: "Ong, Lyndon" <LyOng@Ciena.com>
To: "'Pascal Bouveron (Netbricks)'" <pascal.bouveron@netbricks.com>;
<bidulock@openss7.org>
Cc: "Eva Weilandt" <eva.weilandt@nortelnetworks.com>; <sigtran@ietf.org>;
"Michael Tuexen (Sigtran)" <Michael.Tuexen@lurchi.franken.de>; "Alain
CHAMPENOIS" <alain.champenois@netbricks.com>
Sent: Thursday, February 12, 2004 6:49 PM
Subject: RE: [Sigtran] Silent changes to V5UA draft 04 before moving to RFC
?


| Hi Pascal,
|
| Thanks for your cooperation and comments on V5UA.  As it turns out
| we will need to put out another version when we get to the authors'
| review part of the RFC process, so you will see a version 5 at that
| point.
|
| Regarding the IGs, we did decide to put out a new version of IUA
| rather than an IG for that spec, in response to your and others'
| comments.  We're very close to completing the IG for M3UA now,
| and when we have agreement on this we can consider whether to
| update the RFC or put out a separate document, I think.
|
| Cheers,
|
| Lyndon
|


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



From exim@www1.ietf.org  Thu Feb 12 16:56:31 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 QAA18375
	for <sigtran-archive@odin.ietf.org>; Thu, 12 Feb 2004 16:56:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArOoV-0002JZ-AE
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 16:56:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1CLu33d008896
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 16:56:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArOoU-0002JJ-Ag; Thu, 12 Feb 2004 16:56:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArOo0-0002IU-Ip
	for sigtran@optimus.ietf.org; Thu, 12 Feb 2004 16:55:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18341
	for <sigtran@ietf.org>; Thu, 12 Feb 2004 16:55:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArOnw-0001LV-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 16:55:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArOn0-0001HB-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 16:54:31 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArOmd-0001CO-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 16:54:07 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i1CLs87T012194;
	Thu, 12 Feb 2004 16:54:09 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "John Loughney" <john.Loughney@nokia.com>
Cc: "SIGTRAN Mailing List" <sigtran@ietf.org>
Subject: RE: [Sigtran] SUA v16: Global Titles
Date: Thu, 12 Feb 2004 16:55:38 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOGEIMCEAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <20040128122410.A16922@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
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

John,

Brian is right. The GTI that is defined in section 3.10.2.3 is closer to
ANSI than to ITU. I suggest that you remove "(defined in chapter 3.4.2.3 of
Q.713)".

Barry Nagelberg

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Wednesday, January 28, 2004 2:24 PM
> To: Barry Nagelberg
> Cc: SIGTRAN Mailing List; Seamus Gilchrist; Michael Perler
> Subject: Re: [Sigtran] SUA v16: Global Titles
>
>
> Barry,
>
> I think you'll find that it more closely resembles ANSI T1.112, which does
> not have a nature of address indicator.  Also, encoding scheme is
> only ever
> BCD (odd or even).  GTI in SUA and (for that matter) GTI in ITU
> and ANSI do
> not match.  The GTI in SUA, like ITU and ANSI indicates the fields present
> in the messsage.  If you need to specify any value, use SUA GTI=0100.  The
> SUA GTI does not dictate what is passed to the SS7 network by a gateway.
> The AMF or GTT result will determine that.
>
> Did you have a specific application that cannot be met with the current
> codings?
>
> --brian
>
> Barry Nagelberg wrote:
>                    (Wed, 28 Jan 2004 13:29:39)
> > We have some questions about global titles in SUA.
> >
> > First, in section 3.10.2.3 of SUA draft 16, the definition for
> GTI=0001 does
> > not appear to match with ITU-T Q.713 (1996) 3.4.2.3.1.
> According to Q.713,
> > GTI=0001 means that the global title information only contains
> a nature of
> > address and the global title address. According to the SUA
> draft, GTI=0001
> > means that the nature of address is ignored, that the
> translation type must
> > be 0 (unknown), and that the numbering plan must be 1 (E.164).
> What is the
> > reason for this difference?
> >
> > Also, section 3.10.2.3 does not include an encoding scheme
> field. The draft
> > says "Address signals to be coded as defined in ITU-T Q.713 Section
> > 3.4.2.3.1." That section of the ITU specification includes an
> example of how
> > the digits would be encoded if BCD encoding was used. Does this
> mean that
> > SUA only supports BCD encoding? If other types of encoding can
> be used, how
> > is the encoding scheme specified in the global title?
> >
> > Barry Nagelberg
> >


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



From exim@www1.ietf.org  Thu Feb 12 23:27: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 XAA06868
	for <sigtran-archive@odin.ietf.org>; Thu, 12 Feb 2004 23:27:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArUuw-0003kl-HZ
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 23:27:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1D4R6KC014404
	for sigtran-archive@odin.ietf.org; Thu, 12 Feb 2004 23:27:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArUur-0003k9-8f; Thu, 12 Feb 2004 23:27:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArUug-0003jy-Fw
	for sigtran@optimus.ietf.org; Thu, 12 Feb 2004 23:26:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06829
	for <sigtran@ietf.org>; Thu, 12 Feb 2004 23:26:46 -0500 (EST)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArUuZ-00015o-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 23:26:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArUtS-0000zs-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 23:25:35 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArUsW-0000tx-00
	for sigtran@ietf.org; Thu, 12 Feb 2004 23:24:36 -0500
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1D4Oc315861
	for <sigtran@ietf.org>; Fri, 13 Feb 2004 06:24:38 +0200 (EET)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T67b9f51726ac158f210ad@esvir01nok.ntc.nokia.com>;
 Fri, 13 Feb 2004 06:24:38 +0200
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Fri, 13 Feb 2004 06:24:37 +0200
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Fri, 13 Feb 2004 06:24:36 +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
Subject: RE: [Sigtran] SUA v16: Global Titles
Date: Fri, 13 Feb 2004 06:24:36 +0200
Message-ID: <DADF50F5EC506B41A0F375ABEB3206360143B62D@esebe023.ntc.nokia.com>
Thread-Topic: [Sigtran] SUA v16: Global Titles
Thread-Index: AcPxssJgleRNTMpqQ6WxBrKk/CYdcgANmbhg
To: <barryn@adax.com>
Cc: <sigtran@ietf.org>
X-OriginalArrivalTime: 13 Feb 2004 04:24:37.0062 (UTC) FILETIME=[4A2CA660:01C3F1E9]
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

Hi Barry,

> Brian is right. The GTI that is defined in section 3.10.2.3=20
> is closer to
> ANSI than to ITU. I suggest that you remove "(defined in=20
> chapter 3.4.2.3 of
> Q.713)".

I will add this as something to do.  SUA should be reviewed=20
next week by the IESG, and if all goes well, I can take care
of this during the final authors 48 hour call.

John

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



From exim@www1.ietf.org  Fri Feb 13 12:00:43 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 MAA20152
	for <sigtran-archive@odin.ietf.org>; Fri, 13 Feb 2004 12:00:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Argfl-0004Zj-5D
	for sigtran-archive@odin.ietf.org; Fri, 13 Feb 2004 12:00:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1DH0CwT017581
	for sigtran-archive@odin.ietf.org; Fri, 13 Feb 2004 12:00:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Argfe-0004YK-J5; Fri, 13 Feb 2004 12:00:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Argej-0004X8-NA
	for sigtran@optimus.ietf.org; Fri, 13 Feb 2004 11:59:09 -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 LAA20079
	for <sigtran@ietf.org>; Fri, 13 Feb 2004 11:59:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Argei-0003bX-00
	for sigtran@ietf.org; Fri, 13 Feb 2004 11:59:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Argdm-0003Wy-00
	for sigtran@ietf.org; Fri, 13 Feb 2004 11:58:10 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Argd0-0003Sj-00
	for sigtran@ietf.org; Fri, 13 Feb 2004 11:57:22 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i1DGvJ7T015379;
	Fri, 13 Feb 2004 11:57:20 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Cc: "John Loughney" <john.Loughney@nokia.com>,
        "Michael Perler" <mikep@adax.com>
Subject: RE: [Sigtran] SUA v16: Global Titles
Date: Fri, 13 Feb 2004 11:58:49 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOMEJDCEAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <20040128122410.A16922@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
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Brian,

I don't understand what you mean by "If you need to specify any value, ...".
Of course I, and everyone else, must specify a value - GTI is not an
optional field in the Global Title parameter.

I also don't understand how we are supposed to map the GTI values given in
ITU Q.713 3.4.2.3.1 into the values specified in SUA section 3.10.2.3. These
seem to be two disjoint sets.

Barry Nagelberg

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Wednesday, January 28, 2004 2:24 PM
> To: Barry Nagelberg
> Cc: SIGTRAN Mailing List; Seamus Gilchrist; Michael Perler
> Subject: Re: [Sigtran] SUA v16: Global Titles
>
>
> Barry,
>
> I think you'll find that it more closely resembles ANSI T1.112, which does
> not have a nature of address indicator.  Also, encoding scheme is
> only ever
> BCD (odd or even).  GTI in SUA and (for that matter) GTI in ITU
> and ANSI do
> not match.  The GTI in SUA, like ITU and ANSI indicates the fields present
> in the messsage.  If you need to specify any value, use SUA GTI=0100.  The
> SUA GTI does not dictate what is passed to the SS7 network by a gateway.
> The AMF or GTT result will determine that.
>
> Did you have a specific application that cannot be met with the current
> codings?
>
> --brian
>
> Barry Nagelberg wrote:
>                    (Wed, 28 Jan 2004 13:29:39)
> > We have some questions about global titles in SUA.
> >
> > First, in section 3.10.2.3 of SUA draft 16, the definition for
> GTI=0001 does
> > not appear to match with ITU-T Q.713 (1996) 3.4.2.3.1.
> According to Q.713,
> > GTI=0001 means that the global title information only contains
> a nature of
> > address and the global title address. According to the SUA
> draft, GTI=0001
> > means that the nature of address is ignored, that the
> translation type must
> > be 0 (unknown), and that the numbering plan must be 1 (E.164).
> What is the
> > reason for this difference?
> >
> > Also, section 3.10.2.3 does not include an encoding scheme
> field. The draft
> > says "Address signals to be coded as defined in ITU-T Q.713 Section
> > 3.4.2.3.1." That section of the ITU specification includes an
> example of how
> > the digits would be encoded if BCD encoding was used. Does this
> mean that
> > SUA only supports BCD encoding? If other types of encoding can
> be used, how
> > is the encoding scheme specified in the global title?
> >
> > Barry Nagelberg
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


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



From exim@www1.ietf.org  Fri Feb 13 12:59: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 MAA22985
	for <sigtran-archive@odin.ietf.org>; Fri, 13 Feb 2004 12:59:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Arhag-00023Y-DF
	for sigtran-archive@odin.ietf.org; Fri, 13 Feb 2004 12:59:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1DHx2Se007879
	for sigtran-archive@odin.ietf.org; Fri, 13 Feb 2004 12:59:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Arhaf-00022m-Ig; Fri, 13 Feb 2004 12:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArhZu-0001tY-2U
	for sigtran@optimus.ietf.org; Fri, 13 Feb 2004 12:58:14 -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 MAA22886
	for <sigtran@ietf.org>; Fri, 13 Feb 2004 12:58:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArhZs-0001Sk-00
	for sigtran@ietf.org; Fri, 13 Feb 2004 12:58:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArhZ1-0001O0-00
	for sigtran@ietf.org; Fri, 13 Feb 2004 12:57:20 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[v1qCuwIREe3/BuaQ25RxfIDNSN1gh879])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArhYN-0001If-00
	for sigtran@ietf.org; Fri, 13 Feb 2004 12:56:39 -0500
Received: from ns.pigworks.openss7.net (IDENT:rVY5c8XqrkPIC8LStX8ZV/gfnvVQTaVb@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1DHuSI10694;
	Fri, 13 Feb 2004 10:56:28 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1DHuS614058;
	Fri, 13 Feb 2004 10:56:28 -0700
Date: Fri, 13 Feb 2004 10:56:28 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry Nagelberg <barryn@adax.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>,
        John Loughney <john.Loughney@nokia.com>,
        Michael Perler <mikep@adax.com>
Subject: Re: [Sigtran] SUA v16: Global Titles
Message-ID: <20040213105628.B13075@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry Nagelberg <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>,
	John Loughney <john.Loughney@nokia.com>,
	Michael Perler <mikep@adax.com>
References: <20040128122410.A16922@openss7.org> <JBECLENKLBCKAAKFGAJOMEJDCEAA.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: <JBECLENKLBCKAAKFGAJOMEJDCEAA.barryn@adax.com>; from barryn@adax.com on Fri, Feb 13, 2004 at 11:58:49AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Barry,

What I was trying to say was that SUA GTI 0100 global titles can map
nature of address into Q.713 GTI 0001 if you want to specify NAI from
SUA.  Normally, the SCCP GTT function at the SG would decide how to map
SUA GT fields (SCCP-User provided values) into SCCP GT fields.  This
mapping is not specified in SUA, because it is the business of the SS7 node,
however, as SUA GTI 0100 specifies all fields, it is always possible for SUA
to specify any field of a GT.  If you are looking for a 1:1 mapping between
SUA GTI values and SCCP GTI values there is none.  Again, selecting an SCCP
address format is the business of the GTT function at the SG.  This is a
normal function of SCCP.  So, for example:

                        |
                        |  N_UNITDATA_REQ
                        v
                +----------------+
                |                |
                |      SUA       |
                |     (ASP)      |
                |                |
                +----------------+
                        |
                        | SUA CLDT
                        v
                +----------------+
                |                |
                |      SUA       |
                |    (SG-AMF)    |
                |                |
                +----------------+
                        |
                        |  N_UNITDATA_REQ
                        v
                +----------------+
                |                |
                |      SCCP      |
                |                |
                |  Local GTT     |
                |                |
                +----------------+
                        |
                        |  UDT
                        v

All that is necessary is for SUA to provide fields to the N-UNITDATA-Request
(and other SCCP primitives accepting a Called Party Address).

The format of the Called Party Address parameter to N-CONNECT-Request and
N-UNITDATA-Request primitives is not specified (see, for example,
Q.711/6.2.2.2.1) and is implementation specific.  That is, a particular
implementation of SCCP will have made some choices there.  As ITU and ANSI are
rather different, an implementation of the SCCP/SCCP-User interface meant to
be generic across multiple protocol variants would not use GTI.  It might
indicate the presence or absence of each GT element in a GTI indepdendent
fashion.  I don't know what your specific implementation looks like.

So what I was saying is that if your SUA user wants to specify NAI, it should
formulate an N-UNITDATA-Request containing NAI.  SUA at the ASP can place this
value in the SUA Called Party Address with GTI 0100.  SUA at the SG can then
regenerate an N-UNITDATA-Request an issue that primitive to SCCP at the SG.
The local GTT function at the SG is responsible for deciding GTI and Called
Party Address format based on the N-UNITDATA request according to network
routing policy (local GTT datafill).  It is that function that will utlimately
determine the Called Party Address in any resulting UDT message.

For complete IP domain operation (IPSP) the fields populated in the
N-UNITDATA-Request primitive as placed in the CLDT can be indicated in the
N-UNITDATA-Indication primitive.

--brian


Barry Nagelberg wrote:                                                               (Fri, 13 Feb 2004 11:58:49)
> Brian,
> 
> I don't understand what you mean by "If you need to specify any value, ...".
> Of course I, and everyone else, must specify a value - GTI is not an
> optional field in the Global Title parameter.
> 
> I also don't understand how we are supposed to map the GTI values given in
> ITU Q.713 3.4.2.3.1 into the values specified in SUA section 3.10.2.3. These
> seem to be two disjoint sets.
> 
> Barry Nagelberg
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Wednesday, January 28, 2004 2:24 PM
> > To: Barry Nagelberg
> > Cc: SIGTRAN Mailing List; Seamus Gilchrist; Michael Perler
> > Subject: Re: [Sigtran] SUA v16: Global Titles
> >
> >
> > Barry,
> >
> > I think you'll find that it more closely resembles ANSI T1.112, which does
> > not have a nature of address indicator.  Also, encoding scheme is
> > only ever
> > BCD (odd or even).  GTI in SUA and (for that matter) GTI in ITU
> > and ANSI do
> > not match.  The GTI in SUA, like ITU and ANSI indicates the fields present
> > in the messsage.  If you need to specify any value, use SUA GTI=0100.  The
> > SUA GTI does not dictate what is passed to the SS7 network by a gateway.
> > The AMF or GTT result will determine that.
> >
> > Did you have a specific application that cannot be met with the current
> > codings?
> >
> > --brian
> >
> > Barry Nagelberg wrote:
> >                    (Wed, 28 Jan 2004 13:29:39)
> > > We have some questions about global titles in SUA.
> > >
> > > First, in section 3.10.2.3 of SUA draft 16, the definition for
> > GTI=0001 does
> > > not appear to match with ITU-T Q.713 (1996) 3.4.2.3.1.
> > According to Q.713,
> > > GTI=0001 means that the global title information only contains
> > a nature of
> > > address and the global title address. According to the SUA
> > draft, GTI=0001
> > > means that the nature of address is ignored, that the
> > translation type must
> > > be 0 (unknown), and that the numbering plan must be 1 (E.164).
> > What is the
> > > reason for this difference?
> > >
> > > Also, section 3.10.2.3 does not include an encoding scheme
> > field. The draft
> > > says "Address signals to be coded as defined in ITU-T Q.713 Section
> > > 3.4.2.3.1." That section of the ITU specification includes an
> > example of how
> > > the digits would be encoded if BCD encoding was used. Does this
> > mean that
> > > SUA only supports BCD encoding? If other types of encoding can
> > be used, how
> > > is the encoding scheme specified in the global title?
> > >
> > > Barry Nagelberg
> > >
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >
> > --
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Mon Feb 16 15:42:42 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 PAA20452
	for <sigtran-archive@odin.ietf.org>; Mon, 16 Feb 2004 15:42:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AspZF-000386-Ks
	for sigtran-archive@odin.ietf.org; Mon, 16 Feb 2004 15:42:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1GKgDlM011940
	for sigtran-archive@odin.ietf.org; Mon, 16 Feb 2004 15:42:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AspZ4-00030T-8U; Mon, 16 Feb 2004 15:42:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AspYF-0002Zf-R0
	for sigtran@optimus.ietf.org; Mon, 16 Feb 2004 15:41:11 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20142;
	Mon, 16 Feb 2004 15:41:08 -0500 (EST)
Message-Id: <200402162041.PAA20142@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 16 Feb 2004 15:41:08 -0500
Subject: [Sigtran] I-D ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.txt
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

--NextPart
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id PAA20143
Content-Transfer-Encoding: quoted-printable

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

	Title		: M3UA Implementor=C6s Guide
	Author(s)	: J. Pastor, K. Morneault
	Filename	: draft-ietf-sigtran-m3ua-implementors-guide-07.txt
	Pages		: 70
	Date		: 2004-2-16
=09
This document contains a compilation of all defects found up until
the publication date for M3UA [RFC3332]. These defects may be of an
editorial or technical nature. This document may be thought of as a
companion document to be used in the implementation of M3UA to
clarify errors in the original M3UA document. This document updates
RFC3332 and text within this document supersedes the text found in
RFC3332.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-implementors-=
guide-07.txt

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

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

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html=20
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-implementors-guide-07.txt=
".
=09
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.
	=09
	=09
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-2-16123321.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt

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

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

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Mon Feb 16 15:59: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 PAA23361
	for <sigtran-archive@odin.ietf.org>; Mon, 16 Feb 2004 15:59:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AsppV-00058v-Ct
	for sigtran-archive@odin.ietf.org; Mon, 16 Feb 2004 15:59:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1GKx100019752
	for sigtran-archive@odin.ietf.org; Mon, 16 Feb 2004 15:59:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AsppV-00058P-2h; Mon, 16 Feb 2004 15:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aspog-0004wm-1e
	for sigtran@optimus.ietf.org; Mon, 16 Feb 2004 15:58:10 -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 PAA23137
	for <sigtran@ietf.org>; Mon, 16 Feb 2004 15:58:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aspoe-0005So-00
	for sigtran@ietf.org; Mon, 16 Feb 2004 15:58:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AspnT-0005G0-00
	for sigtran@ietf.org; Mon, 16 Feb 2004 15:56:56 -0500
Received: from sjmail.ciena.com ([12.7.169.25] helo=w2ksjexg01.ciena.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aspm9-00051j-00
	for sigtran@ietf.org; Mon, 16 Feb 2004 15:55:33 -0500
Received: by w2ksjexg01.ciena.com with Internet Mail Service (5.5.2657.72)
	id <1JQB4SY3>; Mon, 16 Feb 2004 12:55:11 -0800
Message-ID: <829F074A10F98943A218DC363D09C92A014769BB@w2ksjexg06.oni.com>
From: "Ong, Lyndon" <LyOng@Ciena.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Date: Mon, 16 Feb 2004 12:55:30 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C3F4CF.36497FE0"
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 IG Last Call
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

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

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

Hi Folks,

It sounds like we may be ready to do a Last Call on the
M3UA IG.  If there are no objections, lets start up
Last Call starting today, Feb. 16th and ending on Monday,
March 1st.  Please add "M3UA IG Last Call Comment" in the
subject line for any emails.

If we have agreement on the basic changes in the IG,
the follow up question will be whether to release the
IG itself as a document or incorporate the changes into
a new M3UA spec.

Thanks,

L. Ong

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Monday, February 16, 2004 12:41 PM
Cc: sigtran@ietf.org
Subject: [Sigtran] I-D
ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.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		: M3UA Implementor=C6s Guide
	Author(s)	: J. Pastor, K. Morneault
	Filename	: draft-ietf-sigtran-m3ua-implementors-guide-07.txt
	Pages		: 70
	Date		: 2004-2-16
=09
This document contains a compilation of all defects found up until
the publication date for M3UA [RFC3332]. These defects may be of an
editorial or technical nature. This document may be thought of as a
companion document to be used in the implementation of M3UA to
clarify errors in the original M3UA document. This document updates
RFC3332 and text within this document supersedes the text found in
RFC3332.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-implementors=
-guide-07.txt

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

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

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html=20
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-implementors-guide-07.txt".
=09
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.
	=09
	=09
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


------_=_NextPart_000_01C3F4CF.36497FE0
Content-Type: message/rfc822

To: 
Subject: 
Date: Mon, 16 Feb 2004 12:55:11 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_002_01C3F4CF.36497FE0"


------_=_NextPart_002_01C3F4CF.36497FE0
Content-Type: text/plain



------_=_NextPart_002_01C3F4CF.36497FE0
Content-Type: application/octet-stream;
	name="ATT12099"
Content-Disposition: attachment;
	filename="ATT12099"

Content-type: message/external-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt

------_=_NextPart_002_01C3F4CF.36497FE0
Content-Type: message/external-body;
	site="internet-drafts";
	dir="draft-ietf-sigtran-m3ua-implementors-guide-07.txt";
	mode="ftp.ietf.org";
	access-type="anon-ftp"


------_=_NextPart_002_01C3F4CF.36497FE0--

------_=_NextPart_000_01C3F4CF.36497FE0--

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



From exim@www1.ietf.org  Mon Feb 16 16:14: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 QAA25469
	for <sigtran-archive@odin.ietf.org>; Mon, 16 Feb 2004 16:14:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Asq42-0006dT-1u
	for sigtran-archive@odin.ietf.org; Mon, 16 Feb 2004 16:14:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1GLE1kg025484
	for sigtran-archive@odin.ietf.org; Mon, 16 Feb 2004 16:14:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Asq40-0006cg-RX; Mon, 16 Feb 2004 16:14:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Asq36-0006ZO-Cj
	for sigtran@optimus.ietf.org; Mon, 16 Feb 2004 16:13:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25153
	for <sigtran@ietf.org>; Mon, 16 Feb 2004 16:13:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Asq34-0000AU-00
	for sigtran@ietf.org; Mon, 16 Feb 2004 16:13:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Asq0n-0007Tg-00
	for sigtran@ietf.org; Mon, 16 Feb 2004 16:10:42 -0500
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AspyZ-00070x-00
	for sigtran@ietf.org; Mon, 16 Feb 2004 16:08:24 -0500
Received: from [10.0.1.2] (p5089EB09.dip.t-dialin.net [80.137.235.9])
	by mail-n.franken.de (Postfix) with ESMTP id A451F2462F
	for <sigtran@ietf.org>; Mon, 16 Feb 2004 22:06:54 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v612)
In-Reply-To: <200402162041.PAA20142@ietf.org>
References: <200402162041.PAA20142@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <E4B6038E-60C3-11D8-AF8F-000A95C37894@lurchi.franken.de>
Content-Transfer-Encoding: quoted-printable
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Sigtran] I-D ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.txt
Date: Mon, 16 Feb 2004 22:05:47 +0100
To: sigtran@ietf.org
X-Mailer: Apple Mail (2.612)
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: 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

Dear all,

is it possible that we specify clearly if the version number is checked
either
for all messages
or
only for ASPU-UP messages.

As explained in my earlier mail I would prefer the first solution.
I also think that there was consensus on this on the list.

The new ID describes only the Error parameter but leaves it open, how
it is used. Please reconsider the text I sent.

Best regards
Michael


On 16. Feb 2004, at 21:41 Uhr, Internet-Drafts@ietf.org wrote:

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

> the IETF.
>
> 	Title		: M3UA Implementor=C6s Guide
> 	Author(s)	: J. Pastor, K. Morneault
> 	Filename	: =
draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> 	Pages		: 70
> 	Date		: 2004-2-16
> =09
> This document contains a compilation of all defects found up until
> the publication date for M3UA [RFC3332]. These defects may be of an
> editorial or technical nature. This document may be thought of as a
> companion document to be used in the implementation of M3UA to
> clarify errors in the original M3UA document. This document updates
> RFC3332 and text within this document supersedes the text found in
> RFC3332.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-=20
> implementors-guide-07.txt
>
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the =20
> message.
>
> Internet-Drafts are also available by anonymous FTP. Login with the =20=

> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE =20
> /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> =09
> 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.
> 	=09
> 	=09
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> Content-Type: text/plain
> Content-ID:	<2004-2-16123321.I-D@ietf.org>


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



From exim@www1.ietf.org  Mon Feb 16 16:16: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 QAA25812
	for <sigtran-archive@odin.ietf.org>; Mon, 16 Feb 2004 16:16:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Asq5y-0006rx-UM
	for sigtran-archive@odin.ietf.org; Mon, 16 Feb 2004 16:16:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1GLG2cp026367
	for sigtran-archive@odin.ietf.org; Mon, 16 Feb 2004 16:16:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Asq5y-0006r9-4L; Mon, 16 Feb 2004 16:16:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Asq5A-0006qK-KS
	for sigtran@optimus.ietf.org; Mon, 16 Feb 2004 16:15:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25631
	for <sigtran@ietf.org>; Mon, 16 Feb 2004 16:15:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Asq58-0000d8-00
	for sigtran@ietf.org; Mon, 16 Feb 2004 16:15:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Asq3E-0000Ch-00
	for sigtran@ietf.org; Mon, 16 Feb 2004 16:13:13 -0500
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Asq14-0007Wm-00
	for sigtran@ietf.org; Mon, 16 Feb 2004 16:10:58 -0500
Received: from [10.0.1.2] (p5089EB09.dip.t-dialin.net [80.137.235.9])
	by mail-n.franken.de (Postfix) with ESMTP
	id A12E62462F; Mon, 16 Feb 2004 22:09:30 +0100 (CET)
In-Reply-To: <829F074A10F98943A218DC363D09C92A014769BB@w2ksjexg06.oni.com>
References: <829F074A10F98943A218DC363D09C92A014769BB@w2ksjexg06.oni.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <40755C6A-60C4-11D8-AF8F-000A95C37894@lurchi.franken.de>
Content-Transfer-Encoding: quoted-printable
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Date: Mon, 16 Feb 2004 22:08:21 +0100
To: "Ong, Lyndon" <LyOng@Ciena.com>
X-Mailer: Apple Mail (2.612)
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
Subject: [Sigtran] M3UA IG 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>
Content-Transfer-Encoding: quoted-printable

Lyndon,

please consider my e-mail, which I sent a minute ago, regarding
the version handling as one comment.

Best regards
Michael

On 16. Feb 2004, at 21:55 Uhr, Ong, Lyndon wrote:

> Hi Folks,
>
> It sounds like we may be ready to do a Last Call on the
> M3UA IG.  If there are no objections, lets start up
> Last Call starting today, Feb. 16th and ending on Monday,
> March 1st.  Please add "M3UA IG Last Call Comment" in the
> subject line for any emails.
>
> If we have agreement on the basic changes in the IG,
> the follow up question will be whether to release the
> IG itself as a document or incorporate the changes into
> a new M3UA spec.
>
> Thanks,
>
> L. Ong
>
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Monday, February 16, 2004 12:41 PM
> Cc: sigtran@ietf.org
> Subject: [Sigtran] I-D
> ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts =20
> directories.
> This draft is a work item of the Signaling Transport Working Group of =20=

> the IETF.
>
> 	Title		: M3UA Implementor=C6s Guide
> 	Author(s)	: J. Pastor, K. Morneault
> 	Filename	: =
draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> 	Pages		: 70
> 	Date		: 2004-2-16
> =09
> This document contains a compilation of all defects found up until
> the publication date for M3UA [RFC3332]. These defects may be of an
> editorial or technical nature. This document may be thought of as a
> companion document to be used in the implementation of M3UA to
> clarify errors in the original M3UA document. This document updates
> RFC3332 and text within this document supersedes the text found in
> RFC3332.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-=20
> implementors-guide-07.txt
>
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the =20
> message.
>
> Internet-Drafts are also available by anonymous FTP. Login with the =20=

> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE =20
> /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> =09
> 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.
> 	=09
> 	=09
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
> Date: 16. February 2004 21:55:11 Uhr CET
> To: Subject:
>
>
>
> <ATT12099>
>


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



From exim@www1.ietf.org  Tue Feb 17 09:31: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 JAA29765
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 09:31:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At6Fh-0003ss-SP
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 09:31:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HEV9Rx014930
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 09:31:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At6Fb-0003qg-V9; Tue, 17 Feb 2004 09:31:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At6Ei-0003pH-Io
	for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 09:30:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29697
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 09:30:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At6Eg-000365-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 09:30:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At6Dm-00033L-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 09:29:11 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At6DH-00030M-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 09:28:39 -0500
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 i1HEScAh020736
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 15:28:38 +0100
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 17 Feb 2004 15:28:38 +0100
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id 1LJVXFH9; Tue, 17 Feb 2004 15:28:38 +0100
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <FAB0H5Z8>; Tue, 17 Feb 2004 15:28:36 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C04331A65@eestqnt105.es.eu.ericsson.se>
X-Sybari-Trust: b25605f1 c77f3eb6 201da35e 00000138
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "'Michael Tuexen'" <Michael.Tuexen@lurchi.franken.de>, sigtran@ietf.org
Subject: RE: [Sigtran]  M3UA IG Last Call Comment
Date: Tue, 17 Feb 2004 15:26:03 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-OriginalArrivalTime: 17 Feb 2004 14:28:38.0446 (UTC) FILETIME=[555FFCE0:01C3F562]
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


Michael,=20

The RFC does not say that the version number is only checked for ASP-UP m=
essage, but it states how to deal with different M3UA versions, normally =
detected during the ASPUP exchange.

All the error procedures are defined when the ERROR message is explained,=
 as it is also now the "invalid version". That should be sufficient to un=
derstand how to respond to a wrong version message.

The text you sent was trying to include the general error parameter proce=
dure inside the ASPUP section, what was not correct. By including the gen=
eral description of this Error Parameter and their use, it should solve t=
he problem since it applies to all messages, as you prefer...=20

Cheers // Javier.


> -----Original Message-----
> From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Michael Tuexen
> Sent: lunes, 16 de febrero de 2004 22:06
> To: sigtran@ietf.org
> Subject: Re: [Sigtran] I-D
> ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.txt
>=20
>=20
> Dear all,
>=20
> is it possible that we specify clearly if the version number=20
> is checked
> either
> for all messages
> or
> only for ASPU-UP messages.
>=20
> As explained in my earlier mail I would prefer the first solution.
> I also think that there was consensus on this on the list.
>=20
> The new ID describes only the Error parameter but leaves it open, how
> it is used. Please reconsider the text I sent.
>=20
> Best regards
> Michael
>=20
>=20
> On 16. Feb 2004, at 21:41 Uhr, Internet-Drafts@ietf.org wrote:
>=20
> > A New Internet-Draft is available from the on-line Internet-Drafts =20=

> > directories.
> > This draft is a work item of the Signaling Transport=20
> Working Group of =20
> > the IETF.
> >
> > 	Title		: M3UA Implementor=C6s Guide
> > 	Author(s)	: J. Pastor, K. Morneault
> > 	Filename	:=20
> draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> > 	Pages		: 70
> > 	Date		: 2004-2-16
> > =09
> > This document contains a compilation of all defects found up until
> > the publication date for M3UA [RFC3332]. These defects may be of an
> > editorial or technical nature. This document may be thought of as a
> > companion document to be used in the implementation of M3UA to
> > clarify errors in the original M3UA document. This document updates
> > RFC3332 and text within this document supersedes the text found in
> > RFC3332.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-=20
> > implementors-guide-07.txt
> >
> > To remove yourself from the IETF Announcement list, send a=20
> message to
> > ietf-announce-request with the word unsubscribe in the body of the =20=

> > message.
> >
> > Internet-Drafts are also available by anonymous FTP. Login=20
> with the =20
> > username
> > "anonymous" and a password of your e-mail address. After logging in,
> > type "cd internet-drafts" and then
> > 	"get draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> >
> > A list of Internet-Drafts directories can be found in
> > http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> >
> > Internet-Drafts can also be obtained by e-mail.
> >
> > Send a message to:
> > 	mailserv@ietf.org.
> > In the body type:
> > 	"FILE =20
> > /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> > =09
> > 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=20
> 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.
> > 	=09
> > 	=09
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.
> > Content-Type: text/plain
> > Content-ID:	<2004-2-16123321.I-D@ietf.org>
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20

This communication is confidential and intended solely for the addressee(=
s). Any unauthorized review, use, disclosure or distribution is prohibite=
d. If you believe this message has been sent to you in error, please noti=
fy the sender by replying to this transmission and delete the message wit=
hout disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interrupt=
ion, unauthorized amendment, tampering and viruses, and we only send and =
receive e-mails on the basis that we are not liable for any such corrupti=
on, interception, amendment, tampering or viruses or any consequences the=
reof.


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



From exim@www1.ietf.org  Tue Feb 17 09:55: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 JAA00668
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 09:55:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At6cq-0005zI-QV
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 09:55:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HEt4Ec023009
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 09:55:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At6cp-0005yo-2H; Tue, 17 Feb 2004 09:55:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At6c8-0005xL-29
	for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 09:54:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00633
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 09:54:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At6c6-0004sy-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 09:54:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At6bF-0004p2-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 09:53:25 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1At6ab-0004k3-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 09:52:45 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i1HEqf7T032231
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 09:52:41 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA IG Last Call
Date: Tue, 17 Feb 2004 09:54:11 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOOEJICEAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <829F074A10F98943A218DC363D09C92A014769BB@w2ksjexg06.oni.com>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by slink5.mtl-nj.adax id i1HEqf7T032231
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

Lyndon,

I vote for a new M3UA spec. My neck is sore from having to turn my head b=
ack
and forth so many times between the spec and the IG. :<(

Barry Nagelberg

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf O=
f
> Ong, Lyndon
> Sent: Monday, February 16, 2004 3:56 PM
> To: 'sigtran@ietf.org'
> Subject: [Sigtran] M3UA IG Last Call
>
>
> Hi Folks,
>
> It sounds like we may be ready to do a Last Call on the
> M3UA IG.  If there are no objections, lets start up
> Last Call starting today, Feb. 16th and ending on Monday,
> March 1st.  Please add "M3UA IG Last Call Comment" in the
> subject line for any emails.
>
> If we have agreement on the basic changes in the IG,
> the follow up question will be whether to release the
> IG itself as a document or incorporate the changes into
> a new M3UA spec.
>
> Thanks,
>
> L. Ong
>
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Monday, February 16, 2004 12:41 PM
> Cc: sigtran@ietf.org
> Subject: [Sigtran] I-D
> ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.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		: M3UA Implementor=C6s Guide
> 	Author(s)	: J. Pastor, K. Morneault
> 	Filename	: draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> 	Pages		: 70
> 	Date		: 2004-2-16
>
> This document contains a compilation of all defects found up until
> the publication date for M3UA [RFC3332]. These defects may be of an
> editorial or technical nature. This document may be thought of as a
> companion document to be used in the implementation of M3UA to
> clarify errors in the original M3UA document. This document updates
> RFC3332 and text within this document supersedes the text found in
> RFC3332.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-implem
entors-guide-07.txt

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

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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt=
".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.



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



From exim@www1.ietf.org  Tue Feb 17 10:06:31 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 KAA01866
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 10:06:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At6nT-0001z9-Vd
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 10:06:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HF63un007605
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 10:06:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At6nS-0001yL-Jm; Tue, 17 Feb 2004 10:06:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At6mw-0001qU-Rd
	for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 10:05:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01603
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 10:05:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At6mu-00063H-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:05:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At6ln-0005qt-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:04:21 -0500
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1At6kJ-0005bt-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:02:47 -0500
Received: from [10.0.1.2] (p5089FD30.dip.t-dialin.net [80.137.253.48])
	by mail-n.franken.de (Postfix) with ESMTP
	id 4E830245F7; Tue, 17 Feb 2004 16:01:18 +0100 (CET)
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C04331A65@eestqnt105.es.eu.ericsson.se>
References: <1AB3D30B989BF141BBD5C70057B2EF7C04331A65@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <FD6C3ABE-6159-11D8-9B75-000A95C37894@lurchi.franken.de>
Content-Transfer-Encoding: quoted-printable
Cc: sigtran@ietf.org
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Sigtran]  M3UA IG Last Call Comment
Date: Tue, 17 Feb 2004 16:00:13 +0100
To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
X-Mailer: Apple Mail (2.612)
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

Javier,

I do see that the 'new text' reads

    The "Invalid Version" error is sent if a message with an unsupported
    version is received, the receiving end responds with an Error
    message, indicating the version the receiving node supports and
    notifies layer management.

But looking at the RFC there is an explicit section M3UA Version Control
under the section ASP Up Procedures which led several people to the
conclusion that they do not have to check it for other messages.

Therefore I'm suggesting to put the text I sent earlier as a new=20
section 4.7
and delete section 4.3.4.1.1.

I understood you argument regarding 4.3.3.1.1 but I think version=20
control
is a general thing and should be stated explicitly in a place for=20
general
things and not only in a subsection regarding ASPUP procedures.

Best regards
Michael


On 17. Feb 2004, at 15:26 Uhr, J.Javier Pastor (ML/EEM) wrote:

>
> Michael,
>
> The RFC does not say that the version number is only checked for=20
> ASP-UP message, but it states how to deal with different M3UA=20
> versions, normally detected during the ASPUP exchange.
>
> All the error procedures are defined when the ERROR message is=20
> explained, as it is also now the "invalid version". That should be=20
> sufficient to understand how to respond to a wrong version message.
>
> The text you sent was trying to include the general error parameter=20
> procedure inside the ASPUP section, what was not correct. By including=20=

> the general description of this Error Parameter and their use, it=20
> should solve the problem since it applies to all messages, as you=20
> prefer...
>
> Cheers // Javier.
>
>
>> -----Original Message-----
>> From: sigtran-admin@ietf.org
>> [mailto:sigtran-admin@ietf.org]On Behalf Of
>> Michael Tuexen
>> Sent: lunes, 16 de febrero de 2004 22:06
>> To: sigtran@ietf.org
>> Subject: Re: [Sigtran] I-D
>> ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.txt
>>
>>
>> Dear all,
>>
>> is it possible that we specify clearly if the version number
>> is checked
>> either
>> for all messages
>> or
>> only for ASPU-UP messages.
>>
>> As explained in my earlier mail I would prefer the first solution.
>> I also think that there was consensus on this on the list.
>>
>> The new ID describes only the Error parameter but leaves it open, how
>> it is used. Please reconsider the text I sent.
>>
>> Best regards
>> Michael
>>
>>
>> On 16. Feb 2004, at 21:41 Uhr, Internet-Drafts@ietf.org wrote:
>>
>>> 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		: M3UA Implementor=C6s Guide
>>> 	Author(s)	: J. Pastor, K. Morneault
>>> 	Filename	:
>> draft-ietf-sigtran-m3ua-implementors-guide-07.txt
>>> 	Pages		: 70
>>> 	Date		: 2004-2-16
>>> =09
>>> This document contains a compilation of all defects found up until
>>> the publication date for M3UA [RFC3332]. These defects may be of an
>>> editorial or technical nature. This document may be thought of as a
>>> companion document to be used in the implementation of M3UA to
>>> clarify errors in the original M3UA document. This document updates
>>> RFC3332 and text within this document supersedes the text found in
>>> RFC3332.
>>>
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-
>>> implementors-guide-07.txt
>>>
>>> To remove yourself from the IETF Announcement list, send a
>> message to
>>> ietf-announce-request with the word unsubscribe in the body of the
>>> message.
>>>
>>> Internet-Drafts are also available by anonymous FTP. Login
>> with the
>>> username
>>> "anonymous" and a password of your e-mail address. After logging in,
>>> type "cd internet-drafts" and then
>>> 	"get draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
>>>
>>> A list of Internet-Drafts directories can be found in
>>> http://www.ietf.org/shadow.html
>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>
>>>
>>> Internet-Drafts can also be obtained by e-mail.
>>>
>>> Send a message to:
>>> 	mailserv@ietf.org.
>>> In the body type:
>>> 	"FILE
>>> /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
>>> =09
>>> 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.
>>> 	=09
>>> 	=09
>>> Below is the data which will enable a MIME compliant mail reader
>>> implementation to automatically retrieve the ASCII version of the
>>> Internet-Draft.
>>> Content-Type: text/plain
>>> Content-ID:	<2004-2-16123321.I-D@ietf.org>
>>
>>
>> _______________________________________________
>> Sigtran mailing list
>> Sigtran@ietf.org
>> https://www1.ietf.org/mailman/listinfo/sigtran
>>
>
> This communication is confidential and intended solely for the=20
> addressee(s). Any unauthorized review, use, disclosure or distribution=20=

> is prohibited. If you believe this message has been sent to you in=20
> error, please notify the sender by replying to this transmission and=20=

> delete the message without disclosing it. Thank you.
>
> E-mail including attachments is susceptible to data corruption,=20
> interruption, unauthorized amendment, tampering and viruses, and we=20
> only send and receive e-mails on the basis that we are not liable for=20=

> any such corruption, interception, amendment, tampering or viruses or=20=

> any consequences thereof.
>
>


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



From exim@www1.ietf.org  Tue Feb 17 10:10: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 KAA02438
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 10:10:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At6rL-0003Uc-6M
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 10:10:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HFA3IU013346
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 10:10:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At6rK-0003St-DR; Tue, 17 Feb 2004 10:10:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At6qX-0003Fc-IG
	for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 10:09:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02206
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 10:09:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At6qV-0006Rz-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:09:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At6pg-0006No-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:08:21 -0500
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1At6ov-0006Ja-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:07:33 -0500
Received: from [10.0.1.2] (p5089FD30.dip.t-dialin.net [80.137.253.48])
	by mail-n.franken.de (Postfix) with ESMTP
	id 4438E24612; Tue, 17 Feb 2004 16:06:04 +0100 (CET)
In-Reply-To: <JBECLENKLBCKAAKFGAJOOEJICEAA.barryn@adax.com>
References: <JBECLENKLBCKAAKFGAJOOEJICEAA.barryn@adax.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <A7E4BB00-615A-11D8-9B75-000A95C37894@lurchi.franken.de>
Content-Transfer-Encoding: quoted-printable
Cc: <sigtran@ietf.org>
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Sigtran] M3UA IG Last Call
Date: Tue, 17 Feb 2004 16:04:59 +0100
To: "Barry Nagelberg" <barryn@adax.com>
X-Mailer: Apple Mail (2.612)
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

Hi Lyndon,

I think a new M3UA RFC is the best, that is why we have the IG as
a diff. It can be applied in an easy way.

Best regards
Michael

On 17. Feb 2004, at 15:54 Uhr, Barry Nagelberg wrote:

> Lyndon,
>
> I vote for a new M3UA spec. My neck is sore from having to turn my=20
> head back
> and forth so many times between the spec and the IG. :<(
>
> Barry Nagelberg
>
>> -----Original Message-----
>> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf=20=

>> Of
>> Ong, Lyndon
>> Sent: Monday, February 16, 2004 3:56 PM
>> To: 'sigtran@ietf.org'
>> Subject: [Sigtran] M3UA IG Last Call
>>
>>
>> Hi Folks,
>>
>> It sounds like we may be ready to do a Last Call on the
>> M3UA IG.  If there are no objections, lets start up
>> Last Call starting today, Feb. 16th and ending on Monday,
>> March 1st.  Please add "M3UA IG Last Call Comment" in the
>> subject line for any emails.
>>
>> If we have agreement on the basic changes in the IG,
>> the follow up question will be whether to release the
>> IG itself as a document or incorporate the changes into
>> a new M3UA spec.
>>
>> Thanks,
>>
>> L. Ong
>>
>> -----Original Message-----
>> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
>> Sent: Monday, February 16, 2004 12:41 PM
>> Cc: sigtran@ietf.org
>> Subject: [Sigtran] I-D
>> ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.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		: M3UA Implementor=C6s Guide
>> 	Author(s)	: J. Pastor, K. Morneault
>> 	Filename	: =
draft-ietf-sigtran-m3ua-implementors-guide-07.txt
>> 	Pages		: 70
>> 	Date		: 2004-2-16
>>
>> This document contains a compilation of all defects found up until
>> the publication date for M3UA [RFC3332]. These defects may be of an
>> editorial or technical nature. This document may be thought of as a
>> companion document to be used in the implementation of M3UA to
>> clarify errors in the original M3UA document. This document updates
>> RFC3332 and text within this document supersedes the text found in
>> RFC3332.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-implem
> entors-guide-07.txt
>
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the=20
> message.
>
> Internet-Drafts are also available by anonymous FTP. Login with the=20
> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE=20
> /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
>
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail =
readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
>
> _______________________________________________
> Sigtran mailing 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 Feb 17 10:47: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 KAA07780
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 10:47:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At7R8-0003ez-7f
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 10:47:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HFl2me014024
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 10:47:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At7R6-0003dr-PG; Tue, 17 Feb 2004 10:47:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At7Q9-0003VI-TX
	for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 10:46:01 -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 KAA07456
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 10:45:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At7Q7-0002Wg-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:45:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At7O1-000267-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:43:51 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At7M3-0001gb-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:41:47 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i1HFfkqY020521
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 16:41:46 +0100 (MET)
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 17 Feb 2004 16:41:46 +0100
Received: from ESEALNT744.al.sw.ericsson.se ([153.88.251.4]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id 166BH4Y5; Tue, 17 Feb 2004 16:41:57 +0100
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <FACTY3RJ>; Tue, 17 Feb 2004 16:41:45 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C04331A6B@eestqnt105.es.eu.ericsson.se>
X-Sybari-Trust: 50d08950 c77f3eb6 201da35e 00000138
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA IG Last Call
Date: Tue, 17 Feb 2004 16:40:50 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-OriginalArrivalTime: 17 Feb 2004 15:41:46.0226 (UTC) FILETIME=[8CB21520:01C3F56C]
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

I also think that putting all together is a better approach.

Cheers // Javier.

> -----Original Message-----
> From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Barry Nagelberg
> Sent: martes, 17 de febrero de 2004 15:54
> To: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA IG Last Call
>=20
>=20
> Lyndon,
>=20
> I vote for a new M3UA spec. My neck is sore from having to=20
> turn my head back
> and forth so many times between the spec and the IG. :<(
>=20
> Barry Nagelberg
>=20
> > -----Original Message-----
> > From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Ong, Lyndon
> > Sent: Monday, February 16, 2004 3:56 PM
> > To: 'sigtran@ietf.org'
> > Subject: [Sigtran] M3UA IG Last Call
> >
> >
> > Hi Folks,
> >
> > It sounds like we may be ready to do a Last Call on the
> > M3UA IG.  If there are no objections, lets start up
> > Last Call starting today, Feb. 16th and ending on Monday,
> > March 1st.  Please add "M3UA IG Last Call Comment" in the
> > subject line for any emails.
> >
> > If we have agreement on the basic changes in the IG,
> > the follow up question will be whether to release the
> > IG itself as a document or incorporate the changes into
> > a new M3UA spec.
> >
> > Thanks,
> >
> > L. Ong
> >
> > -----Original Message-----
> > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> > Sent: Monday, February 16, 2004 12:41 PM
> > Cc: sigtran@ietf.org
> > Subject: [Sigtran] I-D
> > ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.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		: M3UA Implementor=C6s Guide
> > 	Author(s)	: J. Pastor, K. Morneault
> > 	Filename	:=20
> draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> > 	Pages		: 70
> > 	Date		: 2004-2-16
> >
> > This document contains a compilation of all defects found up until
> > the publication date for M3UA [RFC3332]. These defects may be of an
> > editorial or technical nature. This document may be thought of as a
> > companion document to be used in the implementation of M3UA to
> > clarify errors in the original M3UA document. This document updates
> > RFC3332 and text within this document supersedes the text found in
> > RFC3332.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-implem
> entors-guide-07.txt
>=20
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body=20
> of the message.
>=20
> Internet-Drafts are also available by anonymous FTP. Login=20
> 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-implementors-guide-07.txt".
>=20
> 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
>=20
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE=20
> /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
>=20
> 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=20
> 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.
>=20
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>=20
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20

This communication is confidential and intended solely for the addressee(=
s). Any unauthorized review, use, disclosure or distribution is prohibite=
d. If you believe this message has been sent to you in error, please noti=
fy the sender by replying to this transmission and delete the message wit=
hout disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interrupt=
ion, unauthorized amendment, tampering and viruses, and we only send and =
receive e-mails on the basis that we are not liable for any such corrupti=
on, interception, amendment, tampering or viruses or any consequences the=
reof.


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



From exim@www1.ietf.org  Tue Feb 17 10:56: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 KAA08957
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 10:56:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At7Zq-0004yu-OO
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 10:56:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HFu2hL019147
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 10:56:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At7Zq-0004ye-Cf; Tue, 17 Feb 2004 10:56:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At7ZH-0004tw-Jt
	for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 10:55:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08925
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 10:55:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At7ZF-00040Y-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:55:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At7YS-0003vq-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:54:37 -0500
Received: from [66.180.118.20] (helo=sevis-main.SEVISNORTHDOM)
	by ietf-mx with esmtp (Exim 4.12)
	id 1At7Xk-0003nh-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:53:52 -0500
Subject: RE: [Sigtran] M3UA IG Last Call
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 17 Feb 2004 09:55:18 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Message-ID: <9B9A9DE704231348A20E8E2CA7696A952874EA@sevis-main.SEVISNORTHDOM>
Content-Class: urn:content-classes:message
Thread-Topic: [Sigtran] M3UA IG Last Call
Thread-Index: AcP1aG0JMAtCFjXnS0WPrm97Yn8jrQABdEzQ
From: "Nitin Vairagare" <nitin.vairagare@sevis.com>
To: "Michael Tuexen" <Michael.Tuexen@lurchi.franken.de>,
        "Barry Nagelberg" <barryn@adax.com>
Cc: <sigtran@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Vote for new M3UA RFC... So we have to look into one spec only.

Nitin

-----Original Message-----
From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]=20
Sent: Tuesday, February 17, 2004 9:05 AM
To: Barry Nagelberg
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA IG Last Call

Hi Lyndon,

I think a new M3UA RFC is the best, that is why we have the IG as
a diff. It can be applied in an easy way.

Best regards
Michael

On 17. Feb 2004, at 15:54 Uhr, Barry Nagelberg wrote:

> Lyndon,
>
> I vote for a new M3UA spec. My neck is sore from having to turn my=20
> head back
> and forth so many times between the spec and the IG. :<(
>
> Barry Nagelberg
>
>> -----Original Message-----
>> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf

>> Of
>> Ong, Lyndon
>> Sent: Monday, February 16, 2004 3:56 PM
>> To: 'sigtran@ietf.org'
>> Subject: [Sigtran] M3UA IG Last Call
>>
>>
>> Hi Folks,
>>
>> It sounds like we may be ready to do a Last Call on the
>> M3UA IG.  If there are no objections, lets start up
>> Last Call starting today, Feb. 16th and ending on Monday,
>> March 1st.  Please add "M3UA IG Last Call Comment" in the
>> subject line for any emails.
>>
>> If we have agreement on the basic changes in the IG,
>> the follow up question will be whether to release the
>> IG itself as a document or incorporate the changes into
>> a new M3UA spec.
>>
>> Thanks,
>>
>> L. Ong
>>
>> -----Original Message-----
>> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
>> Sent: Monday, February 16, 2004 12:41 PM
>> Cc: sigtran@ietf.org
>> Subject: [Sigtran] I-D
>> ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.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		: M3UA Implementor=C6s Guide
>> 	Author(s)	: J. Pastor, K. Morneault
>> 	Filename	:
draft-ietf-sigtran-m3ua-implementors-guide-07.txt
>> 	Pages		: 70
>> 	Date		: 2004-2-16
>>
>> This document contains a compilation of all defects found up until
>> the publication date for M3UA [RFC3332]. These defects may be of an
>> editorial or technical nature. This document may be thought of as a
>> companion document to be used in the implementation of M3UA to
>> clarify errors in the original M3UA document. This document updates
>> RFC3332 and text within this document supersedes the text found in
>> RFC3332.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-implem
> entors-guide-07.txt
>
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the=20
> message.
>
> Internet-Drafts are also available by anonymous FTP. Login with the=20
> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE=20
> /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
>
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
>
> _______________________________________________
> Sigtran mailing 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 Feb 17 11:34: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 KAA07779
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 10:47:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At7R8-0003ea-4Q
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 10:47:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HFl2iW014022
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 10:47:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At7R6-0003db-3j; Tue, 17 Feb 2004 10:47:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At7QN-0003bA-I8
	for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 10:46:15 -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 KAA07485
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 10:46:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At7QL-0002Zm-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:46:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At7OB-00027x-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:44:02 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1At7MA-0001hz-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:41:54 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1At7MA-0003Xt-3I
	for sigtran@ietf.org; Tue, 17 Feb 2004 10:41:54 -0500
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 i1HFfmAh006410
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 16:41:48 +0100
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 17 Feb 2004 16:41:48 +0100
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id 166BH4ZB; Tue, 17 Feb 2004 16:42:00 +0100
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <FAB0H658>; Tue, 17 Feb 2004 16:41:46 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C04331A6A@eestqnt105.es.eu.ericsson.se>
X-Sybari-Trust: 5f37b50a c77f3eb6 201da35e 00000138
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "'Michael Tuexen'" <Michael.Tuexen@lurchi.franken.de>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran]  M3UA IG Last Call Comment
Date: Tue, 17 Feb 2004 16:39:56 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 17 Feb 2004 15:41:48.0570 (UTC) FILETIME=[8E17BFA0:01C3F56C]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by eagle.ericsson.se id i1HFfmAh006410
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

Dear Michael,=20

Pls, see my comments below...

> -----Original Message-----
> From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
> Sent: martes, 17 de febrero de 2004 16:00
> To: J.Javier Pastor (ML/EEM)
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] M3UA IG Last Call Comment
>=20
>=20
> Javier,
>=20
> I do see that the 'new text' reads
>=20
>     The "Invalid Version" error is sent if a message with an=20
> unsupported
>     version is received, the receiving end responds with an Error
>     message, indicating the version the receiving node supports and
>     notifies layer management.
>=20
> But looking at the RFC there is an explicit section M3UA=20
> Version Control
> under the section ASP Up Procedures which led several people to the
> conclusion that they do not have to check it for other messages.
>=20
Yes I understand, and my personal opinion is that it was due to the lack =
of explanation of this parameter in other sections. Now it is explained i=
n general (all the messages). And a specific section inside the Asp-Up pr=
ocedures is kept due to detection of invalid versions in ASP-Up is the re=
gular procedure to detect different M3UA versions implemented. This is a =
typical case that may happen when operators updated their nodes. But rece=
iving a packet in the middle of the data exchange with the wrong version =
is an error as it may be receiving and invalid ASP identifier. Nothing di=
fferent there. General explanation is enough.

> Therefore I'm suggesting to put the text I sent earlier as a new=20
> section 4.7
> and delete section 4.3.4.1.1.
>=20
> I understood you argument regarding 4.3.3.1.1 but I think version=20
> control
> is a general thing and should be stated explicitly in a place for=20
> general
> things and not only in a subsection regarding ASPUP procedures.


Take into account that there are not specific sections for saying that Me=
ssage Class/Type and other errors are checked in every message either and=
 this point is perfectly understood.  I think the main problem with this =
concrete error during the Plugtests is that the only place where it was t=
reated was inside the ASP-Up procedures (of course it was a typo). Now it=
 is treated as the other ones and it should be understood as the other on=
es.=20

My personal opinion, as I said, is that the current change is enough, but=
 if there are more support to your proposal, I have no problem in changin=
g it.=20


Thanks // Javier.


>=20
> Best regards
> Michael
>=20
>=20
> On 17. Feb 2004, at 15:26 Uhr, J.Javier Pastor (ML/EEM) wrote:
>=20
> >
> > Michael,
> >
> > The RFC does not say that the version number is only checked for=20
> > ASP-UP message, but it states how to deal with different M3UA=20
> > versions, normally detected during the ASPUP exchange.
> >
> > All the error procedures are defined when the ERROR message is=20
> > explained, as it is also now the "invalid version". That should be=20
> > sufficient to understand how to respond to a wrong version message.
> >
> > The text you sent was trying to include the general error parameter=20
> > procedure inside the ASPUP section, what was not correct.=20
> By including=20
> > the general description of this Error Parameter and their use, it=20
> > should solve the problem since it applies to all messages, as you=20
> > prefer...
> >
> > Cheers // Javier.
> >
> >
> >> -----Original Message-----
> >> From: sigtran-admin@ietf.org
> >> [mailto:sigtran-admin@ietf.org]On Behalf Of
> >> Michael Tuexen
> >> Sent: lunes, 16 de febrero de 2004 22:06
> >> To: sigtran@ietf.org
> >> Subject: Re: [Sigtran] I-D
> >> ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> >>
> >>
> >> Dear all,
> >>
> >> is it possible that we specify clearly if the version number
> >> is checked
> >> either
> >> for all messages
> >> or
> >> only for ASPU-UP messages.
> >>
> >> As explained in my earlier mail I would prefer the first solution.
> >> I also think that there was consensus on this on the list.
> >>
> >> The new ID describes only the Error parameter but leaves=20
> it open, how
> >> it is used. Please reconsider the text I sent.
> >>
> >> Best regards
> >> Michael
> >>
> >>
> >> On 16. Feb 2004, at 21:41 Uhr, Internet-Drafts@ietf.org wrote:
> >>
> >>> 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		: M3UA Implementor=C6s Guide
> >>> 	Author(s)	: J. Pastor, K. Morneault
> >>> 	Filename	:
> >> draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> >>> 	Pages		: 70
> >>> 	Date		: 2004-2-16
> >>> =09
> >>> This document contains a compilation of all defects found up until
> >>> the publication date for M3UA [RFC3332]. These defects=20
> may be of an
> >>> editorial or technical nature. This document may be=20
> thought of as a
> >>> companion document to be used in the implementation of M3UA to
> >>> clarify errors in the original M3UA document. This=20
> document updates
> >>> RFC3332 and text within this document supersedes the text found in
> >>> RFC3332.
> >>>
> >>> A URL for this Internet-Draft is:
> >>> http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-
> >>> implementors-guide-07.txt
> >>>
> >>> To remove yourself from the IETF Announcement list, send a
> >> message to
> >>> ietf-announce-request with the word unsubscribe in the body of the
> >>> message.
> >>>
> >>> Internet-Drafts are also available by anonymous FTP. Login
> >> with the
> >>> username
> >>> "anonymous" and a password of your e-mail address. After=20
> logging in,
> >>> type "cd internet-drafts" and then
> >>> 	"get draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> >>>
> >>> A list of Internet-Drafts directories can be found in
> >>> http://www.ietf.org/shadow.html
> >>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >>>
> >>>
> >>> Internet-Drafts can also be obtained by e-mail.
> >>>
> >>> Send a message to:
> >>> 	mailserv@ietf.org.
> >>> In the body type:
> >>> 	"FILE
> >>>=20
> /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> >>> =09
> >>> 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.
> >>> 	=09
> >>> 	=09
> >>> Below is the data which will enable a MIME compliant mail reader
> >>> implementation to automatically retrieve the ASCII version of the
> >>> Internet-Draft.
> >>> Content-Type: text/plain
> >>> Content-ID:	<2004-2-16123321.I-D@ietf.org>
> >>
> >>
> >> _______________________________________________
> >> Sigtran mailing list
> >> Sigtran@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/sigtran
> >>
> >
> > This communication is confidential and intended solely for the=20
> > addressee(s). Any unauthorized review, use, disclosure or=20
> distribution=20
> > is prohibited. If you believe this message has been sent to you in=20
> > error, please notify the sender by replying to this=20
> transmission and=20
> > delete the message without disclosing it. Thank you.
> >
> > E-mail including attachments is susceptible to data corruption,=20
> > interruption, unauthorized amendment, tampering and viruses, and we=20
> > only send and receive e-mails on the basis that we are not=20
> liable for=20
> > any such corruption, interception, amendment, tampering or=20
> viruses or=20
> > any consequences thereof.
> >
> >
>=20

This communication is confidential and intended solely for the addressee(=
s). Any unauthorized review, use, disclosure or distribution is prohibite=
d. If you believe this message has been sent to you in error, please noti=
fy the sender by replying to this transmission and delete the message wit=
hout disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interrupt=
ion, unauthorized amendment, tampering and viruses, and we only send and =
receive e-mails on the basis that we are not liable for any such corrupti=
on, interception, amendment, tampering or viruses or any consequences the=
reof.


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



From exim@www1.ietf.org  Tue Feb 17 11:42: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 LAA15394
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 11:42:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At8IN-00024v-T8
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 11:42:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HGg3nC007966
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 11:42:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At8IL-00024J-IK; Tue, 17 Feb 2004 11:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At8IG-000240-Iz
	for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 11:41:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15326
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 11:41:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At8IF-0003Zw-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 11:41:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At8HL-0003Qx-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 11:41:00 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1At8GT-0003Gp-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 11:40:05 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i1HGe47T032715
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 11:40:04 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Date: Tue, 17 Feb 2004 11:41:34 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOGEJMCEAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <JBECLENKLBCKAAKFGAJOOEOOCCAA.barryn@adax.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M3UA IG Last Call Comment: Routing Key not Currently Provisioned
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Javier and Ken,

My suggested text change below doesn't appear in IG v7. I think that it is
necessary, and I didn't receive any negative comments after posting it on
the list.

Barry Nagelberg

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> Barry Nagelberg
> Sent: Wednesday, December 10, 2003 2:15 PM
> To: SIGTRAN Mailing List
> Subject: RE: [Sigtran] M3UA: Redundant RKM error codes
>
>
> Christophe,
>
> OK, now I understand. Thanks. Then we must fix this typo, and add a little
> more explanation. I suggest this:
>
> "  If an SGP determines that a received Routing Key does not currently
>    exist, and the SGP supports dynamic configuration but requires that
>    the Routing Key first be manually provisioned at the SGP, the SGP
>    returns a Registration Response message to the ASP, containing a
>    Registration Result "Error - Routing Key not Currently Provisioned".
>
> Barry Nagelberg
>
> > -----Original Message-----
> > From: Anzile, Christophe [mailto:christophe.anzile@hp.com]
> > Sent: Wednesday, December 10, 2003 1:08 PM
> > To: Barry Nagelberg; SIGTRAN Mailing List
> > Subject: RE: [Sigtran] M3UA: Redundant RKM error codes
> >
> >
> > Barry,
> > that's typically the case when the received Routing Key
> > does not match any existing SGP Routing Key entry
> > (meaning that the routing key is not valid for that specific SGP),
> > even if the REQ REQ is fine.
> > There are SGs that do not support full dynamic reg. procedures,
> > so that RK should be provisioned first at SGP before being valid.
> > Christophe.
> >
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Barry Nagelberg
> > Sent: Wednesday, December 10, 2003 6:55 PM
> > To: SIGTRAN Mailing List
> > Subject: RE: [Sigtran] M3UA: Redundant RKM error codes
> >
> >
> > Cristophe,
> >
> > I am confused about your typo explanation. If the SGP supports
> > RKM, and the
> > Registration request is valid, and the RK does not currently
> > exist, then why
> > would the SGP return an error? Why wouldn't it just create a new RK?
> >
> > Barry Nagelberg
> >
> > > -----Original Message-----
> > > From: Anzile, Christophe [mailto:christophe.anzile@hp.com]
> > > Sent: Wednesday, December 10, 2003 12:12 PM
> > > To: Barry Nagelberg; SIGTRAN Mailing List
> > > Subject: RE: [Sigtran] M3UA: Redundant RKM error codes
> > >
> > >
> > > Hi,
> > > I don't think these are redundant.
> > > You should be able to differentiate the 2 error cases.
> > >
> > > Therefore, I think there is a typo in the second case.
> > > You should read:
> > > "  If an SGP determines that a received Routing Key does not currently
> > >    exist and the SGP supports dynamic configuration, the SGP
> > >    returns a Registration Response message to the ASP, containing a
> > >    Registration Result "Error - Routing Key not Currently
> Provisioned"."
> > >
> > > You have another example in SUA-15, that is:
> > > "  If an SGP determines that a received Routing Key does not currently
> > >    exist and the SGP supports dynamic configuration but does not have
> > >    the capacity to add new Routing Key and Application Server entries,
> > >    the SGP returns a Registration Response message to the ASP,
> > >    containing a Registration Result "Error - Insufficient Resources".
> > >
> > > Regards,
> > > Christophe.
> > >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
[mailto:sigtran-admin@ietf.org]On Behalf Of
> > Barry Nagelberg
> > Sent: Wednesday, December 10, 2003 5:47 PM
> > To: SIGTRAN Mailing List
> > Subject: [Sigtran] M3UA: Redundant RKM error codes
> >
> >
> > I think that we have 2 redundant RKM error codes, one of which should be
> > removed for clarity's sake. The use of these codes is explained
> in section
> > 4.4.1 of the RFC.
> >
> > In the case in which an SGP doesn't support RKM procedures, the
> RFC covers
> > it twice, with 2 different error codes:
> >
> > "  If the SGP does not support the registration procedure, the SGP
> >    returns an Error message to the ASP, with an error code of
> >    "Unsupported Message Class"."
> >
> > AND
> >
> > "  If an SGP determines that a received Routing Key does not currently
> >    exist and the SGP does not support dynamic configuration, the SGP
> >    returns a Registration Response message to the ASP, containing a
> >    Registration Result "Error - Routing Key not Currently Provisioned"."
> >
> > Barry Nagelberg
> >


_______________________________________________
Sigtran mailing 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 Feb 17 12:18: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 MAA18931
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 12:18:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At8rC-0006LC-DW
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 12:18:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HHI25K024350
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 12:18:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At8rB-0006KE-OR; Tue, 17 Feb 2004 12:18:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At8qN-0006I5-Pd
	for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 12:17:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18813
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 12:17:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At8qM-0000Mv-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 12:17:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At8pW-0000J4-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 12:16:19 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[dP3g9m/9r3kMqb/BUSBT0KGgB4d+JuRK])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At8op-0000DF-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 12:15:36 -0500
Received: from ns.pigworks.openss7.net (IDENT:Gly7Wp99JMKJsEm48imYtDxqPnBIjbpc@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1HHFTI26032;
	Tue, 17 Feb 2004 10:15:29 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1HHFSR30100;
	Tue, 17 Feb 2004 10:15:28 -0700
Date: Tue, 17 Feb 2004 10:15:28 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Ong, Lyndon" <LyOng@Ciena.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA IG Last Call
Message-ID: <20040217101528.A29979@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Ong, Lyndon" <LyOng@Ciena.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <829F074A10F98943A218DC363D09C92A014769BB@w2ksjexg06.oni.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <829F074A10F98943A218DC363D09C92A014769BB@w2ksjexg06.oni.com>; from LyOng@Ciena.com on Mon, Feb 16, 2004 at 12:55:30PM -0800
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 i1HHFTI26032
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

Lyndon,

I agree with a replacement document as well, however, can we have
the draft placed in that form for review?  That is, should we not
then be having a WGLC on draft-ietf-sigtran-rfc3332bis-00.txt?

Can we have one?

Isn't a WGLC on draft-ietf-sigtran-m3ua-implementors-guide-07.txt
then premature?

--brian

Lyndon Ong wrote:                                                        =
           (Mon, 16 Feb 2004 12:55:30)
> Hi Folks,
>=20
> It sounds like we may be ready to do a Last Call on the
> M3UA IG.  If there are no objections, lets start up
> Last Call starting today, Feb. 16th and ending on Monday,
> March 1st.  Please add "M3UA IG Last Call Comment" in the
> subject line for any emails.
>=20
> If we have agreement on the basic changes in the IG,
> the follow up question will be whether to release the
> IG itself as a document or incorporate the changes into
> a new M3UA spec.
>=20
> Thanks,
>=20
> L. Ong
>=20
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Monday, February 16, 2004 12:41 PM
> Cc: sigtran@ietf.org
> Subject: [Sigtran] I-D
> ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts dire=
ctories.
> This draft is a work item of the Signaling Transport Working Group of t=
he IETF.
>=20
> 	Title		: M3UA Implementor=C6s Guide
> 	Author(s)	: J. Pastor, K. Morneault
> 	Filename	: draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> 	Pages		: 70
> 	Date		: 2004-2-16
> =09
> This document contains a compilation of all defects found up until
> the publication date for M3UA [RFC3332]. These defects may be of an
> editorial or technical nature. This document may be thought of as a
> companion document to be used in the implementation of M3UA to
> clarify errors in the original M3UA document. This document updates
> RFC3332 and text within this document supersedes the text found in
> RFC3332.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-implementor=
s-guide-07.txt
>=20
> To remove yourself from the IETF Announcement list, send a message to=20
> ietf-announce-request with the word unsubscribe in the body of the mess=
age.
>=20
> Internet-Drafts are also available by anonymous FTP. Login with the use=
rname
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
>=20
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html=20
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.t=
xt".
> =09
> 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.
> 	=09
> 	=09
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>=20

> To:=20
> Date: Mon, 16 Feb 2004 12:55:11 -0800
> Subject:=20
>=20
>=20

>=20
>    Content-type:     message/external-body;    access-type=3D"mail-serv=
er";
>    server=3D"mailserv@ietf.org"    Content-Type:   text/plain   Content=
-ID:
>    <2004-2-16123321.I-D@ietf.org>        ENCODING        mime        FI=
LE
>    /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt




--=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 Feb 17 12:22: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 MAA19193
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 12:22:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At8v5-0006aF-7g
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 12:22:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HHM3ag025282
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 12:22:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At8v4-0006Zb-IY; Tue, 17 Feb 2004 12:22:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At8uN-0006Wo-QD
	for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 12:21:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19124
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 12:21:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At8uM-0000fr-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 12:21:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At8tQ-0000aR-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 12:20:22 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[G6lpnMcW2R6GBP9UPHrUfFj1EHatZq0B])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At8sk-0000Wb-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 12:19:39 -0500
Received: from ns.pigworks.openss7.net (IDENT:MjRsiQWnLeDdY42vDBr+Hy1kNo1x4fwg@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1HHJcI26073;
	Tue, 17 Feb 2004 10:19:38 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1HHJbh30143;
	Tue, 17 Feb 2004 10:19:37 -0700
Date: Tue, 17 Feb 2004 10:19:37 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
Cc: "'Michael Tuexen'" <Michael.Tuexen@lurchi.franken.de>, sigtran@ietf.org
Subject: Re: [Sigtran]  M3UA IG Last Call Comment
Message-ID: <20040217101937.B29979@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>,
	'Michael Tuexen' <Michael.Tuexen@lurchi.franken.de>,
	sigtran@ietf.org
References: <1AB3D30B989BF141BBD5C70057B2EF7C04331A6A@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C04331A6A@eestqnt105.es.eu.ericsson.se>; from j.javier.pastor@ericsson.com on Tue, Feb 17, 2004 at 04:39:56PM +0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i1HHJcI26073
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

J.Javier,

I fully agree with Michael's proposed changes.

Please edit the document accordingly.

--brian

J.Javier Pastor (ML/EEM) wrote:                                          =
         (Tue, 17 Feb 2004 16:39:56)
> Dear Michael,=20
>=20
> Pls, see my comments below...
>=20
> > -----Original Message-----
> > From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
> > Sent: martes, 17 de febrero de 2004 16:00
> > To: J.Javier Pastor (ML/EEM)
> > Cc: sigtran@ietf.org
> > Subject: Re: [Sigtran] M3UA IG Last Call Comment
> >=20
> >=20
> > Javier,
> >=20
> > I do see that the 'new text' reads
> >=20
> >     The "Invalid Version" error is sent if a message with an=20
> > unsupported
> >     version is received, the receiving end responds with an Error
> >     message, indicating the version the receiving node supports and
> >     notifies layer management.
> >=20
> > But looking at the RFC there is an explicit section M3UA=20
> > Version Control
> > under the section ASP Up Procedures which led several people to the
> > conclusion that they do not have to check it for other messages.
> >=20
> Yes I understand, and my personal opinion is that it was due to the lac=
k of
> explanation of this parameter in other sections. Now it is explained in
> general (all the messages). And a specific section inside the Asp-Up
> procedures is kept due to detection of invalid versions in ASP-Up is th=
e
> regular procedure to detect different M3UA versions implemented. This i=
s a
> typical case that may happen when operators updated their nodes. But
> receiving a packet in the middle of the data exchange with the wrong ve=
rsion
> is an error as it may be receiving and invalid ASP identifier. Nothing
> different there. General explanation is enough.
>=20
> > Therefore I'm suggesting to put the text I sent earlier as a new=20
> > section 4.7
> > and delete section 4.3.4.1.1.
> >=20
> > I understood you argument regarding 4.3.3.1.1 but I think version=20
> > control
> > is a general thing and should be stated explicitly in a place for=20
> > general
> > things and not only in a subsection regarding ASPUP procedures.
>=20
>=20
> Take into account that there are not specific sections for saying that
> Message Class/Type and other errors are checked in every message either=
 and
> this point is perfectly understood.  I think the main problem with this
> concrete error during the Plugtests is that the only place where it was
> treated was inside the ASP-Up procedures (of course it was a typo). Now=
 it
> is treated as the other ones and it should be understood as the other o=
nes.=20
>=20
> My personal opinion, as I said, is that the current change is enough, b=
ut if
> there are more support to your proposal, I have no problem in changing =
it.=20
>=20
>=20
> Thanks // Javier.
>=20
>=20
> >=20
> > Best regards
> > Michael
> >=20
> >=20
> > On 17. Feb 2004, at 15:26 Uhr, J.Javier Pastor (ML/EEM) wrote:
> >=20
> > >
> > > Michael,
> > >
> > > The RFC does not say that the version number is only checked for=20
> > > ASP-UP message, but it states how to deal with different M3UA=20
> > > versions, normally detected during the ASPUP exchange.
> > >
> > > All the error procedures are defined when the ERROR message is=20
> > > explained, as it is also now the "invalid version". That should be=20
> > > sufficient to understand how to respond to a wrong version message.
> > >
> > > The text you sent was trying to include the general error parameter=
=20
> > > procedure inside the ASPUP section, what was not correct.=20
> > By including=20
> > > the general description of this Error Parameter and their use, it=20
> > > should solve the problem since it applies to all messages, as you=20
> > > prefer...
> > >
> > > Cheers // Javier.
> > >
> > >
> > >> -----Original Message-----
> > >> From: sigtran-admin@ietf.org
> > >> [mailto:sigtran-admin@ietf.org]On Behalf Of
> > >> Michael Tuexen
> > >> Sent: lunes, 16 de febrero de 2004 22:06
> > >> To: sigtran@ietf.org
> > >> Subject: Re: [Sigtran] I-D
> > >> ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> > >>
> > >>
> > >> Dear all,
> > >>
> > >> is it possible that we specify clearly if the version number
> > >> is checked
> > >> either
> > >> for all messages
> > >> or
> > >> only for ASPU-UP messages.
> > >>
> > >> As explained in my earlier mail I would prefer the first solution.
> > >> I also think that there was consensus on this on the list.
> > >>
> > >> The new ID describes only the Error parameter but leaves=20
> > it open, how
> > >> it is used. Please reconsider the text I sent.
> > >>
> > >> Best regards
> > >> Michael
> > >>
> > >>
> > >> On 16. Feb 2004, at 21:41 Uhr, Internet-Drafts@ietf.org wrote:
> > >>
> > >>> A New Internet-Draft is available from the on-line Internet-Draft=
s
> > >>> directories.
> > >>> This draft is a work item of the Signaling Transport
> > >> Working Group of
> > >>> the IETF.
> > >>>
> > >>> 	Title		: M3UA Implementor=C6s Guide
> > >>> 	Author(s)	: J. Pastor, K. Morneault
> > >>> 	Filename	:
> > >> draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> > >>> 	Pages		: 70
> > >>> 	Date		: 2004-2-16
> > >>> =09
> > >>> This document contains a compilation of all defects found up unti=
l
> > >>> the publication date for M3UA [RFC3332]. These defects=20
> > may be of an
> > >>> editorial or technical nature. This document may be=20
> > thought of as a
> > >>> companion document to be used in the implementation of M3UA to
> > >>> clarify errors in the original M3UA document. This=20
> > document updates
> > >>> RFC3332 and text within this document supersedes the text found i=
n
> > >>> RFC3332.
> > >>>
> > >>> A URL for this Internet-Draft is:
> > >>> http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-
> > >>> implementors-guide-07.txt
> > >>>
> > >>> To remove yourself from the IETF Announcement list, send a
> > >> message to
> > >>> ietf-announce-request with the word unsubscribe in the body of th=
e
> > >>> message.
> > >>>
> > >>> Internet-Drafts are also available by anonymous FTP. Login
> > >> with the
> > >>> username
> > >>> "anonymous" and a password of your e-mail address. After=20
> > logging in,
> > >>> type "cd internet-drafts" and then
> > >>> 	"get draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> > >>>
> > >>> A list of Internet-Drafts directories can be found in
> > >>> http://www.ietf.org/shadow.html
> > >>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > >>>
> > >>>
> > >>> Internet-Drafts can also be obtained by e-mail.
> > >>>
> > >>> Send a message to:
> > >>> 	mailserv@ietf.org.
> > >>> In the body type:
> > >>> 	"FILE
> > >>>=20
> > /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> > >>> =09
> > >>> 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.
> > >>> 	=09
> > >>> 	=09
> > >>> Below is the data which will enable a MIME compliant mail reader
> > >>> implementation to automatically retrieve the ASCII version of the
> > >>> Internet-Draft.
> > >>> Content-Type: text/plain
> > >>> Content-ID:	<2004-2-16123321.I-D@ietf.org>
> > >>
> > >>
> > >> _______________________________________________
> > >> Sigtran mailing list
> > >> Sigtran@ietf.org
> > >> https://www1.ietf.org/mailman/listinfo/sigtran
> > >>
> > >
> > > This communication is confidential and intended solely for the=20
> > > addressee(s). Any unauthorized review, use, disclosure or=20
> > distribution=20
> > > is prohibited. If you believe this message has been sent to you in=20
> > > error, please notify the sender by replying to this=20
> > transmission and=20
> > > delete the message without disclosing it. Thank you.
> > >
> > > E-mail including attachments is susceptible to data corruption,=20
> > > interruption, unauthorized amendment, tampering and viruses, and we=
=20
> > > only send and receive e-mails on the basis that we are not=20
> > liable for=20
> > > any such corruption, interception, amendment, tampering or=20
> > viruses or=20
> > > any consequences thereof.
> > >
> > >
> >=20
>=20
> This communication is confidential and intended solely for the addresse=
e(s). Any unauthorized review, use, disclosure or distribution is prohibi=
ted. If you believe this message has been sent to you in error, please no=
tify the sender by replying to this transmission and delete the message w=
ithout disclosing it. Thank you.
>=20
> E-mail including attachments is susceptible to data corruption, interru=
ption, unauthorized amendment, tampering and viruses, and we only send an=
d receive e-mails on the basis that we are not liable for any such corrup=
tion, interception, amendment, tampering or viruses or any consequences t=
hereof.
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Tue Feb 17 12:26: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 MAA19545
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 12:26:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At8yw-0006ol-TB
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 12:26:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HHQ2Gg026190
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 12:26:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At8yv-0006o4-Pl; Tue, 17 Feb 2004 12:26:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At8yL-0006n0-B9
	for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 12:25:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19420
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 12:25:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At8yJ-0001Aq-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 12:25:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At8xJ-00011V-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 12:24:22 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[X9x11zecXMcTE82olFtTVmRUIMqfNf7p])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At8wJ-0000sO-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 12:23:20 -0500
Received: from ns.pigworks.openss7.net (IDENT:R3FAyxcIzVvNRlpM/u4cqHXuhiYvuppU@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1HHNJI26120;
	Tue, 17 Feb 2004 10:23:19 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1HHNJN30197;
	Tue, 17 Feb 2004 10:23:19 -0700
Date: Tue, 17 Feb 2004 10:23:18 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry Nagelberg <barryn@adax.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA IG Last Call Comment: Routing Key not Currently Provisioned
Message-ID: <20040217102318.C29979@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry Nagelberg <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>
References: <JBECLENKLBCKAAKFGAJOOEOOCCAA.barryn@adax.com> <JBECLENKLBCKAAKFGAJOGEJMCEAA.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: <JBECLENKLBCKAAKFGAJOGEJMCEAA.barryn@adax.com>; from barryn@adax.com on Tue, Feb 17, 2004 at 11:41:34AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Barry,

I, for one, agree wholeheartedly with your proposed change.  Your
proposed text is a vast improvement on the original paragraph.

Could the editor's of the IG please edit this into the document?

--bria

Barry Nagelberg wrote:                                                               (Tue, 17 Feb 2004 11:41:34)
> Javier and Ken,
> 
> My suggested text change below doesn't appear in IG v7. I think that it is
> necessary, and I didn't receive any negative comments after posting it on
> the list.
> 
> Barry Nagelberg
> 
> > -----Original Message-----
> > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Barry Nagelberg
> > Sent: Wednesday, December 10, 2003 2:15 PM
> > To: SIGTRAN Mailing List
> > Subject: RE: [Sigtran] M3UA: Redundant RKM error codes
> >
> >
> > Christophe,
> >
> > OK, now I understand. Thanks. Then we must fix this typo, and add a little
> > more explanation. I suggest this:
> >
> > "  If an SGP determines that a received Routing Key does not currently
> >    exist, and the SGP supports dynamic configuration but requires that
> >    the Routing Key first be manually provisioned at the SGP, the SGP
> >    returns a Registration Response message to the ASP, containing a
> >    Registration Result "Error - Routing Key not Currently Provisioned".
> >
> > Barry Nagelberg
> >
> > > -----Original Message-----
> > > From: Anzile, Christophe [mailto:christophe.anzile@hp.com]
> > > Sent: Wednesday, December 10, 2003 1:08 PM
> > > To: Barry Nagelberg; SIGTRAN Mailing List
> > > Subject: RE: [Sigtran] M3UA: Redundant RKM error codes
> > >
> > >
> > > Barry,
> > > that's typically the case when the received Routing Key
> > > does not match any existing SGP Routing Key entry
> > > (meaning that the routing key is not valid for that specific SGP),
> > > even if the REQ REQ is fine.
> > > There are SGs that do not support full dynamic reg. procedures,
> > > so that RK should be provisioned first at SGP before being valid.
> > > Christophe.
> > >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > Barry Nagelberg
> > > Sent: Wednesday, December 10, 2003 6:55 PM
> > > To: SIGTRAN Mailing List
> > > Subject: RE: [Sigtran] M3UA: Redundant RKM error codes
> > >
> > >
> > > Cristophe,
> > >
> > > I am confused about your typo explanation. If the SGP supports
> > > RKM, and the
> > > Registration request is valid, and the RK does not currently
> > > exist, then why
> > > would the SGP return an error? Why wouldn't it just create a new RK?
> > >
> > > Barry Nagelberg
> > >
> > > > -----Original Message-----
> > > > From: Anzile, Christophe [mailto:christophe.anzile@hp.com]
> > > > Sent: Wednesday, December 10, 2003 12:12 PM
> > > > To: Barry Nagelberg; SIGTRAN Mailing List
> > > > Subject: RE: [Sigtran] M3UA: Redundant RKM error codes
> > > >
> > > >
> > > > Hi,
> > > > I don't think these are redundant.
> > > > You should be able to differentiate the 2 error cases.
> > > >
> > > > Therefore, I think there is a typo in the second case.
> > > > You should read:
> > > > "  If an SGP determines that a received Routing Key does not currently
> > > >    exist and the SGP supports dynamic configuration, the SGP
> > > >    returns a Registration Response message to the ASP, containing a
> > > >    Registration Result "Error - Routing Key not Currently
> > Provisioned"."
> > > >
> > > > You have another example in SUA-15, that is:
> > > > "  If an SGP determines that a received Routing Key does not currently
> > > >    exist and the SGP supports dynamic configuration but does not have
> > > >    the capacity to add new Routing Key and Application Server entries,
> > > >    the SGP returns a Registration Response message to the ASP,
> > > >    containing a Registration Result "Error - Insufficient Resources".
> > > >
> > > > Regards,
> > > > Christophe.
> > > >
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > Barry Nagelberg
> > > Sent: Wednesday, December 10, 2003 5:47 PM
> > > To: SIGTRAN Mailing List
> > > Subject: [Sigtran] M3UA: Redundant RKM error codes
> > >
> > >
> > > I think that we have 2 redundant RKM error codes, one of which should be
> > > removed for clarity's sake. The use of these codes is explained
> > in section
> > > 4.4.1 of the RFC.
> > >
> > > In the case in which an SGP doesn't support RKM procedures, the
> > RFC covers
> > > it twice, with 2 different error codes:
> > >
> > > "  If the SGP does not support the registration procedure, the SGP
> > >    returns an Error message to the ASP, with an error code of
> > >    "Unsupported Message Class"."
> > >
> > > AND
> > >
> > > "  If an SGP determines that a received Routing Key does not currently
> > >    exist and the SGP does not support dynamic configuration, the SGP
> > >    returns a Registration Response message to the ASP, containing a
> > >    Registration Result "Error - Routing Key not Currently Provisioned"."
> > >
> > > Barry Nagelberg
> > >
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Tue Feb 17 13:13: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 NAA23259
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 13:13:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At9iS-0003Lh-3P
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 13:13:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HID4bv012850
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 13:13:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At9iO-0003JR-Uu; Tue, 17 Feb 2004 13:13:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At9he-0003Cn-4b
	for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 13:12:14 -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 NAA23135
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 13:12:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At9hc-0005un-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 13:12:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At9gd-0005o3-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 13:11:12 -0500
Received: from sjmail.ciena.com ([12.7.169.25] helo=w2ksjexg01.ciena.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1At9ff-0005gM-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 13:10:11 -0500
Received: by w2ksjexg01.ciena.com with Internet Mail Service (5.5.2657.72)
	id <1JQB46QF>; Tue, 17 Feb 2004 10:09:50 -0800
Message-ID: <829F074A10F98943A218DC363D09C92A014769C2@w2ksjexg06.oni.com>
From: "Ong, Lyndon" <LyOng@Ciena.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA IG Last Call
Date: Tue, 17 Feb 2004 10:10:04 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=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

Hi Brian,

I was hoping that review of the IG first would bring out
any contentious points to resolve.  Reviewing the full
integrated spec might be more difficult, esp. without a
capability for change bars.

Cheers,

Lyndon

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: Tuesday, February 17, 2004 9:15 AM
To: Ong, Lyndon
Cc: 'sigtran@ietf.org'
Subject: Re: [Sigtran] M3UA IG Last Call


Lyndon,

I agree with a replacement document as well, however, can we have
the draft placed in that form for review?  That is, should we not
then be having a WGLC on draft-ietf-sigtran-rfc3332bis-00.txt?

Can we have one?

Isn't a WGLC on draft-ietf-sigtran-m3ua-implementors-guide-07.txt
then premature?

--brian

Lyndon Ong wrote:                                                       =
            (Mon, 16 Feb 2004 12:55:30)
> Hi Folks,
>=20
> It sounds like we may be ready to do a Last Call on the
> M3UA IG.  If there are no objections, lets start up
> Last Call starting today, Feb. 16th and ending on Monday,
> March 1st.  Please add "M3UA IG Last Call Comment" in the
> subject line for any emails.
>=20
> If we have agreement on the basic changes in the IG,
> the follow up question will be whether to release the
> IG itself as a document or incorporate the changes into
> a new M3UA spec.
>=20
> Thanks,
>=20
> L. Ong
>=20
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Monday, February 16, 2004 12:41 PM
> Cc: sigtran@ietf.org
> Subject: [Sigtran] I-D
> ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.txt
>=20
>=20
> 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.
>=20
> 	Title		: M3UA Implementor=C6s Guide
> 	Author(s)	: J. Pastor, K. Morneault
> 	Filename	: draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> 	Pages		: 70
> 	Date		: 2004-2-16
> =09
> This document contains a compilation of all defects found up until
> the publication date for M3UA [RFC3332]. These defects may be of an
> editorial or technical nature. This document may be thought of as a
> companion document to be used in the implementation of M3UA to
> clarify errors in the original M3UA document. This document updates
> RFC3332 and text within this document supersedes the text found in
> RFC3332.
>=20
> A URL for this Internet-Draft is:
> =
http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-implementors=
-guide-07.txt
>=20
> To remove yourself from the IETF Announcement list, send a message to =

> ietf-announce-request with the word unsubscribe in the body of the =
message.
>=20
> 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-implementors-guide-07.txt".
>=20
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html=20
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE =
/internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> =09
> 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.
> 	=09
> 	=09
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>=20

> To:=20
> Date: Mon, 16 Feb 2004 12:55:11 -0800
> Subject:=20
>=20
>=20

>=20
>    Content-type:     message/external-body;    =
access-type=3D"mail-server";
>    server=3D"mailserv@ietf.org"    Content-Type:   text/plain   =
Content-ID:
>    <2004-2-16123321.I-D@ietf.org>        ENCODING        mime        =
FILE
>    /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt




--=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 Feb 17 13:18:31 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 NAA23799
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 13:18:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At9nG-0004Tn-S5
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 13:18:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HII2sk017155
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 13:18:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At9nG-0004SC-1Y; Tue, 17 Feb 2004 13:18:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At9mV-0004I0-8o
	for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 13:17:15 -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 NAA23651
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 13:17:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At9mT-0006TR-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 13:17:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At9lT-0006Kd-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 13:16:12 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[80Lq8LXwt1SzVWGOGt+Ofp0Bi0UnbV3j])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At9kW-0006Ch-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 13:15:12 -0500
Received: from ns.pigworks.openss7.net (IDENT:TA5eRtUJvjtkeZGKvkQSnXB0KHxGsEph@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1HIFBI27087;
	Tue, 17 Feb 2004 11:15:11 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1HIFBL30911;
	Tue, 17 Feb 2004 11:15:11 -0700
Date: Tue, 17 Feb 2004 11:15:11 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Ong, Lyndon" <LyOng@Ciena.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA IG Last Call
Message-ID: <20040217111511.E29979@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Ong, Lyndon" <LyOng@Ciena.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <829F074A10F98943A218DC363D09C92A014769C2@w2ksjexg06.oni.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <829F074A10F98943A218DC363D09C92A014769C2@w2ksjexg06.oni.com>; from LyOng@Ciena.com on Tue, Feb 17, 2004 at 10:10:04AM -0800
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 i1HIFBI27087
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

Lyndon,

I don't have a problem with that, providing that we will
also be allowed to review and provide LC comments on the
rfc3332bis draft once it is compiled and before it is
advanced.

--brian

Lyndon Ong wrote:                                                        =
           (Tue, 17 Feb 2004 10:10:04)
> Hi Brian,
>=20
> I was hoping that review of the IG first would bring out
> any contentious points to resolve.  Reviewing the full
> integrated spec might be more difficult, esp. without a
> capability for change bars.
>=20
> Cheers,
>=20
> Lyndon
>=20
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Tuesday, February 17, 2004 9:15 AM
> To: Ong, Lyndon
> Cc: 'sigtran@ietf.org'
> Subject: Re: [Sigtran] M3UA IG Last Call
>=20
>=20
> Lyndon,
>=20
> I agree with a replacement document as well, however, can we have
> the draft placed in that form for review?  That is, should we not
> then be having a WGLC on draft-ietf-sigtran-rfc3332bis-00.txt?
>=20
> Can we have one?
>=20
> Isn't a WGLC on draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> then premature?
>=20
> --brian
>=20
> Lyndon Ong wrote:                                                      =
             (Mon, 16 Feb 2004 12:55:30)
> > Hi Folks,
> >=20
> > It sounds like we may be ready to do a Last Call on the
> > M3UA IG.  If there are no objections, lets start up
> > Last Call starting today, Feb. 16th and ending on Monday,
> > March 1st.  Please add "M3UA IG Last Call Comment" in the
> > subject line for any emails.
> >=20
> > If we have agreement on the basic changes in the IG,
> > the follow up question will be whether to release the
> > IG itself as a document or incorporate the changes into
> > a new M3UA spec.
> >=20
> > Thanks,
> >=20
> > L. Ong
> >=20
> > -----Original Message-----
> > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> > Sent: Monday, February 16, 2004 12:41 PM
> > Cc: sigtran@ietf.org
> > Subject: [Sigtran] I-D
> > ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> >=20
> >=20
> > A New Internet-Draft is available from the on-line Internet-Drafts di=
rectories.
> > This draft is a work item of the Signaling Transport Working Group of=
 the IETF.
> >=20
> > 	Title		: M3UA Implementor=C6s Guide
> > 	Author(s)	: J. Pastor, K. Morneault
> > 	Filename	: draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> > 	Pages		: 70
> > 	Date		: 2004-2-16
> > =09
> > This document contains a compilation of all defects found up until
> > the publication date for M3UA [RFC3332]. These defects may be of an
> > editorial or technical nature. This document may be thought of as a
> > companion document to be used in the implementation of M3UA to
> > clarify errors in the original M3UA document. This document updates
> > RFC3332 and text within this document supersedes the text found in
> > RFC3332.
> >=20
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-implement=
ors-guide-07.txt
> >=20
> > To remove yourself from the IETF Announcement list, send a message to=
=20
> > ietf-announce-request with the word unsubscribe in the body of the me=
ssage.
> >=20
> > Internet-Drafts are also available by anonymous FTP. Login with the u=
sername
> > "anonymous" and a password of your e-mail address. After logging in,
> > type "cd internet-drafts" and then
> > 	"get draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> >=20
> > A list of Internet-Drafts directories can be found in
> > http://www.ietf.org/shadow.html=20
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >=20
> >=20
> > Internet-Drafts can also be obtained by e-mail.
> >=20
> > Send a message to:
> > 	mailserv@ietf.org.
> > In the body type:
> > 	"FILE /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07=
.txt".
> > =09
> > 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.
> > 	=09
> > 	=09
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.
> >=20
>=20
> > To:=20
> > Date: Mon, 16 Feb 2004 12:55:11 -0800
> > Subject:=20
> >=20
> >=20
>=20
> >=20
> >    Content-type:     message/external-body;    access-type=3D"mail-se=
rver";
> >    server=3D"mailserv@ietf.org"    Content-Type:   text/plain   Conte=
nt-ID:
> >    <2004-2-16123321.I-D@ietf.org>        ENCODING        mime        =
FILE
> >    /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt
>=20
>=20
>=20
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/

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

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



From exim@www1.ietf.org  Tue Feb 17 13:19: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 NAA23889
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 13:19:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At9oD-0004hM-Mo
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 13:19:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HIJ1Tx018031
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 13:19:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At9oD-0004gd-7W; Tue, 17 Feb 2004 13:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At9nY-0004dn-48
	for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 13:18:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23773
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 13:18:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At9nW-0006dt-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 13:18:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At9mV-0006Tl-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 13:17:16 -0500
Received: from sjmail.ciena.com ([12.7.169.25] helo=w2ksjexg01.ciena.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1At9lW-0006Kz-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 13:16:14 -0500
Received: by w2ksjexg01.ciena.com with Internet Mail Service (5.5.2657.72)
	id <1JQB4644>; Tue, 17 Feb 2004 10:15:53 -0800
Message-ID: <829F074A10F98943A218DC363D09C92A014769C3@w2ksjexg06.oni.com>
From: "Ong, Lyndon" <LyOng@Ciena.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA IG Last Call
Date: Tue, 17 Feb 2004 10:16:10 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=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

That was my intention.

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: Tuesday, February 17, 2004 10:15 AM
To: Ong, Lyndon
Cc: 'sigtran@ietf.org'
Subject: Re: [Sigtran] M3UA IG Last Call


Lyndon,

I don't have a problem with that, providing that we will
also be allowed to review and provide LC comments on the
rfc3332bis draft once it is compiled and before it is
advanced.

--brian

Lyndon Ong wrote:                                                       =
            (Tue, 17 Feb 2004 10:10:04)
> Hi Brian,
>=20
> I was hoping that review of the IG first would bring out
> any contentious points to resolve.  Reviewing the full
> integrated spec might be more difficult, esp. without a
> capability for change bars.
>=20
> Cheers,
>=20
> Lyndon
>=20
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Tuesday, February 17, 2004 9:15 AM
> To: Ong, Lyndon
> Cc: 'sigtran@ietf.org'
> Subject: Re: [Sigtran] M3UA IG Last Call
>=20
>=20
> Lyndon,
>=20
> I agree with a replacement document as well, however, can we have
> the draft placed in that form for review?  That is, should we not
> then be having a WGLC on draft-ietf-sigtran-rfc3332bis-00.txt?
>=20
> Can we have one?
>=20
> Isn't a WGLC on draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> then premature?
>=20
> --brian
>=20
> Lyndon Ong wrote:                                                     =
              (Mon, 16 Feb 2004 12:55:30)
> > Hi Folks,
> >=20
> > It sounds like we may be ready to do a Last Call on the
> > M3UA IG.  If there are no objections, lets start up
> > Last Call starting today, Feb. 16th and ending on Monday,
> > March 1st.  Please add "M3UA IG Last Call Comment" in the
> > subject line for any emails.
> >=20
> > If we have agreement on the basic changes in the IG,
> > the follow up question will be whether to release the
> > IG itself as a document or incorporate the changes into
> > a new M3UA spec.
> >=20
> > Thanks,
> >=20
> > L. Ong
> >=20
> > -----Original Message-----
> > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> > Sent: Monday, February 16, 2004 12:41 PM
> > Cc: sigtran@ietf.org
> > Subject: [Sigtran] I-D
> > ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> >=20
> >=20
> > 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.
> >=20
> > 	Title		: M3UA Implementor=C6s Guide
> > 	Author(s)	: J. Pastor, K. Morneault
> > 	Filename	: draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> > 	Pages		: 70
> > 	Date		: 2004-2-16
> > =09
> > This document contains a compilation of all defects found up until
> > the publication date for M3UA [RFC3332]. These defects may be of an
> > editorial or technical nature. This document may be thought of as a
> > companion document to be used in the implementation of M3UA to
> > clarify errors in the original M3UA document. This document updates
> > RFC3332 and text within this document supersedes the text found in
> > RFC3332.
> >=20
> > A URL for this Internet-Draft is:
> > =
http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-implementors=
-guide-07.txt
> >=20
> > To remove yourself from the IETF Announcement list, send a message =
to=20
> > ietf-announce-request with the word unsubscribe in the body of the =
message.
> >=20
> > 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-implementors-guide-07.txt".
> >=20
> > A list of Internet-Drafts directories can be found in
> > http://www.ietf.org/shadow.html=20
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >=20
> >=20
> > Internet-Drafts can also be obtained by e-mail.
> >=20
> > Send a message to:
> > 	mailserv@ietf.org.
> > In the body type:
> > 	"FILE =
/internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> > =09
> > 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.
> > 	=09
> > 	=09
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.
> >=20
>=20
> > To:=20
> > Date: Mon, 16 Feb 2004 12:55:11 -0800
> > Subject:=20
> >=20
> >=20
>=20
> >=20
> >    Content-type:     message/external-body;    =
access-type=3D"mail-server";
> >    server=3D"mailserv@ietf.org"    Content-Type:   text/plain   =
Content-ID:
> >    <2004-2-16123321.I-D@ietf.org>        ENCODING        mime       =
 FILE
> >    =
/internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt
>=20
>=20
>=20
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/

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

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



From exim@www1.ietf.org  Tue Feb 17 14:35: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 OAA29092
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 14:35:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtAzo-0005Lq-RE
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 14:35:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HJZ4v6020549
	for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 14:35:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtAzl-0005L4-Oo; Tue, 17 Feb 2004 14:35:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtAz3-0005KN-4E
	for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 14:34:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28946
	for <sigtran@ietf.org>; Tue, 17 Feb 2004 14:34:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtAz0-0005Pr-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 14:34:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtAy2-0005Jp-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 14:33:15 -0500
Received: from sjmail.ciena.com ([12.7.169.25] helo=w2ksjexg01.ciena.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtAx9-0005GG-00
	for sigtran@ietf.org; Tue, 17 Feb 2004 14:32:20 -0500
Received: by w2ksjexg01.ciena.com with Internet Mail Service (5.5.2657.72)
	id <1JQB475F>; Tue, 17 Feb 2004 11:31:59 -0800
Message-ID: <829F074A10F98943A218DC363D09C92A014769C4@w2ksjexg06.oni.com>
From: "Ong, Lyndon" <LyOng@Ciena.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        bidulock@openss7.org
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA IG Last Call
Date: Tue, 17 Feb 2004 11:32:12 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=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

That was my intention (is there an echo in here? :o)

Lyndon

-----Original Message-----
From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
Sent: Tuesday, February 17, 2004 10:18 AM
To: Ong, Lyndon; bidulock@openss7.org
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA IG Last Call


Lyndon,

How about a WG last call on the IG, then integrate it with the
RFC and have a final WG last call on the -bis document?

John

> -----Original Message-----
> From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> ext Ong, Lyndon
> Sent: 17 February, 2004 20:10
> To: 'bidulock@openss7.org'
> Cc: 'sigtran@ietf.org'
> Subject: RE: [Sigtran] M3UA IG Last Call
>=20
>=20
>=20
> Hi Brian,
>=20
> I was hoping that review of the IG first would bring out
> any contentious points to resolve.  Reviewing the full
> integrated spec might be more difficult, esp. without a
> capability for change bars.
>=20
> Cheers,
>=20
> Lyndon
>=20
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Tuesday, February 17, 2004 9:15 AM
> To: Ong, Lyndon
> Cc: 'sigtran@ietf.org'
> Subject: Re: [Sigtran] M3UA IG Last Call
>=20
>=20
> Lyndon,
>=20
> I agree with a replacement document as well, however, can we have
> the draft placed in that form for review?  That is, should we not
> then be having a WGLC on draft-ietf-sigtran-rfc3332bis-00.txt?
>=20
> Can we have one?
>=20
> Isn't a WGLC on draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> then premature?
>=20
> --brian
>=20
> Lyndon Ong wrote:                                            =20
>                       (Mon, 16 Feb 2004 12:55:30)
> > Hi Folks,
> >=20
> > It sounds like we may be ready to do a Last Call on the
> > M3UA IG.  If there are no objections, lets start up
> > Last Call starting today, Feb. 16th and ending on Monday,
> > March 1st.  Please add "M3UA IG Last Call Comment" in the
> > subject line for any emails.
> >=20
> > If we have agreement on the basic changes in the IG,
> > the follow up question will be whether to release the
> > IG itself as a document or incorporate the changes into
> > a new M3UA spec.
> >=20
> > Thanks,
> >=20
> > L. Ong
> >=20
> > -----Original Message-----
> > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> > Sent: Monday, February 16, 2004 12:41 PM
> > Cc: sigtran@ietf.org
> > Subject: [Sigtran] I-D
> > ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> >=20
> >=20
> > A New Internet-Draft is available from the on-line=20
> Internet-Drafts directories.
> > This draft is a work item of the Signaling Transport=20
> Working Group of the IETF.
> >=20
> > 	Title		: M3UA Implementor=C6s Guide
> > 	Author(s)	: J. Pastor, K. Morneault
> > 	Filename	:=20
> draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> > 	Pages		: 70
> > 	Date		: 2004-2-16
> > =09
> > This document contains a compilation of all defects found up until
> > the publication date for M3UA [RFC3332]. These defects may be of an
> > editorial or technical nature. This document may be thought of as a
> > companion document to be used in the implementation of M3UA to
> > clarify errors in the original M3UA document. This document updates
> > RFC3332 and text within this document supersedes the text found in
> > RFC3332.
> >=20
> > A URL for this Internet-Draft is:
> >=20
> http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-im
> plementors-guide-07.txt
> >=20
> > To remove yourself from the IETF Announcement list, send a=20
> message to=20
> > ietf-announce-request with the word unsubscribe in the body=20
> of the message.
> >=20
> > Internet-Drafts are also available by anonymous FTP. Login=20
> 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-implementors-guide-07.txt".
> >=20
> > A list of Internet-Drafts directories can be found in
> > http://www.ietf.org/shadow.html=20
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >=20
> >=20
> > Internet-Drafts can also be obtained by e-mail.
> >=20
> > Send a message to:
> > 	mailserv@ietf.org.
> > In the body type:
> > 	"FILE=20
> /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> > =09
> > 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=20
> 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.
> > 	=09
> > 	=09
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.
> >=20
>=20
> > To:=20
> > Date: Mon, 16 Feb 2004 12:55:11 -0800
> > Subject:=20
> >=20
> >=20
>=20
> >=20
> >    Content-type:     message/external-body;   =20
> access-type=3D"mail-server";
> >    server=3D"mailserv@ietf.org"    Content-Type:   text/plain=20
>   Content-ID:
> >    <2004-2-16123321.I-D@ietf.org>        ENCODING       =20
> mime        FILE
> >   =20
> /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt
>=20
>=20
>=20
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20

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



From exim@www1.ietf.org  Wed Feb 18 09:13: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 JAA11629
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Feb 2004 09:13:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtSRk-00019m-Fq
	for sigtran-archive@odin.ietf.org; Wed, 18 Feb 2004 09:13:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1IED4C4004423
	for sigtran-archive@odin.ietf.org; Wed, 18 Feb 2004 09:13:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtSRh-000193-91; Wed, 18 Feb 2004 09:13:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtSRW-00016l-4d
	for sigtran@optimus.ietf.org; Wed, 18 Feb 2004 09:12:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11594
	for <sigtran@ietf.org>; Wed, 18 Feb 2004 09:12:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtSRU-0000rU-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 09:12:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtSQW-0000o2-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 09:11:49 -0500
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtSPa-0000kJ-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 09:10:50 -0500
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i1IEAIDm008044;
	Wed, 18 Feb 2004 08:10:18 -0600 (CST)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id i1IE9l1C019210;
	Wed, 18 Feb 2004 08:09:47 -0600 (CST)
Date: Wed, 18 Feb 2004 08:09:47 -0600 (CST)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Ong, Lyndon" <LyOng@Ciena.com>
cc: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        bidulock@openss7.org, sigtran@ietf.org
Subject: RE: [Sigtran] M3UA IG Last Call
In-Reply-To: <829F074A10F98943A218DC363D09C92A014769C4@w2ksjexg06.oni.com>
Message-ID: <Pine.SOL.4.10.10402180807320.19998-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.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


Please integrate IG with RFC. I agree to do this.

--Samuel

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

On Tue, 17 Feb 2004, Ong, Lyndon wrote:

> That was my intention (is there an echo in here? :o)
>=20
> Lyndon
>=20
> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
> Sent: Tuesday, February 17, 2004 10:18 AM
> To: Ong, Lyndon; bidulock@openss7.org
> Cc: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA IG Last Call
>=20
>=20
> Lyndon,
>=20
> How about a WG last call on the IG, then integrate it with the
> RFC and have a final WG last call on the -bis document?
>=20
> John
>=20
> > -----Original Message-----
> > From: sigtran-admin@ietf.org=20
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > ext Ong, Lyndon
> > Sent: 17 February, 2004 20:10
> > To: 'bidulock@openss7.org'
> > Cc: 'sigtran@ietf.org'
> > Subject: RE: [Sigtran] M3UA IG Last Call
> >=20
> >=20
> >=20
> > Hi Brian,
> >=20
> > I was hoping that review of the IG first would bring out
> > any contentious points to resolve.  Reviewing the full
> > integrated spec might be more difficult, esp. without a
> > capability for change bars.
> >=20
> > Cheers,
> >=20
> > Lyndon
> >=20
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Tuesday, February 17, 2004 9:15 AM
> > To: Ong, Lyndon
> > Cc: 'sigtran@ietf.org'
> > Subject: Re: [Sigtran] M3UA IG Last Call
> >=20
> >=20
> > Lyndon,
> >=20
> > I agree with a replacement document as well, however, can we have
> > the draft placed in that form for review?  That is, should we not
> > then be having a WGLC on draft-ietf-sigtran-rfc3332bis-00.txt?
> >=20
> > Can we have one?
> >=20
> > Isn't a WGLC on draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> > then premature?
> >=20
> > --brian
> >=20
> > Lyndon Ong wrote:                                            =20
> >                       (Mon, 16 Feb 2004 12:55:30)
> > > Hi Folks,
> > >=20
> > > It sounds like we may be ready to do a Last Call on the
> > > M3UA IG.  If there are no objections, lets start up
> > > Last Call starting today, Feb. 16th and ending on Monday,
> > > March 1st.  Please add "M3UA IG Last Call Comment" in the
> > > subject line for any emails.
> > >=20
> > > If we have agreement on the basic changes in the IG,
> > > the follow up question will be whether to release the
> > > IG itself as a document or incorporate the changes into
> > > a new M3UA spec.
> > >=20
> > > Thanks,
> > >=20
> > > L. Ong
> > >=20
> > > -----Original Message-----
> > > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> > > Sent: Monday, February 16, 2004 12:41 PM
> > > Cc: sigtran@ietf.org
> > > Subject: [Sigtran] I-D
> > > ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> > >=20
> > >=20
> > > A New Internet-Draft is available from the on-line=20
> > Internet-Drafts directories.
> > > This draft is a work item of the Signaling Transport=20
> > Working Group of the IETF.
> > >=20
> > > =09Title=09=09: M3UA Implementor=C6s Guide
> > > =09Author(s)=09: J. Pastor, K. Morneault
> > > =09Filename=09:=20
> > draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> > > =09Pages=09=09: 70
> > > =09Date=09=09: 2004-2-16
> > > =09
> > > This document contains a compilation of all defects found up until
> > > the publication date for M3UA [RFC3332]. These defects may be of an
> > > editorial or technical nature. This document may be thought of as a
> > > companion document to be used in the implementation of M3UA to
> > > clarify errors in the original M3UA document. This document updates
> > > RFC3332 and text within this document supersedes the text found in
> > > RFC3332.
> > >=20
> > > A URL for this Internet-Draft is:
> > >=20
> > http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-im
> > plementors-guide-07.txt
> > >=20
> > > To remove yourself from the IETF Announcement list, send a=20
> > message to=20
> > > ietf-announce-request with the word unsubscribe in the body=20
> > of the message.
> > >=20
> > > Internet-Drafts are also available by anonymous FTP. Login=20
> > with the username
> > > "anonymous" and a password of your e-mail address. After logging in,
> > > type "cd internet-drafts" and then
> > > =09"get draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> > >=20
> > > A list of Internet-Drafts directories can be found in
> > > http://www.ietf.org/shadow.html=20
> > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > >=20
> > >=20
> > > Internet-Drafts can also be obtained by e-mail.
> > >=20
> > > Send a message to:
> > > =09mailserv@ietf.org.
> > > In the body type:
> > > =09"FILE=20
> > /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> > > =09
> > > NOTE:=09The mail server at ietf.org can return the document in
> > > =09MIME-encoded form by using the "mpack" utility.  To use this
> > > =09feature, insert the command "ENCODING mime" before the "FILE"
> > > =09command.  To decode the response(s), you will need "munpack" or
> > > =09a MIME-compliant mail reader.  Different MIME-compliant=20
> > mail readers
> > > =09exhibit different behavior, especially when dealing with
> > > =09"multipart" MIME messages (i.e. documents which have been split
> > > =09up into multiple messages), so check your local documentation on
> > > =09how to manipulate these messages.
> > > =09=09
> > > =09=09
> > > Below is the data which will enable a MIME compliant mail reader
> > > implementation to automatically retrieve the ASCII version of the
> > > Internet-Draft.
> > >=20
> >=20
> > > To:=20
> > > Date: Mon, 16 Feb 2004 12:55:11 -0800
> > > Subject:=20
> > >=20
> > >=20
> >=20
> > >=20
> > >    Content-type:     message/external-body;   =20
> > access-type=3D"mail-server";
> > >    server=3D"mailserv@ietf.org"    Content-Type:   text/plain=20
> >   Content-ID:
> > >    <2004-2-16123321.I-D@ietf.org>        ENCODING       =20
> > mime        FILE
> > >   =20
> > /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> >=20
> >=20
> >=20
> >=20
> > --=20
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20
>=20


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



From exim@www1.ietf.org  Wed Feb 18 15:27:34 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 PAA17731
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Feb 2004 15:27:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtYHg-00007g-B4
	for sigtran-archive@odin.ietf.org; Wed, 18 Feb 2004 15:27:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1IKR4CV000471
	for sigtran-archive@odin.ietf.org; Wed, 18 Feb 2004 15:27:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtYHd-00007Q-OR; Wed, 18 Feb 2004 15:27:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtYGh-0008Or-0K
	for sigtran@optimus.ietf.org; Wed, 18 Feb 2004 15:26:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17644
	for <sigtran@ietf.org>; Wed, 18 Feb 2004 15:26:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtYGf-0003qp-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 15:26:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtYFm-0003p3-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 15:25:06 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtYFS-0003n6-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 15:24:46 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i1IKOg7T006458;
	Wed, 18 Feb 2004 15:24:42 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Cc: "Seamus Gilchrist" <sgilchrist@connetcom.com>
Date: Wed, 18 Feb 2004 15:26:12 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOCEKKCEAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] SUA v16: TID and DRM 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

We have several suggestions for improving the clarity of the definition and
use of the TID and DRM label parameters:

1. Clarity - After some head-scratching and detective work, we think we
understand their purpose. We're assuming that:

a. These labels are simply 16-bit masks that are logically ANDed onto the
received TCAP transaction ID, starting at the "Start" bit.

b. If the result of the AND operation exactly matches the "Label" field,
then the message is sent to the ASP that registered for this label via the
ASPAC msg.

c. An ASP that registers a label will be sent only those TID-bearing
messages that match its label.

d. An ASP that does not register a label may be sent any TID-bearing
message.

If these assumptions are correct, please state them explicitly in the
relevant sections of the draft(3.10.15, 3.10.16, 4.7.2.1 and 4.7.3.1). If
not, please clarify. It's not enough to say, as in 4.7.3.1, "the SG extracts
the label".


2. Redundancy - The label values are fixed length (16 bits). So why do we
need both a "Start" and an "End" position for applying the mask? One or the
other would seem to be enough.

3. Simplicity - Why bother with a partial-sized mask at a specified "start"
bit. Why not just specify a "full-sized" 32-bit (TID) or 23-bit (DRM) mask?

4. Contradictions - Section 4.7.2.1 states that "All the ASPs within the AS
_must_ specify a unique label at a fixed position in the TID or DRN
parameter." The "must" here contradicts that fact the the TID and DRM
parameters are listed as Optional in the ASPAC msg. We're guessing that the
intention here is either:

a. "If at least one of the ASPs within an AS specifies a label, then all the
ASPs within the AS must specify a unique label at a fixed position in the
TID or DRN parameter."

or

b. "All of the labels specified by the ASPs within an AS must start at a
fixed position in the TID or DRN parameter."

or maybe

(a) AND (b). Please clarify.


Barry Nagelberg


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



From exim@www1.ietf.org  Wed Feb 18 16:21: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 QAA21854
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Feb 2004 16:21:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtZ80-0007Kn-DO
	for sigtran-archive@odin.ietf.org; Wed, 18 Feb 2004 16:21:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1ILL7wl028183
	for sigtran-archive@odin.ietf.org; Wed, 18 Feb 2004 16:21:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtZ7x-0007K4-TL; Wed, 18 Feb 2004 16:21:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtZ7A-00076T-S1
	for sigtran@optimus.ietf.org; Wed, 18 Feb 2004 16:20:16 -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 QAA21619
	for <sigtran@ietf.org>; Wed, 18 Feb 2004 16:20:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtZ79-00011A-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 16:20:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtZ5V-0000jq-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 16:18:35 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[NCZ/OIs8xP6PuqjUp20u/16ZzchkLK4p])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtZ41-0000Ss-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 16:17:01 -0500
Received: from ns.pigworks.openss7.net (IDENT:ADsJdSegnKKuN3wB9w3C8eVUk6XSTDg6@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1ILGiI27381;
	Wed, 18 Feb 2004 14:16:44 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1ILGhh03310;
	Wed, 18 Feb 2004 14:16:43 -0700
Date: Wed, 18 Feb 2004 14:16:43 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry Nagelberg <barryn@adax.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>,
        Seamus Gilchrist <sgilchrist@connetcom.com>
Subject: Re: [Sigtran] SUA v16: TID and DRM labels
Message-ID: <20040218141643.C2329@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry Nagelberg <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>,
	Seamus Gilchrist <sgilchrist@connetcom.com>
References: <JBECLENKLBCKAAKFGAJOCEKKCEAA.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: <JBECLENKLBCKAAKFGAJOCEKKCEAA.barryn@adax.com>; from barryn@adax.com on Wed, Feb 18, 2004 at 03:26:12PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Barry,

Barry Nagelberg wrote:                                                               (Wed, 18 Feb 2004 15:26:12)
> We have several suggestions for improving the clarity of the definition and
> use of the TID and DRM label parameters:
> 
> 1. Clarity - After some head-scratching and detective work, we think we
> understand their purpose. We're assuming that:
> 
> a. These labels are simply 16-bit masks that are logically ANDed onto the
> received TCAP transaction ID, starting at the "Start" bit.
> 
> b. If the result of the AND operation exactly matches the "Label" field,
> then the message is sent to the ASP that registered for this label via the
> ASPAC msg.
> 
> c. An ASP that registers a label will be sent only those TID-bearing
> messages that match its label.
> 
> d. An ASP that does not register a label may be sent any TID-bearing
> message.
> 
> If these assumptions are correct, please state them explicitly in the
> relevant sections of the draft(3.10.15, 3.10.16, 4.7.2.1 and 4.7.3.1). If
> not, please clarify. It's not enough to say, as in 4.7.3.1, "the SG extracts
> the label".

That's my understanding.  Some clarity would be good.  Can you provide text?

> 
> 
> 2. Redundancy - The label values are fixed length (16 bits). So why do we
> need both a "Start" and an "End" position for applying the mask? One or the
> other would seem to be enough.

The label does not have to be 16 (significant) bits.

> 
> 3. Simplicity - Why bother with a partial-sized mask at a specified "start"
> bit. Why not just specify a "full-sized" 32-bit (TID) or 23-bit (DRM) mask?

I don't know of any reason not to allow specification of a full 32-bit mask
either.

> 
> 4. Contradictions - Section 4.7.2.1 states that "All the ASPs within the AS
> _must_ specify a unique label at a fixed position in the TID or DRN
> parameter." The "must" here contradicts that fact the the TID and DRM
> parameters are listed as Optional in the ASPAC msg. We're guessing that the
> intention here is either:
> 
> a. "If at least one of the ASPs within an AS specifies a label, then all the
> ASPs within the AS must specify a unique label at a fixed position in the
> TID or DRN parameter."
> 
> or
> 
> b. "All of the labels specified by the ASPs within an AS must start at a
> fixed position in the TID or DRN parameter."
> 
> or maybe
> 
> (a) AND (b). Please clarify.

I think we meant, "The ASPs within the AS specifying a label, must specify a 
unique label at a fixed position in the TID or DRN parameter."  The point
being that no two labels (optionally specified) can overlap.

That said, the label mechanism is still broken, as detailed in previous
threads.  As it is an optional procedure, it might get fixed or fall out of
use in the future.

See draft-bidulock-sigtran-loadsel-02.pdf  I also have a session registration
draft (never submitted) that provides a superior approach to the same problem.
If someone is interested I will sumbit it.

--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  Wed Feb 18 17:22:31 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 RAA26178
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Feb 2004 17:22:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ata4y-0005P9-SO
	for sigtran-archive@odin.ietf.org; Wed, 18 Feb 2004 17:22:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1IMM4Zw020760
	for sigtran-archive@odin.ietf.org; Wed, 18 Feb 2004 17:22:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ata4v-0005Oe-8a; Wed, 18 Feb 2004 17:22:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ata4b-0005OQ-N6
	for sigtran@optimus.ietf.org; Wed, 18 Feb 2004 17:21:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26169
	for <sigtran@ietf.org>; Wed, 18 Feb 2004 17:21:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ata4Z-0005LZ-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 17:21:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ata3k-0005KC-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 17:20:49 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ata3D-0005Hn-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 17:20:15 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i1IMKC7T006883;
	Wed, 18 Feb 2004 17:20:13 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Cc: "Seamus Gilchrist" <sgilchrist@connetcom.com>
Subject: RE: [Sigtran] SUA v16: TID and DRM labels
Date: Wed, 18 Feb 2004 17:21:43 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOIEKMCEAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <20040218141643.C2329@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
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Brian,

Thanks for the clarifications. Regarding your comments:

1. Suggested text - We already provided it. Please see #1 below.

2. Length of mask - Section 3.10.16 states that the length of the mask is 16
bits. No where else in the draft is it mentioned that not all of the bits
are significant. If you are contending that not all of the bits are
significant, then this is another aspect that must be clarified.

3. I agree with you that the label mechanism, as currently specified, is
broken. However it is NOT optional, because there is no mechanism specified
through which the SGP can indicate to the ASP that it doesn't support the
TID Label parameter in the ASPAC message (there is no "Unsupported
parameter" error code). Thus SUA itself is also broken. So the label
mechanism must either be fixed or removed.

Barry Nagelberg


> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Wednesday, February 18, 2004 4:17 PM
> To: Barry Nagelberg
> Cc: SIGTRAN Mailing List; Seamus Gilchrist
> Subject: Re: [Sigtran] SUA v16: TID and DRM labels
>
>
> Barry,
>
> Barry Nagelberg wrote:
>                    (Wed, 18 Feb 2004 15:26:12)
> > We have several suggestions for improving the clarity of the
> definition and
> > use of the TID and DRM label parameters:
> >
> > 1. Clarity - After some head-scratching and detective work, we think we
> > understand their purpose. We're assuming that:
> >
> > a. These labels are simply 16-bit masks that are logically
> ANDed onto the
> > received TCAP transaction ID, starting at the "Start" bit.
> >
> > b. If the result of the AND operation exactly matches the "Label" field,
> > then the message is sent to the ASP that registered for this
> label via the
> > ASPAC msg.
> >
> > c. An ASP that registers a label will be sent only those TID-bearing
> > messages that match its label.
> >
> > d. An ASP that does not register a label may be sent any TID-bearing
> > message.
> >
> > If these assumptions are correct, please state them explicitly in the
> > relevant sections of the draft(3.10.15, 3.10.16, 4.7.2.1 and
> 4.7.3.1). If
> > not, please clarify. It's not enough to say, as in 4.7.3.1,
> "the SG extracts
> > the label".
>
> That's my understanding.  Some clarity would be good.  Can you
> provide text?
>
> >
> >
> > 2. Redundancy - The label values are fixed length (16 bits). So
> why do we
> > need both a "Start" and an "End" position for applying the
> mask? One or the
> > other would seem to be enough.
>
> The label does not have to be 16 (significant) bits.
>
> >
> > 3. Simplicity - Why bother with a partial-sized mask at a
> specified "start"
> > bit. Why not just specify a "full-sized" 32-bit (TID) or 23-bit
> (DRM) mask?
>
> I don't know of any reason not to allow specification of a full
> 32-bit mask
> either.
>
> >
> > 4. Contradictions - Section 4.7.2.1 states that "All the ASPs
> within the AS
> > _must_ specify a unique label at a fixed position in the TID or DRN
> > parameter." The "must" here contradicts that fact the the TID and DRM
> > parameters are listed as Optional in the ASPAC msg. We're
> guessing that the
> > intention here is either:
> >
> > a. "If at least one of the ASPs within an AS specifies a label,
> then all the
> > ASPs within the AS must specify a unique label at a fixed
> position in the
> > TID or DRN parameter."
> >
> > or
> >
> > b. "All of the labels specified by the ASPs within an AS must start at a
> > fixed position in the TID or DRN parameter."
> >
> > or maybe
> >
> > (a) AND (b). Please clarify.
>
> I think we meant, "The ASPs within the AS specifying a label,
> must specify a
> unique label at a fixed position in the TID or DRN parameter."  The point
> being that no two labels (optionally specified) can overlap.
>
> That said, the label mechanism is still broken, as detailed in previous
> threads.  As it is an optional procedure, it might get fixed or
> fall out of
> use in the future.
>
> See draft-bidulock-sigtran-loadsel-02.pdf  I also have a session
> registration
> draft (never submitted) that provides a superior approach to the
> same problem.
> If someone is interested I will sumbit it.
>
> --brian
>
> >
> >
> > Barry Nagelberg


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



From exim@www1.ietf.org  Wed Feb 18 18:59: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 SAA03050
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Feb 2004 18:59:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Atbap-0004f1-Uz
	for sigtran-archive@odin.ietf.org; Wed, 18 Feb 2004 18:59:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1INx3ub017912
	for sigtran-archive@odin.ietf.org; Wed, 18 Feb 2004 18:59:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Atbao-0004ec-23; Wed, 18 Feb 2004 18:59:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtbaV-0004eD-MW
	for sigtran@optimus.ietf.org; Wed, 18 Feb 2004 18:58:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03042
	for <sigtran@ietf.org>; Wed, 18 Feb 2004 18:58:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtbaS-0003Yu-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 18:58:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtbZZ-0003Xq-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 18:57:46 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[PIS0B/gdLX/U1kJTGma17oBF9jsXgFnn])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtbZH-0003WC-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 18:57:27 -0500
Received: from ns.pigworks.openss7.net (IDENT:+VOAr2aQCUOSeKG7OJmr5vITdO3zxaC8@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1INvII29583;
	Wed, 18 Feb 2004 16:57:18 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1INvHP05257;
	Wed, 18 Feb 2004 16:57:17 -0700
Date: Wed, 18 Feb 2004 16:57:17 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Barry Nagelberg <barryn@adax.com>
Cc: SIGTRAN Mailing List <sigtran@ietf.org>,
        Seamus Gilchrist <sgilchrist@connetcom.com>
Subject: Re: [Sigtran] SUA v16: TID and DRM labels
Message-ID: <20040218165717.B4354@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Barry Nagelberg <barryn@adax.com>,
	SIGTRAN Mailing List <sigtran@ietf.org>,
	Seamus Gilchrist <sgilchrist@connetcom.com>
References: <20040218141643.C2329@openss7.org> <JBECLENKLBCKAAKFGAJOIEKMCEAA.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: <JBECLENKLBCKAAKFGAJOIEKMCEAA.barryn@adax.com>; from barryn@adax.com on Wed, Feb 18, 2004 at 05:21:43PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Barry,

I think the decision at last call was that it would neither be fixed nor
removed.  Perhaps John an Lyndon could shed some light on the possibility
of doing either at this late date.

--brian

Barry Nagelberg wrote:                                                               (Wed, 18 Feb 2004 17:21:43)
> Brian,
> 
> Thanks for the clarifications. Regarding your comments:
> 
> 1. Suggested text - We already provided it. Please see #1 below.
> 
> 2. Length of mask - Section 3.10.16 states that the length of the mask is 16
> bits. No where else in the draft is it mentioned that not all of the bits
> are significant. If you are contending that not all of the bits are
> significant, then this is another aspect that must be clarified.
> 
> 3. I agree with you that the label mechanism, as currently specified, is
> broken. However it is NOT optional, because there is no mechanism specified
> through which the SGP can indicate to the ASP that it doesn't support the
> TID Label parameter in the ASPAC message (there is no "Unsupported
> parameter" error code). Thus SUA itself is also broken. So the label
> mechanism must either be fixed or removed.
> 
> Barry Nagelberg
> 
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Wednesday, February 18, 2004 4:17 PM
> > To: Barry Nagelberg
> > Cc: SIGTRAN Mailing List; Seamus Gilchrist
> > Subject: Re: [Sigtran] SUA v16: TID and DRM labels
> >
> >
> > Barry,
> >
> > Barry Nagelberg wrote:
> >                    (Wed, 18 Feb 2004 15:26:12)
> > > We have several suggestions for improving the clarity of the
> > definition and
> > > use of the TID and DRM label parameters:
> > >
> > > 1. Clarity - After some head-scratching and detective work, we think we
> > > understand their purpose. We're assuming that:
> > >
> > > a. These labels are simply 16-bit masks that are logically
> > ANDed onto the
> > > received TCAP transaction ID, starting at the "Start" bit.
> > >
> > > b. If the result of the AND operation exactly matches the "Label" field,
> > > then the message is sent to the ASP that registered for this
> > label via the
> > > ASPAC msg.
> > >
> > > c. An ASP that registers a label will be sent only those TID-bearing
> > > messages that match its label.
> > >
> > > d. An ASP that does not register a label may be sent any TID-bearing
> > > message.
> > >
> > > If these assumptions are correct, please state them explicitly in the
> > > relevant sections of the draft(3.10.15, 3.10.16, 4.7.2.1 and
> > 4.7.3.1). If
> > > not, please clarify. It's not enough to say, as in 4.7.3.1,
> > "the SG extracts
> > > the label".
> >
> > That's my understanding.  Some clarity would be good.  Can you
> > provide text?
> >
> > >
> > >
> > > 2. Redundancy - The label values are fixed length (16 bits). So
> > why do we
> > > need both a "Start" and an "End" position for applying the
> > mask? One or the
> > > other would seem to be enough.
> >
> > The label does not have to be 16 (significant) bits.
> >
> > >
> > > 3. Simplicity - Why bother with a partial-sized mask at a
> > specified "start"
> > > bit. Why not just specify a "full-sized" 32-bit (TID) or 23-bit
> > (DRM) mask?
> >
> > I don't know of any reason not to allow specification of a full
> > 32-bit mask
> > either.
> >
> > >
> > > 4. Contradictions - Section 4.7.2.1 states that "All the ASPs
> > within the AS
> > > _must_ specify a unique label at a fixed position in the TID or DRN
> > > parameter." The "must" here contradicts that fact the the TID and DRM
> > > parameters are listed as Optional in the ASPAC msg. We're
> > guessing that the
> > > intention here is either:
> > >
> > > a. "If at least one of the ASPs within an AS specifies a label,
> > then all the
> > > ASPs within the AS must specify a unique label at a fixed
> > position in the
> > > TID or DRN parameter."
> > >
> > > or
> > >
> > > b. "All of the labels specified by the ASPs within an AS must start at a
> > > fixed position in the TID or DRN parameter."
> > >
> > > or maybe
> > >
> > > (a) AND (b). Please clarify.
> >
> > I think we meant, "The ASPs within the AS specifying a label,
> > must specify a
> > unique label at a fixed position in the TID or DRN parameter."  The point
> > being that no two labels (optionally specified) can overlap.
> >
> > That said, the label mechanism is still broken, as detailed in previous
> > threads.  As it is an optional procedure, it might get fixed or
> > fall out of
> > use in the future.
> >
> > See draft-bidulock-sigtran-loadsel-02.pdf  I also have a session
> > registration
> > draft (never submitted) that provides a superior approach to the
> > same problem.
> > If someone is interested I will sumbit it.
> >
> > --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  Wed Feb 18 23:18:39 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 XAA12028
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Feb 2004 23:18:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtfdX-0000rX-NH
	for sigtran-archive@odin.ietf.org; Wed, 18 Feb 2004 23:18:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1J4I7Ex003314
	for sigtran-archive@odin.ietf.org; Wed, 18 Feb 2004 23:18:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtfdR-0000ir-Fe; Wed, 18 Feb 2004 23:18:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtfdM-0000iC-FZ
	for sigtran@optimus.ietf.org; Wed, 18 Feb 2004 23:17:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11985
	for <sigtran@ietf.org>; Wed, 18 Feb 2004 23:17:53 -0500 (EST)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtfdK-0000Qn-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 23:17:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtfcR-0000Ne-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 23:17:00 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atfbv-0000Kx-00
	for sigtran@ietf.org; Wed, 18 Feb 2004 23:16:27 -0500
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1J4GLK27289;
	Thu, 19 Feb 2004 06:16:21 +0200 (EET)
X-Scanned: Thu, 19 Feb 2004 06:15:26 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i1J4FQAx022506;
	Thu, 19 Feb 2004 06:15:26 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks002.ntc.nokia.com 00YXnLZs; Thu, 19 Feb 2004 06:15:25 EET
Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1J4FPO10354;
	Thu, 19 Feb 2004 06:15:25 +0200 (EET)
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Thu, 19 Feb 2004 06:15:23 +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
Subject: RE: [Sigtran] SUA v16: TID and DRM labels
Date: Thu, 19 Feb 2004 06:15:23 +0200
Message-ID: <DADF50F5EC506B41A0F375ABEB3206360143B6DC@esebe023.ntc.nokia.com>
Thread-Topic: [Sigtran] SUA v16: TID and DRM labels
Thread-Index: AcP2e0rweJJbtfZGS7qMJFvyI/iKmQAI6Wmw
To: <bidulock@openss7.org>, <barryn@adax.com>
Cc: <sigtran@ietf.org>, <sgilchrist@connetcom.com>
X-OriginalArrivalTime: 19 Feb 2004 04:15:23.0590 (UTC) FILETIME=[FEC20660:01C3F69E]
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

It would probably require an implementor's guide or -bis document to
make changes at this late date.

John

> -----Original Message-----
> From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> ext Brian F. G. Bidulock
> Sent: 19 February, 2004 01:57
> To: Barry Nagelberg
> Cc: SIGTRAN Mailing List; Seamus Gilchrist
> Subject: Re: [Sigtran] SUA v16: TID and DRM labels
>=20
>=20
>=20
> Barry,
>=20
> I think the decision at last call was that it would neither=20
> be fixed nor
> removed.  Perhaps John an Lyndon could shed some light on the=20
> possibility
> of doing either at this late date.
>=20
> --brian
>=20
> Barry Nagelberg wrote:                                       =20
>                        (Wed, 18 Feb 2004 17:21:43)
> > Brian,
> >=20
> > Thanks for the clarifications. Regarding your comments:
> >=20
> > 1. Suggested text - We already provided it. Please see #1 below.
> >=20
> > 2. Length of mask - Section 3.10.16 states that the length=20
> of the mask is 16
> > bits. No where else in the draft is it mentioned that not=20
> all of the bits
> > are significant. If you are contending that not all of the bits are
> > significant, then this is another aspect that must be clarified.
> >=20
> > 3. I agree with you that the label mechanism, as currently=20
> specified, is
> > broken. However it is NOT optional, because there is no=20
> mechanism specified
> > through which the SGP can indicate to the ASP that it=20
> doesn't support the
> > TID Label parameter in the ASPAC message (there is no "Unsupported
> > parameter" error code). Thus SUA itself is also broken. So the label
> > mechanism must either be fixed or removed.
> >=20
> > Barry Nagelberg
> >=20
> >=20
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: Wednesday, February 18, 2004 4:17 PM
> > > To: Barry Nagelberg
> > > Cc: SIGTRAN Mailing List; Seamus Gilchrist
> > > Subject: Re: [Sigtran] SUA v16: TID and DRM labels
> > >
> > >
> > > Barry,
> > >
> > > Barry Nagelberg wrote:
> > >                    (Wed, 18 Feb 2004 15:26:12)
> > > > We have several suggestions for improving the clarity of the
> > > definition and
> > > > use of the TID and DRM label parameters:
> > > >
> > > > 1. Clarity - After some head-scratching and detective=20
> work, we think we
> > > > understand their purpose. We're assuming that:
> > > >
> > > > a. These labels are simply 16-bit masks that are logically
> > > ANDed onto the
> > > > received TCAP transaction ID, starting at the "Start" bit.
> > > >
> > > > b. If the result of the AND operation exactly matches=20
> the "Label" field,
> > > > then the message is sent to the ASP that registered for this
> > > label via the
> > > > ASPAC msg.
> > > >
> > > > c. An ASP that registers a label will be sent only=20
> those TID-bearing
> > > > messages that match its label.
> > > >
> > > > d. An ASP that does not register a label may be sent=20
> any TID-bearing
> > > > message.
> > > >
> > > > If these assumptions are correct, please state them=20
> explicitly in the
> > > > relevant sections of the draft(3.10.15, 3.10.16, 4.7.2.1 and
> > > 4.7.3.1). If
> > > > not, please clarify. It's not enough to say, as in 4.7.3.1,
> > > "the SG extracts
> > > > the label".
> > >
> > > That's my understanding.  Some clarity would be good.  Can you
> > > provide text?
> > >
> > > >
> > > >
> > > > 2. Redundancy - The label values are fixed length (16 bits). So
> > > why do we
> > > > need both a "Start" and an "End" position for applying the
> > > mask? One or the
> > > > other would seem to be enough.
> > >
> > > The label does not have to be 16 (significant) bits.
> > >
> > > >
> > > > 3. Simplicity - Why bother with a partial-sized mask at a
> > > specified "start"
> > > > bit. Why not just specify a "full-sized" 32-bit (TID) or 23-bit
> > > (DRM) mask?
> > >
> > > I don't know of any reason not to allow specification of a full
> > > 32-bit mask
> > > either.
> > >
> > > >
> > > > 4. Contradictions - Section 4.7.2.1 states that "All the ASPs
> > > within the AS
> > > > _must_ specify a unique label at a fixed position in=20
> the TID or DRN
> > > > parameter." The "must" here contradicts that fact the=20
> the TID and DRM
> > > > parameters are listed as Optional in the ASPAC msg. We're
> > > guessing that the
> > > > intention here is either:
> > > >
> > > > a. "If at least one of the ASPs within an AS specifies a label,
> > > then all the
> > > > ASPs within the AS must specify a unique label at a fixed
> > > position in the
> > > > TID or DRN parameter."
> > > >
> > > > or
> > > >
> > > > b. "All of the labels specified by the ASPs within an=20
> AS must start at a
> > > > fixed position in the TID or DRN parameter."
> > > >
> > > > or maybe
> > > >
> > > > (a) AND (b). Please clarify.
> > >
> > > I think we meant, "The ASPs within the AS specifying a label,
> > > must specify a
> > > unique label at a fixed position in the TID or DRN=20
> parameter."  The point
> > > being that no two labels (optionally specified) can overlap.
> > >
> > > That said, the label mechanism is still broken, as=20
> detailed in previous
> > > threads.  As it is an optional procedure, it might get fixed or
> > > fall out of
> > > use in the future.
> > >
> > > See draft-bidulock-sigtran-loadsel-02.pdf  I also have a session
> > > registration
> > > draft (never submitted) that provides a superior approach to the
> > > same problem.
> > > If someone is interested I will sumbit it.
> > >
> > > --brian
> > >
> > > >
> > > >
> > > > Barry Nagelberg
> >=20
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20

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



From exim@www1.ietf.org  Thu Feb 19 00:41:31 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 AAA15109
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Feb 2004 00:41:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Atgvo-0006wg-J3
	for sigtran-archive@odin.ietf.org; Thu, 19 Feb 2004 00:41:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1J5f4Nq026674
	for sigtran-archive@odin.ietf.org; Thu, 19 Feb 2004 00:41:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Atgvl-0006vn-Sl; Thu, 19 Feb 2004 00:41:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Atgve-0006vX-43
	for sigtran@optimus.ietf.org; Thu, 19 Feb 2004 00:40:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15099
	for <sigtran@ietf.org>; Thu, 19 Feb 2004 00:40:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atgvb-00044k-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 00:40:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Atgug-00043X-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 00:39:55 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atgu0-00041t-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 00:39:12 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i1J5dDAh024318
	for <sigtran@ietf.org>; Thu, 19 Feb 2004 06:39:13 +0100
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 19 Feb 2004 06:39:13 +0100
Received: from eaubrnt019.epa.ericsson.se ([146.11.9.165]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id FGALB4WW; Thu, 19 Feb 2004 06:39:12 +0100
Received: from E000039C87816 ([146.11.245.253]) by eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id 1VLJZVFH; Thu, 19 Feb 2004 16:38:41 +1100
Message-ID: <007d01c3f6aa$8a2d3e80$fdf50b92@e000039c87816>
X-Sybari-Trust: 192c8a4f c77f3eb6 a03ace1c 00000138
From: "Ian Rytina" <ian.rytina@ericsson.com>
To: "J.Javier Pastor \(ML/EEM\)" <j.javier.pastor@ericsson.com>,
        <sigtran@ietf.org>
References: <1AB3D30B989BF141BBD5C70057B2EF7C04331A6B@eestqnt105.es.eu.ericsson.se>
Subject: Re: [Sigtran] M3UA IG Last Call
Date: Thu, 19 Feb 2004 16:38:00 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-OriginalArrivalTime: 19 Feb 2004 05:39:13.0092 (UTC) FILETIME=[B4932040:01C3F6AA]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by eagle.ericsson.se id i1J5dDAh024318
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable


Hi Javier,

I don't have a problem with merging into one complete document.

When this is done, can I suggest that the authors include a section
"Changes from RFC 3332" which outlines any backward compatibility
issues. And if there are none, then this should be categorically stated.
Examples af a similar approach are in RFC 3550 Appendix B (for RTP)
and RFC 3261 Section 28 (for SIP).

The reason is that many standards bodies and other organisations have the=
ir
own documents that refer to RFC 3332 and it would be very useful informat=
ion
to include in the new RFC in order to aid the process of updating these
documents to refer to the new M3UA RFC.

Regards,

Ian.


----- Original Message -----
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: <sigtran@ietf.org>
Sent: Wednesday, February 18, 2004 2:40 AM
Subject: RE: [Sigtran] M3UA IG Last Call


I also think that putting all together is a better approach.

Cheers // Javier.

> -----Original Message-----
> From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Barry Nagelberg
> Sent: martes, 17 de febrero de 2004 15:54
> To: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA IG Last Call
>
>
> Lyndon,
>
> I vote for a new M3UA spec. My neck is sore from having to
> turn my head back
> and forth so many times between the spec and the IG. :<(
>
> Barry Nagelberg
>
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Ong, Lyndon
> > Sent: Monday, February 16, 2004 3:56 PM
> > To: 'sigtran@ietf.org'
> > Subject: [Sigtran] M3UA IG Last Call
> >
> >
> > Hi Folks,
> >
> > It sounds like we may be ready to do a Last Call on the
> > M3UA IG.  If there are no objections, lets start up
> > Last Call starting today, Feb. 16th and ending on Monday,
> > March 1st.  Please add "M3UA IG Last Call Comment" in the
> > subject line for any emails.
> >
> > If we have agreement on the basic changes in the IG,
> > the follow up question will be whether to release the
> > IG itself as a document or incorporate the changes into
> > a new M3UA spec.
> >
> > Thanks,
> >
> > L. Ong
> >
> > -----Original Message-----
> > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> > Sent: Monday, February 16, 2004 12:41 PM
> > Cc: sigtran@ietf.org
> > Subject: [Sigtran] I-D
> > ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.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 : M3UA Implementor=C6s Guide
> > Author(s) : J. Pastor, K. Morneault
> > Filename :
> draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> > Pages : 70
> > Date : 2004-2-16
> >
> > This document contains a compilation of all defects found up until
> > the publication date for M3UA [RFC3332]. These defects may be of an
> > editorial or technical nature. This document may be thought of as a
> > companion document to be used in the implementation of M3UA to
> > clarify errors in the original M3UA document. This document updates
> > RFC3332 and text within this document supersedes the text found in
> > RFC3332.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-implem
> entors-guide-07.txt
>
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body
> of the message.
>
> Internet-Drafts are also available by anonymous FTP. Login
> with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> "get draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> mailserv@ietf.org.
> In the body type:
> "FILE
> /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
>
> NOTE: The mail server at ietf.org can return the document in
> MIME-encoded form by using the "mpack" utility.  To use this
> feature, insert the command "ENCODING mime" before the "FILE"
> command.  To decode the response(s), you will need "munpack" or
> a MIME-compliant mail reader.  Different MIME-compliant
> mail readers
> exhibit different behavior, especially when dealing with
> "multipart" MIME messages (i.e. documents which have been split
> up into multiple messages), so check your local documentation on
> how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>

This communication is confidential and intended solely for the addressee(=
s). Any
unauthorized review, use, disclosure or distribution is prohibited. If yo=
u believe this
message has been sent to you in error, please notify the sender by replyi=
ng to this
transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interrupt=
ion, unauthorized
amendment, tampering and viruses, and we only send and receive e-mails on=
 the basis that
we are not liable for any such corruption, interception, amendment, tampe=
ring or viruses
or any consequences thereof.


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


This communication is confidential and intended solely for the addressee(=
s). Any unauthorized review, use, disclosure or distribution is prohibite=
d. If you believe this message has been sent to you in error, please noti=
fy the sender by replying to this transmission and delete the message wit=
hout disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interrupt=
ion, unauthorized amendment, tampering and viruses, and we only send and =
receive e-mails on the basis that we are not liable for any such corrupti=
on, interception, amendment, tampering or viruses or any consequences the=
reof.


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



From exim@www1.ietf.org  Thu Feb 19 01: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 BAA15781
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Feb 2004 01:09:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AthMr-0000W6-Ke
	for sigtran-archive@odin.ietf.org; Thu, 19 Feb 2004 01:09:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1J691pc001969
	for sigtran-archive@odin.ietf.org; Thu, 19 Feb 2004 01:09:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AthMq-0000VJ-Pa; Thu, 19 Feb 2004 01:09:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AthLw-0000Rc-Ej
	for sigtran@optimus.ietf.org; Thu, 19 Feb 2004 01:08:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15739
	for <sigtran@ietf.org>; Thu, 19 Feb 2004 01:08:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AthLt-00058V-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 01:08:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AthKq-00056i-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 01:06:57 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[nSuG3MWRl3dAbJKE7LXEQETSsztvgpTK])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AthKT-00054j-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 01:06:33 -0500
Received: from ns.pigworks.openss7.net (IDENT:CZEJcf9oauf81MGL/UlJUqnOfQzpokvW@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1J66PI02556;
	Wed, 18 Feb 2004 23:06:25 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1J66Pf09240;
	Wed, 18 Feb 2004 23:06:25 -0700
Date: Wed, 18 Feb 2004 23:06:25 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: john.loughney@nokia.com
Cc: barryn@adax.com, sigtran@ietf.org, sgilchrist@connetcom.com
Subject: Re: [Sigtran] SUA v16: TID and DRM labels
Message-ID: <20040218230625.A9031@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: john.loughney@nokia.com, barryn@adax.com,
	sigtran@ietf.org, sgilchrist@connetcom.com
References: <DADF50F5EC506B41A0F375ABEB3206360143B6DC@esebe023.ntc.nokia.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: <DADF50F5EC506B41A0F375ABEB3206360143B6DC@esebe023.ntc.nokia.com>; from john.loughney@nokia.com on Thu, Feb 19, 2004 at 06:15:23AM +0200
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,

If you look back to the thread "SUA-09: SCCP Connections and TCAP
Transactions" from Dec 2001/Jan 2002, you will find that at that
"late date" it was too late to remove or fix the labels.  In that
thread there was a proposal for a working solution.  The draft was
advanced to IESG LC Feb 2002.  Now, two years later, it is neither
fixed nor removed, and it is still a late date.  At this rate, expect
corrections some time in 2006, if, of course, it is not still too
late by then ;)

I am concerned, however, that the approach is not clearly marked as
optional.  Which it should be and was always intended to be.  That
change can certainly be made before SUA goes out the door (unless
the authors have been stripped ala M3UA).

--brian

John Loughney wrote:                                                                  (Thu, 19 Feb 2004 06:15:23)
> It would probably require an implementor's guide or -bis document to
> make changes at this late date.
> 
> John
> 
> > -----Original Message-----
> > From: sigtran-admin@ietf.org 
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > ext Brian F. G. Bidulock
> > Sent: 19 February, 2004 01:57
> > To: Barry Nagelberg
> > Cc: SIGTRAN Mailing List; Seamus Gilchrist
> > Subject: Re: [Sigtran] SUA v16: TID and DRM labels
> > 
> > 
> > 
> > Barry,
> > 
> > I think the decision at last call was that it would neither 
> > be fixed nor
> > removed.  Perhaps John an Lyndon could shed some light on the 
> > possibility
> > of doing either at this late date.
> > 
> > --brian
> > 
> > Barry Nagelberg wrote:                                        
> >                        (Wed, 18 Feb 2004 17:21:43)
> > > Brian,
> > > 
> > > Thanks for the clarifications. Regarding your comments:
> > > 
> > > 1. Suggested text - We already provided it. Please see #1 below.
> > > 
> > > 2. Length of mask - Section 3.10.16 states that the length 
> > of the mask is 16
> > > bits. No where else in the draft is it mentioned that not 
> > all of the bits
> > > are significant. If you are contending that not all of the bits are
> > > significant, then this is another aspect that must be clarified.
> > > 
> > > 3. I agree with you that the label mechanism, as currently 
> > specified, is
> > > broken. However it is NOT optional, because there is no 
> > mechanism specified
> > > through which the SGP can indicate to the ASP that it 
> > doesn't support the
> > > TID Label parameter in the ASPAC message (there is no "Unsupported
> > > parameter" error code). Thus SUA itself is also broken. So the label
> > > mechanism must either be fixed or removed.
> > > 
> > > Barry Nagelberg
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: Wednesday, February 18, 2004 4:17 PM
> > > > To: Barry Nagelberg
> > > > Cc: SIGTRAN Mailing List; Seamus Gilchrist
> > > > Subject: Re: [Sigtran] SUA v16: TID and DRM labels
> > > >
> > > >
> > > > Barry,
> > > >
> > > > Barry Nagelberg wrote:
> > > >                    (Wed, 18 Feb 2004 15:26:12)
> > > > > We have several suggestions for improving the clarity of the
> > > > definition and
> > > > > use of the TID and DRM label parameters:
> > > > >
> > > > > 1. Clarity - After some head-scratching and detective 
> > work, we think we
> > > > > understand their purpose. We're assuming that:
> > > > >
> > > > > a. These labels are simply 16-bit masks that are logically
> > > > ANDed onto the
> > > > > received TCAP transaction ID, starting at the "Start" bit.
> > > > >
> > > > > b. If the result of the AND operation exactly matches 
> > the "Label" field,
> > > > > then the message is sent to the ASP that registered for this
> > > > label via the
> > > > > ASPAC msg.
> > > > >
> > > > > c. An ASP that registers a label will be sent only 
> > those TID-bearing
> > > > > messages that match its label.
> > > > >
> > > > > d. An ASP that does not register a label may be sent 
> > any TID-bearing
> > > > > message.
> > > > >
> > > > > If these assumptions are correct, please state them 
> > explicitly in the
> > > > > relevant sections of the draft(3.10.15, 3.10.16, 4.7.2.1 and
> > > > 4.7.3.1). If
> > > > > not, please clarify. It's not enough to say, as in 4.7.3.1,
> > > > "the SG extracts
> > > > > the label".
> > > >
> > > > That's my understanding.  Some clarity would be good.  Can you
> > > > provide text?
> > > >
> > > > >
> > > > >
> > > > > 2. Redundancy - The label values are fixed length (16 bits). So
> > > > why do we
> > > > > need both a "Start" and an "End" position for applying the
> > > > mask? One or the
> > > > > other would seem to be enough.
> > > >
> > > > The label does not have to be 16 (significant) bits.
> > > >
> > > > >
> > > > > 3. Simplicity - Why bother with a partial-sized mask at a
> > > > specified "start"
> > > > > bit. Why not just specify a "full-sized" 32-bit (TID) or 23-bit
> > > > (DRM) mask?
> > > >
> > > > I don't know of any reason not to allow specification of a full
> > > > 32-bit mask
> > > > either.
> > > >
> > > > >
> > > > > 4. Contradictions - Section 4.7.2.1 states that "All the ASPs
> > > > within the AS
> > > > > _must_ specify a unique label at a fixed position in 
> > the TID or DRN
> > > > > parameter." The "must" here contradicts that fact the 
> > the TID and DRM
> > > > > parameters are listed as Optional in the ASPAC msg. We're
> > > > guessing that the
> > > > > intention here is either:
> > > > >
> > > > > a. "If at least one of the ASPs within an AS specifies a label,
> > > > then all the
> > > > > ASPs within the AS must specify a unique label at a fixed
> > > > position in the
> > > > > TID or DRN parameter."
> > > > >
> > > > > or
> > > > >
> > > > > b. "All of the labels specified by the ASPs within an 
> > AS must start at a
> > > > > fixed position in the TID or DRN parameter."
> > > > >
> > > > > or maybe
> > > > >
> > > > > (a) AND (b). Please clarify.
> > > >
> > > > I think we meant, "The ASPs within the AS specifying a label,
> > > > must specify a
> > > > unique label at a fixed position in the TID or DRN 
> > parameter."  The point
> > > > being that no two labels (optionally specified) can overlap.
> > > >
> > > > That said, the label mechanism is still broken, as 
> > detailed in previous
> > > > threads.  As it is an optional procedure, it might get fixed or
> > > > fall out of
> > > > use in the future.
> > > >
> > > > See draft-bidulock-sigtran-loadsel-02.pdf  I also have a session
> > > > registration
> > > > draft (never submitted) that provides a superior approach to the
> > > > same problem.
> > > > If someone is interested I will sumbit it.
> > > >
> > > > --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
> > 

-- 
Brian 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 Feb 19 01:14: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 BAA15884
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Feb 2004 01:14:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AthRh-0001Eb-MI
	for sigtran-archive@odin.ietf.org; Thu, 19 Feb 2004 01:14:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1J6E1DH004720
	for sigtran-archive@odin.ietf.org; Thu, 19 Feb 2004 01:14:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AthRg-0001De-Ov; Thu, 19 Feb 2004 01:14:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AthRX-0001C8-Vm
	for sigtran@optimus.ietf.org; Thu, 19 Feb 2004 01:13:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15868
	for <sigtran@ietf.org>; Thu, 19 Feb 2004 01:13:50 -0500 (EST)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AthRV-0005LJ-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 01:13:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AthQY-0005JK-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 01:12:51 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AthPf-0005Hr-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 01:11:55 -0500
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1J6BpK04620;
	Thu, 19 Feb 2004 08:11:51 +0200 (EET)
X-Scanned: Thu, 19 Feb 2004 08:11:14 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i1J6BEAW023650;
	Thu, 19 Feb 2004 08:11:14 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 008pA4qh; Thu, 19 Feb 2004 08:11:13 EET
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1J6BC710641;
	Thu, 19 Feb 2004 08:11:12 +0200 (EET)
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Thu, 19 Feb 2004 08:11:12 +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
Subject: RE: [Sigtran] SUA v16: TID and DRM labels
Date: Thu, 19 Feb 2004 08:11:08 +0200
Message-ID: <DADF50F5EC506B41A0F375ABEB3206360143B6E2@esebe023.ntc.nokia.com>
Thread-Topic: [Sigtran] SUA v16: TID and DRM labels
Thread-Index: AcP2rqiQiOxAmWp0Tr2IsNwX8XTYCwAAFZrA
To: <bidulock@openss7.org>
Cc: <barryn@adax.com>, <sigtran@ietf.org>, <sgilchrist@connetcom.com>
X-OriginalArrivalTime: 19 Feb 2004 06:11:12.0364 (UTC) FILETIME=[2C8CCAC0:01C3F6AF]
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

Hi Brian,

> If you look back to the thread "SUA-09: SCCP Connections and TCAP
> Transactions" from Dec 2001/Jan 2002, you will find that at that
> "late date" it was too late to remove or fix the labels.  In that
> thread there was a proposal for a working solution.  The draft was
> advanced to IESG LC Feb 2002.  Now, two years later, it is neither
> fixed nor removed, and it is still a late date.  At this rate, expect
> corrections some time in 2006, if, of course, it is not still too
> late by then ;)
>=20
> I am concerned, however, that the approach is not clearly marked as
> optional.  Which it should be and was always intended to be.  That
> change can certainly be made before SUA goes out the door (unless
> the authors have been stripped ala M3UA).

If you want to send text and get support, I can probably make the text
change - if the text change is not too substantial.

Delays due to IESG issues are beyond my control.

John

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



From exim@www1.ietf.org  Thu Feb 19 02:00:41 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 CAA18082
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Feb 2004 02:00:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtiAN-0004KN-EK
	for sigtran-archive@odin.ietf.org; Thu, 19 Feb 2004 02:00:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1J70Adw016596
	for sigtran-archive@odin.ietf.org; Thu, 19 Feb 2004 02:00:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtiAG-0004ID-IK; Thu, 19 Feb 2004 02:00:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ati9M-00044T-OT
	for sigtran@optimus.ietf.org; Thu, 19 Feb 2004 01:59:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17283
	for <sigtran@ietf.org>; Thu, 19 Feb 2004 01:59:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ati9J-0007XY-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 01:59:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ati8F-0007TS-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 01:58:00 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[MmOfrwnhFibyYk8NM7EwSdFvjWlTr5g5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ati7Y-0007Qp-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 01:57:16 -0500
Received: from ns.pigworks.openss7.net (IDENT:1Rper3FzgXJsDMqWwqDPV3xkhjZMpaIY@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1J6vFI03346;
	Wed, 18 Feb 2004 23:57:15 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1J6vFx09780;
	Wed, 18 Feb 2004 23:57:15 -0700
Date: Wed, 18 Feb 2004 23:57:15 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: john.loughney@nokia.com
Cc: barryn@adax.com, sigtran@ietf.org, sgilchrist@connetcom.com
Subject: Re: [Sigtran] SUA v16: TID and DRM labels
Message-ID: <20040218235715.A8947@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: john.loughney@nokia.com, barryn@adax.com,
	sigtran@ietf.org, sgilchrist@connetcom.com
References: <DADF50F5EC506B41A0F375ABEB3206360143B6E2@esebe023.ntc.nokia.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: <DADF50F5EC506B41A0F375ABEB3206360143B6E2@esebe023.ntc.nokia.com>; from john.loughney@nokia.com on Thu, Feb 19, 2004 at 08:11:08AM +0200
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>

John,

John Loughney wrote:                                                                  (Thu, 19 Feb 2004 08:11:08)
> Hi Brian,
> 
> > If you look back to the thread "SUA-09: SCCP Connections and TCAP
> > Transactions" from Dec 2001/Jan 2002, you will find that at that
> > "late date" it was too late to remove or fix the labels.  In that
> > thread there was a proposal for a working solution.  The draft was
> > advanced to IESG LC Feb 2002.  Now, two years later, it is neither
> > fixed nor removed, and it is still a late date.  At this rate, expect
> > corrections some time in 2006, if, of course, it is not still too
> > late by then ;)
> > 
> > I am concerned, however, that the approach is not clearly marked as
> > optional.  Which it should be and was always intended to be.  That
> > change can certainly be made before SUA goes out the door (unless
> > the authors have been stripped ala M3UA).
> 
> If you want to send text and get support, I can probably make the text
> change - if the text change is not too substantial.
> 
> Delays due to IESG issues are beyond my control.

Proposed text addition: "Label procedures are OPTIONAL."

--brian

> 
> John

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

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



From exim@www1.ietf.org  Thu Feb 19 08:54:31 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 IAA18699
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Feb 2004 08:54:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Atoct-0003h4-2C
	for sigtran-archive@odin.ietf.org; Thu, 19 Feb 2004 08:54:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1JDs25Z014156
	for sigtran-archive@odin.ietf.org; Thu, 19 Feb 2004 08:54:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Atocq-0003fr-VE; Thu, 19 Feb 2004 08:54:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Atoby-0003aN-VM
	for sigtran@optimus.ietf.org; Thu, 19 Feb 2004 08:53:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18585
	for <sigtran@ietf.org>; Thu, 19 Feb 2004 08:53:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atobx-0005Le-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 08:53:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Atob0-0005G1-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 08:52:06 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atoa2-0005Br-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 08:51:06 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i1JDp37T009380;
	Thu, 19 Feb 2004 08:51:03 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: <sigtran@ietf.org>
Cc: <sgilchrist@connetcom.com>
Subject: RE: [Sigtran] SUA v16: TID and DRM labels
Date: Thu, 19 Feb 2004 08:52:33 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOEELACEAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <20040218235715.A8947@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
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

It is not good enough to simply state in the draft that the "Label
procedures are OPTIONAL.".

As I noted earlier, there is no mechanism through which the SGP can indicate
to the ASP that it doesn't support the
TID Label parameter in the ASPAC message (there is no "Unsupported
parameter" error code).

So when an ASP implementation _does_ send the TID and/or DRM labels to an
SGP that does not support them, we will be in "non-interoperability hell".
The ASP will assume that the SGP is supporting the labels, while in reality
the SGP will not be supporting them. The ASP will receive transaction IDs
that it does not expect.

These procedures must either be fixed or removed. Why are we rushing to push
through a flawed draft?

Barry Nagelberg

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Thursday, February 19, 2004 1:57 AM
> To: john.loughney@nokia.com
> Cc: barryn@adax.com; sigtran@ietf.org; sgilchrist@connetcom.com
> Subject: Re: [Sigtran] SUA v16: TID and DRM labels
>
>
> John,
>
> John Loughney wrote:
>                     (Thu, 19 Feb 2004 08:11:08)
> > Hi Brian,
> >
> > > If you look back to the thread "SUA-09: SCCP Connections and TCAP
> > > Transactions" from Dec 2001/Jan 2002, you will find that at that
> > > "late date" it was too late to remove or fix the labels.  In that
> > > thread there was a proposal for a working solution.  The draft was
> > > advanced to IESG LC Feb 2002.  Now, two years later, it is neither
> > > fixed nor removed, and it is still a late date.  At this rate, expect
> > > corrections some time in 2006, if, of course, it is not still too
> > > late by then ;)
> > >
> > > I am concerned, however, that the approach is not clearly marked as
> > > optional.  Which it should be and was always intended to be.  That
> > > change can certainly be made before SUA goes out the door (unless
> > > the authors have been stripped ala M3UA).
> >
> > If you want to send text and get support, I can probably make the text
> > change - if the text change is not too substantial.
> >
> > Delays due to IESG issues are beyond my control.
>
> Proposed text addition: "Label procedures are OPTIONAL."
>
> --brian
>
> >
> > John
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


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



From exim@www1.ietf.org  Thu Feb 19 10:43: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 KAA23868
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Feb 2004 10:43:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtqKQ-0006fC-4Z
	for sigtran-archive@odin.ietf.org; Thu, 19 Feb 2004 10:43:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1JFh61B025610
	for sigtran-archive@odin.ietf.org; Thu, 19 Feb 2004 10:43:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtqKN-0006en-7T; Thu, 19 Feb 2004 10:43:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtqJi-0006bB-K3
	for sigtran@optimus.ietf.org; Thu, 19 Feb 2004 10:42:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23846
	for <sigtran@ietf.org>; Thu, 19 Feb 2004 10:42:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtqJg-0003KF-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 10:42:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtqIm-0003GM-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 10:41:25 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtqI1-0003Cm-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 10:40:37 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i1JFeZAh016566
	for <sigtran@ietf.org>; Thu, 19 Feb 2004 16:40:35 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 19 Feb 2004 16:40:35 +0100
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 FGDGVGY2; Thu, 19 Feb 2004 16:40:35 +0100
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <FAB02M6B>; Thu, 19 Feb 2004 16:40:30 +0100
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C04331A77@eestqnt105.es.eu.ericsson.se>
X-Sybari-Trust: 5802cd2f c77f3eb6 1886a979 00000138
From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
To: "Ian Rytina (MC/EPA)" <ian.rytina@ericsson.com>, sigtran@ietf.org
Subject: RE: [Sigtran] M3UA IG Last Call
Date: Thu, 19 Feb 2004 16:39:40 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-OriginalArrivalTime: 19 Feb 2004 15:40:35.0460 (UTC) FILETIME=[B7578C40:01C3F6FE]
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

Hi Ian,=20

I think it would be very useful to include that information...

Thanks for your suggestion.  // Javier.

> -----Original Message-----
> From: Ian Rytina [mailto:ian.rytina@ericsson.com]
> Sent: jueves, 19 de febrero de 2004 6:38
> To: J.Javier Pastor (ML/EEM); sigtran@ietf.org
> Subject: Re: [Sigtran] M3UA IG Last Call
>=20
>=20
>=20
> Hi Javier,
>=20
> I don't have a problem with merging into one complete document.
>=20
> When this is done, can I suggest that the authors include a section
> "Changes from RFC 3332" which outlines any backward compatibility
> issues. And if there are none, then this should be=20
> categorically stated.
> Examples af a similar approach are in RFC 3550 Appendix B (for RTP)
> and RFC 3261 Section 28 (for SIP).
>=20
> The reason is that many standards bodies and other=20
> organisations have their
> own documents that refer to RFC 3332 and it would be very=20
> useful information
> to include in the new RFC in order to aid the process of=20
> updating these
> documents to refer to the new M3UA RFC.
>=20
> Regards,
>=20
> Ian.
>=20
>=20
> ----- Original Message -----
> From: "J.Javier Pastor (ML/EEM)" <j.javier.pastor@ericsson.com>
> To: <sigtran@ietf.org>
> Sent: Wednesday, February 18, 2004 2:40 AM
> Subject: RE: [Sigtran] M3UA IG Last Call
>=20
>=20
> I also think that putting all together is a better approach.
>=20
> Cheers // Javier.
>=20
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Barry Nagelberg
> > Sent: martes, 17 de febrero de 2004 15:54
> > To: sigtran@ietf.org
> > Subject: RE: [Sigtran] M3UA IG Last Call
> >
> >
> > Lyndon,
> >
> > I vote for a new M3UA spec. My neck is sore from having to
> > turn my head back
> > and forth so many times between the spec and the IG. :<(
> >
> > Barry Nagelberg
> >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > Ong, Lyndon
> > > Sent: Monday, February 16, 2004 3:56 PM
> > > To: 'sigtran@ietf.org'
> > > Subject: [Sigtran] M3UA IG Last Call
> > >
> > >
> > > Hi Folks,
> > >
> > > It sounds like we may be ready to do a Last Call on the
> > > M3UA IG.  If there are no objections, lets start up
> > > Last Call starting today, Feb. 16th and ending on Monday,
> > > March 1st.  Please add "M3UA IG Last Call Comment" in the
> > > subject line for any emails.
> > >
> > > If we have agreement on the basic changes in the IG,
> > > the follow up question will be whether to release the
> > > IG itself as a document or incorporate the changes into
> > > a new M3UA spec.
> > >
> > > Thanks,
> > >
> > > L. Ong
> > >
> > > -----Original Message-----
> > > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> > > Sent: Monday, February 16, 2004 12:41 PM
> > > Cc: sigtran@ietf.org
> > > Subject: [Sigtran] I-D
> > > ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.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 : M3UA Implementor=C6s Guide
> > > Author(s) : J. Pastor, K. Morneault
> > > Filename :
> > draft-ietf-sigtran-m3ua-implementors-guide-07.txt
> > > Pages : 70
> > > Date : 2004-2-16
> > >
> > > This document contains a compilation of all defects found up until
> > > the publication date for M3UA [RFC3332]. These defects=20
> may be of an
> > > editorial or technical nature. This document may be=20
> thought of as a
> > > companion document to be used in the implementation of M3UA to
> > > clarify errors in the original M3UA document. This=20
> document updates
> > > RFC3332 and text within this document supersedes the text found in
> > > RFC3332.
> > >
> > > A URL for this Internet-Draft is:
> > > http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-implem
> > entors-guide-07.txt
> >
> > To remove yourself from the IETF Announcement list, send a=20
> message to
> > ietf-announce-request with the word unsubscribe in the body
> > of the message.
> >
> > Internet-Drafts are also available by anonymous FTP. Login
> > with the username
> > "anonymous" and a password of your e-mail address. After logging in,
> > type "cd internet-drafts" and then
> > "get draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> >
> > A list of Internet-Drafts directories can be found in
> > http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> >
> > Internet-Drafts can also be obtained by e-mail.
> >
> > Send a message to:
> > mailserv@ietf.org.
> > In the body type:
> > "FILE
> > /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt".
> >
> > NOTE: The mail server at ietf.org can return the document in
> > MIME-encoded form by using the "mpack" utility.  To use this
> > feature, insert the command "ENCODING mime" before the "FILE"
> > command.  To decode the response(s), you will need "munpack" or
> > a MIME-compliant mail reader.  Different MIME-compliant
> > mail readers
> > exhibit different behavior, especially when dealing with
> > "multipart" MIME messages (i.e. documents which have been split
> > up into multiple messages), so check your local documentation on
> > how to manipulate these messages.
> >
> >
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.
> >
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >
>=20
> This communication is confidential and intended solely for=20
> the addressee(s). Any
> unauthorized review, use, disclosure or distribution is=20
> prohibited. If you believe this
> message has been sent to you in error, please notify the=20
> sender by replying to this
> transmission and delete the message without disclosing it. Thank you.
>=20
> E-mail including attachments is susceptible to data=20
> corruption, interruption, unauthorized
> amendment, tampering and viruses, and we only send and=20
> receive e-mails on the basis that
> we are not liable for any such corruption, interception,=20
> amendment, tampering or viruses
> or any consequences thereof.
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20

This communication is confidential and intended solely for the addressee(=
s). Any unauthorized review, use, disclosure or distribution is prohibite=
d. If you believe this message has been sent to you in error, please noti=
fy the sender by replying to this transmission and delete the message wit=
hout disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interrupt=
ion, unauthorized amendment, tampering and viruses, and we only send and =
receive e-mails on the basis that we are not liable for any such corrupti=
on, interception, amendment, tampering or viruses or any consequences the=
reof.


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



From exim@www1.ietf.org  Thu Feb 19 16:19: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 QAA15731
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Feb 2004 16:19:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtvZZ-0002DU-UG
	for sigtran-archive@odin.ietf.org; Thu, 19 Feb 2004 16:19:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1JLJ5BL008489
	for sigtran-archive@odin.ietf.org; Thu, 19 Feb 2004 16:19:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtvZV-0002BW-An; Thu, 19 Feb 2004 16:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtvZ0-0002As-7i
	for sigtran@optimus.ietf.org; Thu, 19 Feb 2004 16:18:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14354
	for <sigtran@ietf.org>; Thu, 19 Feb 2004 16:18:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtvYy-0000iV-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 16:18:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtvY0-0000fG-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 16:17:29 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtvXN-0000cL-00
	for sigtran@ietf.org; Thu, 19 Feb 2004 16:16:49 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i1JLGm7T011021
	for <sigtran@ietf.org>; Thu, 19 Feb 2004 16:16:48 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: "SIGTRAN Mailing List" <sigtran@ietf.org>
Date: Thu, 19 Feb 2004 16:18:18 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOIELGCEAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] SUA v16: DATA message
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

There are at least 5 instances in the SUA draft that refer to "DATA"
messages. This is apparently a copy-and-paste error from M3UA - there is no
such message type in SUA. These instances should probably be changed to "CL
or CO" messages.


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



From exim@www1.ietf.org  Fri Feb 20 02:20: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 CAA06614
	for <sigtran-archive@odin.ietf.org>; Fri, 20 Feb 2004 02:20:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Au4xM-0001ut-At
	for sigtran-archive@odin.ietf.org; Fri, 20 Feb 2004 02:20:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1K7KCqq007227
	for sigtran-archive@odin.ietf.org; Fri, 20 Feb 2004 02:20:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Au4x9-0001rD-8d; Fri, 20 Feb 2004 02:20:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Au4wu-0001na-PM
	for sigtran@optimus.ietf.org; Fri, 20 Feb 2004 02:19:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06545
	for <sigtran@ietf.org>; Fri, 20 Feb 2004 02:19:45 -0500 (EST)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Au4wr-0004ox-00
	for sigtran@ietf.org; Fri, 20 Feb 2004 02:19:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Au4vx-0004lm-00
	for sigtran@ietf.org; Fri, 20 Feb 2004 02:18:50 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Au4vg-0004ic-00
	for sigtran@ietf.org; Fri, 20 Feb 2004 02:18:32 -0500
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1K7IWK15160;
	Fri, 20 Feb 2004 09:18:32 +0200 (EET)
X-Scanned: Fri, 20 Feb 2004 09:16:53 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i1K7Gr7A030442;
	Fri, 20 Feb 2004 09:16:53 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 00bAeksC; Fri, 20 Feb 2004 09:16:52 EET
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 i1K7Gp703171;
	Fri, 20 Feb 2004 09:16:51 +0200 (EET)
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Fri, 20 Feb 2004 09:16:51 +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
Subject: RE: [Sigtran] SUA v16: DATA message
Date: Fri, 20 Feb 2004 09:16:50 +0200
Message-ID: <DADF50F5EC506B41A0F375ABEB3206360143B70E@esebe023.ntc.nokia.com>
Thread-Topic: [Sigtran] SUA v16: DATA message
Thread-Index: AcP3LugBYP46KTwuRFqjr7Rw+nnQKQAUo51g
To: <barryn@adax.com>, <sigtran@ietf.org>
X-OriginalArrivalTime: 20 Feb 2004 07:16:51.0130 (UTC) FILETIME=[82A689A0:01C3F781]
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

Hi Barry,

> There are at least 5 instances in the SUA draft that refer to "DATA"
> messages. This is apparently a copy-and-paste error from M3UA - there =
is no
> such message type in SUA. These instances should probably be changed =
to "CL
> or CO" messages.

I can do that.

thanks,
John

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



From exim@www1.ietf.org  Fri Feb 20 02:25:31 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 CAA07060
	for <sigtran-archive@odin.ietf.org>; Fri, 20 Feb 2004 02:25:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Au51z-0003Zk-Kr
	for sigtran-archive@odin.ietf.org; Fri, 20 Feb 2004 02:25:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1K7P3BQ013744
	for sigtran-archive@odin.ietf.org; Fri, 20 Feb 2004 02:25:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Au51y-0003Z9-6z; Fri, 20 Feb 2004 02:25:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Au51l-0003VP-64
	for sigtran@optimus.ietf.org; Fri, 20 Feb 2004 02:24:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06991
	for <sigtran@ietf.org>; Fri, 20 Feb 2004 02:24:45 -0500 (EST)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Au51h-0005Dp-00
	for sigtran@ietf.org; Fri, 20 Feb 2004 02:24:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Au50n-0005AY-00
	for sigtran@ietf.org; Fri, 20 Feb 2004 02:23:50 -0500
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Au502-000576-00
	for sigtran@ietf.org; Fri, 20 Feb 2004 02:23:02 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1K7N0T17571;
	Fri, 20 Feb 2004 09:23:00 +0200 (EET)
X-Scanned: Fri, 20 Feb 2004 09:21:33 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id i1K7LX2r027417;
	Fri, 20 Feb 2004 09:21:33 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks001.ntc.nokia.com 00THD2Mq; Fri, 20 Feb 2004 09:21:30 EET
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1K7LAO16111;
	Fri, 20 Feb 2004 09:21:10 +0200 (EET)
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Fri, 20 Feb 2004 09:21:10 +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
Subject: RE: [Sigtran] SUA v16: TID and DRM labels
Date: Fri, 20 Feb 2004 09:21:09 +0200
Message-ID: <DADF50F5EC506B41A0F375ABEB3206360143B710@esebe023.ntc.nokia.com>
Thread-Topic: [Sigtran] SUA v16: TID and DRM labels
Thread-Index: AcP28FRLU/iflSKoS/yDq3pd3bfz7AAkXqlA
To: <barryn@adax.com>, <sigtran@ietf.org>
Cc: <sgilchrist@connetcom.com>
X-OriginalArrivalTime: 20 Feb 2004 07:21:10.0121 (UTC) FILETIME=[1D056D90:01C3F782]
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

Barry,

One concern I have about making this change is that we had a
WG last call on the draft.  Brian raised the point, but there
wasn't much support for his proposal at the time.  We've had
a few bake-offs & a few implementations have been made.  I
don't know the best procedure for fixing this. Perhaps if someone
had a proposal and got strong support from the WG, something
might be done, but the IESG generally frowns upon things like=20
that.

John

> -----Original Message-----
> From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> ext Barry Nagelberg
> Sent: 19 February, 2004 15:53
> To: sigtran@ietf.org
> Cc: sgilchrist@connetcom.com
> Subject: RE: [Sigtran] SUA v16: TID and DRM labels
>=20
>=20
>=20
> It is not good enough to simply state in the draft that the "Label
> procedures are OPTIONAL.".
>=20
> As I noted earlier, there is no mechanism through which the=20
> SGP can indicate
> to the ASP that it doesn't support the
> TID Label parameter in the ASPAC message (there is no "Unsupported
> parameter" error code).
>=20
> So when an ASP implementation _does_ send the TID and/or DRM=20
> labels to an
> SGP that does not support them, we will be in=20
> "non-interoperability hell".
> The ASP will assume that the SGP is supporting the labels,=20
> while in reality
> the SGP will not be supporting them. The ASP will receive=20
> transaction IDs
> that it does not expect.
>=20
> These procedures must either be fixed or removed. Why are we=20
> rushing to push
> through a flawed draft?
>=20
> Barry Nagelberg
>=20
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Thursday, February 19, 2004 1:57 AM
> > To: john.loughney@nokia.com
> > Cc: barryn@adax.com; sigtran@ietf.org; sgilchrist@connetcom.com
> > Subject: Re: [Sigtran] SUA v16: TID and DRM labels
> >
> >
> > John,
> >
> > John Loughney wrote:
> >                     (Thu, 19 Feb 2004 08:11:08)
> > > Hi Brian,
> > >
> > > > If you look back to the thread "SUA-09: SCCP=20
> Connections and TCAP
> > > > Transactions" from Dec 2001/Jan 2002, you will find that at that
> > > > "late date" it was too late to remove or fix the=20
> labels.  In that
> > > > thread there was a proposal for a working solution. =20
> The draft was
> > > > advanced to IESG LC Feb 2002.  Now, two years later, it=20
> is neither
> > > > fixed nor removed, and it is still a late date.  At=20
> this rate, expect
> > > > corrections some time in 2006, if, of course, it is not=20
> still too
> > > > late by then ;)
> > > >
> > > > I am concerned, however, that the approach is not=20
> clearly marked as
> > > > optional.  Which it should be and was always intended=20
> to be.  That
> > > > change can certainly be made before SUA goes out the=20
> door (unless
> > > > the authors have been stripped ala M3UA).
> > >
> > > If you want to send text and get support, I can probably=20
> make the text
> > > change - if the text change is not too substantial.
> > >
> > > Delays due to IESG issues are beyond my control.
> >
> > Proposed text addition: "Label procedures are OPTIONAL."
> >
> > --brian
> >
> > >
> > > John
> >
> > --
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20

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



From exim@www1.ietf.org  Fri Feb 20 02:37:31 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 CAA07835
	for <sigtran-archive@odin.ietf.org>; Fri, 20 Feb 2004 02:37:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Au5Dc-0005ux-0L
	for sigtran-archive@odin.ietf.org; Fri, 20 Feb 2004 02:37:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1K7b3Sm022746
	for sigtran-archive@odin.ietf.org; Fri, 20 Feb 2004 02:37:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Au5DZ-0005uX-Si; Fri, 20 Feb 2004 02:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Au5DH-0005tW-Da
	for sigtran@optimus.ietf.org; Fri, 20 Feb 2004 02:36:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07822
	for <sigtran@ietf.org>; Fri, 20 Feb 2004 02:36:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Au5DD-0005zE-00
	for sigtran@ietf.org; Fri, 20 Feb 2004 02:36:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Au5CI-0005xU-00
	for sigtran@ietf.org; Fri, 20 Feb 2004 02:35:42 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[WWK8gnA2pog/Znkl5VX5c2XiZXa4oQs5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Au5BP-0005vT-00
	for sigtran@ietf.org; Fri, 20 Feb 2004 02:34:47 -0500
Received: from ns.pigworks.openss7.net (IDENT:A0kOAle2nzgdXfuVVBfgUkMpSWKuQDFC@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1K7YkI27978;
	Fri, 20 Feb 2004 00:34:46 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1K7Yjg28156;
	Fri, 20 Feb 2004 00:34:45 -0700
Date: Fri, 20 Feb 2004 00:34:45 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: john.loughney@nokia.com
Cc: barryn@adax.com, sigtran@ietf.org, sgilchrist@connetcom.com
Subject: Re: [Sigtran] SUA v16: TID and DRM labels
Message-ID: <20040220003445.A27423@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: john.loughney@nokia.com, barryn@adax.com,
	sigtran@ietf.org, sgilchrist@connetcom.com
References: <DADF50F5EC506B41A0F375ABEB3206360143B710@esebe023.ntc.nokia.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: <DADF50F5EC506B41A0F375ABEB3206360143B710@esebe023.ntc.nokia.com>; from john.loughney@nokia.com on Fri, Feb 20, 2004 at 09:21:09AM +0200
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>

John,

What about removal?

--brian

John Loughney wrote:                                                                  (Fri, 20 Feb 2004 09:21:09)
> Barry,
> 
> One concern I have about making this change is that we had a
> WG last call on the draft.  Brian raised the point, but there
> wasn't much support for his proposal at the time.  We've had
> a few bake-offs & a few implementations have been made.  I
> don't know the best procedure for fixing this. Perhaps if someone
> had a proposal and got strong support from the WG, something
> might be done, but the IESG generally frowns upon things like 
> that.
> 
> John
> 
> > -----Original Message-----
> > From: sigtran-admin@ietf.org 
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > ext Barry Nagelberg
> > Sent: 19 February, 2004 15:53
> > To: sigtran@ietf.org
> > Cc: sgilchrist@connetcom.com
> > Subject: RE: [Sigtran] SUA v16: TID and DRM labels
> > 
> > 
> > 
> > It is not good enough to simply state in the draft that the "Label
> > procedures are OPTIONAL.".
> > 
> > As I noted earlier, there is no mechanism through which the 
> > SGP can indicate
> > to the ASP that it doesn't support the
> > TID Label parameter in the ASPAC message (there is no "Unsupported
> > parameter" error code).
> > 
> > So when an ASP implementation _does_ send the TID and/or DRM 
> > labels to an
> > SGP that does not support them, we will be in 
> > "non-interoperability hell".
> > The ASP will assume that the SGP is supporting the labels, 
> > while in reality
> > the SGP will not be supporting them. The ASP will receive 
> > transaction IDs
> > that it does not expect.
> > 
> > These procedures must either be fixed or removed. Why are we 
> > rushing to push
> > through a flawed draft?
> > 
> > Barry Nagelberg
> > 
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: Thursday, February 19, 2004 1:57 AM
> > > To: john.loughney@nokia.com
> > > Cc: barryn@adax.com; sigtran@ietf.org; sgilchrist@connetcom.com
> > > Subject: Re: [Sigtran] SUA v16: TID and DRM labels
> > >
> > >
> > > John,
> > >
> > > John Loughney wrote:
> > >                     (Thu, 19 Feb 2004 08:11:08)
> > > > Hi Brian,
> > > >
> > > > > If you look back to the thread "SUA-09: SCCP 
> > Connections and TCAP
> > > > > Transactions" from Dec 2001/Jan 2002, you will find that at that
> > > > > "late date" it was too late to remove or fix the 
> > labels.  In that
> > > > > thread there was a proposal for a working solution.  
> > The draft was
> > > > > advanced to IESG LC Feb 2002.  Now, two years later, it 
> > is neither
> > > > > fixed nor removed, and it is still a late date.  At 
> > this rate, expect
> > > > > corrections some time in 2006, if, of course, it is not 
> > still too
> > > > > late by then ;)
> > > > >
> > > > > I am concerned, however, that the approach is not 
> > clearly marked as
> > > > > optional.  Which it should be and was always intended 
> > to be.  That
> > > > > change can certainly be made before SUA goes out the 
> > door (unless
> > > > > the authors have been stripped ala M3UA).
> > > >
> > > > If you want to send text and get support, I can probably 
> > make the text
> > > > change - if the text change is not too substantial.
> > > >
> > > > Delays due to IESG issues are beyond my control.
> > >
> > > Proposed text addition: "Label procedures are OPTIONAL."
> > >
> > > --brian
> > >
> > > >
> > > > John
> > >
> > > --
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Fri Feb 20 02: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 CAA08001
	for <sigtran-archive@odin.ietf.org>; Fri, 20 Feb 2004 02:44:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Au5KP-0006mE-7N
	for sigtran-archive@odin.ietf.org; Fri, 20 Feb 2004 02:44:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1K7i5w8026031
	for sigtran-archive@odin.ietf.org; Fri, 20 Feb 2004 02:44:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Au5KM-0006lN-RJ; Fri, 20 Feb 2004 02:44:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Au5K8-0006kL-J2
	for sigtran@optimus.ietf.org; Fri, 20 Feb 2004 02:43:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07970
	for <sigtran@ietf.org>; Fri, 20 Feb 2004 02:43:45 -0500 (EST)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Au5K4-0006NE-00
	for sigtran@ietf.org; Fri, 20 Feb 2004 02:43:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Au5J7-0006IJ-00
	for sigtran@ietf.org; Fri, 20 Feb 2004 02:42:45 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Au5IA-0006EA-00
	for sigtran@ietf.org; Fri, 20 Feb 2004 02:41:46 -0500
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1K7fgK11348;
	Fri, 20 Feb 2004 09:41:42 +0200 (EET)
X-Scanned: Fri, 20 Feb 2004 09:39:39 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i1K7ddrr013727;
	Fri, 20 Feb 2004 09:39:39 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks002.ntc.nokia.com 003SFL5S; Fri, 20 Feb 2004 09:39:38 EET
Received: from esebh004.NOE.Nokia.com (esebh004.ntc.nokia.com [172.21.138.84])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1K7dWO24589;
	Fri, 20 Feb 2004 09:39:33 +0200 (EET)
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Fri, 20 Feb 2004 09:39:32 +0200
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Fri, 20 Feb 2004 09:39:32 +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
Subject: RE: [Sigtran] SUA v16: TID and DRM labels
Date: Fri, 20 Feb 2004 09:39:28 +0200
Message-ID: <DADF50F5EC506B41A0F375ABEB3206360143B715@esebe023.ntc.nokia.com>
Thread-Topic: [Sigtran] SUA v16: TID and DRM labels
Thread-Index: AcP3hIV4sDvXRZS6RQuQdtHnN9tFRAAAARTw
To: <bidulock@openss7.org>
Cc: <barryn@adax.com>, <sigtran@ietf.org>, <sgilchrist@connetcom.com>
X-OriginalArrivalTime: 20 Feb 2004 07:39:32.0601 (UTC) FILETIME=[AE268690:01C3F784]
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

Brian,

> What about removal?

If people on the list accept it, with STRONG consensus & we could=20
query any known implementations, I think this may be possible - however
I'd defer to Lyndon as WG chair to verify it.

thanks,
John

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



From exim@www1.ietf.org  Mon Feb 23 09:31:52 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 JAA27805
	for <sigtran-archive@odin.ietf.org>; Mon, 23 Feb 2004 09:31:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvH7E-00052q-DG
	for sigtran-archive@odin.ietf.org; Mon, 23 Feb 2004 09:31:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1NEVOAB019388
	for sigtran-archive@odin.ietf.org; Mon, 23 Feb 2004 09:31:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvH75-00052N-NP; Mon, 23 Feb 2004 09:31:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvH66-0004y0-V8
	for sigtran@optimus.ietf.org; Mon, 23 Feb 2004 09:30:14 -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 JAA27688
	for <sigtran@ietf.org>; Mon, 23 Feb 2004 09:30:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvH64-0007c1-00
	for sigtran@ietf.org; Mon, 23 Feb 2004 09:30:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvH54-0007X8-00
	for sigtran@ietf.org; Mon, 23 Feb 2004 09:29:11 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvH47-0007S4-00
	for sigtran@ietf.org; Mon, 23 Feb 2004 09:28:11 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id JAA22950
	for <sigtran@ietf.org>; Mon, 23 Feb 2004 09:28:09 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: <sigtran@ietf.org>
Subject: RE: [Sigtran] SUA v16: TID and DRM labels
Date: Mon, 23 Feb 2004 09:26:02 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMEEDACEAA.asveren@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <DADF50F5EC506B41A0F375ABEB3206360143B715@esebe023.ntc.nokia.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Although I also believe fixing the label mechanism or replacing it with an
alternative should be the ultimate goal (I also agree that if it is to be
meant "optional", there should be a matching error code to reject an ASPAC
with labels), IMO taking it out at this moment is maybe not the best choice.
As far as I remember, label mechanism had problems, when there is a multiple
SG configuration(?). As it is right now, it looks like working for single SG
case, and practically has some use for such a configuration.

I also agree that a draft is not carved on the stone and is subject to
change(afterall it is just a "draft") but considering that SUA was held
mainly because of security procedures updates for so long time, the
situation is a bit different, i.e. people (at least some of them) did not
expect any procedural changes there.

   Tolga

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> john.loughney@nokia.com
> Sent: Friday, February 20, 2004 2:39 AM
> To: bidulock@openss7.org
> Cc: barryn@adax.com; sigtran@ietf.org; sgilchrist@connetcom.com
> Subject: RE: [Sigtran] SUA v16: TID and DRM labels
>
>
> Brian,
>
> > What about removal?
>
> If people on the list accept it, with STRONG consensus & we could
> query any known implementations, I think this may be possible - however
> I'd defer to Lyndon as WG chair to verify it.
>
> thanks,
> John
>
> _______________________________________________
> Sigtran mailing 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 Feb 23 10:27: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 KAA02295
	for <sigtran-archive@odin.ietf.org>; Mon, 23 Feb 2004 10:27:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvHz3-0008Mu-Gq
	for sigtran-archive@odin.ietf.org; Mon, 23 Feb 2004 10:27:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1NFR1gL032167
	for sigtran-archive@odin.ietf.org; Mon, 23 Feb 2004 10:27:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvHz2-0008MY-Ih; Mon, 23 Feb 2004 10:27:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvHyJ-0008Li-O9
	for sigtran@optimus.ietf.org; Mon, 23 Feb 2004 10:26:15 -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 KAA02274
	for <sigtran@ietf.org>; Mon, 23 Feb 2004 10:26:11 -0500 (EST)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvHyH-0005Cl-00
	for sigtran@ietf.org; Mon, 23 Feb 2004 10:26:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvHxJ-00058c-00
	for sigtran@ietf.org; Mon, 23 Feb 2004 10:25:14 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvHwN-00053k-00
	for sigtran@ietf.org; Mon, 23 Feb 2004 10:24:15 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1NFOAH11211;
	Mon, 23 Feb 2004 17:24:10 +0200 (EET)
X-Scanned: Mon, 23 Feb 2004 17:24:01 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id i1NFO1XY009658;
	Mon, 23 Feb 2004 17:24:01 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks001.ntc.nokia.com 00fq6G4v; Mon, 23 Feb 2004 17:23:59 EET
Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1NFNr722077;
	Mon, 23 Feb 2004 17:23:54 +0200 (EET)
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Mon, 23 Feb 2004 17:23:54 +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
Subject: RE: [Sigtran] SUA v16: TID and DRM labels
Date: Mon, 23 Feb 2004 17:23:52 +0200
Message-ID: <DADF50F5EC506B41A0F375ABEB3206360143B74B@esebe023.ntc.nokia.com>
Thread-Topic: [Sigtran] SUA v16: TID and DRM labels
Thread-Index: AcP6Gg/5ClYBlgTfSWi0lNsHaEw9uQABrCPg
To: <asveren@ulticom.com>, <sigtran@ietf.org>
X-OriginalArrivalTime: 23 Feb 2004 15:23:54.0338 (UTC) FILETIME=[0C477420:01C3FA21]
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

Hi Tolga,

Under the good news/bad news department, the draft tracker shows that =
SUA
was finally approved:

https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dsearch_list&=
search_job_owner=3D0&search_group_acronym=3D&search_status_id=3D&search_c=
ur_state=3D&sub_state_id=3D6&search_filename=3Ddraft-ietf-sigtran-sua&sea=
rch_rfcnumber=3D&search_area_acronym=3D&search_button=3DSEARCH

What this means is usually editorial mistakes can be fixed, but big =
changes=20
cannot.  However, I will defer all comments to the wisdom of our WG =
chair.

John

> -----Original Message-----
> From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> ext Tolga Asveren
> Sent: 23 February, 2004 16:26
> To: sigtran@ietf.org
> Subject: RE: [Sigtran] SUA v16: TID and DRM labels
>=20
>=20
>=20
> Although I also believe fixing the label mechanism or=20
> replacing it with an
> alternative should be the ultimate goal (I also agree that if=20
> it is to be
> meant "optional", there should be a matching error code to=20
> reject an ASPAC
> with labels), IMO taking it out at this moment is maybe not=20
> the best choice.
> As far as I remember, label mechanism had problems, when=20
> there is a multiple
> SG configuration(?). As it is right now, it looks like=20
> working for single SG
> case, and practically has some use for such a configuration.
>=20
> I also agree that a draft is not carved on the stone and is subject to
> change(afterall it is just a "draft") but considering that=20
> SUA was held
> mainly because of security procedures updates for so long time, the
> situation is a bit different, i.e. people (at least some of=20
> them) did not
> expect any procedural changes there.
>=20
>    Tolga
>=20
> > -----Original Message-----
> > From: sigtran-admin@ietf.org=20
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> > john.loughney@nokia.com
> > Sent: Friday, February 20, 2004 2:39 AM
> > To: bidulock@openss7.org
> > Cc: barryn@adax.com; sigtran@ietf.org; sgilchrist@connetcom.com
> > Subject: RE: [Sigtran] SUA v16: TID and DRM labels
> >
> >
> > Brian,
> >
> > > What about removal?
> >
> > If people on the list accept it, with STRONG consensus & we could
> > query any known implementations, I think this may be=20
> possible - however
> > I'd defer to Lyndon as WG chair to verify it.
> >
> > thanks,
> > John
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20

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



From exim@www1.ietf.org  Mon Feb 23 12:06: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 MAA06126
	for <sigtran-archive@odin.ietf.org>; Mon, 23 Feb 2004 12:06:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvJWv-0006vq-CN
	for sigtran-archive@odin.ietf.org; Mon, 23 Feb 2004 12:06:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1NH65BA026646
	for sigtran-archive@odin.ietf.org; Mon, 23 Feb 2004 12:06:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvJWs-0006vG-0O; Mon, 23 Feb 2004 12:06:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvJWE-0006pv-VY
	for sigtran@optimus.ietf.org; Mon, 23 Feb 2004 12:05:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06042
	for <sigtran@ietf.org>; Mon, 23 Feb 2004 12:05:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvJWD-0005CQ-00
	for sigtran@ietf.org; Mon, 23 Feb 2004 12:05:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvJVG-00052l-00
	for sigtran@ietf.org; Mon, 23 Feb 2004 12:04:23 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvJUJ-0004sm-00
	for sigtran@ietf.org; Mon, 23 Feb 2004 12:03:24 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i1NH3H7T027622
	for <sigtran@ietf.org>; Mon, 23 Feb 2004 12:03:18 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: <sigtran@ietf.org>
Subject: RE: [Sigtran] SUA v16: TID and DRM labels
Date: Mon, 23 Feb 2004 12:04:48 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOEEMBCEAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <DADF50F5EC506B41A0F375ABEB3206360143B74B@esebe023.ntc.nokia.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

So does this mean that we will be starting an SUA IG?

> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> john.loughney@nokia.com
> Sent: Monday, February 23, 2004 10:24 AM
> To: asveren@ulticom.com; sigtran@ietf.org
> Subject: RE: [Sigtran] SUA v16: TID and DRM labels
>
>
> Hi Tolga,
>
> Under the good news/bad news department, the draft tracker shows that SUA
> was finally approved:
>
> https://datatracker.ietf.org/public/pidtracker.cgi?command=search_
> list&search_job_owner=0&search_group_acronym=&search_status_id=&se
> arch_cur_state=&sub_state_id=6&search_filename=draft-ietf-sigtran-
> sua&search_rfcnumber=&search_area_acronym=&search_button=SEARCH
>
> What this means is usually editorial mistakes can be fixed, but
> big changes
> cannot.  However, I will defer all comments to the wisdom of our WG chair.
>
> John
>
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > ext Tolga Asveren
> > Sent: 23 February, 2004 16:26
> > To: sigtran@ietf.org
> > Subject: RE: [Sigtran] SUA v16: TID and DRM labels
> >
> >
> >
> > Although I also believe fixing the label mechanism or
> > replacing it with an
> > alternative should be the ultimate goal (I also agree that if
> > it is to be
> > meant "optional", there should be a matching error code to
> > reject an ASPAC
> > with labels), IMO taking it out at this moment is maybe not
> > the best choice.
> > As far as I remember, label mechanism had problems, when
> > there is a multiple
> > SG configuration(?). As it is right now, it looks like
> > working for single SG
> > case, and practically has some use for such a configuration.
> >
> > I also agree that a draft is not carved on the stone and is subject to
> > change(afterall it is just a "draft") but considering that
> > SUA was held
> > mainly because of security procedures updates for so long time, the
> > situation is a bit different, i.e. people (at least some of
> > them) did not
> > expect any procedural changes there.
> >
> >    Tolga
> >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > john.loughney@nokia.com
> > > Sent: Friday, February 20, 2004 2:39 AM
> > > To: bidulock@openss7.org
> > > Cc: barryn@adax.com; sigtran@ietf.org; sgilchrist@connetcom.com
> > > Subject: RE: [Sigtran] SUA v16: TID and DRM labels
> > >
> > >
> > > Brian,
> > >
> > > > What about removal?
> > >
> > > If people on the list accept it, with STRONG consensus & we could
> > > query any known implementations, I think this may be
> > possible - however
> > > I'd defer to Lyndon as WG chair to verify it.
> > >
> > > thanks,
> > > John
> > >
> > > _______________________________________________
> > > Sigtran mailing 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 Feb 23 13:32: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 NAA09774
	for <sigtran-archive@odin.ietf.org>; Mon, 23 Feb 2004 13:32:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvKs8-0004jh-TK
	for sigtran-archive@odin.ietf.org; Mon, 23 Feb 2004 13:32:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1NIW49T018181
	for sigtran-archive@odin.ietf.org; Mon, 23 Feb 2004 13:32:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvKs4-0004j4-QI; Mon, 23 Feb 2004 13:32:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvKrk-0004if-0T
	for sigtran@optimus.ietf.org; Mon, 23 Feb 2004 13:31:40 -0500
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09754
	for <sigtran@odin.ietf.org>; Mon, 23 Feb 2004 13:31:37 -0500 (EST)
Received: from nobody by optimus.ietf.org with local (Exim 4.20)
	id 1AvKrF-0004fh-JN; Mon, 23 Feb 2004 13:31:09 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>,
        RFC Editor <rfc-editor@rfc-editor.org>, <sigtran@ietf.org>
Message-Id: <E1AvKrF-0004fh-JN@optimus.ietf.org>
Date: Mon, 23 Feb 2004 13:31:09 -0500
Subject: [Sigtran] Protocol Action: 'Signalling Connection Control Part User
 Adaptation Layer (SUA)' to Proposed Standard
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

The IESG has approved the following document:

- 'Signalling Connection Control Part User Adaptation Layer (SUA) '
   <draft-ietf-sigtran-sua-16.txt> as a Proposed Standard

This document is the product of the Signaling Transport Working Group. 

The IESG contact persons are Jon Peterson and Allison Mankin.

Technical Summary

  This memo defines a protocol for the transport of a number of telephony
  signaling protocols. Specifically it supports the transport of any
  Signaling Connection Control Part-User (SCCP-User) signaling protocols
  (e.g., Transaction Capabilities Protocol, Radio Access Network Application
  Protocol, etc.) over IP using the Stream Control Transport Protocol (SCTP)

  The protocol is modular and symmetric, to allow it to work in diverse
  architectures, such as a Signaling Gateway to IP Signaling Endpoint
  architecture as well as a peer-to-peer IP Signaling Endpoint architecture.
  Protocol elements have been included to allow operation between peers in 
  the Signaling System-7 (SS7) and IP domains.
 
Working Group Summary
 
  The working group supported the publication of this document and no issues
  were raised during IETF Last-Call.
 
Protocol Quality
 
  This document was reviewed for the IESG by Scott Bradner.


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



From exim@www1.ietf.org  Tue Feb 24 15:43: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 PAA10056
	for <sigtran-archive@odin.ietf.org>; Tue, 24 Feb 2004 15:43:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvjOS-0000a3-Nl
	for sigtran-archive@odin.ietf.org; Tue, 24 Feb 2004 15:43:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1OKh48I002208
	for sigtran-archive@odin.ietf.org; Tue, 24 Feb 2004 15:43:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvjOP-0000ZO-IA; Tue, 24 Feb 2004 15:43:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvjNq-0000Yk-12
	for sigtran@optimus.ietf.org; Tue, 24 Feb 2004 15:42:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09957
	for <sigtran@ietf.org>; Tue, 24 Feb 2004 15:42:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvjNo-0000CF-00
	for sigtran@ietf.org; Tue, 24 Feb 2004 15:42:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvjMs-000071-00
	for sigtran@ietf.org; Tue, 24 Feb 2004 15:41:27 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[AeKrUlZYcAQsi9li7xSj3vwhfRMkY0Mx])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvjMQ-000018-00
	for sigtran@ietf.org; Tue, 24 Feb 2004 15:40:58 -0500
Received: from ns.pigworks.openss7.net (IDENT:ZsCEEXxs8sFNlDGQlpIK64ieoXPo4F9Z@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1OKewI09873;
	Tue, 24 Feb 2004 13:40:58 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1OKeva23328;
	Tue, 24 Feb 2004 13:40:57 -0700
Date: Tue, 24 Feb 2004 13:40:57 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Hecht Martin <Martin.Hecht@comverse.com>
Cc: sigtran@ietf.org
Subject: Re: [SIGTRAN] M2PA Questions regarding draft-ietf-sigtran-m2pa-11 and draft-bidulock-sigtran-m2pa-test-04
Message-ID: <20040224134057.A22018@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Hecht Martin <Martin.Hecht@comverse.com>,
	sigtran@ietf.org
References: <6B1DF6EEBA51D31182F20090274043680B6E7765@mail-in.comverse.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <6B1DF6EEBA51D31182F20090274043680B6E7765@mail-in.comverse.com>; from Martin.Hecht@comverse.com on Tue, Feb 24, 2004 at 01:22:38PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i1OKewI09873
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,SUBJ_HAS_UNIQ_ID 
	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

Martin,

I have submitted draft-bidulock-sigtran-m2pa-test-05 to the I-D editor.
Until they become available on the ietf servers you can get them from
here:

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

The exact links are:

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

We are also publicly releasing our M2PA implementation under GPL that
conforms to a test suite written to this document.  Watch the downloads
page for more information.

See the Changes section towards the end of the document for changes from
Version 0.4 to Version 0.5.  (As usual an index appears at the end of the
document.)

More comments below...

On Tue, 24 Feb 2004, Hecht Martin wrote:

> Brian,
>=20
> I didn't know whether to write this to the whole IETF mailing list or j=
ust
> to you personally.  So I decided to write only to you.

I have copied this response to the sigtran mailing list as your questions
are likely of general interest there.

>=20
> This email concerns:
>=20
> 1) questions concerning Bad BSN handling=20
> 2) questions concerning Bad FSN handling=20
> 3) questions concerning tests that refer to Bad FIBR
> 4) question concerning receiving an MSU in the Aligned Ready state
>=20
> 1) Question concerning Bad BSN handling
>=20
> In test 3.8.10 Abnormal BSN - single Data message, the message is ACK'd=
 and
> sent to L3.
> In test 3.8.11 Abnormal BSN - two consecutive messages
>=20
>         Is the first message ACK'd and sent to L3?
>         Is the second message ACK'd and sent to L3 (prior to the link b=
eing
> taken out-of-service)?

This test case may need correction.  In the diagram it appears that an
abnormal FSN is being sent rather than an abnormal BSN.

>=20
> 2) Questions concerning Bad FSN handling
>=20
> In test 3.8.14 Abnormal FSN, it shows that the link is taken out-of-ser=
vice
> when the abnormal FSN is detected.  In Draft 11, on page 30, it simply =
says
> that the message is discarded.
>=20
>         Should the link be taken out-of-service in this case?

You will see in the new draft that 3.8.14 was removed because it is no lo=
nger
applicable for m2pa-11.

>=20
> 3) Question concerning tests that refer to Bad FIBR
>=20
> Tests 3.3.2,  3.3.4,  3.3.6,  3.3.8,  and 3.8.8 all refer to a Bad FIBR.
>=20
>         Since M2PA does not have a FIB, what is the intention here?

You will see in the new draft that 3.3.2, 3.3.4, 3.3.6 and 3.3.8 have bee=
n
made non-applicable, because they are not applicable to m2pa-11.

>=20
> 4) Question concerning receiving an MSU in the Aligned Ready state
>=20
> In test 3.2.4 Unexpected signal units/orders in "Proving" state, an MSU
> (User Data message) is shown as "ignored" if received in this state. =20

That is correct.  Under Q.703/Q.781 MSUs are ignored in the Proving state.

>=20
> In test 3.2.5 Unexpected signal units/orders in "Aligned Ready" state, =
it
> does not show the case of receiving an MSU.
>=20
>         If an MSU is received in the Aligned Ready state is it ignored?=
=20
>         Or, is the MSU accepted (ACK'd)? =20
>         If it is accepted, does it, or can it, replace the need to rece=
ive a
> Ready message - will the link go In Service?

See test case 3.1.6 for how Data is addressed in the Aligned Ready state,=
 but
generally, the peer should accept Data when In Service is expected just a=
s
Q.703/Q.781 accepts an MSU instead of a FISU in the Aligned Ready state.

>=20
> I hope this isn't too many questions.  I really appreciate any time you=
 will
> spend on this.

Your questions are well in line with the changes made to the document.  P=
lease
review the new document and see if the changes resolve your questions.

--brian

>=20
> Best regards,
> Martin Hecht
> Signaling Core Group, Embedded Division
> Comverse, Inc

--=20
Brian F. G. Bidulock    =A6 The reasonable man adapts himself to the =A6
bidulock@openss7.org    =A6 world; the unreasonable one persists in  =A6
http://www.openss7.org/ =A6 trying  to adapt the  world  to himself. =A6
                        =A6 Therefore  all  progress  depends on the =A6
                        =A6 unreasonable man. -- George Bernard Shaw =A6

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



From exim@www1.ietf.org  Wed Feb 25 09:58: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 JAA19143
	for <sigtran-archive@odin.ietf.org>; Wed, 25 Feb 2004 09:58:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aw0U6-0008JR-VT
	for sigtran-archive@odin.ietf.org; Wed, 25 Feb 2004 09:58:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1PEw2Bg031940
	for sigtran-archive@odin.ietf.org; Wed, 25 Feb 2004 09:58:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aw0U4-0008Iy-RP; Wed, 25 Feb 2004 09:58:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aw0U0-0008Hm-7w
	for sigtran@optimus.ietf.org; Wed, 25 Feb 2004 09:57:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19111
	for <sigtran@ietf.org>; Wed, 25 Feb 2004 09:57:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw0Ty-0000SS-00
	for sigtran@ietf.org; Wed, 25 Feb 2004 09:57:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw0T2-0000Mo-00
	for sigtran@ietf.org; Wed, 25 Feb 2004 09:56:57 -0500
Received: from phl-28-b-170.phl.dsl.cerfnet.com ([63.242.157.170] helo=slink5.mtl-nj.adax)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw0SW-0000HY-00
	for sigtran@ietf.org; Wed, 25 Feb 2004 09:56:25 -0500
Received: from bn001320 (bn001320 [192.168.1.61])
	by slink5.mtl-nj.adax (8.12.8/8.12.8) with SMTP id i1PEuL7T003098;
	Wed, 25 Feb 2004 09:56:21 -0500
From: "Barry Nagelberg" <barryn@adax.com>
To: <sigtran@ietf.org>
Cc: <sgilchrist@connetcom.com>
Subject: RE: [Sigtran] SUA v16: TID and DRM labels
Date: Wed, 25 Feb 2004 09:57:52 -0500
Message-ID: <JBECLENKLBCKAAKFGAJOCENJCEAA.barryn@adax.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <20040218230625.A9031@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
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

We don't think that it would be wise to remove the label mechanism - it
should be fixed and better documented. There is definitely a need for some
sort of Transaction Id routing mechanism. The existing label mechanism is a
good start - it just needs to be improved upon.

Barry Nagelberg

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Thursday, February 19, 2004 1:06 AM
> To: john.loughney@nokia.com
> Cc: barryn@adax.com; sigtran@ietf.org; sgilchrist@connetcom.com
> Subject: Re: [Sigtran] SUA v16: TID and DRM labels
>
>
> Barry,
>
> If you look back to the thread "SUA-09: SCCP Connections and TCAP
> Transactions" from Dec 2001/Jan 2002, you will find that at that
> "late date" it was too late to remove or fix the labels.  In that
> thread there was a proposal for a working solution.  The draft was
> advanced to IESG LC Feb 2002.  Now, two years later, it is neither
> fixed nor removed, and it is still a late date.  At this rate, expect
> corrections some time in 2006, if, of course, it is not still too
> late by then ;)
>
> I am concerned, however, that the approach is not clearly marked as
> optional.  Which it should be and was always intended to be.  That
> change can certainly be made before SUA goes out the door (unless
> the authors have been stripped ala M3UA).
>
> --brian
>
> John Loughney wrote:
>                     (Thu, 19 Feb 2004 06:15:23)
> > It would probably require an implementor's guide or -bis document to
> > make changes at this late date.
> >
> > John
> >
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > ext Brian F. G. Bidulock
> > > Sent: 19 February, 2004 01:57
> > > To: Barry Nagelberg
> > > Cc: SIGTRAN Mailing List; Seamus Gilchrist
> > > Subject: Re: [Sigtran] SUA v16: TID and DRM labels
> > >
> > >
> > >
> > > Barry,
> > >
> > > I think the decision at last call was that it would neither
> > > be fixed nor
> > > removed.  Perhaps John an Lyndon could shed some light on the
> > > possibility
> > > of doing either at this late date.
> > >
> > > --brian
> > >
> > > Barry Nagelberg wrote:
> > >                        (Wed, 18 Feb 2004 17:21:43)
> > > > Brian,
> > > >
> > > > Thanks for the clarifications. Regarding your comments:
> > > >
> > > > 1. Suggested text - We already provided it. Please see #1 below.
> > > >
> > > > 2. Length of mask - Section 3.10.16 states that the length
> > > of the mask is 16
> > > > bits. No where else in the draft is it mentioned that not
> > > all of the bits
> > > > are significant. If you are contending that not all of the bits are
> > > > significant, then this is another aspect that must be clarified.
> > > >
> > > > 3. I agree with you that the label mechanism, as currently
> > > specified, is
> > > > broken. However it is NOT optional, because there is no
> > > mechanism specified
> > > > through which the SGP can indicate to the ASP that it
> > > doesn't support the
> > > > TID Label parameter in the ASPAC message (there is no "Unsupported
> > > > parameter" error code). Thus SUA itself is also broken. So the label
> > > > mechanism must either be fixed or removed.
> > > >
> > > > Barry Nagelberg
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > Sent: Wednesday, February 18, 2004 4:17 PM
> > > > > To: Barry Nagelberg
> > > > > Cc: SIGTRAN Mailing List; Seamus Gilchrist
> > > > > Subject: Re: [Sigtran] SUA v16: TID and DRM labels
> > > > >
> > > > >
> > > > > Barry,
> > > > >
> > > > > Barry Nagelberg wrote:
> > > > >                    (Wed, 18 Feb 2004 15:26:12)
> > > > > > We have several suggestions for improving the clarity of the
> > > > > definition and
> > > > > > use of the TID and DRM label parameters:
> > > > > >
> > > > > > 1. Clarity - After some head-scratching and detective
> > > work, we think we
> > > > > > understand their purpose. We're assuming that:
> > > > > >
> > > > > > a. These labels are simply 16-bit masks that are logically
> > > > > ANDed onto the
> > > > > > received TCAP transaction ID, starting at the "Start" bit.
> > > > > >
> > > > > > b. If the result of the AND operation exactly matches
> > > the "Label" field,
> > > > > > then the message is sent to the ASP that registered for this
> > > > > label via the
> > > > > > ASPAC msg.
> > > > > >
> > > > > > c. An ASP that registers a label will be sent only
> > > those TID-bearing
> > > > > > messages that match its label.
> > > > > >
> > > > > > d. An ASP that does not register a label may be sent
> > > any TID-bearing
> > > > > > message.
> > > > > >
> > > > > > If these assumptions are correct, please state them
> > > explicitly in the
> > > > > > relevant sections of the draft(3.10.15, 3.10.16, 4.7.2.1 and
> > > > > 4.7.3.1). If
> > > > > > not, please clarify. It's not enough to say, as in 4.7.3.1,
> > > > > "the SG extracts
> > > > > > the label".
> > > > >
> > > > > That's my understanding.  Some clarity would be good.  Can you
> > > > > provide text?
> > > > >
> > > > > >
> > > > > >
> > > > > > 2. Redundancy - The label values are fixed length (16 bits). So
> > > > > why do we
> > > > > > need both a "Start" and an "End" position for applying the
> > > > > mask? One or the
> > > > > > other would seem to be enough.
> > > > >
> > > > > The label does not have to be 16 (significant) bits.
> > > > >
> > > > > >
> > > > > > 3. Simplicity - Why bother with a partial-sized mask at a
> > > > > specified "start"
> > > > > > bit. Why not just specify a "full-sized" 32-bit (TID) or 23-bit
> > > > > (DRM) mask?
> > > > >
> > > > > I don't know of any reason not to allow specification of a full
> > > > > 32-bit mask
> > > > > either.
> > > > >
> > > > > >
> > > > > > 4. Contradictions - Section 4.7.2.1 states that "All the ASPs
> > > > > within the AS
> > > > > > _must_ specify a unique label at a fixed position in
> > > the TID or DRN
> > > > > > parameter." The "must" here contradicts that fact the
> > > the TID and DRM
> > > > > > parameters are listed as Optional in the ASPAC msg. We're
> > > > > guessing that the
> > > > > > intention here is either:
> > > > > >
> > > > > > a. "If at least one of the ASPs within an AS specifies a label,
> > > > > then all the
> > > > > > ASPs within the AS must specify a unique label at a fixed
> > > > > position in the
> > > > > > TID or DRN parameter."
> > > > > >
> > > > > > or
> > > > > >
> > > > > > b. "All of the labels specified by the ASPs within an
> > > AS must start at a
> > > > > > fixed position in the TID or DRN parameter."
> > > > > >
> > > > > > or maybe
> > > > > >
> > > > > > (a) AND (b). Please clarify.
> > > > >
> > > > > I think we meant, "The ASPs within the AS specifying a label,
> > > > > must specify a
> > > > > unique label at a fixed position in the TID or DRN
> > > parameter."  The point
> > > > > being that no two labels (optionally specified) can overlap.
> > > > >
> > > > > That said, the label mechanism is still broken, as
> > > detailed in previous
> > > > > threads.  As it is an optional procedure, it might get fixed or
> > > > > fall out of
> > > > > use in the future.
> > > > >
> > > > > See draft-bidulock-sigtran-loadsel-02.pdf  I also have a session
> > > > > registration
> > > > > draft (never submitted) that provides a superior approach to the
> > > > > same problem.
> > > > > If someone is interested I will sumbit it.
> > > > >
> > > > > --brian
> > > > >
> > > > > >
> > > > > >
> > > > > > Barry Nagelberg


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



From exim@www1.ietf.org  Wed Feb 25 10:32: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 KAA22020
	for <sigtran-archive@odin.ietf.org>; Wed, 25 Feb 2004 10:32:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aw110-0001Cb-Ul
	for sigtran-archive@odin.ietf.org; Wed, 25 Feb 2004 10:32:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1PFW25t004621
	for sigtran-archive@odin.ietf.org; Wed, 25 Feb 2004 10:32:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aw10z-0001CH-AA; Wed, 25 Feb 2004 10:32:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aw10x-0001Bz-Ed
	for sigtran@optimus.ietf.org; Wed, 25 Feb 2004 10:31:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21994
	for <sigtran@ietf.org>; Wed, 25 Feb 2004 10:31:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw10u-00047f-00
	for sigtran@ietf.org; Wed, 25 Feb 2004 10:31:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw0zx-000421-00
	for sigtran@ietf.org; Wed, 25 Feb 2004 10:30:58 -0500
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 1Aw0z6-0003wv-00
	for sigtran@ietf.org; Wed, 25 Feb 2004 10:30:04 -0500
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 i1PFTwY05677;
	Wed, 25 Feb 2004 10:29:59 -0500
Received: by mail-in.comverse.com with Internet Mail Service (5.5.2657.72)
	id <F4RBBHA1>; Wed, 25 Feb 2004 10:22:56 -0500
Message-ID: <6B1DF6EEBA51D31182F20090274043680B6E776B@mail-in.comverse.com>
From: Hecht Martin <Martin.Hecht@comverse.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: sigtran@ietf.org
Subject: RE: [SIGTRAN] M2PA Questions regarding draft-ietf-sigtran-m2pa-11
	 and draft-bidulock-sigtran-m2pa-test-04
Date: Wed, 25 Feb 2004 10:22:53 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by us-wkf-interscan1.comverse.com id i1PFTwY05677
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,SUBJ_HAS_UNIQ_ID 
	autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Brian,

Thank you for your response.  Draft 5 clears up the FIBR issue and "part"=
 of
the FSN issue. Your answer to receiving an MSU in the Aligned Ready state
makes that clear.

So, I am left with the following questions/comments.

1) Out-of-order FSN is discarded

If an out-of-order FSN is discarded, then every FSN after that is
potentially out of order and discarded.  The links would fail from Excess=
ive
Delay of ACK.

2) 2 out of 3 Bad BSNs

The question remains whether the messages with the Bad BSN are ACKed and
forwarded to L3 prior to taking the link out of service.

Test 3.8.10 ACKs and forwards the message.  Test 3.8.11 does not show thi=
s.
Although it is not that important because the messages will be retrieved =
on
the peer and not lost.

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


-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: Tuesday, February 24, 2004 3:41 PM
To: Hecht Martin
Cc: sigtran@ietf.org
Subject: Re: [SIGTRAN] M2PA Questions regarding
draft-ietf-sigtran-m2pa-11 and draft-bidulock-sigtran-m2pa-test-04


Martin,

I have submitted draft-bidulock-sigtran-m2pa-test-05 to the I-D editor.
Until they become available on the ietf servers you can get them from
here:

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

The exact links are:

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

We are also publicly releasing our M2PA implementation under GPL that
conforms to a test suite written to this document.  Watch the downloads
page for more information.

See the Changes section towards the end of the document for changes from
Version 0.4 to Version 0.5.  (As usual an index appears at the end of the
document.)

More comments below...

On Tue, 24 Feb 2004, Hecht Martin wrote:

> Brian,
>=20
> I didn't know whether to write this to the whole IETF mailing list or j=
ust
> to you personally.  So I decided to write only to you.

I have copied this response to the sigtran mailing list as your questions
are likely of general interest there.

>=20
> This email concerns:
>=20
> 1) questions concerning Bad BSN handling=20
> 2) questions concerning Bad FSN handling=20
> 3) questions concerning tests that refer to Bad FIBR
> 4) question concerning receiving an MSU in the Aligned Ready state
>=20
> 1) Question concerning Bad BSN handling
>=20
> In test 3.8.10 Abnormal BSN - single Data message, the message is ACK'd
and
> sent to L3.
> In test 3.8.11 Abnormal BSN - two consecutive messages
>=20
>         Is the first message ACK'd and sent to L3?
>         Is the second message ACK'd and sent to L3 (prior to the link
being
> taken out-of-service)?

This test case may need correction.  In the diagram it appears that an
abnormal FSN is being sent rather than an abnormal BSN.

>=20
> 2) Questions concerning Bad FSN handling
>=20
> In test 3.8.14 Abnormal FSN, it shows that the link is taken
out-of-service
> when the abnormal FSN is detected.  In Draft 11, on page 30, it simply
says
> that the message is discarded.
>=20
>         Should the link be taken out-of-service in this case?

You will see in the new draft that 3.8.14 was removed because it is no
longer
applicable for m2pa-11.

>=20
> 3) Question concerning tests that refer to Bad FIBR
>=20
> Tests 3.3.2,  3.3.4,  3.3.6,  3.3.8,  and 3.8.8 all refer to a Bad FIBR.
>=20
>         Since M2PA does not have a FIB, what is the intention here?

You will see in the new draft that 3.3.2, 3.3.4, 3.3.6 and 3.3.8 have bee=
n
made non-applicable, because they are not applicable to m2pa-11.

>=20
> 4) Question concerning receiving an MSU in the Aligned Ready state
>=20
> In test 3.2.4 Unexpected signal units/orders in "Proving" state, an MSU
> (User Data message) is shown as "ignored" if received in this state. =20

That is correct.  Under Q.703/Q.781 MSUs are ignored in the Proving state.

>=20
> In test 3.2.5 Unexpected signal units/orders in "Aligned Ready" state, =
it
> does not show the case of receiving an MSU.
>=20
>         If an MSU is received in the Aligned Ready state is it ignored?=
=20
>         Or, is the MSU accepted (ACK'd)? =20
>         If it is accepted, does it, or can it, replace the need to rece=
ive
a
> Ready message - will the link go In Service?

See test case 3.1.6 for how Data is addressed in the Aligned Ready state,
but
generally, the peer should accept Data when In Service is expected just a=
s
Q.703/Q.781 accepts an MSU instead of a FISU in the Aligned Ready state.

>=20
> I hope this isn't too many questions.  I really appreciate any time you
will
> spend on this.

Your questions are well in line with the changes made to the document.
Please
review the new document and see if the changes resolve your questions.

--brian

>=20
> Best regards,
> Martin Hecht
> Signaling Core Group, Embedded Division
> Comverse, Inc

--=20
Brian F. G. Bidulock    =A6 The reasonable man adapts himself to the =A6
bidulock@openss7.org    =A6 world; the unreasonable one persists in  =A6
http://www.openss7.org/ =A6 trying  to adapt the  world  to himself. =A6
                        =A6 Therefore  all  progress  depends on the =A6
                        =A6 unreasonable man. -- George Bernard Shaw =A6
______________________________________________________________________
  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  Sat Feb 28 14:00:34 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 OAA27926
	for <sigtran-archive@odin.ietf.org>; Sat, 28 Feb 2004 14:00:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ax9h1-0003BO-0s
	for sigtran-archive@odin.ietf.org; Sat, 28 Feb 2004 14:00:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1SJ064H012206
	for sigtran-archive@odin.ietf.org; Sat, 28 Feb 2004 14:00:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ax9gy-0003Aj-7W; Sat, 28 Feb 2004 14:00:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ax9gH-00038x-UD
	for sigtran@optimus.ietf.org; Sat, 28 Feb 2004 13:59:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27905
	for <sigtran@ietf.org>; Sat, 28 Feb 2004 13:59:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ax9gF-0002gV-00
	for sigtran@ietf.org; Sat, 28 Feb 2004 13:59:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ax9fP-0002bj-00
	for sigtran@ietf.org; Sat, 28 Feb 2004 13:58:27 -0500
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ax9f0-0002Vq-00
	for sigtran@ietf.org; Sat, 28 Feb 2004 13:58:02 -0500
Received: from [172.16.48.246] (unknown [210.93.162.110])
	by mail-n.franken.de (Postfix) with ESMTP id 27BF1245D2
	for <sigtran@ietf.org>; Sat, 28 Feb 2004 19:58:00 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v612)
Content-Transfer-Encoding: 7bit
Message-Id: <A40E5B98-6A1F-11D8-8203-000A95DC192A@lurchi.franken.de>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: sigtran@ietf.org
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Date: Sat, 28 Feb 2004 19:55:13 +0100
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M3UA IG Last Call Comment: Padding
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Dear all,

RFC 3332 states:

    Parameter Value: variable length.

       The Parameter Value field contains the actual information to be
       transferred in the parameter.

       The total length of a parameter (including Tag, Parameter Length
       and Value fields) MUST be a multiple of 4 bytes.  If the length of
       the parameter is not a multiple of 4 bytes, the sender pads the
       Parameter at the end (i.e., after the Parameter Value field) with
       all zero bytes.  The length of the padding is NOT included in the
       parameter length field.  A sender SHOULD NOT pad with more than 3
       bytes.  The receiver MUST ignore the padding bytes.

I think we have to change the sentence
       A sender SHOULD NOT pad with more than 3 bytes.
to
       A sender MUST NOT pad with more than 3 bytes.

Without this change a receive is not able to skip unknown
parameters because there is no reliable information where the next 
parameter
starts.

Best regards
Michael


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



