Report information
The Basics
Id:
38110
Status:
open
Priority:
Low/Low
Queue:

People
Owner:
Nobody in particular
Cc:
AdminCc:

BugTracker
Version Fixed:
(no value)
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
(no value)
Priority:
(no value)
Severity:
S2 Normal
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
feature

Attachments
0001-DHCP-Option-97-Client-Machine-Identifier-pxe-client-.patch

Dates
Created:Tue, 16 Dec 2014 12:19:07 -0500
Updated:Wed, 28 Jun 2017 15:29:23 -0400
Closed:Not set



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

Subject: Option 97 - Client Machine Identifier - pxe-client-id
Date: Tue, 16 Dec 2014 18:19:00 +0100
To: dhcp-suggest@isc.org
From: Jiri Popelka <jpopelka@redhat.com>
Hello, I've got couple customer requests for implementing option 97 - PXE client-id as defined in RFC 4578. I have no idea why is this option better than original option 61 (RFC 4361). Anyway, there a patch attached, so I can tick 'sent upstream' :-) Thanks, Jiri Popelka Red Hat, inc.

Message body is not shown because sender requested not to inline it.