Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Inconstancy in RFC 2131 & 2132 #27

Open
d2g opened this issue Dec 14, 2018 · 0 comments
Open

Inconstancy in RFC 2131 & 2132 #27

d2g opened this issue Dec 14, 2018 · 0 comments
Labels
question

Comments

@d2g
Copy link
Owner

d2g commented Dec 14, 2018

The client (v2) currently assumes that the Server Identified (Option 54) is included in the response ACK and NACK packets as per RFC 2131 p28.

This however contradicts RFC 2132 p27.

This issue is to identify if this inconstancy requires addressing within the client. Therefore, if you are aware of an server implementation that doesn't return the server identifier (Option 54) in ACK and/or NACK dhcp4 responses, please provide details.
@d2g d2g added the question label Dec 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@d2g