Re: [Sigtran] M2PA: resynchronization of sequence numbers after PO

"Brian F. G. Bidulock" <bidulock@openss7.org> Mon, 19 November 2007 12:37 UTC

Return-path: <sigtran-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iu5sJ-0004nt-52; Mon, 19 Nov 2007 07:37:15 -0500
Received: from sigtran by megatron.ietf.org with local (Exim 4.43) id 1Iu5sH-0004R6-Dj for sigtran-confirm+ok@megatron.ietf.org; Mon, 19 Nov 2007 07:37:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iu5sG-0004Hb-JD for sigtran@ietf.org; Mon, 19 Nov 2007 07:37:12 -0500
Received: from gw.openss7.com ([206.75.119.236]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iu5sA-0005zc-S4 for sigtran@ietf.org; Mon, 19 Nov 2007 07:37:12 -0500
Received: from ns.pigworks.openss7.net (IDENT:ZotIblPwyoz1iFj9ovh7fF8Y5dqavCrU@ns1.evil.openss7.net [192.168.9.1]) by gw.openss7.com (8.11.6/8.11.6) with ESMTP id lAJCb5e04590; Mon, 19 Nov 2007 05:37:05 -0700
Received: (from brian@localhost) by ns.pigworks.openss7.net (8.11.6/8.11.6) id lAJCb2N05621; Mon, 19 Nov 2007 05:37:02 -0700
Date: Mon, 19 Nov 2007 05:37:02 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: chenxu <chenxu@chinamobile.com>
Subject: Re: [Sigtran] M2PA: resynchronization of sequence numbers after PO
Message-ID: <20071119053702.A5404@openss7.org>
Mail-Followup-To: chenxu <chenxu@chinamobile.com>, Devayya BOPAIAH <devayya.bopaiah@alcatel-lucent.com>, "sigtran@ietf.org" <sigtran@ietf.org>
References: <OF2C505596.C2C1115D-ON48257398.0035731E@chinamobile.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: <OF2C505596.C2C1115D-ON48257398.0035731E@chinamobile.com>; from chenxu@chinamobile.com on Mon, Nov 19, 2007 at 05:47:30PM +0800
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: "sigtran@ietf.org" <sigtran@ietf.org>
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bidulock@openss7.org
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>
Errors-To: sigtran-bounces@ietf.org

chenxu,

chenxu wrote:                                    (Mon, 19 Nov 2007 17:47:30)
> Hi Brian F. G. Bidulock,
> 
> 	There is another possibility,the communication between SCTP and M2PA
> 	is lost in the endpoint which sending the first Ready message.This
> 	endpoint was once in RPO state and now in Ready message sending state.
> 	The second Ready message will not reach its M2PA  ,and its M2PA can
> 	not receive COMMUNICATIONS LOST indication either.

Nor will it receive any other message.  The implementation is seriously broken
and the link will fail.  Hopefully traffic at MTP Level 3 will reroute through
some better implementation after the link fails.

If the implementation breaks, it will break the protocol.

The rest was moot considering this premise.

--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