Re: [dhcwg] WG last calls on several WG documents

Said Ouissal <souissal@redback.com> Sun, 19 November 2006 23:52 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GlwSH-0001jq-NI; Sun, 19 Nov 2006 18:52:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GlwSG-0001jh-4k for dhcwg@ietf.org; Sun, 19 Nov 2006 18:52:08 -0500
Received: from prattle.redback.com ([155.53.12.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GlwSE-00066n-SG for dhcwg@ietf.org; Sun, 19 Nov 2006 18:52:08 -0500
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 7F28828676A; Sun, 19 Nov 2006 15:52:06 -0800 (PST)
Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14054-08; Sun, 19 Nov 2006 15:52:06 -0800 (PST)
Received: from SOUIS-TM5XP.redback.com (login004.redback.com [155.53.12.57]) by prattle.redback.com (Postfix) with ESMTP id B52B1286767; Sun, 19 Nov 2006 15:52:05 -0800 (PST)
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 20 Nov 2006 00:50:52 +0100
To: Ralph Droms <rdroms@cisco.com>, dhcwg <dhcwg@ietf.org>
From: Said Ouissal <souissal@redback.com>
Subject: Re: [dhcwg] WG last calls on several WG documents
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-Id: <20061119235205.B52B1286767@prattle.redback.com>
X-Virus-Scanned: by amavisd-new at redback.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: Stig Venaas <Stig.Venaas@uninett.no>
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>
Errors-To: dhcwg-bounces@ietf.org

Ralph,

At 12:15 16-11-2006, Ralph Droms wrote:
>draft-ietf-dhc-subnet-alloc-04
>   Subnet Allocation Option
>   Need to review IPR claims related to this document

One action item which remains open with regards to this draft was the 
discussion (and decision) of merging this draft with the micro-block 
allocation draft (draft-shen-dhc-block-alloc-00.txt).

To refresh your mind, the view carried by the authors of the 
micro-block allocation draft is that while 
draft-ietf-dhc-subnet-alloc-04 addresses the ability to assign a 
subnet to a dhcp client, it does not well enough address the ability 
to assign a subnet to a DHCP proxy or a "remote DHCP server", which 
in turn can re-assign single IPs to clients. Especially if this DHCP 
proxy is co-located within an edge router, it allows for more 
efficient provisioning and network routing information annoucement 
for reachability reasons.

To be more precise, draft-ietf-dhc-subnet-alloc-04 does address the 
ability to request a subnet (as a client) so that it can be then 
servicing (mentioned in the draft as hierarchical DHCP servers) other 
clients, the main difference is that for Micro-Block the mode of 
operation is based around an intermediate DHCP proxy agent who 
leverages option 82 field and piggy-backs on a true client DHCP IP 
address assignment process. This is a more simple mode of operation 
and does not require a DHCP client operating on the intermediate router/agent.

Tx,
Said.  



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