Re: [Sigtran] Query regarding the sequence message delivery functionality in M3UA layer

"Brian F. G. Bidulock" <bidulock@openss7.com> Thu, 28 July 2016 18:48 UTC

Return-Path: <bidulock@openss7.com>
X-Original-To: sigtran@ietfa.amsl.com
Delivered-To: sigtran@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA99412DCBD for <sigtran@ietfa.amsl.com>; Thu, 28 Jul 2016 11:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.487
X-Spam-Level:
X-Spam-Status: No, score=-5.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YScUXEbfX7M8 for <sigtran@ietfa.amsl.com>; Thu, 28 Jul 2016 11:48:36 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D851112DBDF for <sigtran@ietf.org>; Thu, 28 Jul 2016 11:48:32 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id u6SImUC2015603 for <sigtran@ietf.org>; Thu, 28 Jul 2016 12:48:30 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id u6SImUlg032066 for <sigtran@ietf.org>; Thu, 28 Jul 2016 12:48:30 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id u6SImTqw032065 for sigtran@ietf.org; Thu, 28 Jul 2016 12:48:29 -0600
Date: Thu, 28 Jul 2016 12:48:29 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.com>
To: sigtran@ietf.org
Message-ID: <20160728184829.GA31818@openss7.com>
Mail-Followup-To: sigtran@ietf.org
References: <CAAZxfpfcgxPzDeQjE9i_Wure5u2LnQo8vKtwjNgJB1UUdwLDXQ@mail.gmail.com> <CAAZxfpfd=ToGmRXWNDU4NzFUCCu26Re=eiu6Sj1afipWQGGqUQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAAZxfpfd=ToGmRXWNDU4NzFUCCu26Re=eiu6Sj1afipWQGGqUQ@mail.gmail.com>
Organization: http://www.openss7.com/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.org>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/AxZOytl9CSm0N4cqJzxH3Ovkyjs>
Subject: Re: [Sigtran] Query regarding the sequence message delivery functionality in M3UA layer
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: bidulock@openss7.com
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sigtran/>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2016 18:48:38 -0000

Pradeep,

Please see comments inline...

Pradeep Kumar wrote:                              (Thu, 28 Jul 2016 14:53:11)
>    Hi,
>    Can someone help with the below query?
>    re-posting the text again as:
>    +++++++++++++++++++
> 
>    I had an query regarding the sequence message delivery functionality in
>    M3UA layer.
> 
>    Â
> 
>    As in the SS7/MTP3 layer there is concept of the controlled re-routing
>    in case of links status un-availability, the controlled re-routing
>    buffer and its time controlled procedure ensures that that are messages
>    are delivered in-sequence.  As explained in the RFC section 8.1.1 of
>    T-REC-Q704 as :
> 
>    â8.1.1Â The objective of the controlled rerouting procedure is to
>    restore the optimal signalling
> 
>    routing and to minimize mis-sequencing of messages. Therefore,
>    controlled rerouting includes a
> 
>    time-controlled traffic diversion procedure,â
> 

I believe that force rerouting is performed when a route becomes
unavailable; time-controlled rerouting is performed when a route
is restored.  Nevertheless, these procedures are as applicable
in M3UA as they are in MTP, particularly when the ASP has an AS
connected to multiple SGs acting as STPs in the SS7 network.

> 
>    Now in case of M3UA the same situation can occur, so do we have an
>    similar functionality of controlled re-routing available in
>    M3UA/Sigtran as well? Â

Because they are not explicitly part of the line protocol for
M3UA, you will not find them discussed in RFC 4666.

>    If yes please mentioned the RFC section(I could not find any reference
>    in RFC on this topic). ?

They were discussed, however, in a draft from 2007:

 http://www.openss7.org/docs/draft-bidulock-sigtran-corid-05.txt

Note that the sequenced changeover procedures in this draft have
not been supported by many implementations; however, the time-
controlled versions of the procedures have been implemented by
most SG as STP and some AS implementations.

>    Â  Â  Â  Â  Â  Â  Â  IF NO, then what is the reasoning behind not
>    having the controlled re-routing in M3UA/SIGTRAN? Is it so that we
>    donât need such procedures in IP world and what is the reason for it?

It is a task to be performed above M3UA layer and that is why
it is not included in the M3UA specifications.

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