RE: [Dime] Review of draft-tsou-dime-base-routing-ext-03.txt
<jouni.korhonen@teliasonera.com> Tue, 11 December 2007 15:41 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 1J27EQ-0008P2-Fo; Tue, 11 Dec 2007 10:41:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J27EO-0008Ot-TY for dime@ietf.org; Tue, 11 Dec 2007 10:41:12 -0500
Received: from sehan002bb.han.telia.se ([131.115.18.153]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J27EM-0002mF-ME for dime@ietf.org; Tue, 11 Dec 2007 10:41:12 -0500
Received: from SEHAN021MB.tcad.telia.se ([131.115.18.160]) by sehan002bb.han.telia.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 11 Dec 2007 16:41:09 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Dime] Review of draft-tsou-dime-base-routing-ext-03.txt
Date: Tue, 11 Dec 2007 16:41:07 +0100
Message-ID: <59D7431DE2527D4CB0F1EFEDA5683ED3024F9CF1@SEHAN021MB.tcad.telia.se>
In-Reply-To: <033458F56EC2A64E8D2D7B759FA3E7E750962A@sonusmail04.sonusnet.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Dime] Review of draft-tsou-dime-base-routing-ext-03.txt
Thread-Index: Acg7V1X6yiO+AoLiTfm8vnb3hd0GnQACsyygAAPMaYAAALAHUAAiUxegAADNriA=
References: <4757153B.2060802@gmx.net><59D7431DE2527D4CB0F1EFEDA5683ED3024F9C38@SEHAN021MB.tcad.telia.se><e73a13320712101005l3b2d3e31r69fdfae70b1e40fa@mail.gmail.com> <59D7431DE2527D4CB0F1EFEDA5683ED3024F9CAE@SEHAN021MB.tcad.telia.se> <033458F56EC2A64E8D2D7B759FA3E7E7509626@sonusmail04.sonusnet.com> <59D7431DE2527D4CB0F1EFEDA5683ED3024F9CB0@SEHAN021MB.tcad.telia.se> <033458F56EC2A64E8D2D7B759FA3E7E750962A@sonusmail04.sonusnet.com>
From: jouni.korhonen@teliasonera.com
To: tasveren@sonusnet.com, dime@ietf.org
X-OriginalArrivalTime: 11 Dec 2007 15:41:09.0388 (UTC) FILETIME=[402ACCC0:01C83C0C]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc:
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
Hi Tolga, [snip] > > > [TOLGA]How does this advertisement work? Capability exchange > > > mechanism does not have that type of capability(i.e. > > > advertising application support per realm). > > > > That's typically done before gaining the access to the network. > > The access network may for example use RFC4284 to advertise > realms or > > then some access technology specific way (like .11u, .16g etc). > > > > I am not actually sure what you are after with your > question related > > to capability exchange. > [TOLGA]I was wondering how this would work from Diameter > capability negotiation perspective: > a) Does the NAP need to advertise support for certain > application for different domains? Don't see a reason for this. > b) Or does it use a different Diameter identity for each domain? NAP has one identity. > c) Or do the clients assume that NAP provides access for all > possible domains? The NAP provides access to those realms it advertises. Cheers, Jouni > > > > > Cheers, > > Jouni _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime
- [Dime] Review of draft-tsou-dime-base-routing-ext… Hannes Tschofenig
- Re: [Dime] Review of draft-tsou-dime-base-routing… Tina TSOU
- Re: [Dime] Review of draft-tsou-dime-base-routing… Hannes Tschofenig
- RE: [Dime] Review of draft-tsou-dime-base-routing… Asveren, Tolga
- Re: [Dime] Review of draft-tsou-dime-base-routing… Hannes Tschofenig
- RE: [Dime] Review of draft-tsou-dime-base-routing… Tony Zhang
- RE: [Dime] Review of draft-tsou-dime-base-routing… Asveren, Tolga
- RE: [Dime] Review of draft-tsou-dime-base-routing… jouni.korhonen
- Re: [Dime] Review of draft-tsou-dime-base-routing… Gil Shafran
- RE: [Dime] Review of draft-tsou-dime-base-routing… Asveren, Tolga
- RE: [Dime] Review of draft-tsou-dime-base-routing… jouni.korhonen
- RE: [Dime] Review of draft-tsou-dime-base-routing… Asveren, Tolga
- RE: [Dime] Review of draft-tsou-dime-base-routing… jouni.korhonen
- RE: [Dime] Review of draft-tsou-dime-base-routing… Preeti Shandilya
- RE: [Dime] Review of draft-tsou-dime-base-routing… jouni.korhonen
- RE: [Dime] Review of draft-tsou-dime-base-routing… Glen Zorn
- RE: [Dime] Review of draft-tsou-dime-base-routing… Preeti Shandilya
- Re: [Dime] Review of draft-tsou-dime-base-routing… Tina TSOU
- RE: [Dime] Review of draft-tsou-dime-base-routing… jouni.korhonen
- RE: [Dime] Review of draft-tsou-dime-base-routing… Asveren, Tolga
- RE: [Dime] Review of draft-tsou-dime-base-routing… jouni.korhonen
- RE: [Dime] Review of draft-tsou-dime-base-routing… Glen Zorn
- RE: [Dime] Review of draft-tsou-dime-base-routing… jouni.korhonen
- RE: [Dime] Review of draft-tsou-dime-base-routing… Glen Zorn
- RE: [Dime] Review of draft-tsou-dime-base-routing… Preeti Shandilya
- Re: [Dime] Review of draft-tsou-dime-base-routing… Tina TSOU
- Re: [Dime] Review of draft-tsou-dime-base-routing… Tina TSOU
- Re: [Dime] Review of draft-tsou-dime-base-routing… Tina TSOU