RE: [dhcwg] Status codes for Information-Request
"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Wed, 23 January 2002 17:58 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 MAA18521 for <dhcwg-archive@odin.ietf.org>; Wed, 23 Jan 2002 12:58:11 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id MAA08176 for dhcwg-archive@odin.ietf.org; Wed, 23 Jan 2002 12:58:12 -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 MAA07663; Wed, 23 Jan 2002 12:46: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 MAA07644 for <dhcwg@optimus.ietf.org>; Wed, 23 Jan 2002 12:46:10 -0500 (EST)
Received: from imr1.ericy.com (imr1.ericy.com [208.237.135.240]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17987 for <dhcwg@ietf.org>; Wed, 23 Jan 2002 12:46:08 -0500 (EST)
Received: from mr7.exu.ericsson.se (mr7u3.ericy.com [208.237.135.122]) by imr1.ericy.com (8.11.3/8.11.3) with ESMTP id g0NHk8h19388 for <dhcwg@ietf.org>; Wed, 23 Jan 2002 11:46:08 -0600 (CST)
Received: from eamrcnt749 (eamrcnt749.exu.ericsson.se [138.85.133.47]) by mr7.exu.ericsson.se (8.11.3/8.11.3) with SMTP id g0NHk8925248 for <dhcwg@ietf.org>; Wed, 23 Jan 2002 11:46:08 -0600 (CST)
Received: FROM eamrcnt761.exu.ericsson.se BY eamrcnt749 ; Wed Jan 23 11:45:26 2002 -0600
Received: by eamrcnt761.exu.ericsson.se with Internet Mail Service (5.5.2653.19) id <ZP0Q5CZL>; Wed, 23 Jan 2002 11:45:26 -0600
Message-ID: <66F66129A77AD411B76200508B65AC69B4CDF8@EAMBUNT705>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: 'Ralph Droms' <rdroms@cisco.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] Status codes for Information-Request
Date: Wed, 23 Jan 2002 11:45:24 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1A435.BC846620"
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
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:rdroms@cisco.com] Sent: Wednesday, January 23, 2002 11:33 AM To: dhcwg@ietf.org 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 dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Status codes for Information-Request Ralph Droms
- RE: [dhcwg] Status codes for Information-Request Bernie Volz (EUD)
- RE: [dhcwg] Status codes for Information-Request Richard Barr Hibbs
- RE: [dhcwg] Status codes for Information-Request Ralph Droms