RFC 6644: Rebind Capability in DHCPv6 Reconfigure Messages
In plain English — editorial summary, not part of the RFC
This document updates RFC 3315 (DHCPv6) to allow the Rebind message type to appear in the Reconfigure Message option of a Reconfigure message. It extends the Reconfigure message to allow a DHCPv6 server to cause a DHCPv6 client to send a Rebind message. The document also clarifies how a DHCPv6 client responds to a received Reconfigure message. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6644
- Published
- July 2012
- Authors
- D. Evans; R. Droms; S. Jiang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
- Updates:
- RFC 3315
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2529Transmission of IPv6 over IPv4 Domains without Explicit TunnelsCurrent
March 1999
- RFC 2470Transmission of IPv6 Packets over Token Ring NetworksUpdated
December 1998
- RFC 2467Transmission of IPv6 Packets over FDDI NetworksUpdated
December 1998
- RFC 2464Transmission of IPv6 Packets over Ethernet NetworksUpdated
December 1998
- RFC 3831Transmission of IPv6 Packets over Fibre ChannelObsoleted
July 2004
- RFC 2663IP Network Address Translator (NAT) Terminology and ConsiderationsCurrent
August 1999
- RFC 6434IPv6 Node RequirementsObsoleted
December 2011
- RFC 6275Mobility Support in IPv6Current
July 2011
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?