
From nobody Fri Apr  7 21:48:33 2017
Return-Path: <dan.gora@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 DD3DF1270A3 for <sigtran@ietfa.amsl.com>; Fri,  7 Apr 2017 21:48:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 E3J9obpokZk4 for <sigtran@ietfa.amsl.com>; Fri,  7 Apr 2017 21:48:29 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 11BD81293EC for <sigtran@ietf.org>; Fri,  7 Apr 2017 21:48:29 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id u2so4657587wmu.0 for <sigtran@ietf.org>; Fri, 07 Apr 2017 21:48:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=Qv7Q2Z020Q65Hxv58QLugTGEuHmOrgGXTI5dHG1pz7s=; b=LmtQMVOvXC8e5zoUeciM2jSrcZTsiDFG8vcApHEt99tPx99YpZN9cJiB8Zpr25Syfx 1D9sjhggRpkRscPPCdO3aUo5NJq5UbboIYyeGJhhdMZ14QGjFSX8Z+7jh8eHfdAdnZQv y+A6lV3SzxquftNpXdXf1qrQ3k6qD57g6+SnwfkQ7DI1ksrX7U+DAte7OAjHw19K8ygJ zQfO99SrYgNq+/4JyPPGwok/oKuPxCUw71I2LdhfoPUB5b/B5FalB0rrcU4KM1axvlTS 7ATLdiedLZGi0yL73Lgnxa1/aypWklJLjUTJhzDMtYtmETgLtXWBp5jHLoYytaJmXe60 bkYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Qv7Q2Z020Q65Hxv58QLugTGEuHmOrgGXTI5dHG1pz7s=; b=EPqqZkVZk+UcfgMpk7SW/+O/3TQtVUBofWFuMN03yKYsjKhgBiMfftedz1OM2YSO/P 2BepS17ehTDzBGXj3axVr+VT47irLtu8GzlK9Na6Ite5uEazWSbyM+e3N77qzMFycjLq UXder0xXliIx6S7s4GMqFeAjN0NsxAi10Ax7HHLC7zphzPC3o3gYhAxk4fHeAHa8H4Fu Ib4ltIBrjuXtyz0OwiiYHNOmN4v7EoEYnZnrQn2jp3evCV4Kft57MhE3eBF7N40n4tj8 /EFI6W7RFyTLOKVurtiotogAI9xtGtdHv3+iqdVtCHhXbvvHXh6q/5FSpMkvoEdTmvw4 bbmQ==
X-Gm-Message-State: AN3rC/6bLt/KUOVl5qDiUeH+lPqwz/BRwIXh5Y6wuWRcukiegWP/izq4 ALkyzj59oLq9jcx858WCYO32wCjHJkQJ
X-Received: by 10.28.66.207 with SMTP id k76mr1953991wmi.121.1491626907328; Fri, 07 Apr 2017 21:48:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.175.212 with HTTP; Fri, 7 Apr 2017 21:47:46 -0700 (PDT)
From: Dan Gora <dan.gora@gmail.com>
Date: Sat, 8 Apr 2017 01:47:46 -0300
Message-ID: <CAGyogRamDgU7fhwfS1rgQC19-vrxsjc-uZvQGwx0wpKB846zKA@mail.gmail.com>
To: sigtran@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/d46a7P58bvccv0H3XqtSqfXAEGY>
Subject: [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: Sat, 08 Apr 2017 04:48:32 -0000

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:

   The SGP M3UA layer determines the set of concerned ASPs to be
   informed based on the specific SS7 network for which the primitive
   indication is relevant.  In this way, all ASPs configured to
   send/receive traffic within a particular Network Appearance
   are informed.  If the SGP operates within a single SS7 Network
   Appearance, then all ASPs are informed.


Also it seems pretty clear from the specification that an ASP can
send a DAUD pretty much any time it wants and I've never seen anything
where a message can be "responded to" via a different association (ie
a different ASP).  There is certainly no description of any mechanism
by which sending DAUD has to be coordinated among the ASPs in an AS.

On the other hand...

I cannot find anything definitive about this.

Reading through the mailing list archives
there are notions where "SSNM messages are "per-AS""
(https://www.ietf.org/mail-archive/web/sigtran/current/msg00725.html)
and there is also the "philosophical" notion that an AS is the SAP
though which an MTP3 User accesses the MTP3 network and in this case
the AS is serviced via two (distributed) ASPs, which seems to imply
that the ASPs should have a synchronized view of the DPC status.

So, what should I think about this?  Are we required to synchronize
the destination state for an AS across all the ASPs automatically
(ie by sending a DAUD or receiving a DAVA/DUNA on only one ASP in
the group of ASPs serving this AS)?  If so, where does this appear
(or is even implied) in the spec?

Can I definitely tell the customer that either the SG is totally
broken or else something is misconfigured?

What might possibly be misconfigured to cause the SG to behave this
way? (I realize that this is totally a shot in the dark, we are
supposedly getting more information from the customer...)

Any tips would be most welcome.

thanks,
dan


From nobody Mon Apr 10 01:38:44 2017
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
=20
> Hi All,
>=20
> 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:
>=20
> SG1       AS1
> ---      -----
> SGP1 --- ASP 1
>      +-- ASP 2
>=20
> 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.
>=20
> 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.
>=20
> 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


From dan.gora@gmail.com  Fri Apr  7 21:43:09 2017
Return-Path: <dan.gora@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 C77E6129483 for <sigtran@ietfa.amsl.com>; Fri,  7 Apr 2017 21:43:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 SBNVMFsJ1VYM for <sigtran@ietfa.amsl.com>; Fri,  7 Apr 2017 21:43:07 -0700 (PDT)
Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (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 5E946129451 for <sigtran@ietf.org>; Fri,  7 Apr 2017 21:43:07 -0700 (PDT)
Received: by mail-wr0-x231.google.com with SMTP id c55so46166567wrc.3 for <sigtran@ietf.org>; Fri, 07 Apr 2017 21:43:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=Qv7Q2Z020Q65Hxv58QLugTGEuHmOrgGXTI5dHG1pz7s=; b=kRb2le0eoqTS8NkCXxNUF73ybqVV43CdV8KsOobGy0FFa4aCjGFMSOUZktF81eO1g3 cynBD4rafyELfAnymIG+21XQXRR2xfAECRNGoKh9Nzfp9/eVND1WYyP6s8IBMymKV3zg BjexHP5ITUsyv31JRBd9GkUJQtf+L8Wkp/t7fcfxO/ugndr+/pLSs+AyKE0PqZsdEGvz vCUe0OKCluc+wK1bMpCvItoq0+CPVWRu3yAiB2DKIQX+g1heZi9RKbEI9bC+RWrkNQ3z UkyLZsoo5IfrmIGHP26WjapCekW9CELP1mVoPe7CsuY3OBikABFlE+vLQdK743Jd92DT PMZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Qv7Q2Z020Q65Hxv58QLugTGEuHmOrgGXTI5dHG1pz7s=; b=U/xtQnGCcJkiJdpCtuGpsxBvg6DKjqBPUpWKo7m//KY07giatbiLvmegni/DNrTC7V eqfWJT/J7OJ6wqSSzduJfshmDxuu+ADbdbCh6k7KeEyBV6GZuKVD+Cuj7uSw6IK6vWd5 bGzMetAsQ4wXSrFmVv/RbklwOp9L49j5CfJVTg57VjzEoo09UBKebhzJCBx9J9Tm/h0+ dDhqJTBW+94iQ6R+wRbe/P8U3ZkoE30kMEUp6C2VR6x16n953zqQhsYJIMMe7qupWJ4O XB1BcyUouMkqlpRo44+O9pf6/DTF+3dyPFiyTU8z1sjvJCV8UN2lXqyFi6+9QJpuYKPK H+ZA==
X-Gm-Message-State: AN3rC/56z78UA8fAx9zT/EigoiCXhUtBSHQBRTPOq2GjT5T22CGbppTPRa5RoszI/QholuR9t63sQFJSl7LWuw==
X-Received: by 10.223.182.155 with SMTP id j27mr666839wre.152.1491626585682; Fri, 07 Apr 2017 21:43:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.175.212 with HTTP; Fri, 7 Apr 2017 21:42:25 -0700 (PDT)
From: Dan Gora <dan.gora@gmail.com>
Date: Sat, 8 Apr 2017 01:42:25 -0300
Message-ID: <CAGyogRaee9yuT8geSBPfPkWoyntQRtsftXZnrtTcQrXb_Qxr1A@mail.gmail.com>
To: sigtran@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/GmNcxy2YWVs8b_3BIE_vfdMb-mc>
X-Mailman-Approved-At: Mon, 10 Apr 2017 08:21:22 -0700
Subject: [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: Sat, 08 Apr 2017 04:45:10 -0000

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:

   The SGP M3UA layer determines the set of concerned ASPs to be
   informed based on the specific SS7 network for which the primitive
   indication is relevant.  In this way, all ASPs configured to
   send/receive traffic within a particular Network Appearance
   are informed.  If the SGP operates within a single SS7 Network
   Appearance, then all ASPs are informed.


Also it seems pretty clear from the specification that an ASP can
send a DAUD pretty much any time it wants and I've never seen anything
where a message can be "responded to" via a different association (ie
a different ASP).  There is certainly no description of any mechanism
by which sending DAUD has to be coordinated among the ASPs in an AS.

On the other hand...

I cannot find anything definitive about this.

Reading through the mailing list archives
there are notions where "SSNM messages are "per-AS""
(https://www.ietf.org/mail-archive/web/sigtran/current/msg00725.html)
and there is also the "philosophical" notion that an AS is the SAP
though which an MTP3 User accesses the MTP3 network and in this case
the AS is serviced via two (distributed) ASPs, which seems to imply
that the ASPs should have a synchronized view of the DPC status.

So, what should I think about this?  Are we required to synchronize
the destination state for an AS across all the ASPs automatically
(ie by sending a DAUD or receiving a DAVA/DUNA on only one ASP in
the group of ASPs serving this AS)?  If so, where does this appear
(or is even implied) in the spec?

Can I definitely tell the customer that either the SG is totally
broken or else something is misconfigured?

What might possibly be misconfigured to cause the SG to behave this
way? (I realize that this is totally a shot in the dark, we are
supposedly getting more information from the customer...)

Any tips would be most welcome.

thanks,
dan


From nobody Mon Apr 10 11:56:42 2017
Return-Path: <dan.gora@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 3CA28127369 for <sigtran@ietfa.amsl.com>; Mon, 10 Apr 2017 11:56:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 q1DG3_gzWvPV for <sigtran@ietfa.amsl.com>; Mon, 10 Apr 2017 11:56:38 -0700 (PDT)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 028B1127076 for <sigtran@ietf.org>; Mon, 10 Apr 2017 11:56:38 -0700 (PDT)
Received: by mail-wm0-x22b.google.com with SMTP id o81so46388039wmb.1 for <sigtran@ietf.org>; Mon, 10 Apr 2017 11:56:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=C0tSAIA+kFF10OjRMfTDwDj2ldFpZbVA2zgKFWOc0NM=; b=ShKmbherVHghGXZb3ZAn09ggt+5Y57coWF4N4yNXqkIi6jEBX63LyBu+rlTjYi2Xkd IZBbt1hiZpQFDEtiLebaiCe9hJleAhKV/0cgJmMJ8Zig5Nmqg9oxr6vbCk0cS9MCyF6w vZXrdICB4WQbfKy+2foqXPq4GhFsvs+GIAOwaB+pH/xWgl3J4qtRkbpQ6Vns+jrTv2D3 loYFbVV2RL1gmctY0RuYOtbfsB9qjIBzathx/pVMsrgew5SES6+lez2/HjcapnIE8pdr fa5W8U5HFZ3X3yyDLNkmkvg4F+XHsFPlpAT+ObQiwtMjOoKfwu5WFpe6dAGgEbFMVAhd WWGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=C0tSAIA+kFF10OjRMfTDwDj2ldFpZbVA2zgKFWOc0NM=; b=I2m9XmaZcZ8c8cZ1TraL5AG4Zo+4eP424STRz1tvaouvpGf0h2Uju/Mqe+0B5S18IT N9kRV+ZIcIne1tLjLbOGW5zvRpcHON1Ciaal0NP/WHwqFktcgw5AWMcKp+8AzRo0b0cK Iivpzd6/eylVm3tM8gQCOZ6vggt+cx42TxO78cn9HiBu97Qy1kUolgijdAvCxGMLxVWi LhYUCZyaifbMsHBWhJOPa1sI4egTR2uk/PZD6/5/kQwF1hvlOw3VaXVfoO1poksa7J8u /uVfHZn3Dwge7xEF+Foe8n4J9+UCF+/3aHyC45f/Gxw4d41isKifAcZdJR+roUio7Y6e w3Sg==
X-Gm-Message-State: AN3rC/7XUbQJ84m0dkEY2/nwDUQfp5Owi11CPfqMiCCf39UJ7yDkT9IVYxbUPvybHgj1C+a4q4TzRRdsfgi1gg==
X-Received: by 10.28.234.84 with SMTP id i81mr10857421wmh.80.1491850596505; Mon, 10 Apr 2017 11:56:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.175.212 with HTTP; Mon, 10 Apr 2017 11:55:55 -0700 (PDT)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6DCFFCA61F@AcuExch.aculab.com>
References: <CAGyogRamDgU7fhwfS1rgQC19-vrxsjc-uZvQGwx0wpKB846zKA@mail.gmail.com> <063D6719AE5E284EB5DD2968C1650D6DCFFCA61F@AcuExch.aculab.com>
From: Dan Gora <dan.gora@gmail.com>
Date: Mon, 10 Apr 2017 15:55:55 -0300
Message-ID: <CAGyogRZWziokZbixJyRAY1+Mv=6Q+sKordV-ag4p=gG0tCHqig@mail.gmail.com>
To: David Laight <David.Laight@aculab.com>
Cc: "sigtran@ietf.org" <sigtran@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/YPdRC0YN-Af7dS6doTOpL4MEj2o>
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 18:56:40 -0000

Hi David,

Thanks for your response...

On Mon, Apr 10, 2017 at 5:38 AM, David Laight <David.Laight@aculab.com> wrote:
>> 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.

Is it?  The only difference I can see in rfc 4666 in section 4.5.1 is
the addition of this paragraph:

   For the particular case that an ASP becomes active for an AS and
   destinations normally accessible to the AS are inaccessible,
   restricted, or congested, the SG MAY send DUNA, DRST, or SCON
   messages for the inaccessible, restricted, or congested destinations
   to the ASP newly active for the AS to prevent the ASP from sending
   traffic for destinations that it might not otherwise know that are
   inaccessible, restricted, or congested.  For the newly activating ASP
   from which the SGP has received an ASP Active message, these DUNA,
   DRST, and SCON messages MAY be sent before sending the ASP Active Ack
   that completes the activation procedure.

But RFC 3332 still doesn't really clearly state that the ASPs have to
synchronize their destination state within an AS.  On the contrary,
from 4.5.1 it still seems to imply that the SGP has to send DAVA/DUNA,
etc to _all_ "concerned" ASPs, not just one in an AS.

> 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.

What missing indications are you referring to?  The missing NTFY
messages for the AS (section 5.1.1.1, etc..)?

thanks,
dan


From nobody Mon Apr 10 12:41:27 2017
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/


From nobody Mon Apr 10 12:51:10 2017
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 A8A88129532 for <sigtran@ietfa.amsl.com>; Mon, 10 Apr 2017 12:51:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 nphcbSlM7oPk for <sigtran@ietfa.amsl.com>; Mon, 10 Apr 2017 12:51:07 -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 3506F1270A0 for <sigtran@ietf.org>; Mon, 10 Apr 2017 12:51:07 -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 v3AJp5JE020089; Mon, 10 Apr 2017 13:51:05 -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 v3AJp4RP030995; Mon, 10 Apr 2017 13:51:04 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id v3AJp4AA030994; Mon, 10 Apr 2017 13:51:04 -0600
Date: Mon, 10 Apr 2017 13:51:04 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.com>
To: Dan Gora <dan.gora@gmail.com>, sigtran@ietf.org
Message-ID: <20170410195104.GA30907@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> <20170410194119.GA30425@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170410194119.GA30425@openss7.org>
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/T-uc8cJ44y4s-46uTpu5U4oE9VU>
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:51:09 -0000

Dan,

Brian F. G. Bidulock wrote:       (Mon, 10 Apr 2017 13:41:19)
> 
> 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.
> 

See, for example, RFC 4666/5.4 Auditing Examples.  You
will see that all transactions are between ASP and SGP,
not between AS and SG.

-- 
Brian F. G. Bidulock
bidulock@openss7.com
http://www.openss7.com/


From nobody Mon Apr 10 13:00:57 2017
Return-Path: <dan.gora@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 E329F129AD2 for <sigtran@ietfa.amsl.com>; Mon, 10 Apr 2017 13:00:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 jSlP6pkGF6kk for <sigtran@ietfa.amsl.com>; Mon, 10 Apr 2017 13:00:54 -0700 (PDT)
Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::22f]) (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 3318F129AB7 for <sigtran@ietf.org>; Mon, 10 Apr 2017 13:00:54 -0700 (PDT)
Received: by mail-wr0-x22f.google.com with SMTP id z109so16034949wrb.1 for <sigtran@ietf.org>; Mon, 10 Apr 2017 13:00:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=hMP/deQ2BB+LMyxFYv3HB68GgerTBUPkGj0CrrAvSx4=; b=ELNB1x8MS8WTyiaT3JZnhHfF3lWjETd3GzA0/P6vHHi4FCkF3RKhl7tQWVeIS/Eahk 8XeLbAYpsYQUueRAFaCi8LUwYu5XSNzMSAVfpTcZyb7vJCu5e+uGMs5k5tClbrHS/+fA zS2L0u2t/+P/Jxhgrp/hiqRpqV6UVWUSLZs/SFknvZqqWEu9q4Q4UhapHG+9bcYF/0OW cWjshhHnIcnpIxwZF4QKvcnV0du/lT9ZstxvWPnUdWq2S0rc1qFuBO7xqv/YYOQG35oM ZUxL4pOoEuv9ruPMueqg/psTpDKLwEE/ZNR5g+gPdtQUCjnDcY0U522KcQ0QW02GboMT e4jw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=hMP/deQ2BB+LMyxFYv3HB68GgerTBUPkGj0CrrAvSx4=; b=YhNwE0NFLj7M09sBrFsZczMclAMwN3/ghU50pgN6tnkeWbwnlh8DBGb4QdDGwpZ0aA j40SLfMi0hn0ULi77SweO8avYveQziuEPAbMoW2tIiZK3jGl7KC8yGeJCsh5fP5NuLiY J5y9ldM/7hg1IS1XR7+xJqLxEtSxNos/9qbKg+DreRi62uI5xlybHGcnSci67xT2Y2ty M0xrxpq633KJAeekxhD2IHqvK9OQ+/f3obmfEfow3ddDsSBHo/ZnL58pEQVj39DLix+i XYv9ocH2gDa3ulv9tJND32QWQVB6ut+dTT74gW564aBuEWbVPnpIbqALWw2J6Cc4th3m S8Mg==
X-Gm-Message-State: AN3rC/6xixC1X/qAKYn/RyH1k2N94P2dSVr6DIQRFexAc4wyn9bVgOzZ3/gpZCXa1SEINgyWr+AF8jol1JArOQ==
X-Received: by 10.223.182.155 with SMTP id j27mr10487549wre.152.1491854452715;  Mon, 10 Apr 2017 13:00:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.175.212 with HTTP; Mon, 10 Apr 2017 13:00:12 -0700 (PDT)
In-Reply-To: <20170410195104.GA30907@openss7.org>
References: <CAGyogRamDgU7fhwfS1rgQC19-vrxsjc-uZvQGwx0wpKB846zKA@mail.gmail.com> <20170410194119.GA30425@openss7.org> <20170410195104.GA30907@openss7.org>
From: Dan Gora <dan.gora@gmail.com>
Date: Mon, 10 Apr 2017 17:00:12 -0300
Message-ID: <CAGyogRZvaPevoocFE52NzW-6sL_Zhx9UkHe005V_LtrQs3+GKA@mail.gmail.com>
To: bidulock@openss7.com, Dan Gora <dan.gora@gmail.com>, sigtran@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/0BzAF8y80j6GLgwNSi4Ed2dXB7U>
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 20:00:56 -0000

On Mon, Apr 10, 2017 at 4:51 PM, Brian F. G. Bidulock
<bidulock@openss7.com> wrote:
> Dan,
>
> Brian F. G. Bidulock wrote:       (Mon, 10 Apr 2017 13:41:19)
>>
>> 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.
>>
>
> See, for example, RFC 4666/5.4 Auditing Examples.  You
> will see that all transactions are between ASP and SGP,
> not between AS and SG.

Right... This is what led me to believe that we didn't have to
synchronize the DPC states (and various conversions on the mailing
list), but then again your description of considering ASPs in the same
AS connected to the same SG as links in a linkset is what made be
think that yes, we do need to synchronize the DPC states.

However, this customer's SG seems to be even worse in that it's
replying to a DAUD from ASP2 with a DAVA/DUNA to ASP1, _not_ ASP2 (or
so they say, we still haven't been provided with traces or debug logs
yet..).  That just seems broken to me..

If we have to "fix" this, it seems like it should be safe to
synchronize the states across all the active ASPs.  I cannot think of
a scenario where a DPC would be available in ASP 1 via SG1, but not
via ASP2 as long as both are connected and ASP-Active with the SG1
since the SG1 has to synchronize it's state among all the SGPs in the
SG.  Right?

thanks
dan


From nobody Mon Apr 10 13:09:40 2017
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 CC586129AE0 for <sigtran@ietfa.amsl.com>; Mon, 10 Apr 2017 13:09:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 1fAHvdFZR5DX for <sigtran@ietfa.amsl.com>; Mon, 10 Apr 2017 13:09:37 -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 5F027129AD2 for <sigtran@ietf.org>; Mon, 10 Apr 2017 13:09:35 -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 v3AK9X77020171; Mon, 10 Apr 2017 14:09:33 -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 v3AK9Xew031329; Mon, 10 Apr 2017 14:09:33 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id v3AK9WXg031328; Mon, 10 Apr 2017 14:09:32 -0600
Date: Mon, 10 Apr 2017 14:09:32 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.com>
To: Dan Gora <dan.gora@gmail.com>
Cc: bidulock@openss7.com, sigtran@ietf.org
Message-ID: <20170410200932.GB30907@openss7.org>
Reply-To: bidulock@openss7.com
Mail-Followup-To: Dan Gora <dan.gora@gmail.com>, bidulock@openss7.com, sigtran@ietf.org
References: <CAGyogRamDgU7fhwfS1rgQC19-vrxsjc-uZvQGwx0wpKB846zKA@mail.gmail.com> <20170410194119.GA30425@openss7.org> <20170410195104.GA30907@openss7.org> <CAGyogRZvaPevoocFE52NzW-6sL_Zhx9UkHe005V_LtrQs3+GKA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAGyogRZvaPevoocFE52NzW-6sL_Zhx9UkHe005V_LtrQs3+GKA@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/UG1BJgyt0OxT98mj_pT_uIl4MmY>
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 20:09:39 -0000

Dan,

Please see comments below...

Dan Gora wrote:                    (Mon, 10 Apr 2017 17:00:12)
> 
> If we have to "fix" this, it seems like it should be safe to
> synchronize the states across all the active ASPs.  I cannot think of
> a scenario where a DPC would be available in ASP 1 via SG1, but not
> via ASP2 as long as both are connected and ASP-Active with the SG1
> since the SG1 has to synchronize it's state among all the SGPs in the
> SG.  Right?

Well, no.  We considered that an SG with multiple SGP might get
one or more SGPs partitioned from the others, and potentially
isolated from the network.  Although they are isolated, their
M3UA connections to the ASPs in the AS are still viable and
the unsolicited ASP Inactive Ack procedure might not be
necessary.  In that case, some SGP might send DUNA(*) while the
others still have available routes.  This was a major reason
for sending periodic DAUD to the SGP that sent the corresponding
DUNA, DRST, SCON.

-- 
Brian F. G. Bidulock
bidulock@openss7.com
http://www.openss7.com/

