Re: sockets APIs extensions for Host Identity Protocol

Keith Moore <moore@cs.utk.edu> Wed, 09 May 2007 03:22 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 1HlclK-0001bk-CE; Tue, 08 May 2007 23:22:46 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HlclJ-0001bJ-3M for discuss-confirm+ok@megatron.ietf.org; Tue, 08 May 2007 23:22:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlclI-0001Zj-Om for discuss@apps.ietf.org; Tue, 08 May 2007 23:22:44 -0400
Received: from shu.cs.utk.edu ([160.36.56.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlclH-0006b5-IE for discuss@apps.ietf.org; Tue, 08 May 2007 23:22:44 -0400
Received: from localhost (localhost [127.0.0.1]) by shu.cs.utk.edu (Postfix) with ESMTP id 1F2CF1EE19F; Tue, 8 May 2007 23:22:43 -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 3cvoJUOaSmAi; Tue, 8 May 2007 23:22:38 -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 14C241EE197; Tue, 8 May 2007 23:22:38 -0400 (EDT)
Message-ID: <46413E7D.5060403@cs.utk.edu>
Date: Tue, 08 May 2007 23:22:37 -0400
From: Keith Moore <moore@cs.utk.edu>
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To: Chris Newman <Chris.Newman@Sun.COM>
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]>
In-Reply-To: <31BC7A8C1A51004A84E08DEF@[10.1.110.5]>
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: 79899194edc4f33a41f49410777972f8
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

> If I change my "connectbyname" code again, I will change it once more
> to use a new OS API that hides all the v4 vs. v6 vs. HIP vs. whatever
> junk, preferably to something much simpler than the code today.  If
> such an API isn't produced, I will be very reluctant to change that
> code no matter how cool HIP might or might not be.

If you can figure out how to write that kind of code in a way that works
well for a wide variety of applications, with different requirements for
bandwidth, stability, mobility, etc. all of which affect address
selection, interface selection, etc., and do all of that efficiently and
in the absence of routing information from the network, you should
probably get a prize of some sort.

Granted that programmers want a simple interface, but the more complex
the network gets, the more apps will be expected to do jobs that were
supposed to be done at layer 3.

Keith