Re: [Dime] Diameter application for PMIP6 (chargeable-User-ID) question
Jouni Korhonen <jouni.korhonen@iki.fi> Wed, 16 July 2008 23:21 UTC
Return-Path: <dime-bounces@ietf.org>
X-Original-To: dime-archive@megatron.ietf.org
Delivered-To: ietfarch-dime-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7AC913A6890; Wed, 16 Jul 2008 16:21:38 -0700 (PDT)
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6848B3A687D for <dime@core3.amsl.com>; Wed, 16 Jul 2008 16:21:36 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XOsSUaMM+6hr for <dime@core3.amsl.com>; Wed, 16 Jul 2008 16:21:35 -0700 (PDT)
Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by core3.amsl.com (Postfix) with ESMTP id 43CBD3A6863 for <dime@ietf.org>; Wed, 16 Jul 2008 16:21:35 -0700 (PDT)
Received: from [88.114.68.141] (a88-114-68-141.elisa-laajakaista.fi [88.114.68.141]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by gw02.mail.saunalahti.fi (Postfix) with ESMTP id 80FEA13990D; Thu, 17 Jul 2008 02:22:00 +0300 (EEST)
In-Reply-To: <000901c8e77b$ee64b470$cb2e1d50$@de>
References: <000901c8e77b$ee64b470$cb2e1d50$@de>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <AD97D9AF-E365-46B8-B356-4CB6FD50914D@iki.fi>
From: Jouni Korhonen <jouni.korhonen@iki.fi>
Date: Thu, 17 Jul 2008 02:22:00 +0300
To: Bibi Blocksberg <spawnrr@gmx.de>
X-Mailer: Apple Mail (2.753.1)
Cc: dime@ietf.org
Subject: Re: [Dime] Diameter application for PMIP6 (chargeable-User-ID) question
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: dime-bounces@ietf.org
Errors-To: dime-bounces@ietf.org
Hi Rafael, On Jul 16, 2008, at 10:41 PM, Bibi Blocksberg wrote: > Hi all, > > I've one question regarding the draft 'korhonen-dime-pmip6-03.txt' > (http://tools.ietf.org/id/draft-korhonen-dime-pmip6-03.txt). > > > If the MAG performs a user-authentication toward the HAAA > server, it uses the User-Name AVP to identify the MN. After a > successful authentication the HAAA server replies with a > Chargeable-User-Identity. > > My question: Should the MAG use the Chargeable-User-Identity > for the PBU and its MN-ID option, or should the MAG use the > content of the User-Name AVP as MN-ID option in the PBU? If the Chargeable-User-Identity is returned then that identity is to be used. > Section 6.2 on page 14 says that the User-Name > AVP must contain the MN identity if the LMA sends a Diameter > message toward the HAAA server. The value for the User-Name > AVP the LMA has extracted from the received PBU (MN-ID option). > > In my view it isn't clear if the User-Name AVP toward the HAAA > server should contain the Chargeable-User-ID AVP content to > authorize the > PBU, or if the AA-Request and its User-Name AVP contains > the NAI, which was initially used to authenticate the MN by the MAG? The sequence is as follows: MN -> MAG: identity1 = some auth method or link specific identity MAG -> HAAA: User-Name = identity1 MAG <- HAAA: may return a new identity2 in Chargeable-user-Id MAG -> LMA: PBU MN-ID = identity2, if available, otherwise PBU MN-ID = identity1 LMA -> HAAA: User-name = identity from PBU MN-ID i.e. may be identity1 or identity2 Hope this clarifies. > If the User-Name AVP toward the HAA server contains the Chargeable- > User-ID > AVP content, then the real identity of the MN can be concealed > from the > LMA, but > the HAAA server is able to identify the real identity of MN, as it > has > assigned the > Chargeable User-ID. Yes. > I hope, you can provide me with some information on this matter. > > Thanks you in advance > > Rafael Cheers, Jouni > > > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime
- [Dime] Diameter application for PMIP6 (chargeable… Bibi Blocksberg
- Re: [Dime] Diameter application for PMIP6 (charge… Jouni Korhonen