] This is a big week for Apple. Last week the company
] unveiled the Windows version of its popular, free iTunes
] music-downloading software - and tomorrow, it will
] release Mac OS X version 10.3 ( or Panther), the next
] edition of Apple's three-year-old operating system.

For those of you who (like me) don't pay too much attention to Apple...

Apple's Latest 0.1 Adds a Lot

]
] Google is considering holding a massive online auction of
] shares early next year in an initial public offering that
] investment bankers predict could value the internet
] search-engine company at more than $15bn.

Google Said to Consider Online Auction of I.P.O. Shares

Heh.

Fact Squad Radio: We're don't have an agenda... no... really...

Decius wrote:
] ] Host Identity Protocol [3] (HIP) defines a mechanism that
] ] decouples the transport layer from the internetworking
] ] layer, and introduces a new Host Identity namespace. When
] ] a host uses HIP, the transport layer sockets and IPsec
] ] Security Associations are not bound to IP addresses but
] ] to Host Identifiers. This document specifies how the
] ] mapping from Host Identifiers to IP addresses can be
] ] extended from a static one-to-one mapping into a dynamic
] ] one-to-many mapping. This enables end-host mobility and
] ] multi-homing.
]
]
] Abaddon and I spent some time last summer working on a protocl
] called Adaptive Addressing Protocol (AAP). It was an attempt
] to make Mobile IP less silly by allowing hosts to change their
] IP addresses without dropping connections. It did so by
] associating connections with a unique identifier, secured by a
] Diffie Hellman key exchange. Last night, Jeremy points me at
] this. This is APP, basically. Its amazing how close our
] designs are. Its also *really* frustrating. We were going to
] have a working demo this weekend for Phreaknic.
]
] I'm going to read through this stuff and see if there are any
] design decisions that we made that might be of value to this
] working group. Having said that, its worth memeing this
] documentation. This is the right answer for mobile IP
] and it will probably be the answer we end up with for
] multihoming of small networks because deploying something like
] this is less expensive then renumbering the internet
] geographically.

I've had this idea before as well. Yay!

RE: Host Identity Protocol

] "We can indemnify our users and if anybody's nervous
] about [IBM Unix flavour] AIX or Linux we've got Solaris
] on x86 [32-bit processors] and Solaris in the data
] centre. We run like the wind. We're open. There are no
] down sides."

McNealy's hysteria reminds me of the Iraqi Information Minister during the war...

silicon.com - McNealy: 'I'm thrilled to death SCO can't revoke our Unix licence'

] Linux users outside of the Fortune 1000 cannot buy the
] software license The SCO Group Inc. has been offering
] since August as a way to protect themselves against legal
] action, the company confirmed Tuesday.
]
] "We're trying to execute on this licensing plan (by)
] really starting to deal with the very top players and
] working our way down," said Blake Stowell, a SCO
] spokesman. "After the company has rolled this out to the
] Fortune 1000 and we're satisfied with how the program is
] going ... we'll then roll it down to small to medium
] businesses."

WTF?!

InfoWorld: SCO license currently for biggest users only: October 22, 2003: By : Platforms

]
] BayStar Capital entered the open-source spotlight last
] week with its $50 million investment in the SCO Group,
] which is embroiled in legal wrangling over Linux and Unix
] with IBM and Red Hat. What the companies didn't say so
] loudly, though, is that $30 million of BayStar's
] investment in SCO was from the Royal Bank of Canada,
] according to a Thursday regulatory filing with the U.S.
] Securities and Exchange Commission. BayStar itself
] invested the remaining $20 million.

Weird...

News: Royal Bank of Canada invests in SCO

] // 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

Rattle wrote:

] ] *.com IN SRV host=sitefinder.verisign.com port=80
] priority=1
] ] weight=1
]
] However, you would need a protocol="tcp" flag along with your
] port="80" in your example. :) There are some details that
] need to be hashed out, but I like the general idea.

Oops ... it would look more like this:

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

in other words, for every domain q.com, synthesize a record _http._tcp.q.com

A client asking for the HTTP SRV record for a non-existant domain would get sitefinder; a client asking for the A would get NXDOMAIN.

RE: A DNS RR for specifying the location of services (DNS SRV) (RFC2782)