RFC 5460: DHCPv6 Bulk Leasequery
In plain English — editorial summary, not part of the RFC
The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) has been extended with a Leasequery capability that allows a client to request information about DHCPv6 bindings. That mechanism is limited to queries for individual bindings. In some situations individual binding queries may not be efficient, or even possible. This document expands on the Leasequery protocol, adding new query types and allowing for bulk transfer of DHCPv6 binding data via TCP. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5460
- Published
- February 2009
- Authors
- M. Stapp
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 18
- Also known as
- —
- Updated by:
- RFC 7653
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5454Dual-Stack Mobile IPv4Current
March 2009
- RFC 5549Advertising IPv4 Network Layer Reachability Information with an IPv6 Next HopObsoleted
May 2009
- RFC 5619Softwire Security Analysis and RequirementsCurrent
August 2009
- RFC 5172Negotiation for IPv6 Datagram Compression Using IPv6 Control ProtocolCurrent
March 2008
- RFC 5072IP Version 6 over PPPUpdated
September 2007
- RFC 5007DHCPv6 LeasequeryCurrent
September 2007
- RFC 4980Analysis of Multihoming in Network Mobility SupportCurrent
October 2007
- RFC 5952A Recommendation for IPv6 Address Text RepresentationCurrent
August 2010
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?