IETF Logo Mail Archive

Re: sockets APIs extensions for Host Identity Protocol

Miika Komu <miika@iki.fi> Fri, 11 May 2007 20:32 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 1HmbmZ-0007n9-0O; Fri, 11 May 2007 16:32:07 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HmbmX-0007n4-Gg for discuss-confirm+ok@megatron.ietf.org; Fri, 11 May 2007 16:32:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmbmW-0007mv-Ml for discuss@apps.ietf.org; Fri, 11 May 2007 16:32:04 -0400
Received: from twilight.cs.hut.fi ([130.233.40.5]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmbmV-0003jN-7L for discuss@apps.ietf.org; Fri, 11 May 2007 16:32:04 -0400
Received: by twilight.cs.hut.fi (Postfix, from userid 60001) id 79F8C2CD1; Fri, 11 May 2007 23:32:02 +0300 (EEST)
X-Spam-Checker-Version: SpamAssassin 3.2.0-niksula20070322 (2007-05-01) on twilight.cs.hut.fi
X-Spam-Level:
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.2.0-niksula20070322
X-Spam-Niksula: No
Received: from kekkonen.cs.hut.fi (kekkonen.cs.hut.fi [130.233.41.50]) by twilight.cs.hut.fi (Postfix) with ESMTP id 08ADC2CB8; Fri, 11 May 2007 23:32:02 +0300 (EEST)
Date: Fri, 11 May 2007 23:32:01 +0300
From: Miika Komu <miika@iki.fi>
X-X-Sender: mkomu@kekkonen.cs.hut.fi
To: Keith Moore <moore@cs.utk.edu>
Subject: Re: sockets APIs extensions for Host Identity Protocol
In-Reply-To: <4644CD76.10900@cs.utk.edu>
Message-ID: <Pine.SOL.4.64.0705112330070.8816@kekkonen.cs.hut.fi>
References: <Pine.SOL.4.64.0705041801060.14418@kekkonen.cs.hut.fi> <20070507082737.GB21759@nic.fr> <46413DD7.8020702@cs.utk.edu> <20070509121703.GA21070@nic.fr> <4641CA52.70504@cs.utk.edu> <Pine.LNX.4.64.0705091449360.26169@hermes-1.csi.cam.ac.uk> <4641D94C.9070304@cs.utk.edu> <Pine.SOL.4.64.0705102013550.10049@kekkonen.cs.hut.fi> <46436B10.5090706@cs.utk.edu> <Pine.SOL.4.64.0705102159020.10049@kekkonen.cs.hut.fi> <4643F873.3000501@cs.utk.edu> <Pine.SOL.4.64.0705110851440.24038@kekkonen.cs.hut.fi> <46442588.7020405@cs.utk.edu> <Pine.SOL.4.64.0705111344130.16213@kekkonen.cs.hut.fi> <4644779F.60805@cs.utk.edu> <Pine.SOL.4.64.0705111801430.8816@kekkonen.cs.hut.fi> <4644CD76.10900@cs.utk.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
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

On Fri, 11 May 2007, Keith Moore wrote:

>> Are you fine with a sockaddr_hit structure that contains only the HIT
>> and letting a getsockopt() call to figure out the IP addresses in the
>> context of HIP aware applications? (I think getsockname and
>> getpeername should return the HITs.)
>
> if the sockaddr_hit structure contains only the HIT, how is the kernel
> going to know where it can contact that peer?  It has to get one or more
> IP addresses from somewhere.

If the resolver is used, it can send a hint containing this mapping to the 
HIP daemon.

-- 
Miika Komu                                       http://www.iki.fi/miika/

v2.23.0 | Report a Bug | By Email