Re: [dhcwg] draft-ietf-dhc-dhcpv4-bulk-leasequery-01.txt
Kim Kinnear <kkinnear@cisco.com> Mon, 02 November 2009 16:06 UTC
Return-Path: <kkinnear@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 833FA3A6A51 for <dhcwg@core3.amsl.com>; Mon, 2 Nov 2009 08:06:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.885
X-Spam-Level:
X-Spam-Status: No, score=-7.885 tagged_above=-999 required=5 tests=[AWL=0.714, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FVgsuujTQAh4 for <dhcwg@core3.amsl.com>; Mon, 2 Nov 2009 08:06:21 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 683873A6A50 for <dhcwg@ietf.org>; Mon, 2 Nov 2009 08:06:21 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAOuS7kqtJV2Z/2dsb2JhbADGJ5ZkhDwEgWI
X-IronPort-AV: E=Sophos;i="4.44,667,1249257600"; d="scan'208";a="66026209"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rtp-iport-2.cisco.com with ESMTP; 02 Nov 2009 16:06:40 +0000
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id nA2G6eZ5029005; Mon, 2 Nov 2009 16:06:40 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 2 Nov 2009 11:06:40 -0500
Received: from kkinnear-wxp01.cisco.com ([161.44.65.168]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 2 Nov 2009 11:06:39 -0500
Message-Id: <4.3.2.7.2.20091102104728.0285ac68@email.cisco.com>
X-Sender: kkinnear@email.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 02 Nov 2009 11:05:26 -0500
To: Bud Millwood <budm@weird-solutions.com>, dhcwg@ietf.org
From: Kim Kinnear <kkinnear@cisco.com>
In-Reply-To: <200911021018.56151.budm@weird-solutions.com>
References: <4.3.2.7.2.20091030150748.03e804a8@email.cisco.com> <4.3.2.7.2.20091026092036.02db5978@email.cisco.com> <4.3.2.7.2.20091030150748.03e804a8@email.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginalArrivalTime: 02 Nov 2009 16:06:39.0889 (UTC) FILETIME=[7645B810:01CA5BD6]
Cc: volz@cisco.com, RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com>, Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv4-bulk-leasequery-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2009 16:06:22 -0000
Bud, A couple of comments, preceded by Kim: At 04:18 AM 11/2/2009, Bud Millwood wrote: >Well thanks for your patience; I'm jumping in here at the last minute (as >usual) and not articulating myself particularly well. > >My comments are inline, preceded by 'Bud:'. >[...] >I would say that subclassing an integer from a string does make me slightly >ill. Oh darn, if only I'd use three character letter codes for the various status codes, I don't think we would be having this conversation. So let me try that one more time -- what if, instead of characters that translate into numbers, we simply said that in the context of bulk leasequery, the first three characters MUST be one of an accepted set corresponding to various status codes. And we fix the status codes to have alphabetic "codes" instead of numeric ones so people don't get confused with what we are tying to do. If that doesn't work for you, we'll just burn another option code. >Bud: >I was thinking about the fact that we are short on option numbers. > >In my world, suboptions are processed very much like top-level options, so it >seems reasonable to simply declare a new subencoded option with, say, tag 254 >and declare that when we run out of top-level option numbers, we will start >declaring rfc-standard dhcp options inside option 254. That was my train of >thought. Not directly related to bulk leasequery, but then again indirectly >related to any proposal that requires an option code. While this is certainly possible, and may well be the choice when we truly run out, I believe that processing such options is intrinsically more complex than processing normal, first-class options. There are a lot of issues to work out, not least the fact that many servers give users the ability to define custom options. Defining custom options which are sub-encoded is just that much more complex for users. In addition, there are various difficulties in dealing with sub-options that are really first class options -- but that exist in a sub-option name (number) space. Issues that can certainly be worked out, of course, and are not all that hard to deal with. Still, these all need to be specified in detail, and code has to be written in a number of servers in the same way in order to make all of this work. So, while conceptually simple, I think most folks would like to avoid this as long as possible. Maybe forever. I know that I would! [In large part because the code to do all of this provides *no* ultimate value or increased capability to the end-user except indirectly through the increase in option space. Which is why I'm trying to conserve said option space.] But if you don't like the three character status codes, we'll burn an option for this and that will be that. Cheers -- Kim
- [dhcwg] draft-ietf-dhc-dhcpv4-bulk-leasequery-01.… Kim Kinnear
- Re: [dhcwg] draft-ietf-dhc-dhcpv4-bulk-leasequery… Bud Millwood
- Re: [dhcwg] draft-ietf-dhc-dhcpv4-bulk-leasequery… Kim Kinnear
- Re: [dhcwg] draft-ietf-dhc-dhcpv4-bulk-leasequery… Bud Millwood
- Re: [dhcwg] draft-ietf-dhc-dhcpv4-bulk-leasequery… Kim Kinnear
- Re: [dhcwg] draft-ietf-dhc-dhcpv4-bulk-leasequery… Bernie Volz (volz)
- Re: [dhcwg] draft-ietf-dhc-dhcpv4-bulk-leasequery… Bud Millwood