IETF Logo Mail Archive

[dhcwg] "client identifier" in server replies

narasimha.nelakuditi@nokia.com Mon, 07 July 2003 05:08 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 BAA00890; Mon, 7 Jul 2003 01:08:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZOEL-0005n1-EX; Mon, 07 Jul 2003 01:08:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZODj-0005dR-7R for dhcwg@optimus.ietf.org; Mon, 07 Jul 2003 01:07:23 -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 BAA00850 for <dhcwg@ietf.org>; Mon, 7 Jul 2003 01:07:21 -0400 (EDT)
From: narasimha.nelakuditi@nokia.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZODg-0000Eb-00 for dhcwg@ietf.org; Mon, 07 Jul 2003 01:07:20 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 19ZODf-0000EX-00 for dhcwg@ietf.org; Mon, 07 Jul 2003 01:07:19 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37]) by mgw-x1.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h6757Ja11427 for <dhcwg@ietf.org>; Mon, 7 Jul 2003 08:07:20 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6348359a58ac158f25077@esvir05nok.ntc.nokia.com> for <dhcwg@ietf.org>; Mon, 7 Jul 2003 08:07:14 +0300
Received: from siebh002.NOE.Nokia.com ([172.30.195.17]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Mon, 7 Jul 2003 08:07:14 +0300
Received: from siebe002.NOE.Nokia.com ([172.30.195.13]) by siebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Mon, 7 Jul 2003 13:06:52 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C34445.92A76C06"
Date: Mon, 07 Jul 2003 13:06:50 +0800
Message-ID: <79A2DB53BC51BD448F0D19A86FB1DB637F1AA2@siebe002.apac.nokia.com>
Thread-Topic: "client identifier" in server replies
Thread-Index: AcNERX16Q5CVMv85Qle1Jx/oWz/UrQ==
To: dhcwg@ietf.org
X-OriginalArrivalTime: 07 Jul 2003 05:06:52.0022 (UTC) FILETIME=[93D61960:01C34445]
Subject: [dhcwg] "client identifier" in server replies
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>

Hi, If the client is setting "client identifier" but not "client hardware addr" in the messages that it is sending to server, server is supposed to identify it with "client identifier". But as per RFC2131, server MUST NOT fill "client identifier" option in OFFER and ACK messages. If this is the case, how is client supposed to validate the response (as 'xid' alone is not sufficient)???

regards,
swamy.

v2.23.0 | Report a Bug | By Email