Re: [dhcwg] Internet-Drafts@ietf.org: I-D ACTION:draft-shen-dhc-block-alloc-01.txt

John Schnizlein <jschnizl@cisco.com> Sun, 25 January 2004 17:31 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11724 for <dhcwg-archive@odin.ietf.org>; Sun, 25 Jan 2004 12:31:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ako5p-0000ag-TE for dhcwg-archive@odin.ietf.org; Sun, 25 Jan 2004 12:30:42 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0PHUfPE002264 for dhcwg-archive@odin.ietf.org; Sun, 25 Jan 2004 12:30:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ako5p-0000aR-MN for dhcwg-web-archive@optimus.ietf.org; Sun, 25 Jan 2004 12:30:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11717 for <dhcwg-web-archive@ietf.org>; Sun, 25 Jan 2004 12:30:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ako5j-0001Ly-00 for dhcwg-web-archive@ietf.org; Sun, 25 Jan 2004 12:30:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ako3S-0001F9-00 for dhcwg-web-archive@ietf.org; Sun, 25 Jan 2004 12:28:15 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Ako0e-00017Q-00 for dhcwg-web-archive@ietf.org; Sun, 25 Jan 2004 12:25:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ako0M-0000LS-US; Sun, 25 Jan 2004 12:25:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aknzl-0000Kl-2D for dhcwg@optimus.ietf.org; Sun, 25 Jan 2004 12:24:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11510 for <dhcwg@ietf.org>; Sun, 25 Jan 2004 12:24:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aknze-00013j-00 for dhcwg@ietf.org; Sun, 25 Jan 2004 12:24:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aknw3-0000xt-00 for dhcwg@ietf.org; Sun, 25 Jan 2004 12:20:36 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx with esmtp (Exim 4.12) id 1AknvX-0000sC-00 for dhcwg@ietf.org; Sun, 25 Jan 2004 12:20:03 -0500
Received: from jschnizl-w2k.cisco.com (sjc-vpn2-300.cisco.com [10.21.113.44]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id i0PHJ25l027554; Sun, 25 Jan 2004 09:19:03 -0800 (PST)
Message-Id: <4.3.2.7.2.20040124180124.02052c98@wells.cisco.com>
X-Sender: jschnizl@wells.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sun, 25 Jan 2004 12:19:00 -0500
To: Naiming Shen <naiming@redback.com>
From: John Schnizlein <jschnizl@cisco.com>
Subject: Re: [dhcwg] Internet-Drafts@ietf.org: I-D ACTION:draft-shen-dhc-block-alloc-01.txt
Cc: dhcwg@ietf.org, naiming@redback.com, kishore@redback.com, souissal@redback.com, tom_soon@labs.sbc.com, phantom@kt.co.kr
In-Reply-To: <200401241728.JAA07830@redback.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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.0 required=5.0 tests=none autolearn=no version=2.60

My impression is that this document covers functionality similar the v4 prefix delegation already proposed in draft-ietf-dhc-subnet-alloc-00.txt. 

The biggest advantages of the subnet-alloc draft I can see are these:
1) Specifies the protocol features rather than the allocation behavior,
2) Avoids implications of the size of the allocated subnets,
3) Avoids unnecessary entanglements of DHCP with edge router functionality.
4) Avoids the unnecessary new component of "proxy DHCP server"

John

At 12:28 PM 1/24/2004, Naiming Shen wrote:

>This draft has been posted, please review and comment. The authors
>would like this draft to be adopted as a DHC working-group document.
>...
>        
>A new DHCP address allocation mechanism called Micro-blocking
>   is proposed in this document. It is used for DHCP proxy servers or
>   routers working with DHCP servers to maximize the IP address
>   allocation efficiency while improve dynamic routing scalability
>   in provider's networks. A DHCP sub-option within the relay agent
>   information option 82 is defined in this document. This simple
>   DHCP extension can be applied as a simple IP address-pool management
>   among multiple IP devices.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-shen-dhc-block-alloc-01.txt


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