Re: [dhcwg] Question: in RFC3046 why did Agent Subnet Mask Sub-optiondie
Simon Kelley <simon@thekelleys.org.uk> Mon, 19 March 2007 22:25 UTC
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTQI3-0001St-BA; Mon, 19 Mar 2007 18:25:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTQI2-0001Sa-TE for dhcwg@ietf.org; Mon, 19 Mar 2007 18:25:18 -0400
Received: from cpc2-cmbg4-0-0-cust458.cmbg.cable.ntl.com ([81.98.241.203] helo=thekelleys.org.uk) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTQHw-0003oc-FD for dhcwg@ietf.org; Mon, 19 Mar 2007 18:25:18 -0400
Received: from vaio.thekelleys.org.uk ([192.168.1.179]) by thekelleys.org.uk with asmtp (Exim 3.36 #1 (Debian)) id 1HTQCK-0002Zc-00; Mon, 19 Mar 2007 22:19:24 +0000
Message-ID: <45FF0D10.60600@thekelleys.org.uk>
Date: Mon, 19 Mar 2007 22:22:08 +0000
From: Simon Kelley <simon@thekelleys.org.uk>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060717 Debian/1.7.13-0.2ubuntu1
X-Accept-Language: en
MIME-Version: 1.0
To: "David W. Hankins" <David_Hankins@isc.org>
Subject: Re: [dhcwg] Question: in RFC3046 why did Agent Subnet Mask Sub-optiondie
References: <45EDD246.20605@thekelleys.org.uk> <403B5316AD7A254C9024875BAE481D4E6C314F@zeus.incognito.com> <45EDDE8C.1090704@thekelleys.org.uk> <20070308180602.GB26203@isc.org> <45F14A04.8080500@thekelleys.org.uk> <20070319094329.GM3685@isc.org>
In-Reply-To: <20070319094329.GM3685@isc.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: DHC WG <dhcwg@ietf.org>
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
David W. Hankins wrote: > On Fri, Mar 09, 2007 at 11:50:28AM +0000, Simon Kelley wrote: > >>>I don't like the vector to this line of reasoning. >> >>Would you care to explain why? > > > Sure. > > >>You should look at dnsmasq, which makes it work fine. > > > I know dnsmasq works, I meant for the relay case. > > Adopting a change like this would create a 'subset of compatibility' > where dnsmasq is compatible with certain relays (and network designs > it turns out) but not others. > > It "doesn't work" for any device that adds relay agent options and > either doesn't know about any prefixes on that network (such as a > switch), or doesn't know about /all/ of the prefixes on that network > (such as one of multiple routers, or one of multiple hosts on that > network). > > If it were just a 'dnsmasq works with relay A but not B' thing, I > might be convinced if there were a really good reason (but I think > 'not configuring the network mask' isn't good enough). But 'network > architecture A but not B' is pushing it even further for me. This is already the situation for dnsmasq: currently "shared networks" work with directly connected networks but for networks behind relays, shared networks are not allowed. So providing this facility doesn't add another exception, it allows networks behind relays to work in the same way as directly connected networks and removes the anomally. For relays which don't support the new option, nothing changes. > > DHCP tries hard not to care how the network is put together. It is > a bad vector to create DHCP protocol work that dictates a network > design, I don't think it does. > and intentionally introduces relay<->server compatibility > problems. > I have some sympathy with this, but, at least for dnsmasq, it's possible to argue that it reduces compatibility problems. Cheers, Simon. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Question: in RFC3046 why did Agent Subnet… Simon Kelley
- Re: [dhcwg] Question: in RFC3046 why did Agent Su… Mark Stapp
- RE: [dhcwg] Question: in RFC3046 why did Agent Su… Andre Kostur
- Re: [dhcwg] Question: in RFC3046 why did Agent Su… Simon Kelley
- Re: [dhcwg] Question: in RFC3046 why did Agent Su… Mark Stapp
- Re: [dhcwg] Question: in RFC3046 why did Agent Su… Simon Kelley
- Re: [dhcwg] Question: in RFC3046 why did Agent Su… David W. Hankins
- Re: [dhcwg] Question: in RFC3046 why did Agent Su… Simon Kelley
- RE: [dhcwg] Question: in RFC3046 why did Agent Su… Andre Kostur
- Re: [dhcwg] Question: in RFC3046 why did Agent Su… Simon Kelley
- Re: [dhcwg] Question: in RFC3046 why did Agent Su… Ted Lemon
- Re: [dhcwg] Question: in RFC3046 why did Agent Su… Ralph Droms
- Re: [dhcwg] Question: in RFC3046 why did Agent Su… Ted Lemon
- RE: [dhcwg] Question: in RFC3046 why did Agent Su… Bernie Volz (volz)
- Re: [dhcwg] Question: in RFC3046 why did Agent Su… David W. Hankins
- Re: [dhcwg] Question: in RFC3046 why did Agent Su… Simon Kelley
- Re: [dhcwg] Question: in RFC3046 why did Agent Su… Simon Kelley