Re: [Dime] Call for WG adoption: draft-jones-diameter-group-signaling-01

Tina TSOU <Tina.Tsou.Zouting@huawei.com> Wed, 04 April 2012 23:46 UTC

Return-Path: <Tina.Tsou.Zouting@huawei.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9849411E811C for <dime@ietfa.amsl.com>; Wed, 4 Apr 2012 16:46:54 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FZDjrjFeEC5J for <dime@ietfa.amsl.com>; Wed, 4 Apr 2012 16:46:54 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id F366111E80FE for <dime@ietf.org>; Wed, 4 Apr 2012 16:46:53 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AER00443; Wed, 04 Apr 2012 19:46:53 -0400 (EDT)
Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 4 Apr 2012 16:41:33 -0700
Received: from SZXEML424-HUB.china.huawei.com (10.82.67.163) by dfweml404-hub.china.huawei.com (10.193.5.203) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 4 Apr 2012 16:41:31 -0700
Received: from SZXEML526-MBX.china.huawei.com ([169.254.2.214]) by szxeml424-hub.china.huawei.com ([10.82.67.163]) with mapi id 14.01.0323.003; Thu, 5 Apr 2012 07:41:27 +0800
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: jouni korhonen <jouni.nospam@gmail.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] Call for WG adoption: draft-jones-diameter-group-signaling-01
Thread-Index: AQHNEDyF4CFv35exeUKXaSyq14pyOpaLVqMg
Date: Wed, 04 Apr 2012 23:41:26 +0000
Message-ID: <C0E0A32284495243BDE0AC8A066631A80C92195F@szxeml526-mbx.china.huawei.com>
References: <4C639074-1D3C-44E8-B2EB-D602681818A4@gmail.com>
In-Reply-To: <4C639074-1D3C-44E8-B2EB-D602681818A4@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.193.34.143]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "dime-chairs@tools.ietf.org" <dime-chairs@tools.ietf.org>
Subject: Re: [Dime] Call for WG adoption: draft-jones-diameter-group-signaling-01
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Apr 2012 23:46:54 -0000

Hi Jouni and Mark,
The problem statement is valid and the solution can work in basic scenarios. 
   
However the solution may have some limit in roaming scenario.
 
Consider a network having a WLAN AN (hosting a Diameter Client) requesting some 3G internet resources, visited network proxies and home network server as below:
 
Client -------------- <Visited n/w proxy 1> ---------- {Home network server}
         -------------- <Visited n/w proxy 2> ----------{Home network server}

The session path can be established through either of the visited n/w proxies. For all the messages of same session, client can ensure that the session path through stateful nodes is maintained. The visited n/w proxies would require that the session path be maintained for offline charging etc.
In this scenario, if client uses group signalling method to terminate all sessions in a group using GSTR, only the proxy in the GSTR-GSTA path will be aware of session termination. Since there are no follow-up messages, there is no mechanism to let the other proxy know that the sessions are terminated.
This problem can be avoided in Server initiated group signalling cases (GRAR & GASR) as the PER_SESSION mode can be used for follow up exchanges.
Thus the current solution has a limit if client uses group signalling method for session termination in roaming cases.

I volunteer to work together with Mark to find a solution for this case.

I'm NOT aware of any IPR in this area.


Tina


> -----Original Message-----
> From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf Of
> jouni korhonen
> Sent: Sunday, April 01, 2012 12:20 PM
> To: dime@ietf.org
> Cc: dime-chairs@tools.ietf.org
> Subject: [Dime] Call for WG adoption: draft-jones-diameter-group-
> signaling-01
> 
> 
> Folks,
> 
> During the Dime WG meeting in Paris we decided to adopt draft-jones-
> diameter-group-signaling-01
> "Diameter Group Signaling" as a working group I-D. The I-D is an input for
> the charter mile stone 'Protocol extension for bulk and group signaling'.
> 
> This mail starts a one week verification for the adoption. If you have
> strong concerns that the
> draft-jones-diameter-group-signaling-01 is not appropriate as a _basis_
> for the solution, then express your concerns on the mailing list by 8th
> April.
> 
> - Jouni & Lionel
> 
> 
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime