Re: [IPsec] I-D Action: draft-ietf-ipsecme-rfc4307bis-06.txt

Paul Wouters <paul@nohats.ca> Thu, 07 April 2016 15:09 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EC7712D5BC for <ipsec@ietfa.amsl.com>; Thu, 7 Apr 2016 08:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level:
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, T_RP_MATCHES_RCVD=-0.01] autolearn=no autolearn_force=no
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 MHiXfQmaMnLc for <ipsec@ietfa.amsl.com>; Thu, 7 Apr 2016 08:09:18 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AAC312D7FC for <ipsec@ietf.org>; Thu, 7 Apr 2016 07:56:17 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3qglz30ZP0zDnR; Thu, 7 Apr 2016 16:56:15 +0200 (CEST)
X-OPENPGPKEY: Message passed unmodified
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id qpdmmBZamgdz; Thu, 7 Apr 2016 16:56:13 +0200 (CEST)
Received: from bofh.nohats.ca (206-248-139-105.dsl.teksavvy.com [206.248.139.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 7 Apr 2016 16:56:12 +0200 (CEST)
Received: from [10.210.128.57] (unknown [186.141.131.137]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id CD8836019B72; Thu, 7 Apr 2016 10:56:09 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.10.3 bofh.nohats.ca CD8836019B72
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
References: <20160406165945.24993.3487.idtracker@ietfa.amsl.com> <22277.20520.264319.773683@fireball.acr.fi> <27E13094E90E4AC8BAE9DFF017324AE0@notebook> <22277.35607.896237.279372@fireball.acr.fi> <F40AD8BE6DDA484FB95ED61653259871@notebook> <22278.27137.445934.901390@fireball.acr.fi>
From: Paul Wouters <paul@nohats.ca>
Mime-Version: 1.0 (1.0)
In-Reply-To: <22278.27137.445934.901390@fireball.acr.fi>
Message-Id: <0BB81899-1955-47DA-8A80-491F89C546B7@nohats.ca>
Date: Thu, 07 Apr 2016 11:52:43 -0300
To: Tero Kivinen <kivinen@iki.fi>
X-Mailer: iPhone Mail (13E238)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipsec/geLM5fkT8K3NT1Dc6TonVOk6K50>
Cc: ipsec@ietf.org, Valery Smyslov <svanru@gmail.com>
Subject: Re: [IPsec] I-D Action: draft-ietf-ipsecme-rfc4307bis-06.txt
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 15:09:20 -0000

Fine with me

Sent from my iPhone

> On Apr 7, 2016, at 11:09, Tero Kivinen <kivinen@iki.fi> wrote:
> 
> Valery Smyslov writes:
>> After re-reading the draft I think that I'm also a bit unhappy with
>> the way the last table (Section 4.2) is introduced. The draft says
>> that this table is:
>> 
>>   Recommendation of Authentication Method described in [RFC7427]
>>   notation.
>> 
>> However, the values from this table are just examples in RFC7427.
>> Why exactly these algorithms were selected for recommendation?
> 
> Note, that most of them are MAY, so we should really remove them from
> this draft. And they are the algorithms we expect people to use.
> 
>> What about others (EdDSA, GOST etc)?
> 
> EdDSA is just about getting oid, so we cannot really list it here. For
> GOST I have no idea what the oid would be. Both of them would be in
> the same level as sha256WithRSAEncryption, sha384WithRSAEncryption,
> sha512WithRSAEncryption, sha512WithRSAEncryption, dsa-with-sha256,
> ecdsa-with-sha384, and ecdsa-with-sha512.
> 
>> I understand that the algorithms listed were probably most popular
>> (at least some of them) at the time RFC 7427 ws written. But why
>> continue to maintain this list, when it is just a list of examples
>> in RFC7427?
> 
> One of the reason RF7427 lists that many oids, is that there is no
> centralized registry for them. I.e. you cannot go somewhere and get
> list of OIDs you can use for signatures, so RF7427 tried to collect
> all signature algortihms people might use.
> 
> Anyways I think we need to remove all that is not SHOULD or SHOULD NOT
> from the list, i.e., everything we have MAY recommendation in the
> list. 
> 
>> Well, I understand that some recommendations should be given.
>> But probably only those signing algorithms that have non-MAY
>> status should be listed and a note should be added that
>> all others are MAY (that will refer to any unlisted signature
>> algorithm)?
> 
> I agree on removing all MAY algorithms, we do not need note, as that
> is already said in the section 1.2.
> -- 
> kivinen@iki.fi
> 
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec