Re: [dhcwg] Re: DHCP behind NAT
Ted Lemon <mellon@nominum.com> Sat, 01 September 2001 03:08 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 XAA22564; Fri, 31 Aug 2001 23:08:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA02864; Fri, 31 Aug 2001 23:08:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA02838 for <dhcwg@ns.ietf.org>; Fri, 31 Aug 2001 23:07:58 -0400 (EDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22499 for <dhcwg@ietf.org>; Fri, 31 Aug 2001 23:06:34 -0400 (EDT)
Received: from grosse.bisbee.fugue.com (dsl081-147-128.chi1.dsl.speakeasy.net [64.81.147.128]) by toccata.fugue.com (8.11.3/8.6.11) with ESMTP id f81320f18308; Fri, 31 Aug 2001 20:02:01 -0700 (PDT)
Received: from grosse.bisbee.fugue.com (localhost [127.0.0.1]) by grosse.bisbee.fugue.com (8.11.3/8.6.11) with ESMTP id f7VGslj00311; Fri, 31 Aug 2001 12:54:47 -0400 (EDT)
Message-Id: <200108311654.f7VGslj00311@grosse.bisbee.fugue.com>
To: Bernard Dugas <bernard.dugas@is-production.com>
cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Re: DHCP behind NAT
In-Reply-To: Message from Bernard Dugas <bernard.dugas@is-production.com> of "Wed, 29 Aug 2001 11:32:17 +0200." <3B8CB6A1.FA7237D7@is-production.com>
Date: Fri, 31 Aug 2001 12:54:47 -0400
From: Ted Lemon <mellon@nominum.com>
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
There's no way to make your proposed change RFC2131 at this late date. Too many devices have been deployed that follow the current protocol specification. In order to do what you need, you have to come up with a different method. I would recommend that you investigate the subnet selection option. Send the address to which you want the reply sent in giaddr, and use the subnet-selection-option to store the address you would otherwise have stored in giaddr. I agree with you, by the way, that your proposed way of doing this is better than the way that RFC2131 does it. The problem is not that you're wrong, but that you're too late - this behavior was canonicalized in RFC951, and that's the last time it was possible to fix this the way you propose. :'} _MelloN_ _______________________________________________ dhcwg mailing list dhcwg@ietf.org http://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Re: DHCP behind NAT Bernard Dugas
- Re: [dhcwg] Re: DHCP behind NAT Ted Lemon
- Re: [dhcwg] Re: DHCP behind NAT Bernard Dugas
- Re: [dhcwg] Re: DHCP behind NAT Ted Lemon