IETF Logo Mail Archive

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

Pradeep4 Kumar <pradeep4.kumar@aricent.com> Tue, 26 July 2016 11:11 UTC

Return-Path: <pradeep4.kumar@aricent.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 9F47512B00B for <sigtran@ietfa.amsl.com>; Tue, 26 Jul 2016 04:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.132
X-Spam-Level:
X-Spam-Status: No, score=-1.132 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_WEB=0.77, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=aricent.onmicrosoft.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 kj4zvAipY40x for <sigtran@ietfa.amsl.com>; Tue, 26 Jul 2016 04:11:06 -0700 (PDT)
Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-sg2apc01on0056.outbound.protection.outlook.com [104.47.125.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 472DF12D61F for <sigtran@ietf.org>; Tue, 26 Jul 2016 04:11:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aricent.onmicrosoft.com; s=selector1-Aricent-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=FIUUyRbaP7y1TOiifU0x1asxtBwtzqDX/JnCq5Bjux8=; b=W7Eapbs7W4sYCv/mcXGIBMxsjmmfCZewtw1st4czV864YfNL4muwqnmAoLjvZKoK0e1RDIic0fIjEQy3MHGgtrdwVXqm8jMmD82nDauLcud5ZLNlyqSdQDlMOirJdPsP22v/nyERJnyWVchKhwq/m0iZ6qyMPIi4A+BMuAp6qbk=
Received: from PS1PR04MB1722.apcprd04.prod.outlook.com (10.167.52.16) by PS1PR04MB1723.apcprd04.prod.outlook.com (10.167.52.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.544.10; Tue, 26 Jul 2016 11:11:00 +0000
Received: from PS1PR04MB1722.apcprd04.prod.outlook.com ([10.167.52.16]) by PS1PR04MB1722.apcprd04.prod.outlook.com ([10.167.52.16]) with mapi id 15.01.0544.019; Tue, 26 Jul 2016 11:11:00 +0000
From: Pradeep4 Kumar <pradeep4.kumar@aricent.com>
To: "sigtran@ietf.org" <sigtran@ietf.org>
Thread-Topic: Query regarding the sequence message delivery functionality in M3UA layer
Thread-Index: AdHnLj3iOjI1CbtlT4eNlmt456iL4w==
Date: Tue, 26 Jul 2016 11:10:59 +0000
Message-ID: <PS1PR04MB172269BA2582F52F16885623DE0E0@PS1PR04MB1722.apcprd04.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pradeep4.kumar@aricent.com;
x-originating-ip: [165.225.104.84]
x-ms-office365-filtering-correlation-id: ba6b7cdc-054d-4652-cfd2-08d3b545868b
x-microsoft-exchange-diagnostics: 1; PS1PR04MB1723; 6:cQcyMWP0po+CqKIkyNE1GPTWPOy1iBLJIfCDKAMZNCzywmNVSJCOTymd3+efFVLmw5Sbxg5oYLN4y1EUk7ZENBQ7PQdMV8pa9UFLyQzTztsLj9gnFZH6VfDgoqXfiBMuAPD/wLqTIr6rM2pc4oUZwdE3b4ulRT5FtJrKDC1R5DF773yA+KUxYVJfBZB4nBv0fVDSThE7TneIWHUHjFQKJz8NENelmUL+vb2gHSUhFJqqz81i92e8neIOiST1Rz7A9J4Eul5IrGSbpuK60NBP6IKmehuTPcO7+9qw+UGLlwY6x/ypPmP6qSzb5Ac9X8eW/4MVJPljvsGYmH4U4YMQqw==; 5:VQr29pu4oHw7k0irrKj1Q8c8lAauF2HNA5USJUs+yYxcgxwvvEwsAqZbHndezAHeytFCxwV8JNunk96TSB3bs8U24mm9eF6PxuZ3b2OAPL9LepF9XplqTBS7+MCeHov42A4+Zec5q+m10wmrogYEjg==; 24:trR4EUymnHT2O0DGuBmbKOSo+wC+l4o7hL7xFbexC5DhZ9nsEADg6OdNFQSXZvph84GFROvB/hgboDzzzChfxdrX7gCeyslkS5fgiXE2XYM=; 7:UWNX5JWsRCVECJWLV2zA92+nCOBBfrONtOFbz7BUlpkVNtAtjMGXVOjR7lPhryfZ/KexglTNvitNxDSCWr1qlWyDazY5DHFpINxksJkE634nxbgLIT3l+MWRkrxhHw1YAfjFho6hg4WiaJqHoTF1EJrbv82fNnaLf/FFkidjy8HixJEIPiMDOiv3J0EhHNeKPciVMshXDJKPDb0dv+GtWUtew2/NDvv3KbNmMKv8KQSmVmqrt+TVOXGJEHU3weOW
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:PS1PR04MB1723;
x-microsoft-antispam-prvs: <PS1PR04MB17232CDBC624C0F64726C109DE0E0@PS1PR04MB1723.apcprd04.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6055026); SRVR:PS1PR04MB1723; BCL:0; PCL:0; RULEID:; SRVR:PS1PR04MB1723;
x-forefront-prvs: 00159D1518
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(38564003)(189002)(199003)(10400500002)(11100500001)(68736007)(122556002)(50986999)(54356999)(92566002)(7110500001)(189998001)(106356001)(97736004)(87936001)(5003600100003)(7736002)(7696003)(74316002)(81166006)(19625215002)(1730700003)(8936002)(81156014)(101416001)(86362001)(19300405004)(9326002)(9686002)(5002640100001)(8676002)(19580395003)(2501003)(7846002)(2351001)(16236675004)(586003)(107886002)(110136002)(3846002)(77096005)(102836003)(15975445007)(2900100001)(229853001)(6116002)(15650500001)(790700001)(2420400007)(5630700001)(33656002)(5640700001)(3280700002)(10710500007)(3660700001)(2906002)(76576001)(105586002)(450100001)(66066001)(32563001); DIR:OUT; SFP:1101; SCL:1; SRVR:PS1PR04MB1723; H:PS1PR04MB1722.apcprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: aricent.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_PS1PR04MB172269BA2582F52F16885623DE0E0PS1PR04MB1722apcp_"
MIME-Version: 1.0
X-OriginatorOrg: Aricent.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jul 2016 11:11:00.0679 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: dbb4cbbe-57c5-469d-b342-a9814e1d2382
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PS1PR04MB1723
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/0N7kcxwLqfzyv-28_0OZyUHiXc8>
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 11:11:08 -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."
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."

v2.23.0 | Report a Bug | By Email