[dhcwg] Questions about Invalid Option : I'd like clarification

<Hideshi.Enokihara@jp.yokogawa.com> Mon, 05 March 2007 08:32 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HO8cZ-0000Uh-DK; Mon, 05 Mar 2007 03:32:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HO8cX-0000UZ-ND for dhcwg@ietf.org; Mon, 05 Mar 2007 03:32:37 -0500
Received: from zns001-0m9001.yokogawa.co.jp ([203.174.79.138]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HO8cW-0002dx-2d for dhcwg@ietf.org; Mon, 05 Mar 2007 03:32:37 -0500
Received: from zns001-0m9001.yokogawa.co.jp (localhost [127.0.0.1]) by zns001-0m9001.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id l258WRgs016330 for <dhcwg@ietf.org>; Mon, 5 Mar 2007 17:32:27 +0900 (JST)
Received: from EXCHANGE03.jp.ykgw.net (zex001-0m9003.jp.ykgw.net [10.0.11.23]) by zns001-0m9001.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id l258WRtS016327 for <dhcwg@ietf.org>; Mon, 5 Mar 2007 17:32:27 +0900 (JST)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 05 Mar 2007 17:32:25 +0900
Message-ID: <0260031F55435342859BFB2CCA6773D81B8989B8@EXCHANGE03.jp.ykgw.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Questions about Invalid Option : I'd like clarification
Thread-Index: AcdfAM1/5FQEeBUsQyOeBb4FR7ZeyA==
From: Hideshi.Enokihara@jp.yokogawa.com
To: dhcwg@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Subject: [dhcwg] Questions about Invalid Option : I'd like clarification
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>
Errors-To: dhcwg-bounces@ietf.org

Hello all,

I have some questions about Invalid Options that are not allowed to
appear in the message.
I'd like to clarify following things, because I have to finish writing
the Conformance test specification for IPv6 Ready Logo Program for
DHCPv6.
Could you give me your thoughts, please?


RFC3315 section 15 says,
------------
   Clients and servers SHOULD discard any messages that contain options
   that are not allowed to appear in the received message.  For example,
   an IA option is not allowed to appear in an Information-request
   message. 
------------

And "A. Appearance of Options in Message Types" shows table that 
indicates with a "*" the options are allowed in each DHCP message type.

This mean that without a "*" the options are not allowed in each message
type, right?

I believe that this table information is too old( not correct ). 
I think that we need to clarify which option(message with invalid
option) should be discarded or should be ignored.

Following things are my thoughts. Are these things correct?
------------------
For Server
	Receiving Solict message:
		A Server must discard the Solicit message including
Server Identifier option.
		A Server must ignore all options that are not allowed to
appear in the message except for Server Identifier option. 

	Receiving Confirm message:
		A Server must discard the Confirm message including
Server Identifier option.
		A Server must ignore all options that are not allowed to
appear in the message except for Server Identifier option. 
		
	Receiving Rebind message:
		A Server must discard the Confirm message including
Server Identifier option.
		A Server must ignore all options that are not allowed to
appear in the message except for Server Identifier option. 

	Receiving Information-request message:
		A Server must discard the Confirm message including
Server Identifier option and/or IA_NA option.
		A Server must ignore all options that are not allowed to
appear in the message except for Server Identifier option and IA_NA
option. 

	Other messages(Request/Renew/Release/Decline/Relay-forward):
		A Server must ignore all options that are not allowed to
appear in the message.

	*I'd like to confirm following things.
	RFC3646 section5 says,
	--------------------------
	   The DNS Recursive Name Server option MUST NOT appear in any
other
	   than the following messages: Solicit, Advertise, Request,
Renew,
	   Rebind, Information-Request, and Reply.

	   The Domain Search List option MUST NOT appear in any other
than the
	   following messages: Solicit, Advertise, Request, Renew,
Rebind,
	   Information-Request, and Reply.
	--------------------------
	This means that servers should discard  the
Confirm/Release/Decline/Relay-forward message 
	that including  DNS Recursive Name Server option and/or Domain
Search List option, right?
	Or just ignore the option?
	
For Client
	All messages(Advertise/Reply/Reconfigure).
		A Client must ignore all options that are not allowe to
appear in the message.

For Relay Agent
	All messages
		A Relay Agent just relay the message.
		
---------------------

What do you think?

Best regards,
...Hideshi Enokihara
	

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