Re: [Sigtran] M3UA: Synchronizing DPC availability state between ASPs in the same AS

David Laight <David.Laight@ACULAB.COM> Mon, 10 April 2017 08:38 UTC

Return-Path: <David.Laight@ACULAB.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 9B374127ABE for <sigtran@ietfa.amsl.com>; Mon, 10 Apr 2017 01:38:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.035
X-Spam-Level:
X-Spam-Status: No, score=-2.035 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, SPF_SOFTFAIL=0.665] 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 KIpqE9IuS27N for <sigtran@ietfa.amsl.com>; Mon, 10 Apr 2017 01:38:41 -0700 (PDT)
Received: from smtp-out6.electric.net (smtp-out6.electric.net [192.162.217.192]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BF5F127698 for <sigtran@ietf.org>; Mon, 10 Apr 2017 01:38:40 -0700 (PDT)
Received: from 1cxUqM-0006IW-Uj by out6b.electric.net with emc1-ok (Exim 4.87) (envelope-from <David.Laight@ACULAB.COM>) id 1cxUqN-0006L7-TB; Mon, 10 Apr 2017 01:38:39 -0700
Received: by emcmailer; Mon, 10 Apr 2017 01:38:39 -0700
Received: from [213.249.233.130] (helo=AcuExch.aculab.com) by out6b.electric.net with esmtps (TLSv1:AES128-SHA:128) (Exim 4.87) (envelope-from <David.Laight@ACULAB.COM>) id 1cxUqM-0006IW-Uj; Mon, 10 Apr 2017 01:38:38 -0700
Received: from ACUEXCH.Aculab.com ([::1]) by AcuExch.aculab.com ([::1]) with mapi id 14.03.0123.003; Mon, 10 Apr 2017 09:38:37 +0100
From: David Laight <David.Laight@ACULAB.COM>
To: 'Dan Gora' <dan.gora@gmail.com>, "sigtran@ietf.org" <sigtran@ietf.org>
Thread-Topic: [Sigtran] M3UA: Synchronizing DPC availability state between ASPs in the same AS
Thread-Index: AQHSsCNlqhJxn1IUnkujzWYFB9KCfaG+StYQ
Date: Mon, 10 Apr 2017 08:38:36 +0000
Message-ID: <063D6719AE5E284EB5DD2968C1650D6DCFFCA61F@AcuExch.aculab.com>
References: <CAGyogRamDgU7fhwfS1rgQC19-vrxsjc-uZvQGwx0wpKB846zKA@mail.gmail.com>
In-Reply-To: <CAGyogRamDgU7fhwfS1rgQC19-vrxsjc-uZvQGwx0wpKB846zKA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.202.99.200]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-IP: 213.249.233.130
X-Env-From: David.Laight@ACULAB.COM
X-Proto: esmtps
X-Revdns:
X-HELO: AcuExch.aculab.com
X-TLS: TLSv1:AES128-SHA:128
X-Authenticated_ID:
X-PolicySMART: 3396946, 3397078
X-Virus-Status: Scanned by VirusSMART (c)
X-Virus-Status: Scanned by VirusSMART (s)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/Ppg0hfJ5JWGb8qixzjYV6qbMTi0>
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 08:38:43 -0000

From: Dan Gora
> Sent: 08 April 2017 05:48
 
> Hi All,
> 
> We have a distributed M3UA implementation with two ASPs on different
> physical hosts servicing a single AS talking to a single SGP in a
> single SG:
> 
> SG1       AS1
> ---      -----
> SGP1 --- ASP 1
>      +-- ASP 2
> 
> It's unknown who the SGP/SG vendor is, but our customer is claiming
> that when we start ASP 1 and ASP 2 that both will enter the ASP-Active
> state with SGP1, then both ASP 1 and ASP 2 will each send a DAUD
> message to SGP1.  However the problem is that the SGP will only reply
> with a DAVA/DUNA to ASP 1.  Subsequent DAUD messages from ASP2 to
> SGP1 are "replied to" by the SGP1 by sending the DAVA/DUNA to ASP
> 1, not ASP 2.  They also claim that this "should be sufficient".
> They also claim that we should not need to send DAUD from ASP 2 at
> all, that we should "coordinate" the DAUD sending so that only one
> ASP sends a DAUD message.
> 
> Now this feels wrong to me.  There is nothing in the spec which
> specifically states that the ASPs have to synchronize the destination
> states between themselves just because they belong to the same AS.
> 
> There is also numerous places (RFC 4666: 3.4.1 (DUNA) and 3.4.2)
> where it says that the DUNA/DAVA message is sent to "all concerned
> ASPs" and in 4.5.1 where it says:
...

This is a difference between rfc 4666 and the older 3332.

AFAICT one major network equipment manufacturer has not updated their
protocol stack to conform to rfc4666.

We've a horrid bodge that detects the missing indications.

	David