Re: [Sigtran] [M3UA] DAUD message RC

"Brian F. G. Bidulock" <bidulock@openss7.org> Wed, 27 April 2011 10:55 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 DA7B2E06EC for <sigtran@ietfa.amsl.com>; Wed, 27 Apr 2011 03:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 lvRS+U-PFOxr for <sigtran@ietfa.amsl.com>; Wed, 27 Apr 2011 03:55:35 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [206.75.119.236]) by ietfa.amsl.com (Postfix) with ESMTP id 1E209E06B0 for <sigtran@ietf.org>; Wed, 27 Apr 2011 03:55:34 -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 p3RAsFDL021747; Wed, 27 Apr 2011 04:54:15 -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 p3RAsFNg009586; Wed, 27 Apr 2011 04:54:15 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id p3RAsEvw009585; Wed, 27 Apr 2011 04:54:14 -0600
Date: Wed, 27 Apr 2011 04:54:14 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: David Laight <David.Laight@ACULAB.COM>
Message-ID: <20110427105414.GA9096@openss7.org>
Mail-Followup-To: David Laight <David.Laight@ACULAB.COM>, santhana@huawei.com, sigtran@ietf.org
References: <D02F09AE6384491DA74FFA5E85D6766F@china.huawei.com> <AE90C24D6B3A694183C094C60CF0A2F6D8ACFD@saturn3.aculab.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6D8ACFD@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] DAUD message RC
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: Wed, 27 Apr 2011 10:55:40 -0000

David,

There are many instances where an SG would be unable to process
a DAUD message without an RC in it.  Here are a couple:

1. The SG is an STP that provides GWS, EGWS or BGWS and it is
   unable to determine whether a destination is prohibited or
   allowed to an AS without knowing which AS is asking.

2. The SG supports multiple networks (e.g. national and
   international) and cannot know to which network the
   destinations in the DAUD apply without knowing the
   network (indicated by RC) of the requesting AS.

3. The SG provides prioritized routes based on originator and
   the congestion status is different for different AS (because
   they use different routes).  Therefore, the SG does not know
   what SCON status to report unless the requesting AS is
   identified by RC.

4. Two SG are configured as multiple SG as STP in an SS7 network
   supporting "restricted" destinations.  Because the ASP TM
   status can be different for different AS, the restricted
   status depends upon the AS requesting the status.

I could go on...

Because the ASP should not need to know all of the logic in the
SG and in particular when an RC would be absolutely required or
not, it is relieved of this a priori knowledge burden by the
requirement that it always simply identify the AS in the DAUD.
Therefore, where an ASP is configured for multiple AS, it is
required to provide the RC.

--brian


David Laight wrote:                            (Wed, 27 Apr 2011 09:07:20)
>    My interpretation is that the requirement for the RC depends on the
>    actual implemenation
> 
>    of the SGP and the ASP.
> 
>    This has all the appearances of a fudge to make two existing
>    implementations
> 
>    meet the standard.
> 
> 
> 
>    The SGP has the information available to respond to a DUNA without
>    looking
> 
>    at an RC in the message - even when there are multiple RC.
> 
>    (Similarly both the SGP and ASP can process data messages without
>    needing
> 
>    an RC in the message.)
> 
> 
> 
>    So the requirement for an RC in DAUD by the SGP isn't absolute.
> 
> 
> 
>    Similar interpretations apply to the ASP - which may expect any RC be
> 
>    sent back in the DUNA/DAVA response.
> 
> 
> 
>        David
>      __________________________________________________________________
> 
>    From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org] On
>    Behalf Of Santhana
>    Sent: 18 April 2011 10:19
>    To: sigtran@ietf.org
>    Subject: [Sigtran] [M3UA] DAUD message RC
> 
>    Hi all
> 
>                The RFC4666 says that DAUD message format is same as DUNA
>    mesg. Now when an ASP send DAUD message to SGP about some Destinations,
>    does it need to include all the associated RCs of the Destinations
>    which it is Auditing ?
> 
> 
>    Regards
> 
>    +Santhana
> 
>    Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes,
>    MK1 1PT, UK
>    Registration No: 1397386 (Wales)
> 
>     P Please consider the environment and don't print this e-mail unless
>                              you really need to

> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www.ietf.org/mailman/listinfo/sigtran


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