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

<Pasi.Eronen@nokia.com> Tue, 16 March 2010 12:39 UTC

Return-Path: <Pasi.Eronen@nokia.com>
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 708FA3A67D6 for <ipsec@core3.amsl.com>; Tue, 16 Mar 2010 05:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.537
X-Spam-Level:
X-Spam-Status: No, score=-6.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, 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 pV--c22uGLWt for <ipsec@core3.amsl.com>; Tue, 16 Mar 2010 05:39:09 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id E66133A6A56 for <ipsec@ietf.org>; Tue, 16 Mar 2010 05:39:04 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx03.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o2GCd7Bi029297; Tue, 16 Mar 2010 14:39:09 +0200
Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Mar 2010 14:38:24 +0200
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by vaebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Mar 2010 14:38:19 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Mar 2010 14:38:10 +0200
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-01.mgdnok.nokia.com ([65.54.30.5]) with mapi; Tue, 16 Mar 2010 13:38:09 +0100
From: Pasi.Eronen@nokia.com
To: paul.hoffman@vpnc.org, sheila.frankel@nist.gov, ipsec@ietf.org
Date: Tue, 16 Mar 2010 13:38:08 +0100
Thread-Topic: [IPsec] Response to Pasi's AD comments on the roadmap draft
Thread-Index: AcrETM1U5R26rYKoThqG1zlRBDCxJwAuGj+g
Message-ID: <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]>
In-Reply-To: <p06240819c7c40272a94d@[10.20.30.158]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 16 Mar 2010 12:38:10.0794 (UTC) FILETIME=[899FCCA0:01CAC505]
X-Nokia-AV: Clean
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 12:39:10 -0000

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]".

Best regards,
Pasi