[Mip4] config options with MIP messages
Kuntal Chowdhury <kuntal@iqmail.net> Wed, 06 August 2003 18:33 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28637 for <mip4-archive@odin.ietf.org>; Wed, 6 Aug 2003 14:33:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19kT5q-00036e-Lc for mip4-archive@odin.ietf.org; Wed, 06 Aug 2003 14:33:03 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h76IX2vI011936 for mip4-archive@odin.ietf.org; Wed, 6 Aug 2003 14:33:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19kT5q-00036R-GZ for mip4-web-archive@optimus.ietf.org; Wed, 06 Aug 2003 14:33:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28627 for <mip4-web-archive@ietf.org>; Wed, 6 Aug 2003 14:32:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19kT5n-0005Ze-00 for mip4-web-archive@ietf.org; Wed, 06 Aug 2003 14:33:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19kT5n-0005Zb-00 for mip4-web-archive@ietf.org; Wed, 06 Aug 2003 14:32:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19kT5p-00035i-Ba; Wed, 06 Aug 2003 14:33:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19kT5D-00033d-Tn for mip4@optimus.ietf.org; Wed, 06 Aug 2003 14:32:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28597 for <mip4@ietf.org>; Wed, 6 Aug 2003 14:32:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19kT5B-0005ZU-00 for mip4@ietf.org; Wed, 06 Aug 2003 14:32:21 -0400
Received: from zrc2s0jx.nortelnetworks.com ([47.103.122.112]) by ietf-mx with esmtp (Exim 4.12) id 19kT5A-0005Z2-00 for mip4@ietf.org; Wed, 06 Aug 2003 14:32:20 -0400
Received: from zrc2c001.us.nortel.com (zrc2c001.us.nortel.com [47.103.121.31]) by zrc2s0jx.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h76IVd701342; Wed, 6 Aug 2003 13:31:39 -0500 (CDT)
Received: from zrc2c009.us.nortel.com ([47.103.120.49]) by zrc2c001.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 30FXMFVL; Wed, 6 Aug 2003 13:31:39 -0500
Received: from iqmail.net (chowdury-2.us.nortel.com [47.103.84.37]) by zrc2c009.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id P1LBW6YH; Wed, 6 Aug 2003 13:31:40 -0500
Message-ID: <3F3148D7.3020606@iqmail.net>
Date: Wed, 06 Aug 2003 13:28:39 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Kuntal Chowdhury <kuntal@iqmail.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Basavaraj.Patil@nokia.com
CC: mobile-ip@sunroof.eng.sun.com, mip4@ietf.org
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Mip4] config options with MIP messages
Sender: mip4-admin@ietf.org
Errors-To: mip4-admin@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
draft-le-aaa-diameter-mobileipv6-03.txt:
Section 4.3:
" This Binding Update MUST be authenticated,
therefore a key distribution, e.g. IKE, may need to be executed.
This requires many messages to be exchanged between the mobile
node and the Home Agent.
As an alternative, after the authentication and authorization steps,
the AAA servers can be involved and play a role in the key generation
and/or the key distribution.
"
I am surprised to see that you propose to use AAA infrastructure to do key
distribution -> use AAA messages to do the job of IKE, however you were
objecting to our proposal of using MIP messages to exchange DNS server info
because we have DHCP...
Just an observation.
-Kuntal
_______________________________________________
Mip4 mailing list
Mip4@ietf.org
https://www.ietf.org/mailman/listinfo/mip4
- [Mip4] config options with MIP messages Kuntal Chowdhury