RFC 4704: The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option
In plain English — editorial summary, not part of the RFC
This document specifies a new Dynamic Host Configuration Protocol for IPv6 (DHCPv6) option that can be used to exchange information about a DHCPv6 client's Fully Qualified Domain Name (FQDN) and about responsibility for updating DNS resource records (RRs) related to the client's address assignments. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4704
- Published
- October 2006
- Authors
- B. Volz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4702The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) OptionCurrent
October 2006
- RFC 4703Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) ClientsCurrent
October 2006
- RFC 4701A DNS Resource Record (RR) for Encoding Dynamic Host Configuration Protocol (DHCP) Information (DHCID RR)Updated
October 2006
- RFC 4721Mobile IPv4 Challenge/Response Extensions (Revised)Current
January 2007
- RFC 4755IP over InfiniBand: Connected ModeCurrent
December 2006
- RFC 4649Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID OptionCurrent
August 2006
- RFC 4640Problem Statement for bootstrapping Mobile IPv6 (MIPv6)Current
September 2006
- RFC 4638Accommodating a Maximum Transit Unit/Maximum Receive Unit (MTU/MRU) Greater Than 1492 in the Point-to-Point Protocol over Ethernet (PPPoE)Current
September 2006
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?