Re: [Mip6] mip6-aaa frameworks

Samita Chakrabarti <Samita.Chakrabarti@eng.sun.com> Tue, 15 February 2005 20:34 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09068 for <mip6-web-archive@ietf.org>; Tue, 15 Feb 2005 15:34:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D19kC-0000du-6t for mip6-web-archive@ietf.org; Tue, 15 Feb 2005 15:56:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D19CX-00049F-El; Tue, 15 Feb 2005 15:21:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D195e-0006pV-CC for mip6@megatron.ietf.org; Tue, 15 Feb 2005 15:14:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05845 for <mip6@ietf.org>; Tue, 15 Feb 2005 15:14:32 -0500 (EST)
Received: from nwkea-mail-1.sun.com ([192.18.42.13]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D19Qk-0008ML-VZ for mip6@ietf.org; Tue, 15 Feb 2005 15:36:23 -0500
Received: from jurassic.eng.sun.com ([129.146.82.37]) by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id j1FKEWPD007716; Tue, 15 Feb 2005 12:14:32 -0800 (PST)
Received: from shubho (shubho.SFBay.Sun.COM [129.146.73.85]) by jurassic.eng.sun.com (8.13.3+Sun/8.13.3) with SMTP id j1FKEV3Q480281; Tue, 15 Feb 2005 12:14:31 -0800 (PST)
Message-Id: <200502152014.j1FKEV3Q480281@jurassic.eng.sun.com>
Date: Tue, 15 Feb 2005 12:12:29 -0800
From: Samita Chakrabarti <Samita.Chakrabarti@eng.sun.com>
Subject: Re: [Mip6] mip6-aaa frameworks
To: julien.bournelle@int-evry.fr, alper.yegin@samsung.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset="us-ascii"
Content-MD5: 10gl0pYpu3I4c5/posObFA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.6_54 SunOS 5.10 sun4u sparc
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Samita Chakrabarti <Samita.Chakrabarti@eng.sun.com>
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955


Hi Alper,

Thanks for providing an analysis of different proposals/framework.

I'd agree with Julien, that draft-chakrabati-mip6-bmip-00.txt
goes with Framework 4 very well for retrieving Home Agent address
and initial security association for bootstrap. 
Although the BMIP draft is not about AAA and MIPv6, it can co-exist
with having a AAA server in the foreign network and a AAA back-end server
tied to HA. So, it makes sense to add this draft to the list for
completeness.

In the next version of the draft we are going to clarify that
the BMIP draft can be used for different types of access networks
(802.1X, PANA, UAM, physical access , Local AAA) in order to gain
access to the local network.

Thanks,
-Samita

> > 
> > Framework 4:
> > ------------
> > A backend AAA protocol is executed between the HA and the AAA server in
> > response to the MIP6 signaling between the MN and the HA. Similar to the
> > use of AAA protocols with MIPv4 co-located care-of address case.
> > 
> > Related I-Ds:
> > 
> > draft-giaretta-mip6-aaa-ha-goals-00.txt
> > draft-yegin-mip6-aaa-fwk-00.txt
> 
> I would add:
> draft-chakrabati-mip6-bmip-00.txt
> (DNS to discover HA + IKEv2 and AAA-HA)
> 
> draft-tschofenig-mip6-bootstrapping-pana
> (needs to relax PANA on the one IP hop between PaC and PAA) assumption
> 
> > Discussion:
> > This one appears to be the most needed framework. It is assumed that MN
> > already knows the HA address. 
> > 
> > 
> > Are there other frameworks to add?
> 
> I also wrote a proposition draft-bournelle-pana-mip6-00. This
> proposition rely on PANA. The PAA is in charge of allocating the HA and
> of providing necessary information to HA and MN. The problem with this
> approach is that the HA allocation is only in the visited domain.
> However, the idea is that the AAA server explicitely authorize the service but
> delegate configuration process to an agent.
> 
> Do you think that we can make a framework with this ?
> 
> -- 
> julien.bournelle@int-evry.fr
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6