DHCPv4 Lease Query by Relay Agent Remote ID
RFC 6148, “DHCPv4 Lease Query by Relay Agent Remote ID”, is a Proposed Standard document published in February 2011 by P. Kurapati, R. Desetti, B. Joshi. It updates RFC 4388. The canonical text is published by the RFC Editor.
Abstract
Some relay agents extract lease information from the DHCP messages exchanged between the client and DHCP server. This lease information is used by relay agents for various purposes like antispoofing and prevention of flooding. RFC 4388 defines a mechanism for relay agents to retrieve the lease information from the DHCP server when this information is lost. The existing lease query mechanism is data-driven, which means that a relay agent can initiate the lease query only when it starts receiving data to and from the clients. In certain scenarios, this model is not scalable. This document first looks at issues in the existing mechanism and then proposes a new query type, query by Remote ID, to address these issues. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6148 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6147 DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers
- RFC 6149 MD2 to Historic Status
- RFC 6146 Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
- RFC 6150 MD4 to Historic Status
- RFC 6145 IP/ICMP Translation Algorithm
- RFC 6151 Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms
- RFC 6144 Framework for IPv4/IPv6 Translation
- RFC 6152 SMTP Service Extension for 8-bit MIME Transport