IETF Logo Mail Archive

Re: sockets APIs extensions for Host Identity Protocol

Stephane Bortzmeyer <bortzmeyer@nic.fr> Mon, 07 May 2007 08:27 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 1HkyZP-0000a9-89; Mon, 07 May 2007 04:27:47 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HkyZM-0000TM-42 for discuss-confirm+ok@megatron.ietf.org; Mon, 07 May 2007 04:27:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HkyZL-0000SO-Lj for discuss@apps.ietf.org; Mon, 07 May 2007 04:27:43 -0400
Received: from mx2.nic.fr ([192.134.4.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HkyZI-0001cr-C1 for discuss@apps.ietf.org; Mon, 07 May 2007 04:27:43 -0400
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 4CCF61C00D8; Mon, 7 May 2007 10:27:39 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx2.nic.fr (Postfix) with ESMTP id 476E81C00D7; Mon, 7 May 2007 10:27:37 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay2.nic.fr (Postfix) with ESMTP id 44E1258EBBC; Mon, 7 May 2007 10:27:37 +0200 (CEST)
Date: Mon, 7 May 2007 10:27:37 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Miika Komu <miika@iki.fi>
Subject: Re: sockets APIs extensions for Host Identity Protocol
Message-ID: <20070507082737.GB21759@nic.fr>
References: <Pine.SOL.4.64.0705041801060.14418@kekkonen.cs.hut.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.SOL.4.64.0705041801060.14418@kekkonen.cs.hut.fi>
X-Operating-System: Debian GNU/Linux 4.0
X-Kernel: Linux 2.6.18-4-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: discuss@apps.ietf.org, Thomas Henderson <thomas.r.henderson@boeing.com>
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

On Fri, May 04, 2007 at 06:28:30PM +0300,
 Miika Komu <miika@iki.fi> wrote 
 a message of 27 lines which said:

> 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.

> This latter observation makes me wonder whether there have been such
> considerations previously in the applications area?

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.

v2.8.7 | Report a Bug | By Email