RFC 9844: Entering IPv6 Zone Identifiers in User Interfaces
In plain English — editorial summary, not part of the RFC
This document describes how the zone identifier of an IPv6 scoped address, defined in the IPv6 Scoped Address Architecture specification (RFC 4007), should be entered into a user interface. This document obsoletes RFC 6874 and updates RFCs 4007, 7622, and 8089.
Document record
- Document ID
- RFC9844
- Published
- August 2025
- Authors
- B. Carpenter; R. Hinden
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 8
- Also known as
- —
- Obsoletes:
- RFC 6874
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9837The IPv6 VPN Service Destination OptionCurrent
August 2025
- RFC 9812Clarification of IPv6 Address Allocation PolicyCurrent
October 2025
- RFC 9805Deprecation of the IPv6 Router Alert Option for New ProtocolsCurrent
June 2025
- RFC 9886DRIP Entity Tags (DETs) in the Domain Name SystemCurrent
December 2025
- RFC 9797Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use CasesCurrent
June 2025
- RFC 9915Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
January 2026
- RFC 9769NTP Interleaved ModesCurrent
May 2025
- RFC 9762Using Router Advertisements to Signal the Availability of DHCPv6 Prefix Delegation to ClientsCurrent
June 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?