[Sigtran] Client/Server Operation in M3UA IPSP

Peter Woodhouse <peterw@artesyncp.com> Fri, 23 September 2005 13:35 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIniN-0005m5-SN; Fri, 23 Sep 2005 09:35:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIniL-0005lx-50 for sigtran@megatron.ietf.org; Fri, 23 Sep 2005 09:35:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14656 for <sigtran@ietf.org>; Fri, 23 Sep 2005 09:35:43 -0400 (EDT)
Received: from caly80.spider.com ([194.217.109.12]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EInol-0006se-CY for sigtran@ietf.org; Fri, 23 Sep 2005 09:42:24 -0400
Received: from no.name.available by caly80.spider.com via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with ESMTP; Fri, 23 Sep 2005 14:35:34 +0100
Received: from mailhub.spider.com (mailhub.spider.com [212.240.99.13]) by caly80.spider.com (Postfix) with ESMTP id 883BC6F84 for <sigtran@ietf.org>; Fri, 23 Sep 2005 14:35:29 +0100 (BST)
Received: from mailhub.spider.com by mailhub.spider.com via smtpd (for [172.16.254.22] [172.16.254.22]) with ESMTP; Fri, 23 Sep 2005 14:35:29 +0100
Received: from [212.240.99.34] (glayva.spider.com [212.240.99.34]) by batistuta.spider.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id TN4BX9XD; Fri, 23 Sep 2005 14:35:18 +0100
Message-ID: <433402FD.5030106@artesyncp.com>
Date: Fri, 23 Sep 2005 14:28:29 +0100
From: Peter Woodhouse <peterw@artesyncp.com>
Organization: Artesyn Communications Products
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sigtran@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] Client/Server Operation in M3UA IPSP
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
Sender: sigtran-bounces@ietf.org
Errors-To: sigtran-bounces@ietf.org

Hi All,

After the recent plugtest, it was suggested that this issue should be 
brought up here just for confirmation. So here goes.

In IPSP mode of M3UA, should there be any difference between how the 
client side and the server side operate?
For example, is it valid for the server side to send ASPUP?
Also, should the client send NTFY messages?

The way we interpret the RFC is that there is zero difference between 
client and server at M3UA level. The only difference is that the client 
side brings up the SCTP association.

Looking back through previous drafts of M3UA, section 1.4.8 of 
draft-ietf-sigtran-m3ua-06.txt did say "In the case of IPSP to IPSP 
communication, the peer endpoints using M3UA SHOULD be configured so 
that one always takes on the role of client and the other the role of 
server for initiating SCTP associations and M3UA messaging."
However the M3UA part was removed for draft 07 onwards.

In fact, I don't think Double Exchange would work if you dissallow the 
sending of ASPUP from the server side.

Comments?

Peter

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