Re: [Mip6] Comments on jee-mip6-bootstrap-pana
"Junghoon Jee" <jhjee@etri.re.kr> Mon, 08 November 2004 14:22 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 JAA11421 for <mip6-web-archive@ietf.org>; Mon, 8 Nov 2004 09:22:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRAQQ-00026a-PD for mip6-web-archive@ietf.org; Mon, 08 Nov 2004 09:23:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRAHL-0001Rq-VS; Mon, 08 Nov 2004 09:13:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRA3J-0005y8-6a for mip6@megatron.ietf.org; Mon, 08 Nov 2004 08:59:30 -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 IAA08986 for <mip6@ietf.org>; Mon, 8 Nov 2004 08:59:23 -0500 (EST)
Received: from cms1.etri.re.kr ([129.254.16.11]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRA3n-0001NL-Ty for mip6@ietf.org; Mon, 08 Nov 2004 08:59:59 -0500
Received: from ETRIYSLEE (130.129.135.101 [130.129.135.101]) by cms1.etri.re.kr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id VRH2ZYGT; Mon, 8 Nov 2004 22:58:50 +0900
Message-ID: <001a01c4c59b$19b854d0$65878182@ETRIYSLEE>
From: Junghoon Jee <jhjee@etri.re.kr>
To: Julien Bournelle <Julien.Bournelle@int-evry.fr>
References: <2A8DB02E3018D411901B009027FD3A3F05319F6C@mchp905a.mch.sbs.de><002b01c4c26d$2a6962f0$428feada@ETRIYSLEE> <20041104131957.GL10930@ipv6-5.int-evry.fr>
Subject: Re: [Mip6] Comments on jee-mip6-bootstrap-pana
Date: Mon, 08 Nov 2004 08:58:54 -0500
Organization: CMS
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 2.2 (++)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: Alper Yegin <alper.yegin@samsung.com>, mip6@ietf.org, Tschofenig Hannes <hannes.tschofenig@siemens.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Junghoon Jee <jhjee@etri.re.kr>
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>
Content-Type: multipart/mixed; boundary="===============1182622003=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Hello, Julien. > > hi, > > just a little comment inline, > > > > ps: it might be good to reference an old draft > > > <draft-le-aaa-diameter-mobileipv6-02.txt> which proposed the same approach. > > > i also remember that julien published a draft with a similar idea some time > > > ago. > > > > The previous draft-le-aaa-diameter-mobileipv6-03.txt is a good reference for our work. > > In that draft, BU message is processed during the AAA auth. & authorization phase. > > The BU message can be piggybacked to the AAA auth request message > > or it can be produced on the AAA server. > > In the draft-jee-mip6-bootstrap-aaa-00, BU is processed after the AAA auth & authorization phase. > > This is because the BU MUST be protected by the IPsec SA according to the RFC 3775. > > If the draft-ietf-mip6-auth-protocol-00.txt is used, > > BU may be piggybacked during the AAA auth& authorization phase if the MN's CoA is configured. > > I think that one of the major issue with this approach (defining a > specific AAA application for Mobile IPv6) is that all visited network > MUST use this specific AAA application if you want to bootstrapp Mobile > IPv6. Thus, if the visited network uses > Diameter-EAP or RADIUS-EAP, you can't bootstrapp Mobile IPv6. This imply that all > operators should deploy this solution. > With our approach (draft-giaretta), the visited network does not need to > Mobile IPV6 aware. > > julien.bournelle@int-evry.fr > Right. With my approach(draft-jee), a specific new Diameter Application is required to bootstrap mobile nodes. In my opinion, there are pros. & cons. in using a new Diameter Application or not. New Diameter Mobile IPv6 Bootstrapping Application(draft-jee) supports the HA assignment in the Visited network. If you use a previous Diameter EAP or RADIUS EAP, you cannnot assign a HA in the visited domain. Some of modification or adding are required. The HA assignment in the visited domain is a requirement item in the previous I-D(draft-le-aaa-mipv6-requirements-03.txt). This point is specified in the section 5.5 of that I-D. i think we should consider the HA assignment in the visited domain not only in the home domain. Junghoon
_______________________________________________ Mip6 mailing list Mip6@ietf.org https://www1.ietf.org/mailman/listinfo/mip6
- [Mip6] Comments on jee-mip6-bootstrap-pana Alper Yegin
- Re: [Mip6] Comments on jee-mip6-bootstrap-pana Junghoon Jee
- RE: [Mip6] Comments on jee-mip6-bootstrap-pana Alper Yegin
- Re: [Mip6] Comments on jee-mip6-bootstrap-pana Junghoon Jee
- RE: [Mip6] Comments on jee-mip6-bootstrap-pana Alper Yegin
- Re: [Mip6] Comments on jee-mip6-bootstrap-pana Junghoon Jee
- Re: [Mip6] Comments on jee-mip6-bootstrap-pana Junghoon Jee
- RE: [Mip6] Comments on jee-mip6-bootstrap-pana Alper Yegin
- RE: [Mip6] Comments on jee-mip6-bootstrap-pana Tschofenig Hannes
- Re: [Mip6] Comments on jee-mip6-bootstrap-pana Junghoon Jee
- Re: [Mip6] Comments on jee-mip6-bootstrap-pana Julien Bournelle
- RE: [Mip6] Comments on jee-mip6-bootstrap-pana Tschofenig Hannes
- RE: [Mip6] Comments on jee-mip6-bootstrap-pana Tschofenig Hannes
- Re: [Mip6] Comments on jee-mip6-bootstrap-pana Junghoon Jee
- Re: [Mip6] Comments on jee-mip6-bootstrap-pana Junghoon Jee
- Re: [Mip6] Comments on jee-mip6-bootstrap-pana Lee Garth