Re: [dhcwg] Comments on draft-jinmei-dhc-dhcpv6-clarify-auth-00

JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Mon, 26 July 2004 08:09 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07857; Mon, 26 Jul 2004 04:09:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bp0SF-0003Jj-SE; Mon, 26 Jul 2004 04:03:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bp0Nf-0002q1-Mm for dhcwg@megatron.ietf.org; Mon, 26 Jul 2004 03:58:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07369 for <dhcwg@ietf.org>; Mon, 26 Jul 2004 03:58:41 -0400 (EDT)
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bp0P0-0001Ze-M8 for dhcwg@ietf.org; Mon, 26 Jul 2004 04:00:08 -0400
Received: from ocean.jinmei.org (unknown [3ffe:501:100f:1048:7d91:64be:e17:f09d]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id EE91C15273; Mon, 26 Jul 2004 16:58:39 +0900 (JST)
Date: Mon, 26 Jul 2004 16:58:40 +0900
Message-ID: <y7v7jsrmc7j.wl@ocean.jinmei.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
To: Christian Strauf <strauf@rz.tu-clausthal.de>
Subject: Re: [dhcwg] Comments on draft-jinmei-dhc-dhcpv6-clarify-auth-00
In-Reply-To: <1090333421.11056.266.camel@localhost>
References: <1090333421.11056.266.camel@localhost>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

Hello,

Thanks for your positive feedback, and sorry for the delayed response.

>>>>> On Tue, 20 Jul 2004 16:23:41 +0200, 
>>>>> Christian Strauf <strauf@rz.tu-clausthal.de> said:

> I paragraph 4. you write:

> "A reasonable interpretation of the phrase is probably as follows: a
> DHCPv6 message is called unauthenticated when it fails the validation
> test described in Section 21.4.2, it does not contain an authentication
> option, or when it includes an authentication option but does not have
> authentication information when necessary."

> I would propose a minor rephrasing to clear the language up a little (if
> I understand the above paragraph correctly, the following rewording
> should work):

> "A reasonable interpretation of the phrase is as follows: a DHCPv6
> message is called unauthenticated if it fails the validation test
> described in Section 21.4.2, if it does not contain an authentication
> option, or if it includes an authentication option without the necessary
> authentication information."

OK.  I've modified the local source of the draft with the suggested
change.

> Minor typos:

> para 2.:
> 	-It should also be noted that [RFC3315] does not define how the
>          server should do when it receives
>         +It should also be noted that [RFC3315] does not define what the
>          server should do when it receives

> para 3.:
> 	-3.  What If Reply Is Detected
> 	+3.  What If Replay Is Detected

> para 5.:
> 	-Apparently this contradicts with the requirement in Section
>          21.4.2.
> 	+Apparently this contradicts the requirement in Section 21.4.2.

> para 5.1.:
> 	-Accepting an non-authenticated
> 	+Accepting a non-authenticated

Thanks, fixed in the local source.  (The second and fourth typos
should already be fixed in the published version of the draft.  I
guess your comments are for a preliminary version available at my web
page.)

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg