IETF Logo Mail Archive

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

"Glen Zorn" <glenzorn@comcast.net> Wed, 12 December 2007 03:14 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 1J2I3O-0002f1-A7; Tue, 11 Dec 2007 22:14:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J2I3N-0002es-BJ for dime@ietf.org; Tue, 11 Dec 2007 22:14:33 -0500
Received: from qmta09.emeryville.ca.mail.comcast.net ([76.96.30.96]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J2I3L-0002dV-1U for dime@ietf.org; Tue, 11 Dec 2007 22:14:33 -0500
Received: from OMTA02.emeryville.ca.mail.comcast.net ([76.96.30.19]) by QMTA09.emeryville.ca.mail.comcast.net with comcast id PU331Y0070QkzPw0A11t00; Wed, 12 Dec 2007 03:14:35 +0000
Received: from gwzPC ([67.168.164.234]) by OMTA02.emeryville.ca.mail.comcast.net with comcast id PfEZ1Y00853lGY30800000; Wed, 12 Dec 2007 03:14:35 +0000
X-Authority-Analysis: v=1.0 c=1 a=cKVaRudWhOK2VkHbtnIA:9 a=-qc7naSnD_qXzyZD_PgA:7 a=F0xthONA86SrUxYwYbTxZ0_27XAA:4 a=tqucuuI3bnEA:10
From: Glen Zorn <glenzorn@comcast.net>
To: jouni.korhonen@teliasonera.com
References: <033458F56EC2A64E8D2D7B759FA3E7E7509625@sonusmail04.sonusnet.com> <OFF1D96C66.DAFB08B8-ON652573AE.0016CC5A-652573AE.0017C06A@aricent.com> <59D7431DE2527D4CB0F1EFEDA5683ED3024F9CB8@SEHAN021MB.tcad.telia.se> <00a701c83bcb$8f25acf0$ad7106d0$@net> <59D7431DE2527D4CB0F1EFEDA5683ED3024F9CF5@SEHAN021MB.tcad.telia.se>
In-Reply-To: <59D7431DE2527D4CB0F1EFEDA5683ED3024F9CF5@SEHAN021MB.tcad.telia.se>
Subject: RE: [Dime] Review of draft-tsou-dime-base-routing-ext-03.txt
Date: Tue, 11 Dec 2007 19:11:47 -0800
Message-ID: <00f701c83c6c$bcdace90$36906bb0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acg7rRqyLoXOrcABSj+r85aZOywqsQAE3qnwAAKfSfAACYZF0AAe0EGA
Content-language: en-us
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: preeti.shandilya@aricent.com, 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>
Errors-To: dime-bounces@ietf.org

Glen,

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

References to literature were given earlier in this thread ;)

Anyway, assume two providers connected via "roaming infrastructure
cloud" that cannot guarantee same AAA routes deterministically. The
visited provider has outsourced its AAA based roaming charging to
third party proxies within the "cloud" (each provider may have their
own "third party"). 
[gwz] And? [/gwz]

/Jouni


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

v2.23.0 | Report a Bug | By Email