Skip to main content

Reserving Additional IPv6 Address Prefixes for Use in Documentation
draft-horley-v6ops-expand-doc-02

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Ed Horley , Tom Coffeen , Scott Hogg , Nick Buraglio , Chris Cummings , Kevin Myers , Russ White
Last updated 2022-07-30 (Latest revision 2022-01-26)
Replaced by draft-ietf-v6ops-rfc3849-update
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-v6ops-rfc3849-update
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

To reduce the likelihood of conflict and confusion when relating documented examples to deployed systems, the IPv6 unicast address prefix 2001:db8::/32 is reserved for use in examples in documentation including RFCs, books, articles, vendor manuals, etc. This document proposes the reservation of additional IPv6 prefixes for this purpose; specifically, 3ffe::/16 (formerly 6bone) and fec0::/10 (formerly site-local).

Authors

Ed Horley
Tom Coffeen
Scott Hogg
Nick Buraglio
Chris Cummings
Kevin Myers
Russ White

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)