RE: [dhcwg] additional comments on dhcpv6-24

"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Thu, 16 May 2002 17:33 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03328 for <dhcwg-archive@odin.ietf.org>; Thu, 16 May 2002 13:33:34 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA01393 for dhcwg-archive@odin.ietf.org; Thu, 16 May 2002 13:33:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA01221; Thu, 16 May 2002 13:31:54 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA01200 for <dhcwg@optimus.ietf.org>; Thu, 16 May 2002 13:31:52 -0400 (EDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03208 for <dhcwg@ietf.org>; Thu, 16 May 2002 13:31:36 -0400 (EDT)
Received: from mr7.exu.ericsson.se (mr7att.ericy.com [138.85.224.158]) by imr2.ericy.com (8.11.3/8.11.3) with ESMTP id g4GHVKi14846 for <dhcwg@ietf.org>; Thu, 16 May 2002 12:31:20 -0500 (CDT)
Received: from eamrcnt749 (eamrcnt749.exu.ericsson.se [138.85.133.47]) by mr7.exu.ericsson.se (8.11.3/8.11.3) with SMTP id g4GHVJ409350 for <dhcwg@ietf.org>; Thu, 16 May 2002 12:31:19 -0500 (CDT)
Received: FROM eamrcnt760.exu.ericsson.se BY eamrcnt749 ; Thu May 16 12:31:18 2002 -0500
Received: by eamrcnt760.exu.ericsson.se with Internet Mail Service (5.5.2653.19) id <KVLD7MKA>; Thu, 16 May 2002 12:31:18 -0500
Message-ID: <66F66129A77AD411B76200508B65AC69B4D438@EAMBUNT705>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: "'JINMEI Tatuya / ????'" <jinmei@isl.rdc.toshiba.co.jp>
Cc: dhcwg@ietf.org
Subject: RE: [dhcwg] additional comments on dhcpv6-24
Date: Thu, 16 May 2002 12:31:11 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1FCFF.78C21590"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

Regarding (1), please watch the mailing list as Ralph Droms is issuing update notices for changes being made.

- Bernie

-----Original Message-----
From: jinmei@isl.rdc.toshiba.co.jp [mailto:jinmei@isl.rdc.toshiba.co.jp]
Sent: Thursday, May 16, 2002 12:52 PM
To: Bernie Volz (EUD)
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] additional comments on dhcpv6-24


>>>>> On Wed, 15 May 2002 14:36:37 -0500, 
>>>>> "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> said:

> Regarding (1), based on -24 the server shouldn't be sending an
> Advertise. And, yes, I think your assumption that the client should
> discard it is correct. Having said that, I would like to see the
> Rapid Commit change to be more of just an option. A server set up to
> respond to Rapid Commit would send the Reply. Other servers could
> send an Advertise. The client would use the Reply if received;
> otherwise simply start using the Advertises as if a Solicit w/o
> Rapid Commit was done.

I'm a bit confused...so are you saying the followings?

- the client should discard the unexpected advertise *with the current
  specification*.
- but we should change the spec so that the client will accept an
  advertise.

> Regarding (2), good question ... I would say it should. The logic
> might simply be send a Solicit, wait IRT, check if any Advertises
> received ... if so, go use them otherwise send Solicit again.

Okay.  I don't have a particular opinion on this as long as the
wording is clear.

> Regarding (3), your understanding is correct. I can't see that it
> hurts for us to indicate that RAND be greater than 0.

Okay.  I would simplify the specification so that there will be no
special case, but I don't make an objection to the current spec.

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