Re: sockets APIs extensions for Host Identity Protocol

Keith Moore <moore@cs.utk.edu> Wed, 09 May 2007 03:24 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlcnE-0003mE-Gd; Tue, 08 May 2007 23:24:44 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HlcnD-0003jF-Gv for discuss-confirm+ok@megatron.ietf.org; Tue, 08 May 2007 23:24:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlcnD-0003iF-6t for discuss@apps.ietf.org; Tue, 08 May 2007 23:24:43 -0400
Received: from shu.cs.utk.edu ([160.36.56.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlcnC-0007XJ-0Q for discuss@apps.ietf.org; Tue, 08 May 2007 23:24:43 -0400
Received: from localhost (localhost [127.0.0.1]) by shu.cs.utk.edu (Postfix) with ESMTP id 978CC1EE1A5; Tue, 8 May 2007 23:24:41 -0400 (EDT)
X-Virus-Scanned: by amavisd-new with ClamAV and SpamAssasin at cs.utk.edu
Received: from shu.cs.utk.edu ([127.0.0.1]) by localhost (shu.cs.utk.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kq2NPOyLaSPs; Tue, 8 May 2007 23:24:37 -0400 (EDT)
Received: from lust.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182]) by shu.cs.utk.edu (Postfix) with ESMTP id B02C01EE179; Tue, 8 May 2007 23:24:36 -0400 (EDT)
Message-ID: <46413EF3.1090302@cs.utk.edu>
Date: Tue, 08 May 2007 23:24:35 -0400
From: Keith Moore <moore@cs.utk.edu>
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To: der Mouse <mouse@Rodents.Montreal.QC.CA>
Subject: Re: sockets APIs extensions for Host Identity Protocol
References: <Pine.SOL.4.64.0705041801060.14418@kekkonen.cs.hut.fi> <31BC7A8C1A51004A84E08DEF@[10.1.110.5]> <200705072216.SAA06179@Sparkle.Rodents.Montreal.QC.CA>
In-Reply-To: <200705072216.SAA06179@Sparkle.Rodents.Montreal.QC.CA>
X-Enigmail-Version: 0.95.0
OpenPGP: id=E1473978
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: discuss@apps.ietf.org
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

> Something wrong with getaddrinfo()?  It certainly could use something
> HIPish under the hood, if some implementor decided to.
>   

getaddrinfo() is a disaster.  not only is it the most baroque call in
the entire sockets API, it also invites implementors to abuse its
semantics in numerous ways (for instance, looking up SRV records for
apps that weren't intended to use SRV records).


Keith