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

Tina TSOU <tena@huawei.com> Thu, 13 December 2007 06:46 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 1J2hqO-00075b-QJ; Thu, 13 Dec 2007 01:46:52 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J2hqO-00075W-Dj for dime@ietf.org; Thu, 13 Dec 2007 01:46:52 -0500
Received: from szxga01-in.huawei.com ([61.144.161.53]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J2hqN-0001lD-83 for dime@ietf.org; Thu, 13 Dec 2007 01:46:52 -0500
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JSZ008JT6QVS3@szxga01-in.huawei.com> for dime@ietf.org; Thu, 13 Dec 2007 14:44:55 +0800 (CST)
Received: from huawei.com ([172.24.1.18]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JSZ009AN6QU1F@szxga01-in.huawei.com> for dime@ietf.org; Thu, 13 Dec 2007 14:44:55 +0800 (CST)
Received: from z24109b ([10.70.76.84]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0JSZ00CUM6QUH4@szxml03-in.huawei.com> for dime@ietf.org; Thu, 13 Dec 2007 14:44:54 +0800 (CST)
Date: Thu, 13 Dec 2007 14:44:54 +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: <015401c83d53$ab40cdf0$544c460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
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> <018a01c83bd4$9437a780$544c460a@china.huawei.com> <007b01c83c22$ab1f50d0$015df270$@net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 850245b51c39701e2700a112f3032caa
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="===============1443537643=="
Errors-To: dime-bounces@ietf.org

Dear Glen,
My comments are below demarked with [Tina: ...].

B. R.
Tina
  ----- Original Message ----- 
  From: Glen Zorn 
  To: 'Tina TSOU' ; jouni.korhonen@teliasonera.com ; preeti.shandilya@aricent.com ; tasveren@sonusnet.com 
  Cc: dime@ietf.org ; gshafran@traffixsystems.com 
  Sent: Wednesday, December 12, 2007 2:21 AM
  Subject: RE: [Dime] Review of draft-tsou-dime-base-routing-ext-03.txt


  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.

  [gwz] 

  So what happens if node #a is down?  Is Type 1# service disabled/unavailable?  If not, what's the point of the routing, given that it is unnecessary; if so, doesn't that sort of defeat the purpose of fail-over?

  [/gwz]

  [Tina: Ongoing session will disable/unavailable. But the service can use another stateful proxy agent. It is like one server fails. If one server fails, ongoing session will fail, but another server maybe can take over new session process.] 



  Use case #2:

  The charging data should be sent from that node.

  [gwz] 

  Does this mean that the data path must also pass through that node?

  [/gwz]

  [Tina: It is unnecessary, the node maybe just do charging base on session time.] 



  This use case can be for mobile operator.

   

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