Re: [IPsec] I-D Action:draft-ietf-ipsecme-ikev2bis-04.txt

atsushi.fukumoto@toshiba.co.jp Fri, 10 July 2009 08:31 UTC

Return-Path: <atsushi.fukumoto@toshiba.co.jp>
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 5B5E63A6FF1 for <ipsec@core3.amsl.com>; Fri, 10 Jul 2009 01:31:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.09
X-Spam-Level:
X-Spam-Status: No, score=-4.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, 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 2qQTq6h+4UnC for <ipsec@core3.amsl.com>; Fri, 10 Jul 2009 01:31:56 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by core3.amsl.com (Postfix) with ESMTP id 722533A704C for <ipsec@ietf.org>; Fri, 10 Jul 2009 01:31:56 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp with ESMTP id n6A8WNTj026174 for <ipsec@ietf.org>; Fri, 10 Jul 2009 17:32:23 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp id n6A8WNX5007115 for ipsec@ietf.org; Fri, 10 Jul 2009 17:32:23 +0900 (JST)
Received: from unknown [133.199.192.144] by arc1.toshiba.co.jp with ESMTP id TAA07114; Fri, 10 Jul 2009 17:32:23 +0900
Received: from mx11.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp with ESMTP id n6A8WMF5020303 for <ipsec@ietf.org>; Fri, 10 Jul 2009 17:32:22 +0900 (JST)
Received: by toshiba.co.jp id n6A8WMDI025981; Fri, 10 Jul 2009 17:32:22 +0900 (JST)
To: ipsec@ietf.org
In-reply-to: <20090708220001.E3CBD3A6FB6@core3.amsl.com>
References: <20090708220001.E3CBD3A6FB6@core3.amsl.com>
Comments: In-reply-to Internet-Drafts@ietf.org message dated "Wed, 08 Jul 2009 15:00:01 -0700."
Date: Fri, 10 Jul 2009 17:32:22 +0900
Message-Id: <200907100832.n6A8WMDI025981@toshiba.co.jp>
From: atsushi.fukumoto@toshiba.co.jp
Subject: Re: [IPsec] I-D Action:draft-ietf-ipsecme-ikev2bis-04.txt
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: Fri, 10 Jul 2009 08:31:57 -0000

ikev2bis draft-04 section 1.5 adds about INVALID_MAJOR_VERSION:

   There are two cases when such a one-way notification is sent:
   INVALID_IKE_SPI and INVALID_SPI.  These notifications are sent
   outside of an IKE SA.  Note that such notifications are explicitly
   not Informational exchanges; these are one-way messages that must not
   be responded to.  (INVALID_MAJOR_VERSION is also a one-way message
   which is sent outside of an IKE SA, although it is sent as a response
   to the incoming IKE SA creation.)

I feel it confusing.  Probably "such a one-way notification" should be
"a one-way notification".  I don't understand why
INVALID_MAJOR_VERSION case need to be separated from INVALID_IKE_SPI
and INVALID_SPI.

The word "notification message" seems somewhat ambiguous and
confusing.  In section 3.10, it refers to a Notification payload
rather than an entire message.  In some other places I suppose it
means an INFORMATIONAL exchange request message.

Come to think of it, I note there are two expressions in the draft:
"Notify payload" and "Notification payload".  Also in most places
"INFORMATIONAL exchange" whereas there are some "Informational
exchange" and "informational exchange".


					FUKUMOTO Atsushi
					atsushi.fukumoto@toshiba.co.jp