RFC 8273: Unique IPv6 Prefix per Host
In plain English — editorial summary, not part of the RFC
This document outlines an approach utilizing existing IPv6 protocols to allow hosts to be assigned a unique IPv6 prefix (instead of a unique IPv6 address from a shared IPv6 prefix). Benefits of using a unique IPv6 prefix over a unique service-provider IPv6 address include improved host isolation and enhanced subscriber management on shared network segments.
Document record
- Document ID
- RFC8273
- Published
- December 2017
- Authors
- J. Brzozowski; G. Van de Velde
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 10
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8250IPv6 Performance and Diagnostic Metrics (PDM) Destination OptionCurrent
September 2017
- RFC 8244Special-Use Domain Names Problem StatementCurrent
October 2017
- RFC 8305Happy Eyeballs Version 2: Better Connectivity Using ConcurrencyCurrent
December 2017
- RFC 8239Data Center Benchmarking MethodologyCurrent
August 2017
- RFC 8238Data Center Benchmarking TerminologyCurrent
August 2017
- RFC 8309Service Models ExplainedCurrent
January 2018
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
- RFC 8321Alternate-Marking Method for Passive and Hybrid Performance MonitoringObsoleted
January 2018
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?