RE: [mip4] Clarify the procedure in the case of DHCP failure or IPCP failure.
"Kent Leung (kleung)" <kleung@cisco.com> Mon, 03 December 2007 22:28 UTC
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzJm8-0005mn-DH; Mon, 03 Dec 2007 17:28:28 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IzJm7-0005mS-58 for mip4-confirm+ok@megatron.ietf.org; Mon, 03 Dec 2007 17:28:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzJm6-0005mI-Rs for mip4@ietf.org; Mon, 03 Dec 2007 17:28:26 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzJm3-0000Ug-PX for mip4@ietf.org; Mon, 03 Dec 2007 17:28:26 -0500
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 03 Dec 2007 14:28:23 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id lB3MSNmW011608; Mon, 3 Dec 2007 14:28:23 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lB3MSHqd023511; Mon, 3 Dec 2007 22:28:23 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 3 Dec 2007 14:28:20 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mip4] Clarify the procedure in the case of DHCP failure or IPCP failure.
Date: Mon, 03 Dec 2007 14:28:17 -0800
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC52050C3A1A@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <000001c83557$c2803c70$5d05a40a@china.huawei.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [mip4] Clarify the procedure in the case of DHCP failure or IPCP failure.
Thread-Index: Acg1V8G6Lq/3SrA6QxaMVKU50TrtHAAos6WA
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: qinxia <alice.Q@huawei.com>
X-OriginalArrivalTime: 03 Dec 2007 22:28:20.0308 (UTC) FILETIME=[CED35940:01C835FB]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1853; t=1196720903; x=1197584903; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kleung@cisco.com; z=From:=20=22Kent=20Leung=20(kleung)=22=20<kleung@cisco.com> |Subject:=20RE=3A=20[mip4]=20Clarify=20the=20procedure=20in=20the=20case= 20of=20DHCP=20failure=20or=20IPCP=20failure. |Sender:=20; bh=prwN69h3g/0RDpFzOFtvilSFs3qgmIm5nsguAiynFdE=; b=OQQK8X5wwxfFQguhpjL1A8bv46vNpx4Ff5u4aHmovjNPYN/c1M9UMek0/i8G/zN7Ri/3LB4q 7QK1k81NsUP93XRlD4EZdaSEPqeX1diaw/x8lfnBkdcaHxJBjzODdpXN;
Authentication-Results: sj-dkim-4; header.From=kleung@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org
Hi Alice. I agree that the draft should cover the failure conditions you've mentioned. Also, the DHCP relay agent mode will be updated in the general section. The specifics of the call flow will be documented in the WiMAX section and will be aligned accordingly. This was one of the comments from WiMAX expert review. The draft will address the comments in the next revision. Kent -----Original Message----- From: qinxia [mailto:alice.Q@huawei.com] Sent: Sunday, December 02, 2007 6:54 PM To: Kent Leung (kleung) Cc: mip4@ietf.org Subject: [mip4] Clarify the procedure in the case of DHCP failure or IPCP failure. Hello Kent, IMHO, it is required to clarify the procedure in the case of DHCP failure in section 4.1.1. Proxy Registration during Initial Network Attachment. In step 5, for some reason, DHCP server may reject such address assignment or IPCP machine may shut down, the PMIP registration should be revoked. Moreover, we should clarify another procedure in which DHCP relay does not hold DHCP discovery message and forward it to DHCP server before PMIP registration procedure sepcified in WiMAX. Best regards ALice ************************************************************************ ********* This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! ************************************************************************ ********* -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/
- RE: [mip4] Clarify the procedure in the case of D… Kent Leung (kleung)
- [mip4] Clarify the procedure in the case of DHCP … qinxia