IETF Logo Mail Archive

RE: [dhcwg] Design team for automated address management

"S. Daniel Park" <soohong.park@samsung.com> Wed, 21 April 2004 08:13 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02870 for <dhcwg-archive@odin.ietf.org>; Wed, 21 Apr 2004 04:13:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGCpB-00023w-Io for dhcwg-archive@odin.ietf.org; Wed, 21 Apr 2004 04:11:18 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3L8BHA9007928 for dhcwg-archive@odin.ietf.org; Wed, 21 Apr 2004 04:11:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGCgk-0006f3-CA for dhcwg-web-archive@optimus.ietf.org; Wed, 21 Apr 2004 04:02:34 -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 EAA02331 for <dhcwg-web-archive@ietf.org>; Wed, 21 Apr 2004 04:02:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BGCgh-0000PA-TI for dhcwg-web-archive@ietf.org; Wed, 21 Apr 2004 04:02:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BGCfl-0000Ib-00 for dhcwg-web-archive@ietf.org; Wed, 21 Apr 2004 04:01:34 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BGCep-0000Bg-00 for dhcwg-web-archive@ietf.org; Wed, 21 Apr 2004 04:00:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGCXX-0003FI-5q; Wed, 21 Apr 2004 03:53:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGCW8-0002TZ-O2 for dhcwg@optimus.ietf.org; Wed, 21 Apr 2004 03:51:36 -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 DAA01630 for <dhcwg@ietf.org>; Wed, 21 Apr 2004 03:51:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BGCW6-0006tf-86 for dhcwg@ietf.org; Wed, 21 Apr 2004 03:51:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BGCV6-0006oi-00 for dhcwg@ietf.org; Wed, 21 Apr 2004 03:50:32 -0400
Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx with esmtp (Exim 4.12) id 1BGCUG-0006ev-00 for dhcwg@ietf.org; Wed, 21 Apr 2004 03:49:40 -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 <0HWI00704GDY9J@mailout2.samsung.com> for dhcwg@ietf.org; Wed, 21 Apr 2004 16:49:10 +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 <0HWI002UYGDXLC@mailout2.samsung.com> for dhcwg@ietf.org; Wed, 21 Apr 2004 16:49:09 +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 <0HWI00MCDGDX0X@mmp2.samsung.com> for dhcwg@ietf.org; Wed, 21 Apr 2004 16:49:09 +0900 (KST)
Date: Wed, 21 Apr 2004 16:49:35 +0900
From: "S. Daniel Park" <soohong.park@samsung.com>
Subject: RE: [dhcwg] Design team for automated address management
In-reply-to: <4.3.2.7.2.20040420120119.02f474d0@flask.cisco.com>
To: 'Ralph Droms' <rdroms@cisco.com>, dhcwg@ietf.org
Message-id: <015301c42775$30eb2430$67cadba8@LocalHost>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
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>
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
Content-Transfer-Encoding: 7bit

I am not sure why we need this option to allocate
its required address block in the IPv6 address 
architecture. It seems to be duplicated with current 
prefix delegation mechanism (3633) because a 
requesting router can set its preference for the size 
of the prefix to be delegated in this mechanism. 
I don't have a hard stance on the IPv4 at this stage.

Particularly, I myself am so curious whether it is a 
real dhc charter scope or not because it applies to 
router configuration rather than host configuration as 
ralph stated previous. I am also suffering from this
assumption on the router tunnel auto-configuration.

Nevertheless, DT's analysis would be useful for me (us ?)

Thanks.

- Daniel (Soohong Daniel Park)
- Mobile Platform Laboratory, SAMSUNG Electronics. 

> -----Original Message-----
> From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org] On 
> Behalf Of Ralph Droms
> Sent: Wednesday, April 21, 2004 1:09 AM
> To: dhcwg@ietf.org
> Subject: [dhcwg] Design team for automated address management
> 
> 
> At the WG meeting in Seoul, I promised to "arrange for a discussion to
> reconcile this option with DHCPv6 prefix delegation and 
> earlier ODAP work."
> I would like to identify a small team of volunteers to take 
> up this issue
> and review draft-shen-dhc-block-alloc-01, earlier work on 
> ODAP and DHCPv6
> prefix delegation.  The result of this review will include an 
> analysis of
> the similarities and differences between the various proposals, a
> description of the automated address management problem space and
> recommendations for work on DHCP required in that space.
> 
> I would like to get at least one author from each of the drafts on the
> design team and, of course, other volunteers are welcome.
> 
> - Ralph
> 
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
> 


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

v2.27.8 | Report a Bug | By Email | System Status