Re: [Hipsec] draft-ietf-hip-cert-04-pre01

Ari Keranen <ari.keranen@nomadiclab.com> Wed, 30 June 2010 13:14 UTC

Return-Path: <ari.keranen@nomadiclab.com>
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 8971B3A6AC4 for <hipsec@core3.amsl.com>; Wed, 30 Jun 2010 06:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[AWL=0.504, 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 2C2xMPCGwZtU for <hipsec@core3.amsl.com>; Wed, 30 Jun 2010 06:14:17 -0700 (PDT)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id 08FE53A6AC8 for <hipsec@ietf.org>; Wed, 30 Jun 2010 06:14:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id D4FB04E6CF; Wed, 30 Jun 2010 16:14:26 +0300 (EEST)
X-Virus-Scanned: amavisd-new at nomadiclab.com
Received: from gw.nomadiclab.com ([127.0.0.1]) by localhost (inside.nomadiclab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZbZMPtplUlsu; Wed, 30 Jun 2010 16:14:26 +0300 (EEST)
Received: from [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1] (unknown [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1]) by gw.nomadiclab.com (Postfix) with ESMTP id 064CB4E6C1; Wed, 30 Jun 2010 16:14:25 +0300 (EEST)
Message-ID: <4C2B4331.6040807@nomadiclab.com>
Date: Wed, 30 Jun 2010 16:14:25 +0300
From: Ari Keranen <ari.keranen@nomadiclab.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Samu Varjonen <samu.varjonen@hiit.fi>
References: <4C18A462.40206@hiit.fi> <4C231744.3010204@nomadiclab.com> <4C2B288E.3000703@hiit.fi>
In-Reply-To: <4C2B288E.3000703@hiit.fi>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] draft-ietf-hip-cert-04-pre01
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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: Wed, 30 Jun 2010 13:14:19 -0000

Hi,

On 06/30/2010 02:20 PM, Samu Varjonen wrote:
> Here is the new preversion of the hip-cert with some editorial changes, 
> clean-up, new certificate examples, and so on...
> 
> http://www.cs.helsinki.fi/u/sklvarjo/draft-ietf-hip-cert-04-pre02.txt

Thanks, looks better now. More comments in line.

> Ari Keranen wrote:
>> The document would benefit from using more normative language, i.e., 
>> capitalizing the relevant shoulds/musts/mays and thinking once more 
>> through which form is appropriate.
>>

I still found only one capitalized MUST in the whole document (and no 
MAYs or SHOULDs). Maybe it's just me, but I find a non-informational 
document lacking RFC 2119 keywords a bit disturbing: it looks like it is 
all purely informational.

Then I realized that the document's current status is indeed 
Informational. Shouldn't it be experimental?

>> 2.  CERT Parameter
>>
>>    The CERT parameter is covered by the HIP SIGNATURE field and is a
>>    non-critical parameter.
>>
>> This is better than the previous version, but I'd suggest adding 
>> "(where present)" after "is covered" to point out that in I1 it would 
>> not be covered by a signature.
>>
> 
> OK, changed

This is a true nit, but I would have put the "where present" in 
parenthesis or surrounded it with commas.

>>
>> 7.  IANA Considerations
>>
>> Should the certificate types have their own registry?
>>
> 
> I would say yes, any other opinions.

Yes.


Cheers,
Ari