metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 6148: DHCPv4 Lease Query by Relay Agent Remote ID

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC6148
Published
February 2011
Authors
P. Kurapati; R. Desetti; B. Joshi
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
13
Also known as
—
Updates:
RFC 4388

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/6148-dhcpv4-lease-query-by-relay-agent-remote-id