Re: [dhcwg] Error codes for Decline message

Jim Bound <seamus@bit-net.com> Mon, 21 January 2002 01:37 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 UAA18411 for <dhcwg-archive@odin.ietf.org>; Sun, 20 Jan 2002 20:37:20 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id UAA04337 for dhcwg-archive@odin.ietf.org; Sun, 20 Jan 2002 20:37:24 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA04228; Sun, 20 Jan 2002 20:31:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA04189 for <dhcwg@optimus.ietf.org>; Sun, 20 Jan 2002 20:31:08 -0500 (EST)
Received: from mail.users.bit-net.com (www.bit-net.com [208.146.132.4]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA18341 for <dhcwg@ietf.org>; Sun, 20 Jan 2002 20:31:04 -0500 (EST)
Received: from localhost by mail.users.bit-net.com; (5.65v3.2/1.1.8.2/30Jul96-0143PM) id AA10488; Sun, 20 Jan 2002 20:29:50 -0500
Date: Sun, 20 Jan 2002 20:29:50 -0500 (EST)
From: Jim Bound <seamus@bit-net.com>
To: Vijayabhaskar A K <vijayak@india.hp.com>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Error codes for Decline message
In-Reply-To: <001701c1a1e6$a5aca670$2f290a0f@india.hp.com>
Message-Id: <Pine.OSF.3.95.1020120202412.12067C-100000@www.bit-net.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

Hi Vijay,

Your ahead of us with hands on code for dhc6.  And thanks for putting it
in the public domain that was very nice.  We are trying to get to PS.  I
suggest that we will find more needed error codes once we begin more
implementations and more error codes.  Right now I believe we have the
generic onces to to resolve a response for all errors trying to
extrapolate the possibilities from the spec without writing the code
myself.  So I think adding a new code before PS as you have found as
bonifided implementor is good.  But  I caution the WG positively to not
head down all these paths we will find many new pieces we need from more
implementation and getting to PS is important so other folks are not
implementing specs 3 revs behind as it has engineering cost and thats part
of our job in the IETF is to keep that to a minimum in our work for the
folks that write code.


/jim


On Mon, 21 Jan 2002, Vijayabhaskar A K wrote:

> We need error codes to be defined for Decline message.
> AddrInUse - Address already in use.
> Is there any other scenario for which the client can
> send decline message?
> Will the following scenarios contribute to decline message?
> - The lease time the client has got is not sufficient for it.
> - The client has asked for a prefix A. But the server's
> admin policy says that for that client assign address 
> with prefix B and it does so.
> I think, a mere release is not enough for these above 
> situations. This has to be notified to the admin to take
> corrective action. 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
> 


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