Re: [IPsec] IETFLC comments for draft-ietf-ipsecme-ikev2bis-08

<Pasi.Eronen@nokia.com> Mon, 08 March 2010 07:17 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 C24D23A692A; Sun, 7 Mar 2010 23:17:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.588
X-Spam-Level:
X-Spam-Status: No, score=-6.588 tagged_above=-999 required=5 tests=[AWL=0.011, 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 k8i2K-C5l643; Sun, 7 Mar 2010 23:17:25 -0800 (PST)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id 6EFE93A677D; Sun, 7 Mar 2010 23:17:24 -0800 (PST)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-mx09.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o287GZwM029515; Mon, 8 Mar 2010 01:17:26 -0600
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by vaebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 8 Mar 2010 09:17:04 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.6]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Mon, 8 Mar 2010 09:17:00 +0200
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-02.mgdnok.nokia.com ([65.54.30.6]) with mapi; Mon, 8 Mar 2010 08:16:59 +0100
From: Pasi.Eronen@nokia.com
To: paul.hoffman@vpnc.org, ietf@ietf.org, ipsec@ietf.org
Date: Mon, 08 Mar 2010 08:16:58 +0100
Thread-Topic: [IPsec] IETFLC comments for draft-ietf-ipsecme-ikev2bis-08
Thread-Index: Acq9lWOKOw0+7fnFRxOPZH8X6ltvlwA+WIlg
Message-ID: <808FD6E27AD4884E94820BC333B2DB7758482FF391@NOK-EUMSG-01.mgdnok.nokia.com>
References: <808FD6E27AD4884E94820BC333B2DB7758482FF051@NOK-EUMSG-01.mgdnok.nokia.com> <p06240810c7b8ad71932e@[10.20.30.158]>
In-Reply-To: <p06240810c7b8ad71932e@[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: 08 Mar 2010 07:17:00.0097 (UTC) FILETIME=[5816CB10:01CABE8F]
X-Nokia-AV: Clean
Subject: Re: [IPsec] IETFLC comments for draft-ietf-ipsecme-ikev2bis-08
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: Mon, 08 Mar 2010 07:17:28 -0000

Paul Hoffman wrote:

> >- One of the changes is listed in Section 1.7 twice. I'd suggest
> >combining
> >
> >   In section 1.3.2, changed "The KEi payload SHOULD be included" to
> >   be "The KEi payload MUST be included".  This also led to changes in
> >   section 2.18.
> >
> >and
> >
> >   Section 2.18 requires doing a Diffie-Hellman exchange when rekeying
> >   the IKE_SA.  In theory, RFC 4306 allowed a policy where the Diffie-
> >   Hellman exchange was optional, but this was not useful (or
> >   appropriate) when rekeying the IKE_SA.
> >
> >as follows:
> >
> >   This document requires doing a Diffie-Hellman exchange when
> >   rekeying the IKE_SA (and thus requires including the KEi/KEr
> >   payloads).  In theory, RFC 4306 allowed a policy where the
> >   Diffie-Hellman exchange was optional (and KEi/KEr payloads could be
> >   omitted), this was not useful (or appropriate) when rekeying the
> >   IKE_SA.
> 
> Disagree. Where possible, I tried to list the actual sections where
> changes were made, and your proposed rewording loses the two places.
> The current text is more explicit than the proposed change.

Well, this depends on whether you think Section 1.7 should list
textual changes in the document, or clarification/changes to the
protocol.

IMHO, it should be the latter, but I see that currently it's really
listing the textual changes (even when they clearly don't have any
impact on the protocol); so perhaps listing these separately is
consistent with that...

Best regards,
Pasi