Re: [Dime] Review of draft-tsou-dime-base-routing-ext-03.txt

Tina TSOU <tena@huawei.com> Tue, 11 December 2007 09:10 UTC

Return-path: <dime-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J218F-0000X1-2m; Tue, 11 Dec 2007 04:10:27 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J218C-0000Ml-Ur for dime@ietf.org; Tue, 11 Dec 2007 04:10:25 -0500
Received: from szxga02-in.huawei.com ([61.144.161.54]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J218B-0008F7-Au for dime@ietf.org; Tue, 11 Dec 2007 04:10:24 -0500
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JSV0087ONSQ7G@szxga02-in.huawei.com> for dime@ietf.org; Tue, 11 Dec 2007 17:02:51 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JSV005FFNSEIC@szxga02-in.huawei.com> for dime@ietf.org; Tue, 11 Dec 2007 17:02:50 +0800 (CST)
Received: from z24109b ([10.70.76.84]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0JSV0099WNSEI2@szxml04-in.huawei.com> for dime@ietf.org; Tue, 11 Dec 2007 17:02:38 +0800 (CST)
Date: Tue, 11 Dec 2007 17:02:38 +0800
From: Tina TSOU <tena@huawei.com>
Subject: Re: [Dime] Review of draft-tsou-dime-base-routing-ext-03.txt
To: Glen Zorn <glenzorn@comcast.net>, jouni.korhonen@teliasonera.com, preeti.shandilya@aricent.com, tasveren@sonusnet.com
Message-id: <018a01c83bd4$9437a780$544c460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-Priority: 3
X-MSMail-priority: Normal
References: <033458F56EC2A64E8D2D7B759FA3E7E7509625@sonusmail04.sonusnet.com> <OFF1D96C66.DAFB08B8-ON652573AE.0016CC5A-652573AE.0017C06A@aricent.com> <59D7431DE2527D4CB0F1EFEDA5683ED3024F9CB8@SEHAN021MB.tcad.telia.se> <00a701c83bcb$8f25acf0$ad7106d0$@net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Cc: dime@ietf.org, gshafran@traffixsystems.com
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2039106967=="
Errors-To: dime-bounces@ietf.org

Dear Glen and all,
I know Jouni has two use cases. Jouni, Steve and I talked about them in Vancouver. I am trying to describe as below. If it is not precise, Jouni, please correct me.

Use case #1:
There are several visiting network, and one home network. 
Type 1# service should go via intermediate node #a in visiting network A#.
Type 2# service should go via intermediate node #b in visiting network B#.
......
This use case can be for both mobile and fix network operator.

Use case #2:
The charging data should be sent from that node.

This use case can be for mobile operator.

B. R.
Tina
-------------------------------------------------------------
You know it is Monday when you see cat hair in your cereal.
  ----- Original Message ----- 
  From: Glen Zorn 
  To: jouni.korhonen@teliasonera.com ; preeti.shandilya@aricent.com ; tasveren@sonusnet.com 
  Cc: dime@ietf.org ; gshafran@traffixsystems.com 
  Sent: Tuesday, December 11, 2007 3:58 PM
  Subject: RE: [Dime] Review of draft-tsou-dime-base-routing-ext-03.txt


  ...

  > I am not sure why there is a requirement for subsequent 
  > session oriented message to traverse the same intermediary 
  > hops which the initial message has traversed. 

  What if some of the intermediates are stateful and e.g.
  collect charging data by tracking the user session?

  [gwz] 
  I must admit that I cannot think of a single (real-life) scenario where this
  kind of thing would be desirable (let alone required).  Would you mind
  describing one in detail?
  [/gwz]
   
  ...


  _______________________________________________
  DiME mailing list
  DiME@ietf.org
  https://www1.ietf.org/mailman/listinfo/dime
_______________________________________________
DiME mailing list
DiME@ietf.org
https://www1.ietf.org/mailman/listinfo/dime