Re: [Hipsec] WGLC: draft-ietf-hip-native-api-06

Miika Komu <miika.komu@hiit.fi> Mon, 06 July 2009 16:37 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 AF6053A6B7F for <hipsec@core3.amsl.com>; Mon, 6 Jul 2009 09:37:10 -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=[AWL=0.000, 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 i1zwIeFqHJMe for <hipsec@core3.amsl.com>; Mon, 6 Jul 2009 09:37:10 -0700 (PDT)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id D57283A6CF8 for <hipsec@ietf.org>; Mon, 6 Jul 2009 09:37:09 -0700 (PDT)
Received: from [193.167.187.26] (halko.pc.infrahip.net [193.167.187.26]) by argo.otaverkko.fi (Postfix) with ESMTP id 59E8825ED10; Mon, 6 Jul 2009 19:08:00 +0300 (EEST)
Message-ID: <4A522160.1060205@hiit.fi>
Date: Mon, 06 Jul 2009 19:08:00 +0300
From: Miika Komu <miika.komu@hiit.fi>
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
MIME-Version: 1.0
To: "Ahrenholz, Jeffrey M" <jeffrey.m.ahrenholz@boeing.com>
References: <4A425954.4040500@ericsson.com> <0DF156EE7414494187B087A3C279BDB404AD7B8F@XCH-NW-6V1.nw.nos.boeing.com> <4A4E0F0D.5090905@hiit.fi> <0DF156EE7414494187B087A3C279BDB40CD300FB@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <0DF156EE7414494187B087A3C279BDB40CD300FB@XCH-NW-6V1.nw.nos.boeing.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] WGLC: draft-ietf-hip-native-api-06
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: Mon, 06 Jul 2009 16:37:10 -0000

Ahrenholz, Jeffrey M wrote:

Hi,

>>> You might reference ORCHIDs earlier on (maybe second or 
>> third paragraph
>>> of introduction) as the first time they appear in this 
>> draft is section
>>> 4.2.
>> Done.
> 
> OK, in the new ORCHID text, you might use "derived" instead of
> "derivated".

thanks. This will appear in the next version.

>> I agree that the HIT vs. ORCHID usage was confusing. I replaced all 
>> orchid names with HITs in order to unify the naming scheme in 
>> the API. 
>> Is it ok now?
> 
> yes, I think it is clearer now
> 
>>> but then Section 4.1 Page 6, 2nd paragraph talks about using PF_HIP
>>> "The use of the PF_HIP constant" ...
>> I rephrased this, please check if it is ok now.
> 
> looks good
> 
>>> typedef struct in6_addr orchid_t; typedef orchid_t hip_hit_t;
>> I am not sure what to do about it because I decided to unify the 
>> constants just to use always "hit".
> 
> yes now all the constants use "hit" so the "orchid" name is not needed

Ok, thanks.