RE: [dhcwg] [dhcpv6] UseMulticast

"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Thu, 16 May 2002 13:10 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 JAA23477 for <dhcwg-archive@odin.ietf.org>; Thu, 16 May 2002 09:10:31 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id JAA11371 for dhcwg-archive@odin.ietf.org; Thu, 16 May 2002 09:10:44 -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 JAA11237; Thu, 16 May 2002 09:08:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA11197 for <dhcwg@optimus.ietf.org>; Thu, 16 May 2002 09:08:16 -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 JAA23376 for <dhcwg@ietf.org>; Thu, 16 May 2002 09:08:03 -0400 (EDT)
Received: from mr6.exu.ericsson.se (mr6att.ericy.com [138.85.224.157]) by imr2.ericy.com (8.11.3/8.11.3) with ESMTP id g4GD7ki26973 for <dhcwg@ietf.org>; Thu, 16 May 2002 08:07:46 -0500 (CDT)
Received: from eamrcnt747.exu.ericsson.se (eamrcnt747.exu.ericsson.se [138.85.133.37]) by mr6.exu.ericsson.se (8.11.3/8.11.3) with SMTP id g4GD7ks25961 for <dhcwg@ietf.org>; Thu, 16 May 2002 08:07:46 -0500 (CDT)
Received: FROM eamrcnt760.exu.ericsson.se BY eamrcnt747.exu.ericsson.se ; Thu May 16 08:07:45 2002 -0500
Received: by eamrcnt760.exu.ericsson.se with Internet Mail Service (5.5.2653.19) id <KVLD6XXJ>; Thu, 16 May 2002 08:07:45 -0500
Message-ID: <66F66129A77AD411B76200508B65AC69B4D430@EAMBUNT705>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: "'JINMEI Tatuya / ????'" <jinmei@isl.rdc.toshiba.co.jp>, dhcwg@ietf.org
Subject: RE: [dhcwg] [dhcpv6] UseMulticast
Date: Thu, 16 May 2002 08:07:43 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1FCDA.AA617BB0"
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

My take is that a Reply MUST always include the Server Identifier option (since that identifies the server responding) and it MUST include the Client Identifier option if the client sent one.

I think the statements such as "no other options" should likely be reviewed and perhaps restates as no options containing configuration related information. We probably need a blanket statement somewhere that clarifies that all responses from a server to a client MUST contain:
- The server identifier of the server.
- The client identifier of the client if the client provided it.

- Bernie

-----Original Message-----
From: jinmei@isl.rdc.toshiba.co.jp [mailto:jinmei@isl.rdc.toshiba.co.jp]
Sent: Thursday, May 16, 2002 1:41 AM
To: dhcwg@ietf.org
Subject: [dhcwg] [dhcpv6] UseMulticast


Section 18.2.1 of dhcpv6-24 says:

   When the server receives a Request message via unicast from a
   client to which the server has not sent a unicast option, the server
   discards the Request message and responds with a Reply message
   containing a status code option with value UseMulticast and no other
   options.

On the other hand, section 15.10 says

    -  the message does not include a Server Identifier option
(snip)
    -  the message does not include a Client Identifier option and the
       original message from the client contained a Client Identifier
       option

Those two requirements seem to be inconsistent, or at least be
confusing.  Should the reply message contain the Server Identifier
option (and the Client Identifier option if the original message
contained it) in the Reply even if the server is responding with a
status code option with UseMulticast?  Or should the client loosen the
validation in 15.10 if the reply contains a status code option?  Or
others?

					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