Re: [Sigtran] M2PA questions on synchronization and message handling

"Brian F. G. Bidulock" <bidulock@openss7.org> Thu, 20 December 2007 17:58 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 1J5Pek-0003wm-He; Thu, 20 Dec 2007 12:58:02 -0500
Received: from sigtran by megatron.ietf.org with local (Exim 4.43) id 1J5Pei-0003wb-Ha for sigtran-confirm+ok@megatron.ietf.org; Thu, 20 Dec 2007 12:58:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5Pei-0003wQ-7j for sigtran@ietf.org; Thu, 20 Dec 2007 12:58:00 -0500
Received: from gw.openss7.com ([206.75.119.236]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J5Peg-0006jB-JU for sigtran@ietf.org; Thu, 20 Dec 2007 12:58:00 -0500
Received: from ns.pigworks.openss7.net (IDENT:qKhoxLRKMUkaX+9eEIJknCbyVUY6SWu/@ns1.evil.openss7.net [192.168.9.1]) by gw.openss7.com (8.11.6/8.11.6) with ESMTP id lBKHvvI22604; Thu, 20 Dec 2007 10:57:57 -0700
Received: (from brian@localhost) by ns.pigworks.openss7.net (8.11.6/8.11.6) id lBKHvvS03506; Thu, 20 Dec 2007 10:57:57 -0700
Date: Thu, 20 Dec 2007 10:57:57 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Dario <dario_filjar@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] M2PA questions on synchronization and message handling
Message-ID: <20071220105757.B2813@openss7.org>
Mail-Followup-To: Dario <dario_filjar@yahoo.com>, sigtran@ietf.org
References: <14370241.post@talk.nabble.com> <20071217093027.A26375@openss7.org> <14435533.post@talk.nabble.com> <20071220104512.A2813@openss7.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20071220104512.A2813@openss7.org>; from bidulock@openss7.org on Thu, Dec 20, 2007 at 10:45:12AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc:
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

Dario,

Brian F. G. Bidulock wrote:              (Thu, 20 Dec 2007 10:45:12)
> > 
> > not if they are connected:
> > 
> > 1. message is received with invalid BSN. This message wil be discarded
> > 2. User Data message is received with FSN=x, valid, but it should be
> > discarded according to Q.703 statement above.
> > 3. User Data message is received with FSN=x+1. This is unexpected FSN and
> > the message will be discarded....and so on.
> > 
> > finally ack timer will expire and the link will go Out of Service.
> 
> The peer violated the protocol at 1.  (The rest is just one possible
> result of that.)  You should not find it surprising that signalling
> links fail to operate and eventually find themselves in the out-of-
> service state when one side refuses to follow the protocol.

See also test case 3.8.10-1 in draft-bidulock-sigtran-m2pa-test-08.txt
and section 2.2 of draft-bidulock-sigtran-ig-01.txt.

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