Re: sockets APIs extensions for Host Identity Protocol

Keith Moore <moore@cs.utk.edu> Wed, 09 May 2007 03:20 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 1Hlcij-0000F4-Ly; Tue, 08 May 2007 23:20:05 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1Hlcii-0000Ez-Go for discuss-confirm+ok@megatron.ietf.org; Tue, 08 May 2007 23:20:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hlcii-0000Er-5N for discuss@apps.ietf.org; Tue, 08 May 2007 23:20:04 -0400
Received: from shu.cs.utk.edu ([160.36.56.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hlcig-0005za-U5 for discuss@apps.ietf.org; Tue, 08 May 2007 23:20:04 -0400
Received: from localhost (localhost [127.0.0.1]) by shu.cs.utk.edu (Postfix) with ESMTP id 4B8B71EE19F; Tue, 8 May 2007 23:20:00 -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 X8U0I2-5XaPb; Tue, 8 May 2007 23:19:55 -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 641641EE197; Tue, 8 May 2007 23:19:54 -0400 (EDT)
Message-ID: <46413DD7.8020702@cs.utk.edu>
Date: Tue, 08 May 2007 23:19:51 -0400
From: Keith Moore <moore@cs.utk.edu>
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: sockets APIs extensions for Host Identity Protocol
References: <Pine.SOL.4.64.0705041801060.14418@kekkonen.cs.hut.fi> <20070507082737.GB21759@nic.fr>
In-Reply-To: <20070507082737.GB21759@nic.fr>
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: ea4ac80f790299f943f0a53be7e1a21a
Cc: discuss@apps.ietf.org, Thomas Henderson <thomas.r.henderson@boeing.com>, Miika Komu <miika@iki.fi>
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

Stephane Bortzmeyer wrote:
>> One could conceive that such a level of indirection could be used
>> more generally outside of HIP, to enable applications to be more
>> compatible across IP versions, for instance.
>>     
>
> One important thing: this is only for the C programming language. In
> most (all?) other languages, programmers no longer handle directly IP
> addresses and thus are shielded from things like IPv4 vs. IPv6 or
> addresses vs. handles.
>   

In those cases, the programmers are also crippled and prevented from
dealing effectively with various cases that are now increasingly common
in the Intenet today: NATs,  multiple addresses for source and
destination (not all of which work equally well), IPv4 vs IPv6 (for
which the default address selection rules are woefully inadequate),
multi-faced DNS, LLMNR, etc.
> The big advice should be: use a high-level language (or, in C, a
> high-level library, like Neon - http://www.webdav.org/neon/ - or cURL
> - http://curl.haxx.se/) and you're safe from the changes in IETF
> fashions.
>   

only if you want to limit the deployability and/or efficiency of your
application.


Keith