Subject: RE: [dhcwg] Status codes for Information-Request

From: "Bernie Volz (EUD)" <[email-masked]>
Date: Wed, 23 Jan 2002 11:45:24 -0600

I hate to complicate matters by adding more error codes, but what about adding something like "DUIDneeded"? (This is based on the change from MUST to SHOULD for the client sending a DUID in an Information-Request).

Note however that if a client is capable / willing to provide a DUID, why didn't it provide it in the original request? Therefore, returning this error may not be meaningful to clients that don't want to generate DUID since they won't re-issue the request with a DUID. Though it might add in diagnosing problems when clients can't get configuration information.

- Bernie

-----Original Message-----
From: Ralph Droms [mailto:[email-masked]]
Sent: Wednesday, January 23, 2002 11:33 AM
To: [email-masked]
Subject: [dhcwg] Status codes for Information-Request

Open issue from WG last call:

* What status codes may a server send in response to an
   Information-Request message?

I propose: Success, UnspecFail, AuthFailed, PoorlyFormed, OptionUnavail

- Ralph

_______________________________________________
dhcwg mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/dhcwg