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

Pradeep Kumar <pradeepkumar143@gmail.com> Tue, 26 July 2016 13:07 UTC

Return-Path: <pradeepkumar143@gmail.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 A4C3412DBFD for <sigtran@ietfa.amsl.com>; Tue, 26 Jul 2016 06:07:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 2yE6BkKMqeIo for <sigtran@ietfa.amsl.com>; Tue, 26 Jul 2016 06:07:39 -0700 (PDT)
Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04DFC12DB03 for <sigtran@ietf.org>; Tue, 26 Jul 2016 06:03:31 -0700 (PDT)
Received: by mail-it0-x22e.google.com with SMTP id f6so17615586ith.0 for <sigtran@ietf.org>; Tue, 26 Jul 2016 06:03:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=4RaLYoKn1WUDnfHU5ZJ7LwT1IUQgpzU5N7tNqfMLG7w=; b=hIS9fPpfum8Lx0J/koIrXHWGxPCShOdlAiClJjzXzI5Q2V/c6b1gJ/fm8GDmVRzETi HqiehFSR6bm3sj7vTY/1LSZyQnqfDEMHErjCUP1Fz77cEX1QXiXIlJ0zrSYsjAhHJZCR efqhy/yOGUiFLiuUYK94T7D5vymb0mpm0Mw1henvyVWqIUhbagTVab9ukUAjATVic8Cz jfyUb+YI8Nicl7arU2yU68jfgpaz30MK9Md8x6GkixE6UrTwPwBZcIRzThT6M2sTnzuE DYVRSz3ZgblpLAsJwyce7hfoMzreQ8W44vONPBgihhe8LshVo83cl0N1iKYPIoi2XqWd Sgsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=4RaLYoKn1WUDnfHU5ZJ7LwT1IUQgpzU5N7tNqfMLG7w=; b=aQmow1Es9pVqKs5baKDMN3ZNiRILNfTN77vh23GtIJ7LiVS1FH/CcuHYZA7mEti5/z 7iQt8K3DIg+QLRRfneX8Ls7wwXkFB3taNtNZj1xw0vnvZYyQt9SzFMv3OmrDNyxpXail dgfwY+zeg4bOmC6wjwzCOEi5LLJAEavbJeVWiGx/EReR1H7jzwOwVYbrz1BvzN8Xzl9a ES/bB52E5V/NRYILEISwYu/9fuy8DTHK7zKGCSLNZVCLrWuLbJK8WAnNmgGoCiYs9EHb 1zmmXDO9AY+6OpQEat0Z7WbjViHcMbbJjsCsd/fHINsE/ZnjeyP3ZGeSIbKEHd3HostW 7cJA==
X-Gm-Message-State: AEkoouvsgNUn4ZcTLPjHVGxdrojMEVQBC2kx6nZQE0iF43BLI557G/zMmoFf4k0IeW35H1CHvApSPrCoam+/xw==
X-Received: by 10.202.102.214 with SMTP id m83mr10559945oik.24.1469538210161; Tue, 26 Jul 2016 06:03:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.14.41 with HTTP; Tue, 26 Jul 2016 06:03:29 -0700 (PDT)
From: Pradeep Kumar <pradeepkumar143@gmail.com>
Date: Tue, 26 Jul 2016 18:33:29 +0530
Message-ID: <CAAZxfpfcgxPzDeQjE9i_Wure5u2LnQo8vKtwjNgJB1UUdwLDXQ@mail.gmail.com>
To: sigtran@ietf.org
Content-Type: multipart/alternative; boundary="001a1140a86c002b590538898713"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/YbTCepYUNWVe8cg1Kqoht6jYmZ0>
Subject: [Sigtran] Query regarding the sequence message delivery functionality in M3UA layer
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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: Tue, 26 Jul 2016 15:00:58 -0000

Hi,



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,” *



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?

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

              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?





Best Regards,

Pradeep Kumar

*“The world needs HQ (Humanity quotient) more than IQ.”*