Skip to main content

Expanding the IPv6 Documentation Space
draft-ietf-v6ops-rfc3849-update-05

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-v6ops-rfc3849-update@ietf.org, ed@hexabuild.io, rfc-editor@rfc-editor.org, v6ops-chairs@ietf.org, v6ops@ietf.org, warren@kumari.net
Subject: Document Action: 'Expanding the IPv6 Documentation Space' to Informational RFC (draft-ietf-v6ops-rfc3849-update-05.txt)

The IESG has approved the following document:
- 'Expanding the IPv6 Documentation Space'
  (draft-ietf-v6ops-rfc3849-update-05.txt) as Informational RFC

This document is the product of the IPv6 Operations Working Group.

The IESG contact persons are Warren Kumari and Mahesh Jethanandani.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-v6ops-rfc3849-update/


Ballot Text

Technical Summary

   The document describes the reservation of an additional IPv6 address
   prefix for use in documentation.  This update to RFC 3849 expands on
   the existing 2001:db8::/32 address block with the reservation of an
   additional, larger prefix.  The addition of a /20 allows documented
   examples to more closely reflect a broader range of realistic,
   current deployment scenarios and more closely aligns with
   contemporary allocation models for large networks.

Working Group Summary

   This document had an robust and rapid email discussion.  In the end there was 
general consensus that additional documentation space was needed however the 
size and/or quantity of prefixes and if they should be from the global unicast 
address space or made up fake space lacked consensus. A few individuals 
proposed using made up or fake address space that does not conform to the 
RFC standards for IPv6 addresses.  The working group chairs called for 
consensus on the document, which caused some additional emails about the 
nature and size and number of prefixes.

It appeared that using a new allocation, not from the current 2000::/3, that
is a single /20, with a unique enough left nibble numbering to be distinct
from the current documentation prefix would work for the majority who responded.

 

Document Quality

   The document is clear, well written and concise. The document is primarily an "Administrative" document (it requests IANA assign more IPv6 documentation space) and so there are no implementations.

Personnel

   Ed Horley is DS. 
   Warren "Ace" Kumari is RAD!!!!!!!

RFC Editor Note