RADIUS Attributes Permitted in RADIUS Attributes DHCP Suboption
draft-boucadair-dhcwg-rfc4014-update-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mohamed Boucadair | ||
| Last updated | 2022-10-17 | ||
| Replaced by | draft-ietf-opsawg-add-encrypted-dns | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources |
GitHub Repository
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-opsawg-add-encrypted-dns | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The RADIUS Attributes suboption, specified in RFC 4014, enables a DHCP relay agent to pass identification and authorization information received during RADIUS authentication to a DHCP server. However, RFC 4014 defines a frozen list of RADIUS attributes that can be included in such a suboption. This document updates RFC 4014 by relaxing that constraint and allowing to tag additional RADIUS Attributes as permitted in the RADIUS Attributes DHCP suboption.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)