Re: [v6ops] IANA assigned prefix for IPv6 benchmarking

Tore Anderson <tore@fud.no> Mon, 27 July 2015 18:59 UTC

Return-Path: <tore@fud.no>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43C491B326E for <v6ops@ietfa.amsl.com>; Mon, 27 Jul 2015 11:59:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 ODwsf7Lxpyz3 for <v6ops@ietfa.amsl.com>; Mon, 27 Jul 2015 11:59:06 -0700 (PDT)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EC8F1B326C for <v6ops@ietf.org>; Mon, 27 Jul 2015 11:59:06 -0700 (PDT)
Received: from [2a02:c0:2:1:1194:17:0:1029] (port=55397 helo=envy.fud.no) by greed.fud.no with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from <tore@fud.no>) id 1ZJnc4-0006Y2-5t; Mon, 27 Jul 2015 20:59:00 +0200
Date: Mon, 27 Jul 2015 20:58:59 +0200
From: Tore Anderson <tore@fud.no>
To: Erik Kline <ek@google.com>
Message-ID: <20150727205859.689a0df5@envy.fud.no>
In-Reply-To: <CAAedzxqK=tmVk0kQxF+FtmXPR68=faG8qadGgk6YpN95GGafUA@mail.gmail.com>
References: <6b60e612c4f0.55b20091@naist.jp> <6c008406e2af.55b200cf@naist.jp> <6c00eec89ab8.55b2010d@naist.jp> <6bf095d99dae.55b2014a@naist.jp> <6b50ff96a9ad.55b20188@naist.jp> <6c50a92cde54.55b201c6@naist.jp> <6c50be138e83.55b20205@naist.jp> <6bf08db1e13f.55b20243@naist.jp> <6bf0f7dbdadf.55b20280@naist.jp> <6bf0898ffbd5.55b21ea8@naist.jp> <55B29026.1070906@gmail.com> <6b70d3cfd2f6.55b365ea@naist.jp> <6b70bfbf8107.55b36628@naist.jp> <6c30a2fefa4c.55b36666@naist.jp> <6c50d867e570.55b366a4@naist.jp> <6bf0c04ef47e.55b382fb@naist.jp> <55B48402.1040202@gmail.com> <CAAedzxqK=tmVk0kQxF+FtmXPR68=faG8qadGgk6YpN95GGafUA@mail.gmail.com>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.28; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/ExsDpqxSUq24_z0A20JuJMHC9lk>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] IANA assigned prefix for IPv6 benchmarking
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2015 18:59:08 -0000

* Erik Kline

> Regardless of ULA or some other space, I think a useful property for
> the GUA(-like) prefix used by Apple's NAT64 test network would be
> randomness.
> 
> If, for instance, *every time a NAT64 test network was started* a new
> random ULA was generated or, say, 2001:2:0:$RAND16::/64 were used,
> then developers would be less likely to accidentally make assumptions
> about the consistency of addresses.

Same thing goes for NAT64/DNS64 translation prefix. This could be
tempting for developers to hard-code as well - my gut feeling tells me
that most NAT64 deployments in 3GPP networks out are using the WKP from
RFC6052 (64:ff9b::/96) for their translation prefix.

As I also mentioned in the WG session I think that Apple should simply
obtain a GUA prefix through the registry system for this purpose (never
to be advertised into the DFZ). That way they wouldn't have to squat on
prefixes reserved for other purposes (like 2001:2::/48), and they would
be able to document what the prefix is actually used for and link to
further information in the prefix' whois entry, so people who
accidentally find themselves connected to such a network has a chance
to figure out what's going on.

The cost would be negligible - a /48 PI costs only €50/year here.

Tore