RE: [Sigtran] Client/Server Operation in M3UA IPSP

"Tolga Asveren" <asveren@ulticom.com> Fri, 23 September 2005 17:54 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIrl5-0002nq-Du; Fri, 23 Sep 2005 13:54:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIrl3-0002nl-53 for sigtran@megatron.ietf.org; Fri, 23 Sep 2005 13:54:49 -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 NAA27251 for <sigtran@ietf.org>; Fri, 23 Sep 2005 13:54:47 -0400 (EDT)
Received: from 192-73-206-10.ulticom.com ([192.73.206.10] helo=colby.ulticom.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EIrrU-0004Xh-PK for sigtran@ietf.org; Fri, 23 Sep 2005 14:01:31 -0400
Received: from pcasveren (pc-asveren.ulticom.com [172.25.33.55]) by colby.ulticom.com (8.12.10/8.12.10) with SMTP id j8NHsTa4000051 for <sigtran@ietf.org>; Fri, 23 Sep 2005 13:54:30 -0400 (EDT)
From: Tolga Asveren <asveren@ulticom.com>
To: sigtran@ietf.org
Subject: RE: [Sigtran] Client/Server Operation in M3UA IPSP
Date: Fri, 23 Sep 2005 13:37:58 -0400
Message-ID: <GBEBKGPKHGPAOFCLBNAMKEBJDGAA.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)
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
In-Reply-To: <433402FD.5030106@artesyncp.com>
Importance: Normal
X-Scanned-By: MIMEDefang 2.40
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
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

one more comment below...

    Tolga

> -----Original Message-----
> From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org]On
> Behalf Of Peter Woodhouse
> Sent: Friday, September 23, 2005 9:28 AM
> To: sigtran@ietf.org
> Subject: [Sigtran] Client/Server Operation in M3UA IPSP
>
>
>
> 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.
[TOLGA] Yes, it won't. Actually, DE-mode is more like two coupled
client/server relationships rather than a real peer-to-peer model.
>
> Comments?
>
> Peter
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


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