[dhcwg] clarification needed about dhcp client-server interaction
Muneer <muneerch@gmail.com> Thu, 07 July 2005 13:10 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqW8w-0006GK-2l; Thu, 07 Jul 2005 09:10:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqW8t-0006BE-9z for dhcwg@megatron.ietf.org; Thu, 07 Jul 2005 09:10:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04451 for <dhcwg@ietf.org>; Thu, 7 Jul 2005 09:10:13 -0400 (EDT)
Received: from wproxy.gmail.com ([64.233.184.204]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DqWa4-0006dK-1Y for dhcwg@ietf.org; Thu, 07 Jul 2005 09:38:21 -0400
Received: by wproxy.gmail.com with SMTP id i22so191092wra for <dhcwg@ietf.org>; Thu, 07 Jul 2005 06:10:02 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=nAeyGMpa1jsM840GLKvDy5VVq5afLxvPnBQ2v2fWnFrlWh+fzcy+lZako2qUuUHBjmfKqVUJDbPI+fojNoXNPnMINE0BQlQWOyHkXJwsiECm12Loq2YTszl5BKYydlDCX/H8JOt0UlcGu8oEMx9JmyS/JMhlv3cUOW6SVp0gI8s=
Received: by 10.54.30.4 with SMTP id d4mr748633wrd; Thu, 07 Jul 2005 06:10:02 -0700 (PDT)
Received: by 10.54.23.9 with HTTP; Thu, 7 Jul 2005 06:10:02 -0700 (PDT)
Message-ID: <72a9b062050707061052321424@mail.gmail.com>
Date: Thu, 07 Jul 2005 18:40:02 +0530
From: Muneer <muneerch@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: quoted-printable
Subject: [dhcwg] clarification needed about dhcp client-server interaction
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Muneer <muneerch@gmail.com>
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Hi
I have gone through the rfc2131. I have following doubt. Can you clarify it?
rfc 2131 section
3.1 - 4 says: "The combination of 'client identifier' or
'chaddr' and assigned network address constitute a unique
identifier for the client's lease and are used by both the client
and server to identify a lease referred to in any DHCP messages"
and in section 4.4.1: The table given says that any dhcp decline
messages should fill ciaddr field with 0.
I feel server will fail to identify the binding corresponding to the
decline message received, and to add that particular offered IP
address as "cannot assign" list. Since the server will record the
lease after ACK message is sent, and will receive the Decline message
later which contains no information about the ip address offered, How
the server will identify the wrongly assigned IP ?
--
Imagination is more important than knowledge...
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] clarification needed about dhcp client-se… Muneer
- Re: [dhcwg] clarification needed about dhcp clien… David W. Hankins