[Hipsec] draft-ietf-hip-native-api-09-pre

Miika Komu <miika.komu@hiit.fi> Thu, 20 August 2009 21:07 UTC

Return-Path: <miika.komu@hiit.fi>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 952073A6B95 for <hipsec@core3.amsl.com>; Thu, 20 Aug 2009 14:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TzdZT3+0bJyC for <hipsec@core3.amsl.com>; Thu, 20 Aug 2009 14:07:29 -0700 (PDT)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 92DC73A6A0C for <hipsec@ietf.org>; Thu, 20 Aug 2009 14:07:29 -0700 (PDT)
Received: from ip104.infrahip.net (cs27101111.pp.htv.fi [89.27.101.111]) by argo.otaverkko.fi (Postfix) with ESMTP id 811FE25ED16 for <hipsec@ietf.org>; Fri, 21 Aug 2009 00:07:34 +0300 (EEST)
Message-ID: <4A8DBB16.3010705@hiit.fi>
Date: Fri, 21 Aug 2009 00:07:34 +0300
From: Miika Komu <miika.komu@hiit.fi>
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
MIME-Version: 1.0
To: hip WG <hipsec@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: [Hipsec] draft-ietf-hip-native-api-09-pre
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: miika.komu@hiit.fi
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Aug 2009 21:07:30 -0000

Hi,

we got an extra review to the native API from Stefan Götz. The new 
preversion is here:

http://www.iki.fi/miika/docs/draft-ietf-hip-native-api-09-pre1.txt

The changes are editorial readability changes throughout the document. 
Especially section 4.1 contains now more clarifications on the fields of 
sockaddr_hip structure and wildcards

We'd like to move on with the document, but we have two questions for 
the working group:

#1 How to future proof HITs in case we need 256 bit HITs? This is 
important also from the view point of comparison of HITs (currently 
draft suggests memcmp() in section 4.1. Unless, there's other 
suggestions, I'd go for alternative (i):

     * Alternative (i): separate sockaddr_hip structure for larger HITs
     * Alternative (ii): make larger HIT structure in sockaddr_hip with 
zero padding for 128 bit HITs

#2 How should the socket calls react to only-hip wildcard. Currently 
section 4.1.1 describes:

    With the HIP_HIT_ANY address,
    the underlying system allows only HIP-based data flows with the
    corresponding socket.  For incoming packets, the system transparently
    discards all other traffic arriving at the socket than HIP related.
    For outgoing packets, the system returns -1 in the socket call and
    sets errno to ECOMM when the system failed to deliver the packet over
    a HIP-based data channel.