Re: [IPsec] Response to Pasi's AD comments on the roadmap draft

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 16 March 2010 14:52 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ipsec@core3.amsl.com
Delivered-To: ipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E63BB3A6A2E for <ipsec@core3.amsl.com>; Tue, 16 Mar 2010 07:52:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.867
X-Spam-Level:
X-Spam-Status: No, score=-5.867 tagged_above=-999 required=5 tests=[AWL=0.179, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
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 rk7EVVBZ+OD1 for <ipsec@core3.amsl.com>; Tue, 16 Mar 2010 07:52:29 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 358D83A6996 for <ipsec@ietf.org>; Tue, 16 Mar 2010 07:52:25 -0700 (PDT)
Received: from [10.20.30.163] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id o2GEdZH1021560 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Mar 2010 07:39:36 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240805c7c5489d1e14@[10.20.30.163]>
In-Reply-To: <808FD6E27AD4884E94820BC333B2DB775848478AFD@NOK-EUMSG-01.mgdnok.nokia.com>
References: <D7A0423E5E193F40BE6E94126930C49307964A8F07@MBCLUSTER.xchange.nist.gov> <808FD6E27AD4884E94820BC333B2DB775848477F15@NOK-EUMSG-01.mgdnok.nokia.com> <p06240819c7c40272a94d@[10.20.30.158]> <808FD6E27AD4884E94820BC333B2DB775848478AFD@NOK-EUMSG-01.mgdnok.nokia.com>
Date: Tue, 16 Mar 2010 07:39:35 -0700
To: Pasi.Eronen@nokia.com, sheila.frankel@nist.gov, ipsec@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [IPsec] Response to Pasi's AD comments on the roadmap draft
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 16 Mar 2010 14:52:30 -0000

At 1:38 PM +0100 3/16/10, <Pasi.Eronen@nokia.com> wrote:
>Paul Hoffman wrote:
>
>> > > >  - Section 5.7.4: "It also includes 3 EC DH groups (groups 19-21)
>> >> >  that were previously defined in [RFC4753]". The normative
>> >> >  specification for groups 19-21 in IKE is still 4753/5753bis, so I
>> >> >  would propose just omitting this sentence.
>> >>
>> >> OK - but won't people be confused if they look at RFC 5114 and see
>> >> that there are additional groups defined there?
>> >
>> >The situation of RFC 5114 is quite confusing, I agree (because it's
>> >IMHO not totally clear whether the errata for RFC 4753 would apply to
>> >RFC 5114 too).
>> >
>> >Perhaps "It also includes 3 EC DH groups (groups 19-21) for
>> >information; however, the normative specification for these groups
>> >is [4753bis]."?
>>
>> It is inappropriate for this document to say what the normative
>> specification for another document is, particularly one that is as
>> confusing as RFC 5114.
>
>Assuming 4753bis gets approved by IESG before the roadmap (which seems
>very likely), I think we can say this. Or perhaps we could
>say "current" instead "normative"?
>
>  "RFC 5114 also included 3 EC DH groups (groups 19-21) that were
>  originally defined in [RFC4753]; however, the current specification
>  for these groups is [4753bis]".

That works for me.

--Paul Hoffman, Director
--VPN Consortium