Re: Additional Documentation Prefixes (was Re: AD Evaluation : draft-ietf-6man-ra-pref64-06)

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 03 November 2019 22:47 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 9BD901200F7 for <ipv6@ietfa.amsl.com>; Sun, 3 Nov 2019 14:47:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 CQyadZ9B3f0n for <ipv6@ietfa.amsl.com>; Sun, 3 Nov 2019 14:47:11 -0800 (PST)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CC03120090 for <ipv6@ietf.org>; Sun, 3 Nov 2019 14:47:11 -0800 (PST)
Received: by mail-pf1-x436.google.com with SMTP id 3so10854411pfb.10 for <ipv6@ietf.org>; Sun, 03 Nov 2019 14:47:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=0APwQfLaMsompbtBes7C6JxjNu6phV9kobqmPf5birE=; b=gdA5rj1zWrMpbnXGi+UrZyF4GLP96FD8qYPUGt/tHnIKB8Ca/AHQ2KKFYAyw4JEcEa qyiR9uhpioKmgjHkzzyhmh/4t2zWUxDSzkkrqfl/ZcMj8c3q7L3RGjO3YSLbmlJVYrjX tOcJNbbJOylCu0fi6BYMDsyAFUYPpXvwy7V4aaUTITI2I/X8J1wiWcu8t5VDvk2RkKrY N+fSjPiz7PdKWGY3H2LyU93o9gA8rgNFDXgvAzQkebssoVY5/buQ6q4S+5qfDESdN4UI Yn3c/a0mSzTBIYgIEaGe1xor8+jW8ZDNYolZkTRkkRAIjZpDnEpZrnEy5Ie5A650EmKe i8kA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=0APwQfLaMsompbtBes7C6JxjNu6phV9kobqmPf5birE=; b=uPHWeA500SahTegtVOvMyGK5yVjjX5x2IwxW1eoHEgaAUQrvSdHqCQRnSXDgm5Y0xl wYPTWm7AA4Cv3BrihJ6hBt7Cu41UK+BnEZgn2Lzw2HXHze/bbLEDzfqyugAxZObcPCXN yDCgOmhwgpL48lH+FF5JPYMoseJB1MGhp1Sd5rF6kU5WQnDtT13j4Z/Csfmdc2Pn3Q6M OjYrlHesGbHisQiPM8vLzuN5hV4MIL7KC29t4Xn86Jcak83ehhR3VgrcM8CzPdCNop0/ QRlpGs+5iKKTsH8tUhwJ5vnjUm/PNcyY3m8xbJO31+0vwKeT9f9Fp6gfyS06ClBg5nHf 2n1Q==
X-Gm-Message-State: APjAAAVXKuAjCs1wpdP6mopwIiqpDGJsgN1SQv5eQZTUCXFxvS2igoVR m07kvpWVhZ3Ix8hMzgXnL4u+AMwU
X-Google-Smtp-Source: APXvYqx9D09r34RUmli9PxZdjiFhOz2x2vy4/+IQdOR9KMu0XhN8KvM2XflaV04vo0OowWA6WdHXcg==
X-Received: by 2002:a63:e145:: with SMTP id h5mr26977215pgk.447.1572821230612; Sun, 03 Nov 2019 14:47:10 -0800 (PST)
Received: from [192.168.178.30] (46.137.69.111.dynamic.snap.net.nz. [111.69.137.46]) by smtp.gmail.com with ESMTPSA id 70sm14775815pfw.160.2019.11.03.14.47.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 03 Nov 2019 14:47:10 -0800 (PST)
Subject: Re: Additional Documentation Prefixes (was Re: AD Evaluation : draft-ietf-6man-ra-pref64-06)
To: Mark Smith <markzzzsmith@gmail.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Suresh Krishnan <suresh@kaloom.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
References: <F1B31C38-7CDB-4057-A573-D6AF76B264D3@kaloom.com> <CAKD1Yr1vOqTvEsv0oCm+bu7CkFwiyFv8_G1XM+4JAKYLoA21aA@mail.gmail.com> <27802.1572732078@localhost> <F95A29A5-CEAF-4A23-A678-C5465B248E42@kaloom.com> <24180.1572801507@localhost> <7fd283ed-2328-6a9e-eb86-c5c155ebfd84@gmail.com> <CAO42Z2wd+uycvhe8+NNkOG_HFvaRMUonzb2_Q0xxNE2OfigSGg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <4058c92e-ae64-b2ce-85d4-652a5ee4f63d@gmail.com>
Date: Mon, 4 Nov 2019 11:47:05 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CAO42Z2wd+uycvhe8+NNkOG_HFvaRMUonzb2_Q0xxNE2OfigSGg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/uVxxrebR46O6WUxHusOKY-H4csQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 03 Nov 2019 22:47:14 -0000

On 04-Nov-19 11:34, Mark Smith wrote:
> 
> 
> On Mon, 4 Nov 2019, 06:33 Brian E Carpenter, <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> 
>     On 04-Nov-19 06:18, Michael Richardson wrote:
>     >
>     > Suresh Krishnan <Suresh@kaloom.com <mailto:Suresh@kaloom.com>> wrote:
>     ...
>     >     >> I'd also like to have three or four additional IPv6 documentation prefixes,
>     >     >> plus some documentation space from ULA-R and ULA-C.
>     >
>     >     > What is ULA-R? Did you mean ULA-L? If so, it would be a pain to reserve
>     >     > something now since we also need to update RFC4193 to make sure that
>     >     > the Random “Global ID”s will not collide with the reserved prefixes. If
>     >     > ULA-C does take off, this would be a good idea to do something like
>     >     > this.
>     >
>     > I guess L=1 is why you call it ULA-L. I have known it as ULA-Random.
>     > We are both talking about RFC4193 though.  So such a document would need to
>     > update RFC4193.
> 
>     I think this is a bad and pointless idea. Pointless because it is 100% OK
>     to use any RFC4193 prefix as an example, since by definition it will never
>     be used on the Internet, and the chance of collision on a given ULA site
>     is 1 in 2**40 (and who cares anyway?). Bad because it means that millions
>     of existing boxes that can generate ULA prefixes would be non-conformant
>     and, seriously, is any vendor going to update date their firmware for this?
> 
> 
> I redacted my ULA in examples in a presentation I did recently. That made it impossible to type in and for somebody to duplicate.
> 
> If the goal is ensure people can't try to use these example addresses on real networks, then perhaps using invalid addresses in the document with a note that they're examples and invalid on purpose is a better idea.
> 
> For example, using non-hexidecimal letters, with a note about them being substitutes for 'a' through 'f'.
> 
> E.g.
> 
> 2001:db8:xxxx:yyyy::zzz1
> 

Yes, that makes sense, and could be applied to link-local and RFC1918
addresses too. It's a much less fiddly solution.

    Brian