Re: [Sigtran] M3UA: SCON: congestion condition never abates
"Brian F. G. Bidulock" <bidulock@openss7.org> Tue, 23 October 2012 22:20 UTC
Return-Path: <bidulock@openss7.org>
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 E6EB71F0C95 for <sigtran@ietfa.amsl.com>; Tue, 23 Oct 2012 15:20:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.222
X-Spam-Level:
X-Spam-Status: No, score=-5.222 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_MED=-4, RCVD_IN_SORBS_DUL=0.877]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2NXo3eJHB+r0 for <sigtran@ietfa.amsl.com>; Tue, 23 Oct 2012 15:20:09 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) by ietfa.amsl.com (Postfix) with ESMTP id 0F9D411E80A3 for <sigtran@ietf.org>; Tue, 23 Oct 2012 15:20:06 -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 q9NMJvkC025389; Tue, 23 Oct 2012 16:19:58 -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 q9NMJvQd025238; Tue, 23 Oct 2012 16:19:57 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id q9NMJveF025237; Tue, 23 Oct 2012 16:19:57 -0600
Date: Tue, 23 Oct 2012 16:19:57 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: David Laight <David.Laight@ACULAB.COM>
Message-ID: <20121023221957.GA25013@openss7.org>
Mail-Followup-To: David Laight <David.Laight@ACULAB.COM>, urte plesske <uplesske@hotmail.com>, sigtran@ietf.org
References: <COL121-W23F22A9E026C4B6D0C3F4CD790@phx.gbl> <AE90C24D6B3A694183C094C60CF0A2F6026B705C@saturn3.aculab.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6026B705C@saturn3.aculab.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: SCON: congestion condition never abates
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: bidulock@openss7.org
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: <http://www.ietf.org/mail-archive/web/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, 23 Oct 2012 22:20:12 -0000
David, SCON(0) is a valid message indicating "No congestion" for networks the implement multiple congestion levels. SCON messages for international method do not include a congestion level parameter. In international networks, congestion abatement is signalled in response to DAUD with a DAVA not preceded by a SCON. There is an implementation note undef RFC4666/3.4.4 that indicates that an M3UA may maintain a timer to control congestion notification vality that will be useful in cases where the peer node fails to indicate congestion abatement. There is also a note undef RFC4666/4.5.3 ASP Auditing that states that periodic DAUD should not be initiated in response to SCON(0) (i.e. multiple congestion level network signalling congestion abatement). --brian David Laight wrote: (Tue, 23 Oct 2012 16:21:38) > I presume this is (supposed to be) M3UA? > > M3UA is an abstraction of the interface between MTP3 and its userparts > (typically SCCP and ISUP). > > This means that the `AS' box isn't running MTP3, so your descriptions > about routing are incorrect. > > > The M3UA SCON indication is telling the userpart that MTP3 received a > TFC for the route. > > This could be used by the userpart to reduce its traffic. > > There is no network message that indicates that congestion has ceased. > > IIRC M3UA also doesn't contain any such message. > > The `congestion level' will be 1, 2 or 3 in ansi networks, and always 0 > in ITU networks. > > > David > -- Brian F. G. Bidulock bidulock@openss7.org http://www.openss7.org/
- [Sigtran] M3UA: SCON: congestion condition never … urte plesske
- Re: [Sigtran] M3UA: SCON: congestion condition ne… Nemana, Satya
- Re: [Sigtran] M3UA: SCON: congestion condition ne… Brian F. G. Bidulock
- Re: [Sigtran] M3UA: SCON: congestion condition ne… Brian F. G. Bidulock
- Re: [Sigtran] M3UA: SCON: congestion condition ne… David Laight
- Re: [Sigtran] M3UA: SCON: congestion condition ne… Brian F. G. Bidulock
- Re: [Sigtran] M3UA: SCON: congestion condition ne… Brian F. G. Bidulock
- Re: [Sigtran] M3UA: SCON: congestion condition ne… Brian F. G. Bidulock