MIME-Version: 1.0
content-type: text/plain; charset="utf-8"
Message-ID: <B1E78D234B7B479A9123FA00147B9FCE@sb.litts.net>
Subject: OMAPI versioning
Thread-Index: ActtQA1wKyVw1CdPT3yVVAUl3zp5rQ==
Date: Sat, 16 Oct 2010 10:40:18 -0400
To: <dhcp-bugs@isc.org>
Content-Transfer-Encoding: 7bit
From: "Timothe Litt" <litt@acm.org>
Content-Length: 1052

dhcpd 4.1.1-P1

In trying to work with the OMAPI/dhcpctl libraries,
it became clear that the interface is unstable.

As noted in the dhcpd man page about the failover-object's state:
"Note that some of the above values have changed since DHCP 3.0.x."

Maybe this was required - but as far as I can tell, there
is no way for an application to determine the version of
DHCP on the other end of the wire.  So interpreting the
value in the state variable correctly is impossible in
the general case.

Omapi has a version in the protocol - but it is not exposed
thru dhcpctl.  And even if it was, that version remains 1.0.

I'd like to see:
 o API changes increment some version number.
 o That version number exposed via the dhcpctl API.

Ideally, the version would be an API version, but it
would also be useful if something (say, the control 
object) also output the dhcpd server version.

Thanks.

---------------------------------------------------------
This communication may not represent my employer's views,
if any, on the matters discussed.