RE: [dhcwg] REMINDER: dhc WG last call on dhc WG last call on draft-ietf-dhc-dna-ipv4-07.txt

Soohong Daniel Park <soohong.park@samsung.com> Thu, 24 June 2004 17:05 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29853; Thu, 24 Jun 2004 13:05:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdXIE-00019l-KB; Thu, 24 Jun 2004 12:41:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bd2Gz-0005kL-2O for dhcwg@megatron.ietf.org; Wed, 23 Jun 2004 03:34:21 -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 DAA25840 for <dhcwg@ietf.org>; Wed, 23 Jun 2004 03:34:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bd2Gw-00030T-LQ for dhcwg@ietf.org; Wed, 23 Jun 2004 03:34:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bd1Ix-0007bU-00 for dhcwg@ietf.org; Wed, 23 Jun 2004 02:32:20 -0400
Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx with esmtp (Exim 4.12) id 1Bcymj-00051A-00 for dhcwg@ietf.org; Tue, 22 Jun 2004 23:50:54 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0HZQ00E01TBWSZ@mailout2.samsung.com> for dhcwg@ietf.org; Wed, 23 Jun 2004 12:50:20 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0HZQ004MSTBVT6@mailout2.samsung.com> for dhcwg@ietf.org; Wed, 23 Jun 2004 12:50:20 +0900 (KST)
Received: from LocalHost ([168.219.202.103]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0HZQ0013ATBQ5L@mmp2.samsung.com> for dhcwg@ietf.org; Wed, 23 Jun 2004 12:50:14 +0900 (KST)
Date: Wed, 23 Jun 2004 12:51:08 +0900
From: Soohong Daniel Park <soohong.park@samsung.com>
Subject: RE: [dhcwg] REMINDER: dhc WG last call on dhc WG last call on draft-ietf-dhc-dna-ipv4-07.txt
In-reply-to: <4.3.2.7.2.20040621175636.020da900@flask.cisco.com>
To: dhcwg@ietf.org
Message-id: <EDELKJDGPGNIPOAOHMNPMEJIFMAA.soohong.park@samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

This draft looks good and I second it.

My comments are as below;

[1] Category is correct as PS ? I think BCP would be better.

[2] 1. Introduction, 
>This document concerns the interaction of mechanisms used by IPv4
>protocol stacks.  Network attachment detection and its interaction
>with interface configuration is considered elsewhere, for example in
>Neighbor Discovery for IPv6 [RFC2461], IPv6 Stateless Address
>Autoconfiguration [RFC2462] and Mobility Support in IPv6 [MIPv6].

I am not sure why this draft refers rfc2461,2462 and even MIPv6.
This draft is strictly bound to IPv4 especially DHCPv4 and IPv4LL 
and something like that, so I think we don't need to refer IPv6 protocol.

[3] 2.3 IPv4 Address Acquisition
To obtain its IPv4 address quickly, Rapid Commit option of DHCPv4
can be used for optimizing detection of network attachment on mobile
hosts. With my experience, it's stable and fast than current
mechanism, thus if feasible, you can indicate this utility at this
section. 
http://www.ietf.org/internet-drafts/draft-ietf-dhc-rapid-commit-opt-03.txt
(I updated and published it as 04 version yesterday)

For reference, I cite a result of comparison between them.
(It was tested on both wired and wireless though testbed was so simple)

===========================================
Item			Mean value	Standard deviation
===========================================
Time delay
(sec.)	       Existing	0.051269	0.002349
                   New	0.001541	0.001213
===========================================
Packet loss
(packet)       Existing	417.04		53.10322
                   New	366.02		32.55092
===========================================

Hope this helps




- Daniel (Soohong Daniel Park)
- Mobile Platform Lab. Samsung Electronics.
 

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