] more broadly than that, a full dns client-side api is
] needed. we drafted one a couple of years ago but couldn't
] find the funding for it. c and c programmers should
] have the same high level access to the dns protocol that
] perl programmers have (through the excellent Net::DNS
] module).

I finally pinged the IETF DNS WG about resolver API foo that
I've been whining about for years. Here's Vixie's initial reply.

Re: SRV resolver API?

]
] As long suspected by some, the IETF is going to be
] closing up the Mail Transfer Agent Authentication in DNS
] (MARID) Working Group according to today's post by Ted
] Hardie, co-AD for Applications. Larry Seltzer of eWeek
] was right on target about this:
]
] The rest of the SID standards process will now be a
] waste of time thanks to Microsoft, and the other
] participants will afterwards pick up the pieces and get
] the job done with another spec.

MARID is Dead

]
] The marketing effort that has been invested in this
] report is impressive. A friend of mine who has no
] Internet-specific expertise (although interested in
] technology generally) heard about it on the radio here in
] Australia and asked me if I knew of it. But the fact that
] the report is being sold as a product makes it
] intrinsically less valuable to me. Not only can I not
] afford to buy it (as a PhD student), I wouldn't consider
] it very valuable if I were given a complimentary copy,
] since the limited readership reduces the amount of
] intelligent discussion available on it.

Can TCP/IP Survive?

] Ultimately, many of the issues with domain names arise as
] the result of efforts to use the DNS as a directory.
] While, at the time this document was written, sufficient
] pressure or demand had not occurred to justify a change,
] it was already quite clear that, as a directory system,
] the DNS is a good deal less than ideal. This document
] suggests that there actually is a requirement for a
] directory system, and that the right solution to a
] searchable system requirement is a searchable system, not
] a series of DNS patches, kludges, or workarounds.

RFC3467: Role of the DNS

] The grand city of Philadelphia unveiled today an
] ambitious plan to coat the city with Wi-Fi, using a mix
] of public and private funds to provide the service.

!!!

Philly goes Wi-Fi crazy | The Register

Reuters is running a story that Vint Cerf announced at the ICANN
meeting that ICANN is "turning on IPv6." The story is scant
on details and icann.org has no information. I think they're maybe
talking about publishing IPv6 addresses (IN AAAA) for root servers...
anyone know anything else?

U:
Japan and Korea have apparently "turned it on" insofar as they've
published ipv6 addrs for their root servers.

$ dig -t aaaa a.dns.jp

...

;; QUESTION SECTION:
;a.dns.jp. IN AAAA

;; ANSWER SECTION:
a.dns.jp. 96996 IN AAAA 2001:dc4::1

] Binc IMAP is a well designed, modular IMAP server for
] Maildir. Its goals are to be secure, stable, and fast,
] yet flexible and easy to maintain.

"Binc is not Courier!" I've been using this with QMail for awhile now. Its written in C++ and the authors are less "politically fussy" than Courier's.

BincIMAP

]
] This article proposes the reservation of a special use
] TLD to allow a more convenient addressing of devices by
] general physical location or context.

I'm going to come out and say that this is *not* what DNS is for
and that this is a bad idea.

Top-Level Domains for Addressing by Physical Context

] // getsrvbyname.c -- A trivial implementation of a DNS
] // SRV [RFC2782] resolver.

Here's my code. Probably buggy. BSD license.

getsrvbyname()

] In my mind, the single largest technical issue with
] SiteFinder was that of the assumption that the WWW is the
] Internet - i.e., that a wildcard for Web users wouldn't
] affect other services. This, obviously, is not the case -
] A resource records are protocol-agnostic, as we all know.
] However, there is a rough equivalent to A RRs which are
] protocol-specific: SRV records.

(I think Tom blogged this but I lost it)

Looks like someone beat me to it. I wonder if he has code, though :P

Read on down the thread; sounds like

_http._tcp.*.com IN SRV ...

is not kosher ... but at the same time breaks much less than

*.com IN A ...

[sitefinder-tech-discuss] A small technical suggestion