RE: [dhcwg] Leasequery: should it be standardized?

Mark Stapp <mjs@cisco.com> Thu, 27 February 2003 21:40 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 QAA25081 for <dhcwg-archive@odin.ietf.org>; Thu, 27 Feb 2003 16:40:52 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1RLp1Y24321 for dhcwg-archive@odin.ietf.org; Thu, 27 Feb 2003 16:51: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 h1RLp1p24318 for <dhcwg-web-archive@optimus.ietf.org>; Thu, 27 Feb 2003 16:51:01 -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 QAA25076 for <dhcwg-web-archive@ietf.org>; Thu, 27 Feb 2003 16:40:20 -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 h1RLnNp24231; Thu, 27 Feb 2003 16:49:23 -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 h1RLmRp24198 for <dhcwg@optimus.ietf.org>; Thu, 27 Feb 2003 16:48:27 -0500
Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24985 for <dhcwg@ietf.org>; Thu, 27 Feb 2003 16:37:46 -0500 (EST)
Received: from mjs-w2k01.cisco.com (dhcp-161-44-149-90.cisco.com [161.44.149.90]) by sj-msg-core-3.cisco.com (8.12.2/8.12.6) with ESMTP id h1RLfSP8009280; Thu, 27 Feb 2003 13:41:28 -0800 (PST)
Message-Id: <4.3.2.7.2.20030227163310.01e32248@goblet.cisco.com>
X-Sender: mjs@goblet.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 27 Feb 2003 16:41:10 -0500
To: Steve Gonczi <steve@relicore.com>
From: Mark Stapp <mjs@cisco.com>
Subject: RE: [dhcwg] Leasequery: should it be standardized?
Cc: dhcwg@ietf.org
In-Reply-To: <BFELJLKGHEJOPOPGJBKKEEHACEAA.steve@relicore.com>
References: <4.3.2.7.2.20030226171308.01dd94b8@goblet.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>

I don't have much interest in a new, tcp-based, general-purpose query 
protocol. There was interest in a way for dhcp speakers to ask some 
questions, and that's what leasequery offers, and it's been implemented and 
deployed by several vendors. The point was that the questions be askable by 
devices and applications that already knew dhcp.

-- Mark

At 04:16 PM 2/27/2003 -0500, Steve Gonczi wrote:
>Greetings,
>
>You guys are clearly on to something here.
>
>I have just re-read the 04 draft. It proposes a solution to a rather
>specific problem. It would indeed make sense to generalize it into
>a more broadly applicable query protocol.
>
>Let's try bit more radical tack:
>
>It would be useful to add a list-query capability, so that the
>protocol could return lists of addresses, based on a flexible set of
>search criteria.
>E.g.: all assigned IP-s on subnet x. Also, the query could enumerate the
>pieces of information e desired.(e.g. expiration time, client id...
>whatever)
>
>The currently specified 04 draft would be a functional subset of the
>general purpose protocol.
>
>BTW.. I am surprised to see that the messaging formats is
>very much inspired by the DHCP/BOOTP message structure.
>
>Since this would be a brand new protocol, I fail to see the need to
>carry this baggage. Err.. why do we need to have the bootp header in
>the messages?
>
>I respectfully propose to lay out the protocol messages
>in a compact manner, fitted to the need of the
>query protocol itself.
>
>For all intensive purposes, the protocol could even be TCP based,
>similar to the failover protocol.
>
>If there is sufficient interest, I will be glad to provide some
>examples of "general purpose" query and response formats.
>
>/sG
>
>
>
>-----Original Message-----
>From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org]On Behalf Of
>Mark Stapp
>Sent: Wednesday, February 26, 2003 5:38 PM
>To: Thomas Narten
>Cc: Bernie Volz (EUD); 'Kevin A. Noll'; Kim Kinnear; dhcwg@ietf.org;
>Ralph Droms
>Subject: RE: [dhcwg] Leasequery: should it be standardized?
>
>
> > I agree with Bernie and Kevin. I particularly liked the 'data-centric'
> > words in Kevin's post. DHCP servers tend to know information about DHCP
> > clients and IP addresses, they're the sole authority for that information,
> > and that information may be useful to other applications or entities on
>the
> > network....
>
>.....rest of the discussion clipped......
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/dhcwg

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