Re: [Sigtran] M3UA: Synchronizing DPC availability state between ASPs in the same AS
"Brian F. G. Bidulock" <bidulock@openss7.com> Mon, 10 April 2017 19:41 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 5A19D129A9C for <sigtran@ietfa.amsl.com>; Mon, 10 Apr 2017 12:41:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.801
X-Spam-Level:
X-Spam-Status: No, score=-2.801 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] 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 zkx41jSrCflv for <sigtran@ietfa.amsl.com>; Mon, 10 Apr 2017 12:41:23 -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 36C36129532 for <sigtran@ietf.org>; Mon, 10 Apr 2017 12:41:22 -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 v3AJfJVM020059; Mon, 10 Apr 2017 13:41:20 -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 v3AJfJ3w030753; Mon, 10 Apr 2017 13:41:19 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id v3AJfJpK030752; Mon, 10 Apr 2017 13:41:19 -0600
Date: Mon, 10 Apr 2017 13:41:19 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.com>
To: Dan Gora <dan.gora@gmail.com>
Cc: sigtran@ietf.org
Message-ID: <20170410194119.GA30425@openss7.org>
Reply-To: bidulock@openss7.com
Mail-Followup-To: Dan Gora <dan.gora@gmail.com>, sigtran@ietf.org
References: <CAGyogRamDgU7fhwfS1rgQC19-vrxsjc-uZvQGwx0wpKB846zKA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAGyogRamDgU7fhwfS1rgQC19-vrxsjc-uZvQGwx0wpKB846zKA@mail.gmail.com>
Organization: http://www.openss7.org/
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/SkKqjDJXwe4hATV6Htz_WvA3Fww>
Subject: Re: [Sigtran] M3UA: Synchronizing DPC availability state between ASPs in the same AS
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 10 Apr 2017 19:41:25 -0000
Dan, When an SG sends DUNA, DAVA, DRST, SCON for an AS, we had long discussions and agreed that it was sufficient that the SG sends the indication to at least one ASP active for the AS with the SG. Even so, many SG vendors send the indication to _every_ ASP active for the AS. Multiple M3UA associations between SG and AS can be viewed as links in a linkset, and, following the analogy, an STP will only send TFP, TFA, etc. on one link in the linkset. However, this was never really the case for DAUD. DAUD is sent from ASP to SGP not from AS to SG. For periodic DAUD, the recommendation is that the DAUD be sent from an ASP to the SGP that send the corresponding DUNA, DAVA, DRST, SCON. For MTP Restart procedure, the recommendation was that the SGP send DUNA, DAVA, DRST, SCON after receiving the ASP Active and before sending the ASP Active Ack, so that the ASP will not send traffic to unavailable destinations when it becomes active. So, yes and no, you may have to correlate the receipt of DUNA, DAVA, DRST, SCON at any ASP across all ASPs active for the AS (if the SG does not broadcast); however, you should never have to do so in response to DAUD. -- Brian F. G. Bidulock bidulock@openss7.com http://www.openss7.com/
- [Sigtran] M3UA: Synchronizing DPC availability st… Dan Gora
- Re: [Sigtran] M3UA: Synchronizing DPC availabilit… David Laight
- Re: [Sigtran] M3UA: Synchronizing DPC availabilit… Brian F. G. Bidulock
- Re: [Sigtran] M3UA: Synchronizing DPC availabilit… Brian F. G. Bidulock
- Re: [Sigtran] M3UA: Synchronizing DPC availabilit… Dan Gora
- Re: [Sigtran] M3UA: Synchronizing DPC availabilit… Brian F. G. Bidulock
- Re: [Sigtran] M3UA: Synchronizing DPC availabilit… Dan Gora