IETF Logo Mail Archive

Re: [dhcwg] Confusion on RFC 3011 subnet selection option

Ted Lemon <mellon@nominum.com> Tue, 05 February 2002 16:59 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08254 for <dhcwg-archive@odin.ietf.org>; Tue, 5 Feb 2002 11:59:22 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id LAA15124 for dhcwg-archive@odin.ietf.org; Tue, 5 Feb 2002 11:59:25 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA10298; Tue, 5 Feb 2002 11:14:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA10277 for <dhcwg@optimus.ietf.org>; Tue, 5 Feb 2002 11:14:27 -0500 (EST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06268 for <dhcwg@ietf.org>; Tue, 5 Feb 2002 11:14:24 -0500 (EST)
Received: from green.bisbee.fugue.com (dsl-64-193-175-153.telocity.com [64.193.175.153]) by toccata.fugue.com (8.11.3/8.6.11) with ESMTP id g15FvIX07413; Tue, 5 Feb 2002 07:57:19 -0800 (PST)
Received: from dechen (localhost [127.0.0.1]) by green.bisbee.fugue.com (8.10.2/8.6.11) with ESMTP id g15G0bM02743; Tue, 5 Feb 2002 10:00:37 -0600 (CST)
Date: Tue, 05 Feb 2002 10:00:37 -0600
Subject: Re: [dhcwg] Confusion on RFC 3011 subnet selection option
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v480)
Cc: dhcwg@ietf.org, Matt Frick <mfrick@netopia.com>
To: Glenn Waters <gww@nortelnetworks.com>
From: Ted Lemon <mellon@nominum.com>
In-Reply-To: <0D7FC1D8D861D511AEA70002A52CE5E6013703ED@zcard0ke.ca.nortel.com>
Message-Id: <7EB34DD9-1A51-11D6-ABCA-00039317663C@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.480)
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Content-Transfer-Encoding: 7bit

Glenn, I'd just like to point out that DHCP packets are never sent on 
subnets.   They are sent on links.   Normally we can get away with 
confusing subnets for links, but in the case of DHCP, it winds up creating 
a great deal of confusion.   A DHCP server cannot tell on what subnet a 
client's broadcast was sent - all it can tell is on what link a client's 
broadcast was sent.

So unfortunately there is a natural opportunity to become confused about 
what the subnet selection option does, which I believe is what happened 
here.   I hate to suggest updating anyhting that's made it to RFC when we 
have so much other work that's still pending, but it might be worth adding 
some clarification about this.


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

v2.23.0 | Report a Bug | By Email