RE: [dhcwg] <draft-ietf-dhc-agent-subnet-selection-03.txt> - Clas sfull ?

Van Aken Dirk <VanAkenD@thmulti.com> Thu, 10 October 2002 14:37 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06317 for <dhcwg-archive@odin.ietf.org>; Thu, 10 Oct 2002 10:37:12 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AEcqT14189 for dhcwg-archive@odin.ietf.org; Thu, 10 Oct 2002 10:38:52 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AEcpv14186 for <dhcwg-web-archive@optimus.ietf.org>; Thu, 10 Oct 2002 10:38:51 -0400
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06314 for <dhcwg-web-archive@ietf.org>; Thu, 10 Oct 2002 10:36:41 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AEZcv13564; Thu, 10 Oct 2002 10:35:43 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AEYav13534 for <dhcwg@optimus.ietf.org>; Thu, 10 Oct 2002 10:34:36 -0400
Received: from ns1.thmulti.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06132 for <dhcwg@ietf.org>; Thu, 10 Oct 2002 10:32:21 -0400 (EDT)
Received: from smtprelay2.thmulti.com (smtprelay2 [141.11.195.242]) by ns1.thmulti.com (8.9.3/8.9.1) with ESMTP id QAA13292; Thu, 10 Oct 2002 16:34:06 +0200 (MET DST)
Received: from parexch9.paris.thmulti.com (localhost [127.0.0.1]) by smtprelay2.thmulti.com (8.9.3/8.9.1) with ESMTP id QAA24239; Thu, 10 Oct 2002 16:34:05 +0200 (MET DST)
Received: by outlook.paris.thmulti.com with Internet Mail Service (5.5.2653.19) id <SYZGWNXJ>; Thu, 10 Oct 2002 16:34:08 +0200
Message-ID: <421CB3B9B2D2F645B548D213C0A90E55090E41@edgmsmsg01.eu.thmulti.com>
From: Van Aken Dirk <VanAkenD@thmulti.com>
To: "'Bernie Volz (EUD)'" <Bernie.Volz@am1.ericsson.se>, "'Ted Lemon'" <Ted.Lemon@nominum.com>
Cc: "'dhcwg@ietf.org'" <dhcwg@ietf.org>, Dedecker Hans <DedeckerH@thmulti.com>, Dekeyser Miek <DekeyserM@thmulti.com>, "'Dirk.Ooms@alcatel.be'" <Dirk.Ooms@alcatel.be>
Subject: RE: [dhcwg] <draft-ietf-dhc-agent-subnet-selection-03.txt> - Clas sfull ?
Date: Thu, 10 Oct 2002 16:31:37 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C27069.BDBCD9A4"
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>

If a relay agent supplies a masked IP address only, the scenario only works
fine provided the server does "longest prefix matching" on its available
pools.
If the server does not start with the pool having the smallest mask,
situations where VLSM (Variable Length Subnet Mask) is applied will not
converge no ?

-----Original Message-----
From: Bernie Volz (EUD) [mailto:Bernie.Volz@am1.ericsson.se]
Sent: Thursday 10 October 2002 2:59
To: Van Aken Dirk; 'Ted Lemon'
Cc: 'dhcwg@ietf.org'.org'; Dedecker Hans; Dekeyser Miek; 'Dirk.Ooms@alcatel.be'
Subject: RE: [dhcwg] <draft-ietf-dhc-agent-subnet-selection-03.txt> - Clas
sfull ?



There is no need to do this. What's the benefit? 

You'd have to configure the relay agent with more information than it
currently 
needs. (While in many cases the relay is probably a router and has this 
information, why is it needed?) The server can figure out the subnet without

the prefix because the server needs both the address and subnet mask length
for 
all of the subnets (at least those it will be allocating addresses on). 

Also, what happens if the server and relay agent disagree on the subnet mask

length? Suppose you wrongly configured the relay to send 20.0.0.0/23 and the

server is configured with 20.0.0.0/24? 

- Bernie 

-----Original Message----- 
From: Van Aken Dirk [ mailto:VanAkenD@thmulti.com
<mailto:VanAkenD@thmulti.com> ] 
Sent: Thursday, October 10, 2002 3:16 AM 
To: 'Ted Lemon' 
Cc: 'dhcwg@ietf.org'.org'; Dedecker Hans; Dekeyser Miek; 
'Dirk.Ooms@alcatel.be' 
Subject: RE: [dhcwg] <draft-ietf-dhc-agent-subnet-selection-03.txt> - 
Clas sfull ? 


Hi Ted, 

As you as you mentioned in the reply, it is indeed exactly the same problem 
as with giaddr. 

But why can this problem not be solved ? After all, the overloading of 
giaddr (communication with the relay agent and address pool selection) was 
defined 17 years ago (RFC951-1985). All networks were classfull at that time

but today almost all IP systems can operate in a classless environment.. 

As it is a totally new DHCP Relay Information Sub-Option, one can easily 
define two fields: IP address and IP mask or IP address and Prefix length. 

One could eventually reuse the syntax of <draft-ietf-dhc-csr-07.txt> - The 
Classless Static Route Option for DHCPv4. 

Best regards - Dirk 

                     

-----Original Message----- 
From: Ted Lemon [ mailto:Ted.Lemon@nominum.com
<mailto:Ted.Lemon@nominum.com> ] 
Sent: Tuesday 8 October 2002 11:32 
To: Van Aken Dirk 
Cc: 'dhcwg@ietf.org'.org'; Dedecker Hans; Dekeyser Miek 
Subject: Re: [dhcwg] <draft-ietf-dhc-agent-subnet-selection-03.txt> - 
Classfull ? 


> I wonder though how the DHCP server can derive a subnet from a single 
> quantity being an IP address. e.g. 20.0.0.0 can be an alias for 
> 20.0.0.0/8 
> or 20.0.0.0/29. 
> So my guess is that the only way the DHCP server can derive the subnet 
> form 
> is based on the leading bits of the address being either class A, B or 
> C. 

The DHCP server is configured with a list of subnets.   It has to be, 
to make address assignment decisions. 

This is exactly the same problem that you have if you use giaddr for 
subnet selection. 

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