on the need for documentation addresses of all types

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 27 February 2017 14:23 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 591A81298BD for <ipv6@ietfa.amsl.com>; Mon, 27 Feb 2017 06:23:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1jREGFa0HjTb for <ipv6@ietfa.amsl.com>; Mon, 27 Feb 2017 06:23:56 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9838129954 for <6man@ietf.org>; Mon, 27 Feb 2017 06:23:56 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7DA61E206 for <6man@ietf.org>; Mon, 27 Feb 2017 09:46:05 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9A0B96381A for <6man@ietf.org>; Mon, 27 Feb 2017 09:23:54 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: 6man@ietf.org
Subject: on the need for documentation addresses of all types
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 27 Feb 2017 09:23:54 -0500
Message-ID: <10130.1488205434@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/VjOrEg29YksEecW_Xl2s22HEujM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 14:23:58 -0000

rfc3849 gives us 2001:DB8::/32 for use in documentation.

I find that I am often giving example addresses in fe80:: (Link Local), and
fd00::/8 (ULA) addresses when those prefixes are appropriate for the
protocol.   I worry that someone will think the numbers I've chosen are
special in some way.  There are clearly far less concern about duplication
since both spaces are designed to be duplicated (LL) and
not-guaranteed-to-be-unique (ULA).

I'd still be happier if someone google'ed the prefixes in the document, and
found that they were documentation examples.

I'd also like to have three additional documentation prefixes from GUA
space so that examples involving inner and outer addresses, and senders and
receivers could be better distinguished.  Yes, we currently can carve
/48 blocks out of 2001:DB8::/32 for this purpose, but it would be nice if
the pattern was even more unique.

Would it also be useful to have documentation addresses for the multicast
ranges, and the like?

--
Michael Richardson <mcr+IETF@sandelman.ca>;, Sandelman Software Works
 -= IPv6 IoT consulting =-