IETF Logo Mail Archive

[Dime] Defining a new Application for mip6-split ?

Julien Bournelle <julien.bournelle@int-evry.fr> Thu, 18 May 2006 09:43 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fgf2I-0001Or-8B; Thu, 18 May 2006 05:43:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fgf2G-0001Ol-Md for dime@ietf.org; Thu, 18 May 2006 05:43:12 -0400
Received: from smtp2.int-evry.fr ([157.159.10.45]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fgf2D-0003VF-Lw for dime@ietf.org; Thu, 18 May 2006 05:43:11 -0400
Received: from ipv6-3.int-evry.fr (ipv6-3.int-evry.fr [157.159.100.76]) by smtp2.int-evry.fr (Postfix) with ESMTP id 03934808F; Thu, 18 May 2006 11:42:50 +0200 (CEST)
Received: from jb by ipv6-3.int-evry.fr with local (Exim 4.52) id 1Fge5Q-0005h0-VV; Thu, 18 May 2006 10:42:24 +0200
Date: Thu, 18 May 2006 10:42:24 +0200
From: Julien Bournelle <julien.bournelle@int-evry.fr>
To: dime@ietf.org
Message-ID: <20060518084224.GA21878@ipv6-3.int-evry.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-SpamCheck:
X-MailScanner-From: jb@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: hannes.tschofenig@gmx.net
Subject: [Dime] Defining a new Application for mip6-split ?
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 all,

 we're in the process of updating/writing the document describing use of
 Diameter for the Mobile IPv6 split scenario.

 In the split scenario, the Mobile Node (MN) uses IKEv2 with the HA to
 setup IPsec SAs. This exchange is also used by the HA to authenticate
 the MN using EAP. The HA may rely on a AAA/EAP server for this. So we
 have the following scheme:

 MN <-- IKEv2-EAP --> HA <--------> AAA

 A priori Diameter EAP (RFC 4072) can be used between HA and AAA. 

 The problem is that Diameter EAP is normally used for Network Access
 authentication. 

 In our case, the AAA server must perform AAA functionality for the
 Mobile IPv6 service. The AAA server must know that it has to authorize
 the mip6 service and the accounting (ASR/ASA) is also for mip6 and not
 for network access.

 For the above reason, it seems that we should define a new Diameter
 Application. However, in the same time, the messages defined in
 Diameter EAP could be reused.

 So I'd like to hear opinions concerning this issue.

 Thanks,


 - Julien B.


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

v2.23.0 | Report a Bug | By Email