Re: [dhcwg] Minor inconsistencies with draft-ietf-dhc-packetcable-04.txt
Ted Lemon <Ted.Lemon@nominum.com> Thu, 14 November 2002 16:55 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 LAA24326 for <dhcwg-archive@odin.ietf.org>; Thu, 14 Nov 2002 11:55:21 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gAEGvTw08536 for dhcwg-archive@odin.ietf.org; Thu, 14 Nov 2002 11:57:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGvTv08533 for <dhcwg-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 11:57:29 -0500
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 LAA24322 for <dhcwg-web-archive@ietf.org>; Thu, 14 Nov 2002 11:54:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGs1v08332; Thu, 14 Nov 2002 11:54:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGklv08072 for <dhcwg@optimus.ietf.org>; Thu, 14 Nov 2002 11:46:47 -0500
Received: from toccata.fugue.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24006; Thu, 14 Nov 2002 11:44:08 -0500 (EST)
Received: from nominum.com (dsl-64-193-175-153.telocity.com [64.193.175.153]) by toccata.fugue.com (8.11.6/8.6.11) with ESMTP id gAEGfN213567; Thu, 14 Nov 2002 10:41:23 -0600 (CST)
Date: Thu, 14 Nov 2002 10:46:43 -0600
Subject: Re: [dhcwg] Minor inconsistencies with draft-ietf-dhc-packetcable-04.txt
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ietf@ietf.org, dhcwg@ietf.org
To: Bud Millwood <budm@weird-solutions.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <200211141155.09167.budm@weird-solutions.com>
Message-Id: <A805EF52-F7F0-11D6-B15B-00039317663C@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
> Second, I'd rather see suboption 3 broken out into two different > suboptions > denoting the different data types. I'm not aware of any other DHCP > option > that has a type field. This is an excellent point. Options with variable formats _always_ require special code in the DHCP server to support them. I think the authors should choose either an IP address or an FQDN as the format in which the SIP server's IP address is communicated. If this is not possible, then the draft should at least be consistent with the SIP RFC (rfc3361), which does something similar, but chooses exactly the opposite meaning for the flag byte. The problem with allowing the option to contain either an FQDN or an IP address is that now the DHCP server has to have special code to support this specific option. Most DHCP servers (well, admittedly, I only have experience with two) are table-driven with respect to option formats, so this is a big deal. For example, because of the need for a special hack, I don't know when or if the ISC DHCP server will support the SIP option described in rfc3361, since I am no longer working on it. If SIP had chosen one or the other format, it would already be supported. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg