RFC 6939: Client Link-Layer Address Option in DHCPv6
In plain English — editorial summary, not part of the RFC
This document specifies the format and mechanism that is to be used for encoding the client link-layer address in DHCPv6 Relay-Forward messages by defining a new DHCPv6 Client Link-Layer Address option.
Document record
- Document ID
- RFC6939
- Published
- May 2013
- Authors
- G. Halwasia; S. Bhandari; W. Dec
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6936Applicability Statement for the Use of IPv6 UDP Datagrams with Zero ChecksumsCurrent
April 2013
- RFC 6935IPv6 and UDP Checksums for Tunneled PacketsCurrent
April 2013
- RFC 6944Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm Implementation StatusObsoleted
April 2013
- RFC 6934Applicability of the Access Node Control Mechanism to Broadband Networks Based on Passive Optical Networks (PONs)Current
June 2013
- RFC 6946Processing of IPv6 "Atomic" FragmentsCurrent
May 2013
- RFC 6930RADIUS Attribute for IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)Current
April 2013
- RFC 6926DHCPv4 Bulk LeasequeryUpdated
April 2013
- RFC 6925The DHCPv4 Relay Agent Identifier Sub-OptionCurrent
April 2013
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?