ObsoletedPROPOSED STANDARDIETF stream

RFC 6874: Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9844.

Current version: RFC 9844Entering 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 as <zone_id> in the IPv6 Scoped Address Architecture (RFC 4007), can be represented in a literal IPv6 address and in a Uniform Resource Identifier that includes such a literal address. It updates the URI Generic Syntax specification (RFC 3986) accordingly.

Document record

Document ID
RFC6874
Published
February 2013
Authors
B. Carpenter; S. Cheshire; R. Hinden
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
10
Also known as
Obsoleted by:
RFC 9844

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/6874-representing-ipv6-zone-identifiers-in-address-literals-and-uniform-resource-iden