RFC 7943: A Method for Generating Semantically Opaque Interface Identifiers (IIDs) with the Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
In plain English — editorial summary, not part of the RFC
This document describes a method for selecting IPv6 Interface Identifiers that can be employed by Dynamic Host Configuration Protocol for IPv6 (DHCPv6) servers when leasing non-temporary IPv6 addresses to DHCPv6 clients. This method is a DHCPv6 server-side algorithm that does not require any updates to the existing DHCPv6 specifications. The aforementioned method results in stable addresses within each subnet, even in the presence of multiple DHCPv6 servers or DHCPv6 server reinstallments. It is a DHCPv6 variant of the method specified in RFC 7217 for IPv6 Stateless Address Autoconfiguration.
Document record
- Document ID
- RFC7943
- Published
- September 2016
- Authors
- F. Gont; W. Liu
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9446Reflections on Ten Years Past the Snowden RevelationsCurrent
July 2023
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 8576Internet of Things (IoT) Security: State of the Art and ChallengesCurrent
April 2019
- RFC 7293The Require-Recipient-Valid-Since Header Field and SMTP Service ExtensionCurrent
July 2014
- RFC 9414Unfortunate History of Transient Numeric IdentifiersCurrent
July 2023
- RFC 9415On the Generation of Transient Numeric IdentifiersCurrent
July 2023
- RFC 9416Security Considerations for Transient Numeric Identifiers Employed in Network ProtocolsCurrent
July 2023
- RFC 9724State of Affairs for Randomized and Changing Media Access Control (MAC) AddressesCurrent
March 2025
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?