Re: [Hipsec] WGLC: draft-ietf-hip-rfc5205-bis

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Tue, 05 May 2015 13:59 UTC

Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 087AE1ACE5C for <hipsec@ietfa.amsl.com>; Tue, 5 May 2015 06:59:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.201
X-Spam-Level:
X-Spam-Status: No, score=-104.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QZcH0jvW_Maq for <hipsec@ietfa.amsl.com>; Tue, 5 May 2015 06:59:53 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 892961ACE6D for <hipsec@ietf.org>; Tue, 5 May 2015 06:59:51 -0700 (PDT)
X-AuditID: c1b4fb2d-f794d6d000004501-7b-5548ccd53786
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 85.B1.17665.5DCC8455; Tue, 5 May 2015 15:59:49 +0200 (CEST)
Received: from [131.160.36.183] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.59) with Microsoft SMTP Server id 14.3.210.2; Tue, 5 May 2015 15:59:49 +0200
Message-ID: <5548CCD5.9010108@ericsson.com>
Date: Tue, 5 May 2015 16:59:49 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Tom Henderson <tomh@tomh.org>, HIP <hipsec@ietf.org>
References: <5530E4C1.8070509@ericsson.com> <554780D0.9070301@tomh.org>
In-Reply-To: <554780D0.9070301@tomh.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBLMWRmVeSWpSXmKPExsUyM+Jvje7VMx6hBrv2GFtMXTSZ2aLx7h8m ByaPJUt+MnnsuaYRwBTFZZOSmpNZllqkb5fAlXF6hknBNKGKBTtvMDUwbuDrYuTkkBAwkVh5 +x8LhC0mceHeerYuRi4OIYGjjBK3p2xmhnBWM0oseb2eCaSKV0Bb4sntK2wgNouAisTuJ1fB bDYBC4ktt+6DTRIViJKY+PUQC0S9oMTJmU/AbBGgmgPH+8BsYQEzien/34L1Cgm4Szw5cIkZ xOYU0JBYeH422C5mAQOJI4vmsELY8hLb385hhqjXllj+rIVlAqPALCQrZiFpmYWkZQEj8ypG 0eLU4uLcdCNjvdSizOTi4vw8vbzUkk2MwKA8uOW37g7G1a8dDzEKcDAq8fAqqHiECrEmlhVX 5h5ilOZgURLntTM+FCIkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBccLGiQESx+LbIpdWrVRa EWi6eNHEL+fuLc5u29+SMTXf4ulMfRu+GWvUuJPunPtUt9q8qeZBxL4W52eRNZUBctvlIiZG tXqK3X4suv38n09977cKTLNadnWXzsHH81XSvrE/eX4opu2//vnn5qLFn/m8+xjeyp0Xmf+q 5YXOLR5f0ZXVhSfb5JVYijMSDbWYi4oTAWy7kskrAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/hipsec/u2TFf513NUUcVUHICArwS2cDFRA>
Subject: Re: [Hipsec] WGLC: draft-ietf-hip-rfc5205-bis
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.15
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/options/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: Tue, 05 May 2015 13:59:55 -0000

Thanks for the review, Tom.

Julien, could you please look into Tom's comments and address them in a
new revision of the draft?

Thanks,

Gonzalo

On 04/05/2015 5:23 PM, Tom Henderson wrote:
> On 04/17/2015 03:47 AM, Gonzalo Camarillo wrote:
>> Hi,
>>
>> I would like to start a WGLC on the following draft. This WGLC will end
>> on May 4th:
>>
>> https://datatracker.ietf.org/doc/draft-ietf-hip-rfc5205-bis/
>>
>> Please, send your comments to this list.
>>
>> Thanks,
>>
>> Gonzalo
> 
> I had a fresh read of this specification and have the following comments.
> 
> (possibly) technical
> --------------------
> 
> RFC 7401 specifies ECDSA and ECDSA_LOW as separate algorithm types, but
> this document only mentions ECDSA.  For alignment with RFC 7401, I
> suggest to replace references to "ECDSA" with "ECDSA and ECDSA_LOW" as
> appropriate (it seems to me that they can reuse the same codepoint).
> 
> I could not find discussion about TTL considerations; are there any?  If
> there are no special considerations about TTL, caching, and how records
> may be updated, perhaps it would be helpful to state this (and possibly
> reference the specification that describes how to expire resource records).
> 
> The document doesn't seem to have any discussion of what to do when a
> host wants to register more than one host identity.  I suggest something
> along the lines of "there may be multiple HIP RRs associated with a
> single name.  It is outside the scope of this specification as to how a
> host chooses from between multiple RRs when more than one is returned.
> The RVS information may be copied and aligned across multiple RRs, or
> may be different for each one; a host SHOULD check that the RVS used is
> associated with the HI being used, when multiple choices are present."
> 
> editorial
> ---------
> 
> IANA considerations could be made more explicit about exactly what we
> are requesting IANA to do; e.g., "the reference to the RR type code
> should be updated from RFC 5205 to this specification."  and "this
> document requests that IANA allocate a new codepoint for 'ECDSA and
> ECDSA_LOW' in the existing registry for IPSECKEY RR."
> 
> Suggest to replace "Singly" with "Single" and "degenerated" with
> "degenerate".
> 
> 
> 
> 
>