Re: [Sigtran] Query regarding the sequence message delivery functionality in M3UA layer
Pradeep Kumar <pradeepkumar143@gmail.com> Thu, 28 July 2016 09:23 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 43E2712DBEC for <sigtran@ietfa.amsl.com>; Thu, 28 Jul 2016 02:23:15 -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 7N_BelAdEQQz for <sigtran@ietfa.amsl.com>; Thu, 28 Jul 2016 02:23:13 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 EECA712DBDE for <sigtran@ietf.org>; Thu, 28 Jul 2016 02:23:12 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id l72so54852578oig.2 for <sigtran@ietf.org>; Thu, 28 Jul 2016 02:23:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=WUiRaPqwqSP0ZwXEOF740PBsGtv+kaVLJzGAHhuVR0w=; b=i8IMNZ/j9mGNgMpevq3gjrAwjcjV3SKTLVWAmrLMYTa3ais7jQzx590op6yVcLZylC xUInw5XqqdECrh18TsYBohE3mQt9XxilrhKsBA5lslmyv9L77f+lpT/n0FAhjEghZQ0Z 3s4YYtLBlxYA1/M0Ou/7VzouNrfe6weY/J32M31zS2c/1+c/YHZMbmDYflCnCDCpTr62 zvZeW+WmacY4X+Z0NjXDMiz5b4s+Emhtsk3qJL8Yrk9h2x0pXRQVEO8Bq/HtlHeMqrkL BLb/V63p6i7M9WGSTZp/K8osuNi2yelNohy3sCjR/xWfoMzcZ+PTtnvfNWbIjmpPVxmG Ra/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=WUiRaPqwqSP0ZwXEOF740PBsGtv+kaVLJzGAHhuVR0w=; b=iIXdQ75ds8kMT4VI6FjDu1kb7CLxsvm3JyN4wq4XRC3/hrywfgIIbqZcLbH06sbboo 70e3c8mb5Y7yRnUatrUMvBJSg6hjMq6eOZDW7i3S3fxUl/QvnPaj+muVy50CT7luXRSw sK9jDjKDM1WGf/R1JfvhABzQ/KTcQ0IiEtVv0jH9R7GBskxbtaoBSnKWOPYpJnbagZmw gUwIS9VimdSO2K2F7424bqg4w+BhEb5PgPObRYff8rNg5MrJO2Hry4Q4AoiPbWIbJAM4 Nti25oh/dAyV9X5/FOgt85jYpsZLb6czhkurd8o5zUuYzpdSwS2veu22whS1Pf9VAy6Q woLQ==
X-Gm-Message-State: AEkoousknr3x2YTRVR6tilriOQeLkErv7T9jRyOztn8ydgnNTocnLisC71VL+DUllKAbpBBVrT0AC/v+1tI4HQ==
X-Received: by 10.202.4.135 with SMTP id 129mr18528009oie.128.1469697792104; Thu, 28 Jul 2016 02:23:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.14.41 with HTTP; Thu, 28 Jul 2016 02:23:11 -0700 (PDT)
In-Reply-To: <CAAZxfpfcgxPzDeQjE9i_Wure5u2LnQo8vKtwjNgJB1UUdwLDXQ@mail.gmail.com>
References: <CAAZxfpfcgxPzDeQjE9i_Wure5u2LnQo8vKtwjNgJB1UUdwLDXQ@mail.gmail.com>
From: Pradeep Kumar <pradeepkumar143@gmail.com>
Date: Thu, 28 Jul 2016 14:53:11 +0530
Message-ID: <CAAZxfpfd=ToGmRXWNDU4NzFUCCu26Re=eiu6Sj1afipWQGGqUQ@mail.gmail.com>
To: sigtran@ietf.org
Content-Type: multipart/alternative; boundary="001a11c03308d398bf0538aeaea1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/HcLUCItf2zFn6M8dSmjfwKHNer8>
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
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 09:23:15 -0000
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,”* 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? +++++++++++++++++++ Regards, Pradeep Kumar On Tue, Jul 26, 2016 at 6:33 PM, Pradeep Kumar <pradeepkumar143@gmail.com> wrote: > 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.”* > >
- Re: [Sigtran] Query regarding capacity of sigtran… Brian F. G. Bidulock
- Re: [Sigtran] Query regarding capacity of sigtran… Abhishek Bhatt
- Re: [Sigtran] Query regarding capacity of sigtran… David Laight
- [Sigtran] Query regarding capacity of sigtran link Abhishek Bhatt
- [Sigtran] Query regarding the sequence message de… Pradeep4 Kumar
- Re: [Sigtran] Query regarding the sequence messag… Brian F. G. Bidulock
- Re: [Sigtran] Query regarding the sequence messag… Pradeep Kumar
- [Sigtran] Query regarding the sequence message de… Pradeep Kumar