[prev in list] [next in list] [prev in thread] [next in thread] 

List:       namedroppers
Subject:    Re: SRV resolver API?
From:       Paul Vixie <paul () vix ! com>
Date:       2004-11-16 16:51:27
Message-ID: 20041116165127.DB54A13E14 () sa ! vix ! com
[Download RAW message or body]

> Paul, is the funding needed for the work to get the standardization
> pushed through the various standards bodies or for the implementation?

depends on which standards body you mean.  the advanced bsd api rfc for
ipv6 seems to have resulted, for the first time ever, in portability of
socket-api applications.  the posix socket api wasn't able to achieve
this in the ipv4 days -- there were way more #ifdef's then than now.

i believe two things.  first, in the power of implementation.  the glibc
project has created a defacto standard that's a superset of ansi/posix,
and the original bsd socket api (by which i intend to include things like
gethostbyname) and the original bsd dns api (by which i mean to include
things like res_query()) have been wildly successful, widely emulated
on non-unix platforms, and generally acceptable.

second, in the danger of the power of implementation.  more reviewers and
more creative minds would have caught a lot of errors and omissions early
on which are still painful today because implementation was so powerful.

while ietf's charter is all about on-the-wire protocols and formats, it
did good work with the advanced bsd api rfc for ipv6, and i think that
doing an advanced dns api rfc would be just as successful.

isc's original funding request to the "bind vendors" on this topic 
included both an openly-developed api, and an open-source implementation
of it.

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>
[prev in list] [next in list] [prev in thread] [next in thread]