Authentication draft comment (hops must be zeroed, too!)
Shawn Mamros <mamros@ftp.com> Tue, 20 February 1996 16:07 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa21951;
20 Feb 96 11:07 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa21947;
20 Feb 96 11:07 EST
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa06084;
20 Feb 96 11:07 EST
Received: from localhost by reef.bucknell.edu with SMTP
(5.65/IDA-1.2.8) id AA21366; Tue, 20 Feb 1996 10:50:05 -0500
Date: Tue, 20 Feb 1996 10:50:05 -0500
Message-Id: <9602201458.AA14323@mailserv-C.ftp.com>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
X-Orig-Sender: dhcp-v4@bucknell.edu
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Shawn Mamros <mamros@ftp.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Authentication draft comment (hops must be zeroed, too!)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
(I've tried sending this twice before, and it's been bounced both times; hopefully third time is the charm...) The draft on authentication for DHCP messages mentions how the giaddr field must be set to all zeroes when the message digest is computed. It turns out that there is one other field which will have to be treated similarly: the little-known and little-used "hops" field. RFC 1542 states that relay agents MUST increment this field (see section 4.1.1), so it will have to be zeroed for message digest computation as well. Fortunately, RFC 1542 also states that all other fields MUST be preserved intact... -Shawn Mamros E-mail to: mamros@ftp.com
- Authentication draft comment (hops must be zeroed… Shawn Mamros