IETF Logo Mail Archive

[dhcwg] Client behavior with Parameter Request List

"Kevin A. Noll" <kevin.noll@perfectorder.com> Wed, 19 May 2004 03:17 UTC

Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08687; Tue, 18 May 2004 23:17:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQHTy-0003MZ-2X; Tue, 18 May 2004 23:11:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQHSA-00036s-El for dhcwg@optimus.ietf.org; Tue, 18 May 2004 23:09:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08163 for <dhcwg@ietf.org>; Tue, 18 May 2004 23:09:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQHS6-0001uG-HF for dhcwg@ietf.org; Tue, 18 May 2004 23:09:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQHQY-0001nL-00 for dhcwg@ietf.org; Tue, 18 May 2004 23:07:33 -0400
Received: from endeavor.poss.com ([198.70.184.137] helo=smtp.poss.com) by ietf-mx with esmtp (Exim 4.12) id 1BQHPP-0001dO-00 for dhcwg@ietf.org; Tue, 18 May 2004 23:06:19 -0400
Received: from conversion-daemon.endeavor.poss.com by endeavor.poss.com (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) id <0HXX00001XSQUL@endeavor.poss.com> for dhcwg@ietf.org; Tue, 18 May 2004 23:05:50 -0400 (EDT)
Received: from kan1 (user188.net390.oh.sprint-hsd.net [65.40.75.188]) by endeavor.poss.com (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTPA id <0HXX0005GXXKFZ@endeavor.poss.com> for dhcwg@ietf.org; Tue, 18 May 2004 23:05:49 -0400 (EDT)
Date: Tue, 18 May 2004 23:05:48 -0400
From: "Kevin A. Noll" <kevin.noll@perfectorder.com>
In-reply-to: <4.3.2.7.2.20040503151126.02b61840@flask.cisco.com>
To: dhcwg@ietf.org
Message-id: <PPEKLDPHBHOIHMHKFGLLMEOLDAAA.kevin.noll@perfectorder.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Client behavior with Parameter Request List
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Section 4.4.1 of RFC 2131 says "If the client included a list of
requested parameters in a DHCPDISCOVER message, it MUST include
that list in all subsequent messages".

I can't find any statement as to what should happen if the client
*does not* include the list. Clearly it would be a protocol violation
and therefore a broken client if it didn't, but what should the 
server do about it? I assume it should drop the message.

Taking this to a different level of discussion - I question the
purpose of making this requirement. I can understand why you 
would want to require options like "Client Identifier" to always
be sent, I'm not sure why the parameter request list must always
be included.

--kan--


--
Kevin A. Noll, KD4WOZ
CCIE 10948, CCDP
Perfect Order, Inc.		
Kevin.Noll@perfectorder.com
717-796-1936


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

v2.23.0 | Report a Bug | By Email