Re: RE: [dhcwg] Mobile Ipv6 bootstrap issue
Li Qin <liqin@cse.buaa.edu.cn> Sat, 04 December 2004 14:31 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 JAA02341 for <dhcwg-web-archive@ietf.org>; Sat, 4 Dec 2004 09:31:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cab2A-0001rc-Mw for dhcwg-web-archive@ietf.org; Sat, 04 Dec 2004 09:37:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Caauj-0000dw-3F; Sat, 04 Dec 2004 09:29:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV9Aa-0006gb-D2 for dhcwg@megatron.ietf.org; Fri, 19 Nov 2004 08:51:24 -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 IAA02128 for <dhcwg@ietf.org>; Fri, 19 Nov 2004 08:51:20 -0500 (EST)
Received: from mx2.buaa.edu.cn ([219.239.227.26]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV9DM-0004ov-JI for dhcwg@ietf.org; Fri, 19 Nov 2004 08:54:18 -0500
Received: from mx1.buaa.edu.cn (unknown [192.168.128.6]) by mx2.buaa.edu.cn (Postfix) with ESMTP id 0456A37F72 for <dhcwg@ietf.org>; Fri, 19 Nov 2004 21:50:49 +0800 (CST)
Received: from [211.71.8.37] by 10.0.0.131 with StormMail ESMTP id 9652.262235339; Fri, 19 Nov 2004 22:02:44 +0800 (CST)
Message-ID: <419DFA3D.6080303@cse.buaa.edu.cn>
Date: Fri, 19 Nov 2004 21:50:53 +0800
From: Li Qin <liqin@cse.buaa.edu.cn>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040926)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dhcwg@ietf.org
Subject: Re: RE: [dhcwg] Mobile Ipv6 bootstrap issue
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sat, 04 Dec 2004 09:29:31 -0500
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
>I believe that DHCP is a good solution whenever DHCP is available on the >client. >That's why DHCP is here. If DHCP is not available, we can't use it of course. I think current operators would not extend DHCP to support other service. So they prefer not modify DHCP, but use a specifical protocol. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- Re: RE: [dhcwg] Mobile Ipv6 bootstrap issue Li Qin
- [dhcwg] Mobile Ipv6 bootstrap issue DENG, HUI -HCHIBJ
- RE: [dhcwg] Mobile Ipv6 bootstrap issue Alper Yegin
- RE: [dhcwg] Mobile Ipv6 bootstrap issue DENG, HUI -HCHIBJ
- Re: RE: [dhcwg] Mobile Ipv6 bootstrap issue Daniel Park